Skip to content
Sample program data

Operations Dashboard

See the operating chain through demand, stage timing, queue signals, delivery control and provider workflow evidence.

The program data is synthetic and illustrative, not a client or market benchmark.

AudienceOperationsPeriodQ1 2026Evidence throughApr 11, 2026Full dataset225 deliveriesDatasetJPK Program Evidence v3.1

Explore the evidence

Rates and turnaround measures are withheld below five applicable records. Queue and touch measures describe recorded operating time and do not indicate staffing, headcount or utilization.

Programs
All programsOpen Program filter
Projects
All projectsOpen Project filter
Workflows
All workflowsOpen Workflow filter
Priorities
All prioritiesOpen Prioritie filter
LSPs
All LSPsOpen LSP filter
Translators
All translatorsOpen Translator filter
Reviewers
All reviewersOpen Reviewer filter
LQAers
All LQAersOpen LQAer filter

Selected population:225 deliveries386,726 source words8 languagesJan 1, 2026 to Mar 31, 2026
Full Q1 evidence is shown below. Interactive filtering and tab switching become available when the dashboard script loads successfully.

Operations overview

Follow delivery, downstream stage control, completion and extension pressure across the selected request cohort.

Deliveries
225
386,726 source words
Gross delivery OTD
93.3%
210 of 225 deliveries
Review OTD
77.8%
133 of 171 review records
LQA OTD
88.6%
78 of 88 LQA records
Internal completion OTD
91.6%
206 of 225 deliveries
Median completion TAT
42.3h
225 delivery records | P90 102.4h

What the selected evidence shows

  • Gross delivery is 93.3% on time across 225 deliveries. Review is 77.8% across 171 records, LQA is 88.6% across 88, and internal completion is 91.6% across 225 deliveries.
  • 5 deliveries are late on the original deadline and on time on the gross-delivery clock. The source does not expose a distinct approved-deadline signal, so these are not labeled approved-deadline recoveries.
  • 35 of 225 deliveries requested an extension and 23 had an approved extension. Arbitration OTD is 58.3%.

Stage punctuality ladder

Each stage uses only records where that stage occurred. Gross delivery and internal completion uses the selected delivery population.

Stage punctuality ladder
Stage / clockResultPopulation
Original deadline91.1%205 of 225 deliveries
Gross delivery93.3%210 of 225 deliveries
Vendor-attributable delivery97.8%220 of 225 deliveries
Review77.8%133 of 171 review records
LQA88.6%78 of 88 LQA records
Arbitration58.3%7 of 12 arbitration records
Program completion91.6%206 of 225 deliveries

Extension control

Requested and approved extensions stay separate. Reason shares use requested extensions with a recorded controlled reason.

Extension control
MeasureResultPopulation
Extension requests15.6%35 of 225 deliveries
Approved extensions10.2%23 of 225 deliveries
Original deadline OTD91.1%205 of 225 deliveries
Gross delivery OTD93.3%210 of 225 deliveries
Original late to gross on time5Difference between two recorded clocks, not an approved-deadline recovery

Extension reasons

Extension reasons
ReasonRequestsShare
Source update1028.6%
Scope increase822.9%
Dependency delay720.0%
Approved capacity adjustment617.1%
Late reference material411.4%

Provider operating comparison

Providers are shown alphabetically with their own applicable stage populations. This is descriptive evidence, not a provider ranking.

Provider operating comparison
ProviderDeliveriesWordsGross OTDVendor-attributable OTDReview OTDLQA OTDCompletion OTDMedian completion TATExtension requests
LSP 167117,28392.5%100.0%85.1%92.3%94.0%42.3h16.4% (11)
LSP 255110,77192.7%96.4%63.6%93.3%94.5%38.4h9.1% (5)
LSP 35296,90598.1%100.0%73.0%85.7%96.2%50.4h21.2% (11)
LSP 45161,76790.2%94.1%88.4%84.6%80.4%62.6h15.7% (8)

Punctuality glossary

The four delivery-level clocks are distinct from Review, LQA and Arbitration stage OTD.

Original deadline OTDDelivery against the original recorded deadline.
Gross delivery OTDRecorded delivery punctuality before delay ownership is reassigned.
Vendor-attributable OTDDelivery punctuality after delay ownership is attributed to the provider or elsewhere.
Internal completion OTDCompletion of the internal program workflow against its priority-specific internal completion SLA.

Stage timing

Separate elapsed time, recorded touch time and queue signals without turning those signals into staffing conclusions.

Recorded translation queue
8.1h
225 deliveries | source field | like-for-like derived 21.0h
Translation touch
2.8h
225 deliveries | median 1.2h
Comparable queue / touch
7.6x
Elapsed-minus-touch basis | 225 deliveries
Review queue
23.1h
171 review records | touch 1.4h
LQA queue
29.9h
88 LQA records | touch 1.3h
Arbitration queue
62.4h
12 arbitration records | touch 2.5h

What the selected evidence shows

  • The recorded Translation queue field averages 8.1h. On the same elapsed-minus-touch basis used downstream, Translation is 21.0h; use that derived figure for stage-to-stage comparison.
  • Review averages 23.1h of derived queue time across 171 records, while LQA averages 29.9h across 88 records. Translation and Review are therefore close on the like-for-like basis before queue time rises later in the process.
  • Arbitration averages 62.4h of derived queue time and 2.5h of recorded touch time across 12 arbitration records. These are operating timing measures, not staffing or utilization measures.

Elapsed, touch and queue by stage

Comparable queue is derived as elapsed TAT minus touch for all four stages. Translation also retains the separately recorded 8.1h workbook queue as a source reference. Stage populations keep their own denominators.

Stage timing data
StageApplicableElapsed avgElapsed medianTouch avgComparable queue avgComparable queue / touchRecorded queue reference
Translation22523.8h11.7h2.8h21.0h7.6x8.1h source field
Review17124.5h19.2h1.4h23.1h16.6xNot separately recorded
LQA8831.2h28.3h1.3h29.9h22.2xNot separately recorded
Arbitration1264.9h55.0h2.5h62.4h24.9xNot separately recorded

Provider translation timing

Providers are shown alphabetically. Translation queue uses the recorded queue field; queue and touch remain descriptive operating measures.

Provider translation timing
ProviderDeliveriesMedian translation TATRecorded queue avgTouch avgRecorded queue / touchGross OTDVendor-attributable OTD
LSP 16710.4h7.1h2.9h2.4x92.5%100.0%
LSP 25513.3h9.3h3.2h2.9x92.7%96.4%
LSP 35212.1h8.4h3.0h2.9x98.1%100.0%
LSP 45110.9h7.8h1.8h4.3x90.2%94.1%

Workflow translation timing

Workflow timing uses the recorded Translation queue field and is shown with gross delivery and internal completion OTD so elapsed time is not read alone.

Workflow translation timing
WorkflowDeliveriesMedian translation TATRecorded queue avgTouch avgRecorded queue / touchGross OTDCompletion OTD
AI-assisted translation5111.6h8.9h2.0h4.5x92.2%92.2%
AI-first with human validation1410.3h7.3h1.2h6.2x100.0%85.7%
Human translation4612.6h8.1h5.1h1.6x97.8%91.3%
MTPE - full post-edit5712.2h7.7h3.4h2.3x91.2%89.5%
MTPE - light post-edit5711.1h8.1h1.3h6.1x91.2%94.7%

Timing interpretation

For stage-to-stage comparison, use the comparable queue columns only. Translation is 21.0h on that basis versus Review at 23.1h; the separately recorded Translation queue field is 8.1h and should not be read down the comparable column.

Elapsed TATRecorded clock time from stage assignment or start to completion.
Touch timeRecorded active handling hours for the stage.
Comparable queueElapsed TAT minus touch time for every stage, including Translation. This is the like-for-like cross-stage measure.
Recorded Translation queueThe separate Translation_Queue_Hours source field. It is retained as source evidence but is not used for cross-stage comparison.
Comparable queue / touchThe comparable elapsed-minus-touch queue divided by active handling. It is an operating signal, not a staffing diagnosis.

Demand & load

Read operating load through request volume, transaction size, batching, workflow and extension pressure rather than word volume alone.

Deliveries
225
386,726 source words
Source words
386,726
225 selected deliveries
Median words / delivery
765
P90 4,822
Peak request month
Mar 2026
143,926 words | 85 deliveries
Extension requests
15.6% (35)
225 selected deliveries
Batched deliveries
22.2% (50)
225 selected deliveries

What the selected evidence shows

  • Mar 2026 carries 143,926 selected source words across 85 deliveries. This is request-cohort demand, not completion-month throughput.
  • Micro and small work accounts for 44.4% of deliveries and 5.7% of source words, so transaction count and word volume describe different parts of operating load.
  • 35 of 225 selected deliveries requested an extension. Extension volume is shown as schedule pressure, not as proof of insufficient staffing.

Demand by request month

Request month uses the selected request cohort. The chart and details table use the same delivery population.

View demand data
Demand by request month data
Request monthDeliveriesSource words
Jan 202668134,123
Feb 202672108,677
Mar 202685143,926

Delivery size mix

All accepted size bands remain visible, including zero-count bands after filtering.

Delivery size mix
Size bandDeliveriesDelivery shareWordsWord share
Micro 50-1506026.7%6,1031.6%
Small 151-6004017.8%15,8344.1%
Standard 601-25008035.6%115,78929.9%
Large 2501-60003515.6%152,82339.5%
Campaign 6001+104.4%96,17724.9%

Batching mix

All accepted batching states remain visible so a filtered zero is not mistaken for missing data.

Batching mix
Batching statusDeliveriesDelivery shareWordsWord share
Batched5022.2%9,2462.4%
Standalone5022.2%12,6913.3%
Not applicable12555.6%364,78994.3%

Workflow mix

All accepted workflows remain visible with volume, translation TAT and gross delivery OTD.

Workflow mix
WorkflowDeliveriesDelivery shareWordsWord shareMedian translation TATGross OTD
Human translation4620.4%77,87420.1%12.6h97.8%
MTPE - full post-edit5725.3%121,35831.4%12.2h91.2%
MTPE - light post-edit5725.3%80,46820.8%11.1h91.2%
AI-assisted translation5122.7%84,99022.0%11.6h92.2%
AI-first with human validation146.2%22,0365.7%10.3h100.0%

Priority load

Priority mix is shown with source volume and extension requests. It does not imply priority effectiveness.

Priority load
PriorityDeliveriesDelivery shareWordsExtension requests
P1188.0%9,58411.1% (2)
P26629.3%118,28822.7% (15)
P310747.6%183,83012.1% (13)
P43415.1%75,02414.7% (5)

Content-type mix

Content types are shown with transaction count, source volume and median translation TAT for operating context.

Content-type mix
Content typeDeliveriesDelivery shareWordsMedian translation TAT
Campaign114.9%31,09010.7h
Conversational UI167.1%14,48211.8h
Help Center3113.8%32,31410.8h
Legal135.8%31,75113.2h
Lifecycle Email167.1%19,61310.6h
Microcopy3515.6%58,53111.7h
Multimedia52.2%17,51912.6h
Presentation10.4%1,764Below floor (1)
Product UI6328.0%56,01910.9h
Release Notes31.3%8,199Below floor (3)
Sales Enablement20.9%1,320Below floor (2)
Technical Documentation114.9%44,01212.2h
Training Module188.0%70,11227.4h

What demand evidence can and cannot show

Request volume, words, batching, workflow mix, extensions and timing describe operating load. They do not establish available headcount, scheduled capacity, utilization or whether staffing is sufficient.

Provider & workflow

Compare operating populations without turning descriptive differences into a provider ranking.

Providers represented
4
225 selected deliveries
Workflows represented
5
225 selected deliveries
Median deliveries / provider
54
4 represented providers
Gross delivery OTD
93.3%
210 of 225 deliveries
Vendor-attributable OTD
97.8%
220 of 225 deliveries
Extension requests
15.6% (35)
225 selected deliveries

What the selected evidence shows

  • The selected population spans 4 providers and 5 workflows across 225 deliveries. Provider rows remain alphabetical and no composite score is calculated.
  • Gross delivery OTD is 93.3% across 225 deliveries and vendor-attributable OTD is 97.8% across 225. The difference reflects ownership treatment, not a second delivery event.
  • Review OTD uses 171 stage records and LQA OTD uses 88. Provider percentages therefore need their own stage denominators rather than the full delivery count.

Provider operating comparison

Providers are shown alphabetically with stage-specific denominators. No composite score or ranking is calculated.

Provider operating comparison
ProviderDeliveriesWordsGross OTDVendor-attributable OTDReview OTDLQA OTDCompletion OTDMedian completion TATExtension requests
LSP 167117,28392.5%100.0%85.1%92.3%94.0%42.3h16.4% (11)
LSP 255110,77192.7%96.4%63.6%93.3%94.5%38.4h9.1% (5)
LSP 35296,90598.1%100.0%73.0%85.7%96.2%50.4h21.2% (11)
LSP 45161,76790.2%94.1%88.4%84.6%80.4%62.6h15.7% (8)

Workflow operating comparison

Workflow volume, timing and downstream stage OTD stay together.

Workflow operating comparison
WorkflowDeliveriesWordsMedian translation TATRecorded translation queue / touchGross OTDReview OTDLQA OTDCompletion OTDExtension requests
AI-assisted translation5184,99011.6h4.5x92.2%85.4%90.0%92.2%15.7% (8)
AI-first with human validation1422,03610.3h6.2x100.0%85.7%90.9%85.7%14.3% (2)
Human translation4677,87412.6h1.6x97.8%67.6%81.3%91.3%19.6% (9)
MTPE - full post-edit57121,35812.2h2.3x91.2%74.4%76.5%89.5%10.5% (6)
MTPE - light post-edit5780,46811.1h6.1x91.2%79.1%100.0%94.7%17.5% (10)

Provider by workflow delivery mix

Counts show where the selected work sits. The matrix does not score or rank providers.

Provider by workflow delivery mix
ProviderAI-assisted translationAI-first with human validationHuman translationMTPE - full post-editMTPE - light post-edit
LSP 1124201417
LSP 212272113
LSP 311414716
LSP 416451511

Comparison boundary

Provider evidence should be read with volume, workflow and applicable-stage population before interpreting any percentage.

Gross delivery OTDRecorded provider delivery punctuality before ownership is reassigned.
Vendor-attributable OTDDelivery punctuality after delay ownership is assigned to the provider or elsewhere.
Stage OTDReview and LQA rates use only stage records that occurred for the selected provider or workflow.
No rankingNo composite provider score, best-provider label or worst-provider label is generated.
Method, definitions, sources, and limitations

Data identity

Sample program data. Q1 2026, evidence through Apr 11, 2026, 225 deliveries. Source: JPK Program Evidence Dataset v3.1. Illustrative only; not a benchmark, client dataset, staffing model, or provider ranking.

Method

Filters define the selected delivery population first, then stage evidence is linked through Delivery_ID. Review, LQA, and Arbitration use only records where the stage occurred. Translation queue is shown both as its recorded source field and, where stated, as elapsed time minus recorded touch time for like-for-like stage comparison.

Operating limits

Queue, touch, elapsed time, request load, extension volume, provider mix, and workflow mix describe recorded operations. They do not establish headcount, scheduled capacity, utilization, causal performance, or staffing sufficiency.

Abbreviations and units

OTD = on-time delivery; TAT = turnaround time; LQA = linguistic quality assurance; LSP = language service provider. Compact KPI and table labels use h for hours.

Privacy and runtime

The dashboard contains fixed JPK-authored sample evidence. Filtering runs in the browser. The selected view and section may appear in the page URL for deep linking; the dashboard does not require personal, client, or confidential input.

Sample program data. Illustrative only, not a benchmark.