Checkpoints are the granular items inside a stage — 'Posts Set', 'Trusses Up', 'Order Placed', 'Material Received'. They render as toggle rows in the stage modal and as an inline expandable checklist on each stage in the project cockpit. Completion drives the progress bars, the customer's portal, the PM pipeline and the stage-complete notifications.
Also called: checklist · milestones · tick off the work · stage checklist · job checklist
Each stage carries the list of work inside it
Post Set, Girts Done, Equipment on Site, Trusses Up, Bracing Complete, Framing Inspection — the specific items that make up framing, not one status flag on a bar. Ticking them is what drives the progress bars, the customer's portal and the project board. It is the paper checklist off the truck dash, in the one place the office can see it.
The stage finishes when the work does, not when someone remembers
Completing every applicable checkpoint marks the stage complete and sends the customer their update. That rule lives in exactly one place, so the progress bar, the board badge and the email always agree. It has to: an earlier version measured completion against boxes anyone had touched, which meant a stage announced itself finished — and emailed the customer — on its very first tick.
Proof attaches to the checkpoint, not to a folder
Marking a checkpoint complete offers Take Photo or Choose from Library, and you can add as many shots as the job needs in one pass. They stay on that item as a “3 photos” pill that opens to thumbnails, and proof can be added later to something already ticked. When a customer says a thing was not done, the answer is on the row that says it was.
A checkpoint that doesn't apply stops counting — nothing gets deleted
This job has no garage doors, so that item is marked not applicable: it keeps its label, drops out of the denominator, is hidden from the customer, and records who marked it and why. The stage then reads 3/3 and closes honestly instead of hanging open forever on one irrelevant box. Renaming or deleting the item instead would quietly change what everyone agreed to.
Once the job starts, the checklist stops moving
Checkpoint names, their existence and their order are fixed at project start, so the crew, the office and the customer are all looking at what was agreed. Tailoring for one job — an extra step, a different word — happens before that, on the Start Project screen. A checklist anyone can rewrite mid-build is a checklist nobody can be held to.
Ticked on a phone, visible in the office and on the customer's page
A checkpoint ticked or photographed on site shows up on the office computer, and the customer's own page lists the same items with the date each one was finished. Progress that lives in a group text has to be found, read and retyped before anyone can act on it.
- 1The checkpoint list comes from the project's own snapshot (task.checkpoints), falling back to the platform catalogue for older projects
- 2A tick writes locally for instant response and mirrors to the server through the single milestone writer
- 3The same tick dual-writes to the stage-instance model, keyed by the legacy (project, task, checkpoint) triple
- 4Completing every applicable checkpoint marks the stage complete and triggers the notification path
- 5The completion rule lives in one place so every progress bar, badge and predicate agrees
Stage completion was measured against the checkpoints anyone had touched rather than all the checkpoints there are — so a stage declared itself finished on its very first tick and sent the customer a 'your framing is complete' email while the crew were still framing. Customers were congratulated on work with a week left in it, and the builder found out when they called asking about the next payment. Completion is counted against the full checklist, and both sides of that comparison were changed together on purpose: correcting only one of them would have left every multi-item stage permanently silent instead, with nothing on screen to show it had gone quiet.
- Stage status too coarse to reflect real progress
- Premature 'stage complete' messages to customers
- Checklists living on paper and never reaching the office
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 →