MTD Capacity Pressure Test
What did the first MTD quarterly cycle consume, and where will the pressure increase? Answer from your own volumes and handling, and this estimates where capacity is going — on your inputs, with your uncertainty, not ours.
What this is, and what it is not
- An estimate of what your own numbers imply about avoidable effort in one workflow.
- A statement of how confident that estimate can be, given where your numbers came from.
- A list of the assumptions doing the most work, and the evidence that would settle them.
- Capable of concluding that there is probably not enough concentrated avoidable work to justify investigating further — and it says so when your inputs imply it.
- A saving. Nothing here is money you will recover, and the tool never says it is.
- A measurement. It runs on what you tell it, and it is exactly as good as that.
- A substitute for the engagement. Establishing what the workflow actually costs, and which intervention is justified, is what the Evidence Sprint is for.
- A benchmark. There is no peer comparison here, and there will not be one until the sample supports it.
Six numbers and two answers
Loads the published synthetic accountancy figures, so you can see how the result reads before answering anything. Its two drivers apportion the published model's single avoidable-minutes figure — 40 minutes chasing and 20 minutes exception handling — so the total is exactly the published one. Synthetic demonstration case: not a client, and not a result.
What happens to these answers. Your answers and the result are stored so the result can be reproduced if the calculation changes. Nothing identifies you: there is no account, no cookie and no tracking across visits, and the session reference exists only to show you this result. Nothing is sent anywhere until you press the button.