Preventive vs. Detective Controls: First Define the Event

Before calling a control preventive or detective, finish the sentence: before or after which event?

An original hypothetical case

A cold-chain distributor requires an authorised release before a truck leaves its loading bay. The unwanted event in this example is dispatch without that authorisation. The case uses no real company, shipment data or food-safety thresholds.

Before dispatch

A gate check compares the shipment with a valid authorised release before departure. If the release is missing, it blocks dispatch. Relative to the event we defined, that is a preventive barrier.

The important design question is what happens when a user overrides it. In this fictional business, management would need a clear authority, a recorded reason and an accountable review rather than an informal instruction to let the truck through.

After dispatch

An end-of-day reconciliation compares all gate departures with authorised releases. An unmatched departure identifies a possible breach that has already happened. Relative to unauthorised dispatch, that is detective.

A report is only the signal. A responsible person still has to investigate, decide what action is possible and escalate it in time. Finding the departure does not, by itself, retrieve the goods or reverse every consequence.

The same check can face two directions

Suppose the reconciliation is completed before customer invoicing. It may detect an earlier dispatch breach while also helping prevent a later billing error. Its classification depends on the event and purpose, not the name of the report.

A clean report can hide missing data

In the fictional case, imagine an unrecorded gate departure. A comparison that uses only captured departures may show no unmatched items. That would not establish that every truck was authorised. A useful design therefore asks how departure records are captured, how sequence gaps are investigated and how the release data is protected.

Timing determines whether detection can help

Daily review is this case's illustrative design, not a recommended frequency for every operation. If an unauthorised shipment needs intervention within minutes, an end-of-day review may arrive too late. Management should define a response window and decide whether the signal can reach someone able to act within it.

Build the mix around the risk

For this distributor, the design discussion combines a before-dispatch barrier, an after-dispatch signal and an assigned response. Neither label establishes effectiveness. Missing records, bypasses or weak follow-up can undermine both.

Practice

Choose one unwanted event in a process you know. Mark its exact point. Add a barrier before it and a signal after it. For each, name the owner, evidence, escalation route and response window. Then ask what could disappear from the data without anyone noticing.

Concept reference: GAO's Green Book explains preventive and detective activities in a US federal context. It is used here as learning guidance, not as an Indonesian requirement.

Beyond the numbers. Inside the business.