WFM Labs · working tool

POD / POA assumptions grid

Lay the point of departure against the point of arrival for every characteristic that moves volume, handle time or supply, call each difference, and the register and panels 1 and 2 of the weekly outlook pack build themselves.

Excel version: worked example · blank template (grid, questions, register, dashboard). Reports generated from the example: Word readout · sponsor slides; the wiki pack runs it from Claude Desktop.

Saved in this browser only. Export JSON to keep or share a copy.

The migration

The approach, in six questions

Rule 1: the departure baseline is the client's own history for the migrating markets, pre-migration months only. Rule 2: ranges, never single numbers. Rule 3: nobody signs a go-live without laying the incoming plan against the outgoing plan.

Rows with a gold edge are mandatory for the archetypes ticked on tab 1; a shaded row is mandatory and still empty. Different is fine; the call is whether a difference moves CPT, AHT or supply. Give a central FTE effect for the bridge and a low/high range for the tornado.

#CharacteristicPoint of departurePoint of arrivalCallDrivesPhaseFTE centralLowHighEvidenceOwnerDateNotes

Open assumptions

Every Watch, Problem or Unknown row, ranked the way panel 2 ranks them: width of the range × weakness of the evidence (Open 1.0 · Asserted 0.8 · Inferred 0.5 · Established 0.2).

RCharacteristicCallCentralRangeEvidenceRank scoreOwnerDate

Change log

When a direction changes or an assumption fails, log it the same day: who said it, what changed, what the model did. This is the record you go back to three weeks later.

DateRow #What changed (from → to)Said byEvidenceFTE changeModel updated?

1Approach — baseline to plan

Central FTE effects summed by what they drive. Rows without a central estimate do not move the bridge until they are sized.

2Assumptions — sensitivity, FTE

The five open rows with the widest range on the weakest evidence: what to go and confirm first.