Athena Forms™Athena Forms™ All resources
A field guide

Counting the saves, not just the misses.

The times your safety worked are your best data. Here is how to turn "nothing happened" into proof your controls are real.

The science first

"Nothing happened" is not nothing

A worker breaks into a high-pressure line. It was locked out, bled to zero, and checked at the gauge first. Nothing happens. No injury, no incident, nothing to file. By every traditional count, it was a non-event.

But it was not nothing. It was your isolation procedure being put to the test by real, lethal energy, and passing. That is the single best piece of evidence you have that the control is real and your people use it. Most safety programs throw that evidence away, because they only count what goes wrong.

An injury log can only tell you where you got hurt

It cannot tell you your lockout works. The only way to know a control is real is to catch it holding, on purpose, while the danger is live.

What most programs count

The misses

Injuries, incidents, days lost. All of it is a record of the times your safety did NOT work. Useful, but it only ever grows when someone is already hurt, and it is silent about every control that is quietly doing its job.

What you should also count

The saves

The times lethal energy was present, a worker was exposed, and a verified control stood in the way and held. Each one is proof a safeguard is real, maintained, and used. This is the data that grows when things go right.

What a save actually is

A save is not "we had a good day." It is the same three-question read landing a specific way: real energy was present, a worker was exposed, and this time the control held. When all three are true, you have a Safety held, what the new SIF standard calls an observed safeguard success. Flip the last part, the control was missing or never checked, and the very same scene becomes a Serious potential, a close call you got lucky on.

The same event, one variable. A worker enters a confined space. If the atmosphere was tested and continuously monitored, that is a save worth recording. If the test was skipped or the monitor was never on, it is a serious close call that only luck kept from being a fatality. The difference is one thing: was the control actually there and verified. That is the thing worth measuring.

A tick-box lies. A sentence does not.

Here is the trap. If you ask a worker to tick "control in place: yes," you learn nothing, and you teach them to tick. A real verification is a short, plain sentence about what they checked and how they knew it held: "Verified the line was isolated and bled to zero by checking the gauge at the bleed valve before I broke it." That sentence is evidence. It names the energy, the control, and the check. A box with no words is just an empty box, and an empty box cannot prove anything.

This is the difference between assuming a control held and verifying it did. The standard is explicit about it: a safeguard only counts if it can be verified through observation, and training or coaching by itself is not a safeguard at all.

From saves to a number you can trust

Once you are catching saves with real evidence, two numbers fall out, and they are numbers an injury rate can never give you.

Capacity
How many times a control was challenged by real energy and held. "Our fall-arrest system was put to the test 62 times last quarter."
Reliability
Held, divided by held plus failed, for each control. 500 held and 0 failed is a control you can mathematically trust.

Now you can answer the question every safety leader actually loses sleep over: not "how many people got hurt," but "are the things I am counting on to keep them alive actually working." That is a forward-looking number. It improves before anyone is hurt, not after.

How Athena reads your saves

The hard part is that saves are buried in the same reports as everything else, and nobody has time to re-read thousands of them looking for the ones where a control quietly held. Athena does that. It reads the observations and reports your team already writes, finds the saves, the times real energy was present and a verified control held, and counts them per control, with the exact sentence from the report that proves it. So a person can always check the call.

Most safety software only counts what went wrong. Athena also shows you what went right. Not as a feel-good number, but as hard evidence: the controls that were tested by real danger and held, how often, and where one is starting to slip. That is the difference between hoping your safeguards work and knowing they do.

This is where the standard is going

Modern serious-injury prevention asks for exactly this. The ideal safety condition is workers protected by verified safeguards even when human error happens, and because those successes are observable, they can be found and analyzed. Counting the saves is not a nice extra. It is becoming the definition of a mature safety program.

Book a demo Start with the energy wheel How serious-injury risk is measured
The short version An injury log tells you where you got hurt. It cannot tell you your controls work. A save is the times real, lethal energy was present and a verified control held anyway, and it is the best proof you have that your safeguards are real. Athena finds the saves in the reports your team already writes, and counts them.