A safety observation log that proves it got fixed.

Write down what was seen, who is fixing it and by when, and check it before you close it. A log like this turns a hallway conversation into a record.

Free
No signup
Print · CSV · Markdown

Download CSV Download Markdown

Safety observation log

os.construction · free template

Project
Week of
Recorded by
Distribution

Observations

#	Location	Hazard	Behavior or condition	Priority	Assigned to	Corrective action	Status
1	L2 stair 2 landing	Housekeeping: debris and cords in path (SAMPLE · delete this row)	Condition	Medium	Drywall	Clear path; route cords overhead	Initiated
2	Roof, east edge	Guardrail section removed for material hoist	Condition	Urgent	Roofing	Reinstall rail or set warning line before work resumes	Ready for review
3	Site gate	Delivery driver without hi-vis vest	Behavior	Low	GC super	Vests at gate; brief at next toolbox talk	Closed

Sample rows are illustrative and marked for deletion. Your contract, drawings and specifications govern. Template from os.construction/resources/templates/safety-observation-log

How to use it

Using the safety observation log

Record it when you see it: location, what the hazard is, and whether it is a behavior or a condition.
Set the priority by what could happen, and stop the work on the spot when it can’t wait for a log.
Assign one company or person to fix it, with a due date and the corrective action you expect.
When they say it’s fixed, mark it ready for review and look before you close it. If it isn’t right, send it back.
Review open observations weekly, at the toolbox talk or the coordination meeting, and look for repeats by trade or location.

Observed and recordedLocation, hazard, priority
InitiatedAssigned, awaiting correction
Ready for reviewAssignee says it’s fixedNot accepted: back to “Initiated”
ClosedChecked and accepted

How an observation moves to closed

Text version

Observed and recorded: Location, hazard, priority
Initiated: Assigned, awaiting correction
Ready for review: Assignee says it’s fixed
Closed: Checked and accepted

Not accepted: from “Ready for review” back to “Initiated”.

In os.construction

Do this in os.construction instead of a spreadsheet

Observations in os.construction are typed under Safety, Quality, Commissioning or Warranty, with a priority from Low to Urgent, an assignee, a due date and a Safety panel for the hazard, contributing behavior and contributing condition. They move from Initiated to Ready For Review to Closed (or Not Accepted, back for rework), with a response log and photos, and can be converted to an RFI or a punch item. Save common observations as templates.

Try it on the sample project

Every trial workspace includes a sample project to run this workflow on. 14-day free trial. Pricing for paid plans isn't set yet.

Start free trial Read the guide: Observations

FAQ

Questions about the safety observation log

What is a safety observation?

A recorded note of an unsafe behavior or condition seen on site, with who is responsible for correcting it and by when. Many safety programs also record positive observations.

Is this log a replacement for our safety program?

No. It is a tracking sheet. Your safety program, the competent person on site and the regulations that apply to your work decide what has to be done and documented.

What about injuries and incidents?

Report those through your incident procedure and any required recordkeeping. Use this log for the hazards you find and correct.

Who should close an observation?

Someone other than the person who fixed it: they mark it ready for review, and the person who raised it, or the safety lead, checks and closes it.

Can I export observations from os.construction?

Not from the Observations tool today. Use filters and saved views to share the current list in the app.

Keep going

Keep exploring