A Blocked button on the crew screen opens a fixed list of reasons: no materials, weather, can't get on site, equipment down, permit or inspection, crew short, scope question, something else. Weather asks one more question — which kind, from rain to smoke — so the days lost to each can be counted. Reporting notifies everyone you have designated and flags the stage delayed with that reason attached. The plan's dates stay exactly where they were.
Also called: crew can't work · waiting on materials · report a delay from site · crew stuck
Four men waiting on a delivery is money burning right now
One button on the crew screen, then eight chips: no materials, weather, can't get on site, equipment down, permit or inspection, crew short, scope question, something else. Tapping one notifies everyone you have designated, in that minute. Every hour between the crew stopping and you hearing about it is an hour you have already paid for.
A blocked crew usually tells somebody at the end of the day, by which point you have paid four men to stand and wait. The office finds out when the hours land, not while it could still send the missing bundle.
Chips rather than a text box, so the reasons can be counted
Try itTyping on a site in gloves and glare is close to impossible, and a typed reason cannot be counted, filtered or learned from. A fixed list makes the same delay look the same every time it happens — and weather asks which kind, so we always lose days to the wind becomes a count of wind days rather than a feeling.
It marks the stage delayed. It never moves your dates.
Reporting blocked flags the stage delayed with the reason attached and starts the clock on it, so the cost accrues visibly instead of being reconstructed on Friday. What it does not do is shift the plan. A framer tapping a chip at 7am must not quietly re-promise the customer a completion date — rescheduling stays your decision, made off the record this creates.
The chips add up into where your days actually go
Overrun days are grouped by reason and ranked by total days lost, with the crews each reason hit and how often it happened. Stages that ran over with no reason recorded show up as exactly that rather than being quietly dropped. A tap in the field becomes office analysis with nobody re-entering anything.
The man who reported it is told whether anyone was reached
The screen says The office has been told only when the notification actually reached somebody; if it reached nobody, it says Reported and nothing more. On a site where the alternative is ringing the office and getting voicemail, knowing the message landed is the difference between a crew using this next month and abandoning it after the first time.
- 1He taps Blocked and picks one of eight chips — weather adds a second tap for which kind.
- 2The job comes off his open shift; if he isn't clocked in and runs more than one job, he picks it first.
- 3Everyone you have designated is notified in that minute.
- 4The stage is marked delayed, with the reason attached and the clock running on it.
- 5The screen says The office has been told only when somebody actually was — otherwise just Reported.
Four men standing on a site waiting for a delivery cost money by the hour, and every hour before the office hears about it is spent. One tap reports blocked: everyone who needs to know is told, the stage is flagged with the reason, and the clock on the delay starts. What it never does is move the promised dates — a framer tapping a chip at 7am must not quietly re-promise the customer a completion date. And the reason is chosen from a list rather than typed, because typing on a site in gloves and glare is close to impossible, and a typed reason cannot be counted.
- Hours of paid standing time before the office hears about a blocker.
- Delay reasons that were never captured in a countable form.
- Field reports silently re-promising customer dates.
