How to record a work stoppage on a construction site: weather, materials and inspections

A construction site work stoppage record is a short incident record that captures, on the same day, when work stopped, between which hours, in which block and floor, which crew was affected and why. The cause may be rain, late materials, a power cut or an inspection visit; what matters is that the stoppage is a record kept that day, not a memory recalled later.

When work stops on site, everyone knows what happened. The trouble starts months later: why did the schedule slip, why was the timesheet low that week, why does the subcontractor say “we were waiting”? The answers usually sit in a WhatsApp group, inside a message nobody can find again.

Which situations should be recorded as a work stoppage?

Not every short wait needs its own record. But every situation in which a crew cannot do its planned work is worth recording. The most common causes on construction sites are:

• Weather: Concrete pours, scaffolding work or roof work postponed because of rain, snow, strong wind or frost.
• Materials: Ordered concrete, rebar or formwork material not arriving on time.
• Equipment: A crane, pump or generator breakdown, or a power or water cut.
• Inspections and visits: Work held during a check, an inspection or a visit by the client.
• Safety: An area closed because of an occupational health and safety (OHS) incident or a hazardous situation.
• Dependent work: The next crew unable to start because the previous crew has not finished.

Fields a work stoppage record should contain

The value of the record comes from keeping the same fields every time. Even when the foreman writes in a hurry, the following should not be missing:

1. Date and time range: When did the stoppage start, when did work resume, or was the day closed?
2. Location: Block, floor and section, such as “Block C, 4th floor slab”.
3. Cause: One sentence, without interpretation, such as “pump breakdown” or “concrete did not arrive until 2 pm”.
4. Affected crew: Which subcontractor or crew waited, with how many people, or was moved to other work?
5. Evidence: A photo, an image of the delivery note or a note on the weather.
6. Continuation: Did the work continue the same day or move to the next day?

A practical way to record it the same day

The hardest part of a work stoppage is that it has to be recorded on site. At that moment the foreman is busy moving the crew to other work and calling the supplier; sitting down to fill in a separate form is usually left for the evening, and then for never. That is why the record should come through the channel the foreman already uses.

“Block B, 2nd floor, slab concrete stopped at 11 because of rain, Kaba crew of 12 moved to stripping formwork.”

This single message carries the time, location, cause and affected crew. SahaSesi AI receives such texts, voice messages and photos via WhatsApp and sorts them as incident records; work stoppages, work accidents and inspection visits are kept separately. The record is read back to the foreman as “Saved: …”, and if anything was misunderstood, the foreman corrects it with a message.

Weather and the daily report

For weather-related stoppages, the most frequent question is what the weather was that day. In SahaSesi AI, the daily report and the evening PDF are prepared together with the site’s weather information for that day. When the stoppage record and the weather information sit on the same page, you do not need to look for a separate source later.

Review and approval in the office

A record from the field is not enough on its own; the office needs to review it. Messages that cannot be interpreted with confidence or cannot be processed land on a “pending review” list in the panel, so no record is lost silently. When the site manager approves the daily report, it is locked; later changes can only be made by an administrator, and every change leaves a trail. Managers receive a one-page report with a section per site every evening at 19.00 by WhatsApp and e-mail. If work stopped because of an OHS incident, the incident appears in red at the top of the report. If you also track occupational safety inside the office, the OHS incident and near-miss management module is a separate option for internal follow-up of incidents.

Common mistakes

• Discussing the stoppage only in a WhatsApp group: the bot cannot read groups; the message in the group has to be sent to the bot with “Forward”.
• Writing records in bulk a few days later: the hours and the affected crew get lost in the meantime.
• Writing the cause but leaving out the affected crew: the drop in the timesheet cannot be explained later.
• Keeping photos in a separate folder: the evidence should be attached to the record itself.

Recording work stoppages on the same day and in the same format resolves one of the most frequent disputes between the office and the site from the start. SahaSesi AI is currently being rolled out with its first sites through a pilot program; to see how a foreman’s WhatsApp message turns into a record and an evening report, you can visit the SahaSesi AI page.