The working desk / local interactive tools
Make the assumptions
visible.
Explore a workload scenario and prepare a release review. These tools explain their rules. They do not approve a deployment, predict an SLA, or send any information.
01 / What work is left?
A scenario.
Not a forecast.
Start with explicitly hypothetical values, then change one assumption at a time. Everything runs in this page; inputs are not stored or transmitted.
Hypothetical example / not live service data
8.0 hours of arithmetic headroom. This does not establish sufficient staffing or an SLA.
Inspect the arithmetic
500 × (1 − 50%) = 250 initial unresolved contacts. 250 × 20% = 50 extra contacts. 300 × 12 ÷ 60 + 4 = 64 work hours. 12 × 6 = 72 available hours.
Daily averages hide arrival spikes, simultaneous demand, queue mix, skill coverage, absence, repeat chains and waiting time. “Completion” must be validated against the actual task outcome. Review work may remain even at 100% automation.
Read the planning method ↗02 / What evidence is missing?
Bring evidence.
Not a green score.
Check a box only when the corresponding artifact exists and a responsible reviewer has inspected it. This is a local worksheet—not certification, a risk score or permission to launch.