Method and management system

When does a control count as a barrier?

The measured validity test asks three things: is the barrier <strong>effective</strong> (can it stop that pathway on its own), <strong>independent</strong> (would it fail together with another barrier), and <strong>auditable</strong> (can it be shown to work). A box that fails one of the three is removed or flagged as a weak control. This is exactly where the value of a bowtie appears: what matters is not how many boxes are on the page, but how many pass the test.

Three tests

  1. Effective — the barrier must be able to stop that pathway on its own. "It helps a bit" is not a barrier.
  2. Independent — the same failure, the same person or the same supply must not take two barriers down together.
  3. Auditable — its working must be demonstrable through a record, a test or an observation.

Boxes that typically fail

Written asFails on
"Work carefully"Auditability — it cannot be measured
"There is a procedure"Effectiveness — a document alone stops no pathway
Two interlocks fed from one panelIndependence — one supply takes both down
"An experienced operator"Auditability — person dependent, no record
Annual trainingEffectiveness — it raises awareness, it does not stop the pathway

Weak controls need not be deleted

Controls that fail the test are often useful; they are simply not barriers. Leaving them with a separate mark is more honest than deleting them: "we do something here, but there is nothing to rely on".

What the test really produces

In practice the test reduces the barrier count; a third of the boxes on a crowded diagram fall away. That is a gain, not a loss: what remains is what can actually be relied on, and maintenance, testing and budget go there.

Manage this in Optifora

Optifora is not a single program but a compliance platform assembled from modules. The catalogue states which module is ready today and which is on the roadmap.

See what Optifora is