The stoppage nobody recorded as a stoppage
Work stops. A permit was not obtained, or an incident triggered a stand-down, or an area was closed while something was investigated.
HSE records it, thoroughly, because that is what the function exists to do. The schedule records something else entirely: an activity that didn't progress as expected.
Both records are accurate and there is usually no link between them.
Months later, when somebody asks why that activity slipped, the answer exists in two systems and in neither.
How it reaches you, and when
Sometimes it comes up in the daily coordination meeting, which is the good case. Sometimes it appears in the daily report. And sometimes it emerges days later, during variance analysis, when somebody is working out why a figure came in low and a site engineer mentions that the area was shut for two days.
That last case is the common one, and the delay matters more than it sounds. A stoppage discovered on the day can be planned around. A stoppage discovered a week later has already consumed the float
somebody would have used.
Two systems that don't touch
HSE keeps a permit register, an incident log and a record of stand-downs. Project controls keeps a schedule and a progress record. Neither has a field that points at the other.
So the schedule impact is calculated separately, by a planner, from a conversation, and it is recorded as a delay with a duration and no cause. It looks like every other slippage.
The consequence appears much later. When a delay analysis is done — for an extension of time, or a claim, or simply to explain a bad quarter — the events that caused it have to be reconstructed from memory. Claims Week 6 explains why the contemporaneous record carries the weight it does. This is one of the places it is routinely not made.
Not safety management
It is worth being clear about what a planner is doing here, because it is easy to be resented for it.
The planner is not measuring safety performance, not auditing the permit system, and not commenting on whether a stand-down was justified. Those are HSE's and they are none of project controls' business.
What the planner needs is narrower: a stoppage happened, it lasted this long, it affected these activities. That is a scheduling fact that happens to have originated in another function, and asking for it is not an intrusion into how that function does its job.
Framing it that way is usually the difference between getting the information and not.
The permit as a readiness test
There is a forward-looking use as well as a backward one.
Permits are one of the six readiness tests from Week 9, and unlike the other five they are frequently the last one checked. A crew arrives at a workface with drawings, material, plant and access, and can't start because the permit was applied for that morning.
Permit lead time is knowable. It is a number HSE can give you, it doesn't change much, and adding it to the look-ahead check costs nothing.
System design
Nothing here asks HSE to change how it works. It asks for one fact in a form the schedule can use.
| Record | Produced by | Required quality | Verified against | Feeds |
|---|---|---|---|---|
| Permit status | HSE | Current, per activity and location | Permit register | Readiness test |
| Permit lead time | HSE | A historic average, not a target | Permit history | Look-ahead check |
| Stoppage | HSE or site | Duration and area, on the day | Daily report | Progress variance |
| Cause of variance | Project controls | One word from a fixed list, on every delayed line | The stoppage record | Delay analysis, claims |
The last row is a single field on the progress update, filled from a short list. It is the cheapest contemporaneous record a project can keep and the one most often missing.
Practical insight
Take last month's activities that lost time and, for each, write the cause in one word. Weather, materials, drawings, access, permit, incident, other.
You won't be able to do it for all of them, and the ones you can't are the point. Those are the delays that have already lost their explanation, and next month there will be more.
Then add a single field to the progress update: cause of variance, from a short list. It takes seconds per line, and it is the difference between a delay analysis built from records and one built from recollection.
Key takeaways
- HSE records the event and the schedule records the delay. Nothing links them.
- Stoppages often reach the planner days late, during variance analysis rather than on the day.
- A stoppage found late has already consumed the float that could have absorbed it.
- Delays recorded without a cause can't be reconstructed when a delay analysis needs them.
- The planner is not auditing safety. The requirement is narrow: it happened, it lasted, it affected these activities.
- Permits are the readiness test checked last and the one most often missing on the day.
- A one-word cause field on the progress update
Figure 3 — Seconds per line on the progress update, and it is the difference between an analysis built from evidence and one built from recollection. is the cheapest contemporaneous record on a project.
Records born here. Permit register · stoppage log with durations · cause-of-variance field on every progress line.
What is coming next
That completes the sources. Everything from here is what you send back, starting with the date that decides how much of it was measured.
Next week: document control — revision status, and the reason half the site can be building to something superseded.
Enjoyed this lesson?
Join with Google to get each new lesson the moment it's published — and help me see which topics matter most to you. No spam, one email a week, unsubscribe anytime.
Already following on LinkedIn works too — this is just for the weekly email.