Walk one disputed invoice backwards
Read from the top, it goes back in time. Each step was small, and each one is a place the dispute could have been stopped.
An invented example, not a client and not a forecast.
| When | What happened | Upstream cause |
|---|---|---|
| Day 5 after close | Finance rebuilds the $15,000 milestone invoice by hand, editing quantities and a rate. The client disputes $3,000 of it. | Billing rebuilt at the end |
| Month-end | Some hours cannot be tied to a milestone or budget line, so the WIP balance is debated. | Time and costs not linked |
| Week 9 | The client asks for a refinement. The team does it. No price is set and no one approves it. | Informal change control |
| Week 1 | Delivery builds its plan from a kickoff briefing. A rate concession agreed by email is missed. | Poor handover |
| The sale | The job is priced at a high level. What is out of scope is never written down. | Weak scoping |
Finance saw it last. Everyone before them could have seen it first.