Each stage and each checkpoint can carry a description in the builder's own words. These appear as info tips beside the stage title and each checkpoint row in the stage modal. Unlike labels, descriptions are NOT frozen onto a project — correcting one reaches every crew immediately, including on jobs already in progress.
Also called: stage description · what does this checkpoint mean · explain the checklist · crew doesn't know what to tick
- 1Descriptions are stored on stage_definitions / checkpoint_definitions (migration 148)
- 2The Gantt reads them through GET /api/stage-library, which is open to any signed-in member and keyed by legacy slug
- 3A slug appearing in several templates takes the FIRST description rather than merging — 'concatenating two builders' wordings produces a sentence neither of them wrote'
- 4Descriptions are treated as an enhancement: a failed fetch never blocks the checklist
A description of what dirtwork actually includes is written for the crew doing the dirtwork, and it was readable only by administrators — so the only people who could open it were the people who already knew. Crews read the stage and checkpoint descriptions on the jobs they are working. A checkpoint's name stays frozen once a job starts, so the crew and the customer always see what was agreed, but the explanation behind it is guidance, and corrected guidance reaches the crew currently on site rather than waiting for the next job.
- Checkpoints meaning different things to different crew members
- Guidance trapped behind an admin-only screen
- Corrections only reaching future jobs
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 →