A dedicated delay modal with eight cause codes (Weather, Crew No-Show, Material Issue, Equipment, Permit Delay, Site Access, Scope Change, Other), a days/hours impact field, a free-text description, and photo attachment. Saving both sets the stage to Delayed and logs the reason. Multiple delays can be reported against one stage.
Also called: report a delay · why is the job late · weather delay · crew no show · what caused the delay
- 1Choosing 'Delayed' as a status opens the modal rather than flipping the status directly — the modal's Save sets it
- 2A picked cause is held as a DRAFT in memory; nothing reaches the database until Save
- 3Completed stages that ran early or late get a lighter inline flow instead, with early-completion reasons ('Smaller scope', 'Good equipment', 'Extra crew', 'Great weather')
- 4In-progress stages show nothing — no 'any issues to report?' chip wall on a healthy stage
- 5Photos attached to a delay are persisted onto the stage
Clicking a delay reason recorded it immediately, before anyone had said how many days or why. Pick Weather, get called away, close the window — and the job carries a permanent record that a delay happened, for an unknown number of days, for an unrecorded reason. Most of the delay records in use had both fields blank, which is why 'which causes cost us the most days' had never been answerable, and the supplier and weather arguments stayed anecdotal. Nothing is written until the days and the reason are filled in.
- Delay rows with no cause and no cost
- No answer to which causes cost the most time
- Delay explanations living only in a conversation
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 →