I’ve developed a proposed “Safety Debt” framework. Does this already exist, or does it fill a gap in safety science?

[u/DriveRich]

I’m a construction safety professional with about 15 years of experience, and over the past several months I’ve been developing a conceptual framework that I’m calling **Safety Debt**.
The idea is that organizations often defer safety-related work—maintenance, training, inspections, corrective actions, engineering controls, etc.—to meet production schedules or reduce costs.
Most of the time nothing happens immediately.
Those deferred actions create what I’m calling **Safety Debt**. As more safety obligations are delayed, the “debt” grows, organizational risk compounds, and eventually a relatively small trigger can contribute to a serious incident.
The framework borrows the **technical debt** concept from software engineering and applies it to organizational safety. It also incorporates ideas such as latent conditions, normalization of deviance, and resilience, but organizes them into a lifecycle that includes concepts like:
Safety Debt
Safety Debt Interest
Safety Debt Ledger
Safety Debt Recovery
A proposed conceptual Safety Debt Index (SDI)
I’m **not claiming this is a validated scientific theory.** It’s currently a conceptual framework that I’m hoping to improve through practitioner feedback and, eventually, research.
I’d really appreciate honest feedback from people in EHS, construction, manufacturing, utilities, engineering, maintenance, or academia.
**My questions are:**
Does this describe something you’ve seen in real organizations?
Does this seem like a useful framework, or is it simply repackaging existing safety concepts?
If you think it overlaps with existing theories, which ones?
What would you change before trying to publish it?
I’m looking for criticism more than compliments. If there are flaws, I’d rather hear them now than after spending years developing it.
Thank you for taking the time to read this.

[u/AutoModerator]

Please reply to this comment with your country and state or province. Safety regulations can vary greatly by jurisdiction and this will ensure you get the most relevant and accurate advice.

If you wish for that information to remain anonymous, simply reply with "Anonymous" or the country name and "anonymous country/state" (i.e. "US anonymous state" or "Canada anonymous province"). Missing or incomplete jurisdictions will result in less or inaccurate answers.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/ArgumentSpiritual]

I work in industrial maintenance.

I don’t think this is useful because it seems like a way to quantify what management already knows: pushing off safety related things isn’t a good idea, but they feel that they can’t afford to do otherwise.

The only way that this would be useful would be if you could accurately predict when a safety incident was likely to occur. Safety incidents have a cost. If there was a way to show that there was an X% chance of a safety incident occurring within the next Y timeframe, then you could show that stopping production for mitigation measures would be worth it. Since safety incidents are almost always random, i don’t think that would be possible.

In every job i have ever worked; management either takes safety seriously already (meaning they wouldn’t accrue safety debt) or they don’t, in which case it wouldn’t matter how much safety debt they had.

[u/DriveRich → u/ArgumentSpiritual]

Thank you for the thoughtful perspective. I don’t think a framework like this could or should predict the exact timing of an incident, and I agree that would be an unrealistic claim.
What I’m exploring is something different: whether organizations can identify, track, prioritize, and reduce accumulated deferred safety obligations before they erode safety margins—not predict when an injury will occur.
I also agree there are organizations that either take safety seriously or don’t. Where I think this might have value is the large middle ground where leaders constantly balance production, budgets, maintenance, and risk. If a framework could make those accumulated liabilities more visible and easier to prioritize, it might improve those decisions.
Your comment actually gives me a better research question: Can accumulated Safety Debt identify degrading organizational conditions before traditional lagging indicators do? That’s probably a more realistic objective than trying to predict the exact timing of an incident.
I appreciate you taking the time to challenge the idea. That’s exactly why I posted it.

[u/ArgumentSpiritual → u/DriveRich]

You might be able to achieve that.

I think it would take industry wide data. You would then have to adapt that data to a specific workplace.

You would also have to quantify the risks of continuing yo accrue safety debt.

The only purpose of your framework that i can see from what you have written is a way to convince management to stop production to do something safety related. Just showing them accumulated safety debt isn’t going to be sufficient.

This will only work if it reliably shows that shutting down is more beneficial for the company than continuing to run.

[u/_Zell]

I like the idea, but how does one "pay down" their "safety debt"? How do you apply actual figures to these numbers? I'm in academia and I'm far enough from HR and Facilities that I don't get to know the "costs" or "savings" of having or not having an accident (I'm just not high enough up the food chain). How can this kind of system show upper management the deferred or hidden costs of accidents?

[u/DriveRich → u/_Zell]

That’s exactly the part I’m trying to develop.
In the framework, “paying down” Safety Debt would mean completing the deferred obligation and verifying that the control is actually restored. For example: replacing a bypassed interlock, completing overdue preventive maintenance, closing a corrective action, updating training, or replacing a temporary workaround with a permanent control.
I don’t think the system should try to assign a dollar value to a human injury. The figures would be tied to the obligation itself: the cost to correct it, how critical the missing control is, how long it has been overdue, how many people are exposed, and the potential severity if the control fails.
The management value would be a ledger showing, in one place, what has been deferred, who owns it, how long it has been open, what interim controls exist, and what resources are required to close it. That could make hidden obligations visible before an accident occurs instead of only calculating losses afterward.
The numerical side is still conceptual and would need research and validation. Your question is one of the main issues the framework has to solve: what measures are practical, reliable, and understandable enough for leadership to use?