Most contractors think about incident documentation after an incident. That is too late. The documentation that protects the business is made in the first thirty minutes, while the scene is unchanged and the crew’s memory is current.

The field safety system includes what the crew does when a hazard is present. The incident protocol is what the crew does when the hazard produced an injury, near-miss, or property damage. Both need to be built and practiced before either is needed.

This article covers the incident side: what to document, in what order, and why the first thirty minutes determine the quality of the entire record. The distinction from the ongoing job file in Article 12 is timing: that article covers the record built across the job; this one covers the record made at the moment of an event.

The Incident Documentation Protocol is three steps that run in sequence. The sequence matters. Each step has a specific purpose, and steps done out of order produce an incomplete or unreliable record.

Why Post-Incident Documentation Fails

The obvious problem is memory. A crew member who documents an incident two days after it happened is working from a memory shaped by conversations with other crew members. The documentation is not contemporaneous. It is a consensus narrative.

The less visible cost is legal exposure. Insurance adjusters and attorneys distinguish between a contemporaneous record and a reconstruction made later. The contemporaneous record has a date and time. The reconstruction can be challenged; both are documents, but only one is protection.

The deepest cost is the pattern. A contractor who never builds an incident protocol leaves crew members to figure out what to do under pressure. Their instinct will be to help anyone injured, not to document the scene. Documentation is not instinct; it has to be trained.

The Incident Documentation Protocol

The Incident Documentation Protocol runs immediately after an incident is confirmed: after anyone injured is stabilized and any active hazard is controlled. The documentation step is not the first step. It is the second. Stabilize first, then document.

Step 1 documents the scene before anything changes

Step 1 is the immediate record: photographs from multiple angles, a written description of what happened, who was present, and the time.

The scene changes fast: equipment gets moved, conditions shift, and memory adjusts. The documentation made in the first thirty minutes reflects what was actually there. Documentation made an hour later reflects what people remember.

Before: The crew addresses the incident and returns to work. The scene is altered. Documentation is created later from recollection. After: Photographs and a written description are made before the scene changes, with timestamps and a witness list.

Step 2 notifies the right parties in the right order

Step 2 is notification: who the contractor calls, in what order, and what they say. For a reportable injury, the notification sequence goes: injured party’s family if needed, employer, insurance carrier, and OSHA if the severity requires it.

The notification step exists in the protocol before the incident. The contractor should not be looking up OSHA reporting thresholds while standing on the job site after an injury. That information should already be in the incident protocol.

Step 3 preserves the evidence and the record

Step 3 is preservation: what to keep, what not to disturb, and what to protect until any required investigation is complete. This includes the photos taken in Step 1, any physical evidence relevant to what caused the incident, and the written record.

Step 3 also includes post-incident documentation from the next 24 to 48 hours. This covers conversations with the injured party, statements taken, OSHA filings, and the business’s internal response record.

How the Conductor Activates Your Incident Documentation Protocol

An employee slips on a roof edge. The lead calls the owner. Before any documentation decisions are made, the owner needs to know what the protocol says.

The Living Library maintains the incident protocol the owner has built. It includes the documentation steps, the notification sequence, OSHA thresholds, and the record of prior incidents. The Conductor reads from that protocol and returns the specific steps for this incident type and jurisdiction. Not generic OSHA guidance, but what this business’s protocol says to do.

The crew leads with the right steps. The record is made while the scene is still current.

Write the Protocol Before the Next Job Starts

Don’t build the incident protocol after an incident. Build it at the start of the next job, in a calm thirty minutes when there is no pressure.

Write down three things: what to document at the scene, who to notify and in what order, and the OSHA thresholds for the trade. That is the protocol.

Attach it to the field safety system so it is in the same place the crew finds the JHA and Toolbox Talk.

The Crew That Knows What to Do Has a Different Incident Record

A crew that has practiced the incident protocol produces a record in the first thirty minutes that covers the business’s position completely. A crew that improvises produces whatever memory and instinct generate under pressure. The record made under a practiced protocol is the record that holds up. Try Kiluma free for 14 days at kiluma.ai.