Synthetic demonstration case — calculated preview

MTD quarterly-update preparation

The process converts client digital records into a complete quarterly-update pack ready for qualified tax review. Client-service coordinators log and check submissions, processing analysts structure the records and resolve standard operational exceptions, and a senior operations reviewer completes a second readiness check where required. The workflow runs continuously during each quarterly reporting cycle.

Problems appear during initial completeness checking and preparation. Missing digital records, incomplete categorisation, missing authorisation, unsupported files and unclear transactions create repair queues, repeated handling and missed turnaround targets.

Every figure on this page is calculated from the downloadable synthetic operational log. Nothing here is client data.

Process boundary

Process boundary

Client records received and logged to complete quarterly-update pack ready for qualified review.

Calculated preview

Calculated operational baseline

ILL180 cases
Operational log rowsSYN
ILL85.56%
Service-level attainmentSYN
ILL154 cases
Within service levelSYN
ILL26 cases
Service-level breachesSYN
ILL351.06 min
Mean turnaroundSYN
ILL359 min
Median turnaroundSYN
ILL494.5 min
90th percentile turnaroundSYN
ILL523.8 min
95th percentile turnaroundSYN
ILL44.44%
First-time-rightSYN
ILL55.56%
Rework rateSYN
ILL221.84 min
Mean queue timeSYN
ILL129.22 min
Mean processing timeSYN
Mean queue time
221.84 min
Mean processing time
129.22 min
First-time-right
44.44%
Rework rate
55.56%
Defect Pareto

Where the repair work concentrates

  1. Missing digital records14 cases · 53.8% (synthetic)
  2. Incomplete income or expense categorisation7 cases · 26.9% (synthetic)
  3. Duplicate or unclear transaction2 cases · 7.7% (synthetic)
  4. Missing client authorisation2 cases · 7.7% (synthetic)
  5. Unsupported source file1 cases · 3.8% (synthetic)
Illustrative scenario

Illustrative benefit — every input stated

The arithmetic is deliberately exposed: volume, affected share, reduction, adoption and rate are stated inputs, not a black-box output.

ILL40,000 cases
Stated annual volumeSYN
ILL35%
Affected share (stated)SYN
ILL30%
Assumed reductionSYN
ILL70%
Assumed adoptionSYN
ILL60 min
Minutes saved per affected caseSYN
ILL£38
Stated hourly rateSYN
Illustrative scenario2,940 cases
Calculated affected casesSynthetic
Illustrative scenario2,940 hours
Calculated capacity releasedSyntheticCalculated preview from the stated inputs.
Illustrative scenario£111,720
Illustrative annual capacity valueSyntheticIllustrative conversion at the stated rate; realised cash depends on management action.
The economics

What the released capacity is, and what the engagement covers

Two separate facts. The capacity below is what the illustrative scenario releases in a year; the engagement beside it buys the decision and the design that would establish whether any of it is real.

Illustrative scenario£111,720
Illustrative annual capacity valueSynthetic
Illustrative scenario2,940 hours
Illustrative capacity releasedSynthetic
Illustrative scenario1.6 FTE
Illustrative capacity released, as full-time equivalentSyntheticIllustrative, on the stated inputs above. Not a forecast, not realised cash, and not a promise of savings.

Stated full-time equivalent year: 1,800 hours.

Released capacity recurs while the change is sustained — which is a thing to verify, not to assume. How realised value is verified →

What the engagement covers

The engagement covers the decision and the design: whether the workflow is worth changing, and what the pilot must prove. Implementation is scoped separately, once the intervention is selected.

The boundary

What this does not prove

  • The records are synthetic and do not describe a real client.
  • Candidate Xs are hypotheses, not validated root causes.
  • The benefit is illustrative, not realised cash.
  • Tax review and underwriting assessment are downstream professional judgements.
  • The page is a calculated preview, not a verified production run.
Inspect the example

The operational log, first rows

Every figure above is computed from the operational log below. The first rows of that log are shown here, exactly as the analysis reads them.

The operational log, first rows — 8 of 180 rows
case_idreceived_atcompleted_atturnaround_minutessla_target_minutessla_metdefect_categoryrework_countmissing_fields_countqueue_wait_minutesprocessing_minutesmanual_toucheshigh_value_flagsecondary_approval_requiredoriginator_channelfirst_time_rightoutcome_status
MTD-00012026-06-01T08:002026-06-01T11:27207480TrueNo recorded defect00117902FalseFalseSpreadsheet uploadTrueReady for qualified review
MTD-00022026-06-01T08:372026-06-01T12:37240480TrueNo recorded defect00161792FalseFalseSpreadsheet uploadTrueReady for qualified review
MTD-00032026-06-01T09:142026-06-01T13:19245480TrueNo recorded defect00157883FalseFalseEmailTrueReady for qualified review
MTD-00042026-06-01T09:512026-06-01T14:13262480TrueNo recorded defect001611016TrueTrueSpreadsheet uploadTrueReady for qualified review
MTD-00052026-06-01T10:282026-06-01T17:40432480TrueUnsupported source file222671657FalseFalseSpreadsheet uploadFalseReady for qualified review
MTD-00062026-06-01T11:052026-06-01T14:22197480TrueNo recorded defect00961012FalseFalseEmailTrueReady for qualified review
MTD-00072026-06-01T11:422026-06-01T16:06264480TrueNo recorded defect001381265FalseTrueEmailTrueReady for qualified review
MTD-00082026-06-01T12:192026-06-01T21:43564480FalseMissing digital records233971679TrueTrueClient portalFalseReady for qualified review

8 of the 180 synthetic rows. Every figure above is computed from all 180, not from these 8.

Downloads
Behind identification

The full worked pack

The operating procedure and the complete operational log, together. They are what rebuilds this example rather than reads it, so we ask who is asking.

  • The standard operating procedure for this workflow (PDF)
  • The complete synthetic operational log, all rows (CSV)

Four details, and the pack opens in this browser.

We use these details to send the pack and to follow up about your workflow. No newsletter unless you ask for one.

The sprint runs this discipline on your workflow, not a synthetic one.

Discuss a workflow