Safety observation report template

A safety observation report records one unsafe condition or unsafe act: where it was, when it was seen, and what was done about it before the observer walked away. The photograph and the time it was taken carry most of the weight. Everything else in the template is there so the entry can be closed.

An observation is not an incident report

An incident report is written after something happened. Somebody was hurt, or nearly was. A safety observation is written before, about a condition that could lead there, like an open slab edge or an extension lead lying in standing water.

That timing changes what the report is for. The questions are whether the hazard was controlled, who fixed it, and whether it came back.

A template built like an incident form, with a narrative box and a witness section, gets filled in once and then never again.

Write it while you are still standing there

Observations written up at the end of the shift lose the detail that makes them useful. By 4pm the open edge is "somewhere on level 4" and the time is a guess.

Take the photo first, before anything is moved. Then say what you see in a sentence or two, out loud or typed. Then act: stop the work, tell the foreman, tape the area off. Then take a second photo once the hazard is controlled.

The two photos and their times are the record that it was seen and dealt with. The gap between them answers the question somebody always asks later, which is how long the edge stayed open after you saw it.

Twelve fields, most of them one line

Category lists grow if you let them. Keep this one short enough that nobody has to think, and let "other" catch the rest. When "other" becomes the biggest category in a month, that is the time to add one.

Split conditions from acts

An unsafe condition is something about the site: a missing guardrail, an uncapped rebar end, a blocked exit. An unsafe act is something a person did: working at height without a harness, taking a guard off a saw to clear a jam.

They need different follow ups. A condition gets fixed and mostly stays fixed. An act gets a conversation. If the same act keeps turning up across different crews, the problem is usually how the work is set up rather than the people doing it, and you cannot see that pattern when the two share a column.

Observations of acts name a crew or a trade, not a person. The report goes to people who were not there, and a name in it turns a site record into a disciplinary document. Have that conversation separately.

Photograph the hazard and where it is

Take one photo close enough to show the hazard. Take another from further back that puts it against something fixed, like a column or a stair core. The close photo proves the condition existed. The wide one lets somebody who was not there find it tomorrow.

Put something in frame for scale when size matters. A tape held against the top rail, or a boot beside a gap in the decking. "Guardrail too low" starts an argument. A photo of the tape reading 34 inches at the top rail does not.

The time has to come from the device that took the picture. A photo sent to a group chat and saved three days later carries the wrong date, and the one time the date matters will be the time somebody checks it.

A filled example, from a site that does not exist

Project: Harbour Street residential, six storeys, concrete frame. Observations for September 24, 2026, by D. Okafor, site safety adviser.

Entry 41 was open for 48 minutes, and the report can say so because both photos carry their times. That is the number a client or an insurer will look for first.

Entry 44 is worth its line. A report listing only serious hazards reads as if the adviser walked past everything else, and the small items are what the day was mostly made of.

Close every entry, or nobody reads the report

A log with forty open rows is a list everyone has learned to ignore. The last two columns are the reason to use a template at all.

Close an entry only when somebody has gone back and looked. A follow up marked done from the office is a follow up nobody checked. A closing photo taken from the same spot as the first one settles it in a way initials alone do not.

Once a week, read the open rows and the categories together. Three falls observations on the same slab edge in one week point to one problem with the sequence of work, and that belongs at the next coordination meeting.

Safe work can go in the same log

Some sites record safe practice as well as hazards. The same fields work: "what was seen" describes the practice worth repeating, and the action columns stay empty. Whether to do it is a site culture decision. If you do, keep both in one log so the ratio is visible, and filter the positive entries out of the version that goes to whoever fixes things.

Sitewise covers the capture half of this on iPhone and iPad. Each photo is timestamped when it is taken and, with location on, carries a GPS pin. The description can be dictated and transcribes on the device, which helps when you are wearing gloves. It works with no signal in a basement or a stair core and syncs later, and the day's observations export as a PDF or DOCX. It does not assign follow ups, send reminders, track closeout across a team or collect signatures, so the Closed column is still somebody's job.

The rest of the day's record belongs in the daily construction report. A problem with finished work, rather than a hazard, belongs in a defect report.