The completion test used to stamp Delivered and to advance to Wrap-Up now reads the stage's own checkpoint list from the project and merges it with what is actually stored, rather than trusting the payload.
Also called: says delivered but nothing arrived · one checkbox marked the whole stage done
- 1The stage's snapshotted checkpoint ids are the denominator
- 2Stored completion is read back and merged with the incoming toggle, because the client sends only what it changed
- 3Legacy stages with no checkpoint list fall back to the old payload reading rather than never completing
- 4Materials 'Delivered' requires the receive checkpoint or a genuinely complete stage
Ticking one checkbox marked the whole stage done. The screen sends only the box that was toggled, and the test for 'is everything finished' was run against that one box, which was of course complete. A builder ticked Order Placed on a job and one second later the card stamped Delivered on material he had not received, while the same card still read 'Order not sent'. The same test decided whether a build was finished, so a single checkbox on a final stage could have declared an entire job complete and emailed the customer to congratulate them. Completion is measured against every checkpoint on the stage as it actually stands, including on jobs whose builders customised the checklist and have no delivery checkpoint at all.
- One tick being read as a completed stage
- A build declared finished from a single checkbox
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →