BBS programs count behaviors. HOP learning teams find the conditions that make those behaviors inevitable — and that's where your leading indicators actually live.
A 15-person specialty concrete subcontractor in Denver had a strong BBS program on paper. Observation cards were being filled out. Safe behaviors were getting counted. Their safety coordinator was tracking ratios and presenting them at monthly meetings. And then a form carpenter fell six feet from an unsecured work platform and spent three weeks out of work — a recordable, a DART case, and a $15,625 OSHA serious violation for inadequate fall protection. The BBS numbers had looked fine the week before.
That gap — between a program that looks functional and a jobsite that isn't — is exactly what Human and Organizational Performance addresses. And the leading indicators it surfaces are ones most BBS programs are structurally incapable of finding.
Behavior-based safety, at its best, uses the ABC model — Antecedent, Behavior, Consequence — to identify at-risk behaviors and change them through reinforcement. Done well, it works. The problem is that most commercial construction operations run BBS at the compliance-theater level: a foreman fills out an observation card every two weeks to hit a quota, marks "safe" for whatever he watched for 90 seconds, and drops it in a box.
What that process captures: the behavior a worker performs when they know someone is watching.
What it does not capture: the latent conditions — the understaffed crew, the platform that was "always a little off," the foreman who knew something was wrong but didn't have a channel to report it without looking like he was slowing down the pour — that made the unsafe behavior rational in the first place.
This is the counterintuitive part. Most safety coordinators assume the observation card program is their leading indicator. The real problem is that it's measuring the wrong thing entirely. Observation cards count what people do. HOP learning teams ask why the conditions made that the easiest thing to do.
A learning team is not a post-incident committee. It is not a root cause analysis meeting. It is a structured conversation — usually 45 to 60 minutes — between a safety professional or trained facilitator and the people doing the work, before or after a near-miss, a first-aid event, or even a task that "almost went wrong."
On a commercial framing crew, this might look like: a competent person and two lead carpenters sitting down after a near-miss where a bundle of lumber shifted during a crane pick. No forms. No blame. The question is simple: walk me through what that pick actually looks like on your worst day — not the SOP version, the real version.
From that conversation, a safety coordinator might learn that the rigging hardware inspection is getting skipped not because workers don't care, but because the inspection form lives in the job trailer and the picks happen from a staging area 200 feet away. That is a latent condition. BBS would have observed the rigging check as "not performed" and logged an at-risk behavior. HOP finds the system failure that made skipping it the path of least resistance.
According to OSHA's own guidance on incident investigation, identifying root causes — not just immediate causes — is the standard. HOP learning teams operationalize that at the front end, before the incident, which is where the leading indicator value comes from. See OSHA's incident investigation resources at osha.gov/incident-investigation.
When learning teams run consistently — even once a week on a mid-size GC project — they generate data that no observation card program touches:
Back to the Denver concrete sub. The $15,625 OSHA serious violation was the visible number. The less visible ones: their EMR ticked up on the next renewal cycle, their primary GC put them on a watch list for prequalification, and two bids they submitted in the following six months didn't convert — not because they were formally disqualified, but because the GC's safety director had flagged the incident and the relationship cooled. A 10-person sub losing two concrete contracts in a single season is not an abstraction. That is a cash-flow event.
A willful or repeat OSHA violation for the same fall protection issue would have reached $161,323. For a 15-person operation, that is not a fine. That is a company-ending number.
The leading indicators that HOP learning teams surface — the rigging inspection form that lives in the wrong place, the foreman who stopped saying anything because the last time he did nothing changed — those are the things that show up in the incident three months later. BBS was watching the behavior. Nobody was watching the system.
A safety meeting pushes information down — here's the hazard, here's the rule, sign the form. A HOP learning team pulls information up — tell me how the work actually happens, where it gets hard, what you do when the procedure doesn't fit reality. The direction of information flow is the entire difference.
Yes, but only if someone is trained to facilitate the conversations without using them as disciplinary intake. A foreman can facilitate, a safety coordinator can facilitate — the role matters less than the approach. If the conversation ever results in someone getting written up for what they said in a learning team session, the program is over. Nobody will talk again.
After any near-miss or first-aid event, without exception. Beyond that, a weekly cadence — even a short one — on active phases with high-energy hazard exposure: crane picks, forming operations, elevated work platforms, trenching. The frequency should match the hazard density of the current phase, not a fixed calendar.
They can run together, but they answer different questions. BBS asks: is this behavior safe or at-risk? HOP asks: why does this behavior make sense given the conditions? Both are legitimate. A program that only runs BBS is missing the system-level data. A program that runs both — and uses HOP findings to redesign the antecedents that drive at-risk BBS behaviors — is the one that actually moves the needle.
Running learning teams, closing corrective actions, tracking system-level leading indicators — that work requires a safety coordinator's actual attention, on the site, in the conversation. It cannot happen if the same person is also updating ISNetworld, chasing training records, maintaining written programs, and managing OSHA 300 logs manually.
EHS, Inc. handles the administrative layer — prequalification portals, LMS tracking, OSHA recordkeeping, written programs — so the safety professional can stay in the field doing the work that actually prevents the next incident. Talk to EHS and see what that looks like in practice.
Aaron West
Founder, EHS, Inc. — 18+ years in EHS compliance and contractor safety
Aaron West has spent over 18 years helping contractors and businesses navigate OSHA compliance, ISNetworld® certification, and workplace safety management. He founded EHS, Inc. to make enterprise-level EHS accessible to companies of all sizes — serving contractors and businesses nationwide — without long-term contracts or enterprise overhead.
Our team handles the complexity so you can focus on running your business. No long-term contracts, no learning curve.
Talk to EHSIn upstream drilling and well servicing, the citation isn't for the hazard — it's for the missing verification record.
Your EMR tells you what already went wrong. Here's what data-driven safety pros in manufacturing track before the next incident.
The paperwork gap—not the hazard itself—is what gets upstream oil and gas contractors cited and what lets SIF events slip through undetected.
Framework to achieve zero incidents
Stop hitting paywalls
54 topics in English & Spanish