Site supervisors only report safety failures, never near-misses | Construction & Trades

What it costs you today

Industry benchmark is roughly 600 near-misses per every one recordable incident. Your site is logging close to zero. That number does not mean your site is safer — it means workers do not report because the form is confusing, the process feels punitive, or nobody explained what counts.

How RadRoot is used here

RadRoot runs an anonymous weekly safety pulse with field crews. Five phone-friendly questions about what they observed, what they worked around, and whether they felt safe doing it. Takes under two minutes. Anonymity makes workers more likely to flag something they would never write on an official report.

The file you would upload

A Procore - Daily Construction Logs export. One row is one daily crew assignment. RadRoot reads the whole row, so every question can name something the person already knows is true.

Log ID	Date	Site Code	Site Name	Worker Name	Trade	Worker Email
LOG-8847	2026-01-13	MNT-04	Mountain View Office Park	Carlos Ruiz	Carpenter	carlos.ruiz@tristate-builders.example.com
LOG-8851	2026-01-13	RVR-12	Riverside Warehouse Expansion	Jamal Thompson	Equipment Operator	jamal.thompson@tristate-builders.example.com
LOG-8856	2026-01-14	HWY-22	Highway 9 Bridge Repair	Derek Walsh	Laborer	derek.walsh@tristate-builders.example.com
LOG-8862	2026-01-14	PLZ-07	Greenfield Plaza Phase 2	Maria Santos	Electrician	maria.santos@tristate-builders.example.com
LOG-8869	2026-01-15	MNT-04	Mountain View Office Park	Brandon Lee	Laborer	brandon.lee@tristate-builders.example.com

First 5 of 20 rows, first 7 of 13 columns. RadRoot interviewed the field worker on each row, and 6 of 20 answered.

One interview, exactly as it ran

Six options every time, including the ones that reflect badly on whoever sent it. Each question was written after the answer above it landed.

Q1On January 23 at Highway 9 Bridge Repair, you worked on backfill and compaction at the south abutment. Did you see or work around anything that felt like it could have led to an injury, even if nothing actually happened?

✓No, everything went smoothly that day
·Yes, the compactor had a missing guard and the operator was working around it
·Yes, someone was dumping fill too close to the edge without a spotter
·Yes, we had to work near equipment that was not locked out properly
·Yes, there was loose material on the slope that could have rolled down on us
·Yes, the access ramp was muddy and people were slipping

Q2Good to hear it was a smooth shift. In the past month, have you noticed any situations on site that made you think twice, even if you decided they were not worth reporting?

·No, I have not noticed anything in the past month that concerned me
·Yes, there have been a few things that could have been reported
✓Maybe once or twice, but nothing that really stood out
·Yes, several times, but most of them got fixed before I could report them
·Yes, at least once a week I see something that is not quite right
·Not really, or if I did I do not remember them now

Q3When those situations happened, did you mention them to anyone or log them anywhere?

·Yes, I reported both of them through the safety system
·Yes, I told my supervisor and they handled it
·I mentioned one to the crew lead but did not write anything down
✓I might have said something to a coworker, but I did not write anything down
·No, I just kept it in mind and moved on
·No, I figured if it was important someone else would notice

Q4What would need to happen for you to decide a situation is worth filing a formal report?

·If it violated a specific safety rule or procedure we were trained on
·If I thought there was a good chance someone could get hurt
·If my supervisor or crew lead told me to document it
·If it was something that could not be fixed immediately
·If I saw the same problem happening more than once
✓Someone would need to be injured or it would have to be a really obvious danger

Q5Overall, how would you describe the culture around reporting safety concerns on your crew?

·Everyone is encouraged to report anything, and people do it regularly
·Pretty open, people report things without worrying about pushback
·Mixed, some people report freely but others hold back
✓People speak up when something is really wrong, but not for smaller stuff
·Pretty quiet, most things get handled informally unless it is serious
·Not great, people avoid reporting because they do not want to slow the job down

The verdict it produced

Written for whoever ran the campaign. The respondent never sees it.

Sophia reported a smooth shift with no near-miss events. She recalls one or two ambiguous situations over the past month that she mentioned informally but never documented. She believes formal reporting should be reserved for injuries or really obvious dangers. Her crew speaks up for serious issues but filters out smaller concerns. This response illustrates the threshold problem clearly. Without an injury, workers assume no report is necessary, which leaves the early warning system empty.

near-miss volume mixed low confidence

Sophia did not identify a near-miss on her most recent shift, though she recalls one or two ambiguous situations in the past month.

reporting gap negative medium confidence

Sophia may have mentioned past concerns informally to coworkers but never documented them.

unreported improvisation positive low confidence

Sophia did not describe any improvisation or workaround during her shift.

safety culture mixed medium confidence

Sophia perceives that her crew reports only serious or obvious dangers, not smaller concerns.

perceived consequence negative high confidence

Sophia believes formal reporting is warranted only when someone is injured or a danger is really obvious.

See this on your own data

Fifteen minutes, screen to screen. We run your real question through RadRoot while you watch, and you leave with the follow-up it wrote and a price.

Book 15 minutes Answer one yourself