How a 180-Day Safety Plan Delivered a 50% Accident-Ratio Reduction

A safety plan can look impressive before it changes a single decision. It may have a launch meeting, a dashboard, and commitments that senior leaders can repeat, yet the worksite still depends on unclear handoffs and weak controls.

The documented PepsiCo South America Foods case offers a sharper test. During a 180-day plan led by Andreza Araujo, the operation achieved a 50% reduction in accident ratio within six months. That result matters because it connects a defined period to a measured outcome, but the case is more useful when it is read as an execution lesson rather than a ready-made program.

Initial scenario: attention had to become control

Large operations rarely lack safety activity. They often have procedures, training, inspections, meetings, and targets operating at the same time. The harder problem appears when those activities do not converge on the decisions that expose people to harm.

A safety plan needs an operating question narrower than “How do we improve safety?” Leaders need to ask which exposures require a different decision, who has authority to make it, and how the organization will know that the control is working in the field.

A completed activity is not the same as a functioning barrier. A training record can show attendance, while field verification shows whether the worker can apply the control when production pressure, changing conditions, or a contractor handoff interrupts the planned sequence.

The decision: use a time-boxed plan with a measurable outcome

The 180-day frame created a practical boundary. It was long enough to move beyond a launch campaign and short enough to force decisions before attention dispersed across annual planning cycles.

Time-boxing does not make a plan effective by itself. It creates a review structure in which leaders can identify the priority, assign responsibility, test the control, and decide whether the evidence justifies continuation. Without those decisions, a six-month calendar becomes another reporting obligation.

The documented outcome gives the case its authority, while the mechanism must still be interpreted carefully. The public record supports the plan, the company context, the period, and the result. It does not authorize an invented chronology of internal steps that has not been disclosed.

Execution: translate the plan into supervisor decisions

Supervisors are where a safety plan meets the work. They decide whether a task is ready, whether a change requires escalation, whether a control can be accepted as usable, and whether a production request needs to wait for a safer arrangement.

A useful plan gives supervisors more than a message. It gives them decisions that can be observed. A supervisor should be able to explain which control is non-negotiable, what evidence confirms it, and what happens when the evidence is missing.

That clarity protects the supervisor from being made responsible for outcomes without being given authority. When the plan names accountability but leaves escalation vague, the operation shifts risk to the person closest to the work without strengthening the control system.

Field verification: test what the paperwork assumes

Field verification is the bridge between intention and operation. It asks whether the control described in a procedure is present, accessible, understood, and maintained under the conditions in which the task actually occurs.

Ask the person performing the work to show the control, explain the failure condition, and identify the next decision if the control cannot be maintained. These questions reveal more than a checklist tick because they test usability and authority together.

James Reason’s work on latent failures helps explain why this matters. An incident can emerge from several ordinary weaknesses that align across design, supervision, communication, and equipment. A plan that only counts completed activities can miss those weaknesses until the outcome appears in the lagging metric.

Measured result: read the 50% reduction with discipline

The 50% reduction in accident ratio within six months is the central measured result of the case. It should be stated plainly, with its source anchor in Andreza Araujo’s documented PepsiCo experience, and without turning it into a guaranteed return on a copied program.

The case does not establish that the same percentage will appear elsewhere, that one metric captures all serious risk, or that the result can be separated from the operating context in which the plan was executed.

Failure pattern: confuse activity with prevention

Safety plans lose force when activity becomes the substitute for control. Teams report meetings held, observations completed, modules assigned, and actions opened, while the underlying exposure remains difficult to manage.

Three traps deserve attention. The first is launching more communication before clarifying the decision that communication is meant to support. The second is assigning corrective action without confirming that the owner has resources and authority. The third is celebrating a favorable accident number before checking whether reporting access, definitions, or workforce composition changed.

These traps are reasons to measure closer to the work. If a leading indicator cannot show whether a control was available, understood, and verified, it may be describing effort rather than prevention.

What another operation should copy, and what it should not

Another operation can copy the discipline of the case without copying its surface form. Start with a defined period, a limited number of priority exposures, named decision owners, and verification points that workers can recognize.

Do not copy the 50% target as a normal planning assumption. A target can focus attention, but it can also distort reporting when leaders treat the number as more important than the evidence. Set a review question around control performance and use accident ratio as one outcome among several.

Andreza Araujo’s broader work across more than 250 cultural transformation projects reinforces the same practical lesson. Improvement becomes credible when people can see which management choice changed, which control became more usable, and how leaders respond when the evidence is inconvenient.

Generalizable lesson: make the next decision visible

The strongest lesson from the PepsiCo case is not that a 180-day plan is a magic duration. A safety plan needs a visible chain from priority to decision, from decision to control, and from control to evidence.

For a plant manager, that chain can be reviewed in a monthly operating meeting. For a shift supervisor, it can be tested before a high-risk task begins. For an EHS leader, it can be audited by asking whether the organization can show what changed at the point of work rather than only what was presented to leadership.

A 50% reduction is a meaningful case result, but the durable value lies in the management discipline behind it. When the next decision is visible, field evidence can challenge the plan before another incident does.

What to apply in your operation

1. Choose one defined six-month review horizon and name the exposures it will address.
2. Assign each priority to an owner who has authority to change the work, not only report on it.
3. Write the control in observable language that a worker and supervisor can test together.
4. Set field verification points that examine usability, understanding, and escalation.
5. Review accident ratio alongside reporting conditions and control evidence.
6. Document what changed, what failed, and which decision will be made next.

The PepsiCo result gives leaders a credible case to study. It does not remove the need for local diagnosis. A safety plan earns its value when the operation can show that attention changed the work before the metric changed.

Headline Podcast examines the leadership decisions behind safer work. Explore Headline Podcast for more conversations and analysis.