New Near-Miss Program Owner in 75 Days: Turn Early Warnings Into Control Decisions

A near-miss program often starts with good intentions and ends as a monthly count that nobody trusts. The new program owner has 75 days to turn early warnings into decisions that change exposure, controls, and follow-up.

This role is not a reporting-secretary position. It sits between frontline voice, incident investigation, operations, and leadership, which means the first quarter must establish a reliable route from a concern in the field to a verified change in work.

What a near-miss program owner needs to understand before starting

A near miss is useful only when it reveals a credible path to harm and produces a decision about that path. A high volume of reports can indicate trust, but it can also indicate a campaign, duplicate entries, or a low threshold for recording trivial events. A low volume can reflect stable work, but it can also show that workers see no benefit in speaking up.

James Reason's work on latent failures provides the right starting point. The visible event is only one layer of the risk story. The program owner must examine the conditions that made the exposure possible, including work design, supervision, maintenance, planning, and the quality of critical controls.

Andreza Araujo's Safety Culture: From Theory to Practice makes a related point through the gap between declared culture and daily practice. A near-miss system becomes credible when the organization can show that a report changes a decision, not when it can display a larger number of reports.

Days 1 to 15: define the signal before counting it

Start by writing a one-page operating definition. State what qualifies as a near miss, what qualifies as a high-potential near miss, who can submit a report, and which events require immediate escalation. Keep the language concrete enough for a supervisor to apply during a shift.

Review the last three months of records with an operations partner. Look for duplicate categories, vague descriptions, closed actions without evidence, and reports that were classified as low consequence even though a critical control was absent. Do not rewrite history to make the baseline look cleaner. Mark uncertainty where the original record cannot support a confident conclusion.

The first useful measure is not report volume. It is the proportion of reports that contain a clear exposure, an accountable decision owner, and a verification date. That measure tells you whether the system can carry information from the field into control management.

Days 16 to 30: build a triage route that supervisors can use

Create a short triage conversation for the first reviewer. The reviewer should ask what could have happened, which barrier was expected to prevent it, what actually happened, and what must change before the same work is repeated. Those questions are more useful than asking the reporter to assign a technical root cause.

Set three routes. Immediate escalation should cover credible fatal or permanent-harm exposure, loss of a critical control, and events that could repeat before the next shift. Structured review should cover meaningful exposure that needs a decision owner and a verification plan. Local correction should cover a bounded issue that the supervisor can resolve and confirm without a wider investigation.

During her career across multinational operations, Andreza Araujo has emphasized that safety leadership becomes visible through decisions and follow-through. Your triage route should therefore show who receives the signal, who decides, and how the reporter learns what happened next.

Days 31 to 45: make the review conversation evidence-based

Run a weekly review with one operations leader, one frontline supervisor, and the person responsible for the affected control. Keep the group small enough to discuss the work as it was performed, including time pressure, access, tools, interfaces, and the information available at the moment.

Use a simple evidence sequence. Describe the task, identify the exposure, locate the expected control, compare the control with its real condition, and decide what will be changed. If the review ends with retraining alone, ask what design or supervision feature will make the safer action easier to perform under pressure.

A near miss should not become a performance trial for the person who reported it. When the reporter expects blame, the program receives polished descriptions instead of useful evidence. That is why the owner must protect factual detail while still distinguishing an understandable mistake from a conscious breach of a known boundary.

Days 46 to 60: connect reports to critical controls

Map recurring near-miss themes to the controls that are supposed to prevent serious harm. For a hazardous-energy exposure, the map might include isolation planning, lock verification, boundary control, and supervisor confirmation. For vehicle interaction, it might include separation, visibility, route design, and pedestrian compliance.

Do not create a new control register if the organization already has one. Add a near-miss evidence field to the existing register, then review whether the control was present, suitable, used, and verified. This connection helps leaders see when repeated reports point to a weak barrier rather than a weak attitude.

Use a single dashboard view for open decisions, overdue verification, repeat exposures, and high-potential events. Avoid presenting report count without context, because volume alone can reward activity while hiding unresolved risk.

Days 61 to 75: prove that the system changes work

Select two or three recurring exposures and follow each one from report to field verification. The final review should show the original concern, the decision taken, the person accountable, the date of implementation, and the evidence that the control works where the task occurs.

Ask the reporter or a peer who performs the task whether the change is visible and usable. A procedure can be revised while the work remains unchanged. Verification must therefore examine the point of exposure, not only the document repository.

At day 75, publish a short operating review. Explain what the system can now see, which decisions remain unresolved, where reporting quality is weak, and what leadership must decide next. Andreza Araujo's experience leading safety transformation, including a 50% reduction in accident ratio over six months at PepsiCo South America, reinforces the value of a defined cadence that links leadership attention with operating action. That result is not a promise for every site. It is a reminder that improvement requires disciplined execution over time.

Common mistakes that weaken the program

Counting before defining. A dashboard cannot repair an ambiguous signal. Write the operating definition before setting a target.

Sending every report to a large committee. Central review can create delay and discourage reporting. Use escalation criteria so the response matches the exposure.

Closing actions when the document changes. A revised procedure is not proof of control. Require field verification at the task location.

Rewarding the most reports. Incentives can produce quantity, duplicate entries, or safe-looking stories. Recognize useful evidence and completed decisions instead.

Turning the reporter into the investigation. The report is an entry point into the system, not an invitation to assign personal blame. Examine the work conditions and the control path.

Resources to deepen the role

Begin with Safety Culture: From Theory to Practice for the relationship between maturity and daily behavior. Use Make The Difference: Be a Leader in Health & Safety when the role requires difficult conversations with supervisors and operations leaders. Andreza Araujo also develops practical safety leadership through Escola da Seguran�a, where the emphasis remains on engineering, creativity, and care rather than on reporting theater.

For a second perspective, revisit James Reason's treatment of latent failures and organizational accidents. The goal is not to turn every near miss into a long investigation. The goal is to make the important signals travel far enough to change the conditions that produced them.

The decision at the end of the first quarter

After 75 days, the near-miss program owner should be able to answer one question with evidence: which early warnings changed a control, and how was that change verified in the work? If the answer is unclear, the system is still collecting stories rather than managing risk.

Safety is about coming home, and a credible near-miss program gives leaders a practical way to act before harm makes the lesson irreversible. For more perspective on safety leadership and culture, visit Headline Podcast.