New Emergency Planning Coordinator in 60 Days: Build Response Readiness Before the Next Alarm

A new emergency planning coordinator often inherits a thick plan, a calendar of drills, and a long list of actions that nobody can fully explain. The pressure is to update the document quickly. That is usually the wrong first move.

Response readiness depends on decisions that must work during confusion, noise, missing information, and competing operational priorities. A coordinator who spends the first 60 days only editing procedures may produce a cleaner file while leaving the real response unchanged.

What does the role need to establish before changing the plan?

The emergency planning coordinator should begin by defining the operating boundary of the role. The coordinator maintains the response architecture, tests its assumptions, and escalates barriers, but the plant manager, site leader, and emergency team leaders still own the decisions and resources that protect people.

That distinction prevents a common failure. When the coordinator becomes the person who is expected to solve every access problem, purchase every resource, and contact every external agency, operational leaders can treat readiness as someone else’s project. The system then depends on one specialist instead of building distributed capability.

Start with a one-page map that names the credible scenarios, the first decision-maker, the escalation route, the response team, the external interface, and the condition that ends the emergency phase. OSHA 29 CFR 1910.38 requires an emergency action plan for covered general-industry situations, and the coordinator’s work is to make the planned actions usable at the point of need.

Andreza Araujo’s safety leadership work consistently connects technical control with leadership behavior. Across more than 250 cultural transformation projects, the practical question is not whether a rule exists, but whether the organization has made the important decision easy to recognize and difficult to ignore.

How should the first 10 days reveal the real response condition?

Use the first 10 days to build an evidence-based baseline. Read the emergency plan, previous exercise reports, inspection findings, incident reviews, contractor agreements, maintenance records, and training records, but do not treat any document as proof that the response works.

Walk the site with the people who would act during an emergency. Ask them where they would go, whom they would call, what information they would need, and what they would do if the normal route were blocked. Their answers reveal whether the plan has reached the work or remains a management artifact.

Check the physical conditions that a response depends on, including alarm audibility, emergency lighting, muster-point access, radio coverage, rescue equipment, isolation points, first-aid resources, spill controls, and current contact lists. A listed resource that cannot be reached, opened, powered, or used is not a reliable barrier.

Record the gap without inflating it. Separate a missing document from a missing capability, because the second condition requires an owner and a work change. If a communication channel fails in a noisy area, rewriting the contact list will not solve the problem.

What should the coordinator verify in days 11 to 20?

Days 11 to 20 should turn the baseline into a control-and-ownership register. Each gap needs a plain description, an accountable operational owner, an interim control when exposure is immediate, a target date, and a verification method.

Do not assign every action to EHS. Operations owns staffing, access, work sequencing, production decisions, and the availability of competent people. Maintenance owns equipment reliability. Security may own access control. Human resources may support contact and welfare arrangements. The coordinator keeps the interfaces visible so that a gap cannot disappear between functions.

Include the handoffs that occur before, during, and after the emergency. A shift change, contractor transfer, or command transition can create a dangerous pause when the incoming person does not know which areas are isolated, which people are unaccounted for, or which controls are temporary. The four risk-transfer states in a shift handover provide a useful way to examine that boundary.

Also define the evidence boundary. The response team must protect life first, but the organization should know when photographs, access logs, equipment status, witness details, and scene controls need to be preserved. A clear incident evidence handoff avoids the later argument that important information was lost during the first response.

How can readiness be tested without creating a theatre exercise?

Days 21 to 30 are the right time to choose an exercise that matches the gap. A tabletop discussion can test recognition and decisions. A functional exercise can test communications, coordination, and resource movement. A full-scale exercise can test the interaction of people, equipment, access, and external support.

The correct question is not which exercise looks most impressive. It is which exercise can test the uncertain part of the response without creating avoidable exposure. The existing comparison of tabletop, functional, and full-scale emergency exercises helps the coordinator match the method to the decision that needs evidence.

Write the scenario so that participants must make choices. Remove one expected resource, introduce a delayed message, change the access route, or create a conflicting operational demand, provided the exercise remains controlled and authorized. If every participant receives the answer in advance, the exercise measures memory rather than readiness.

Observe time to recognize the trigger, clarity of the first message, authority to stop affected work, quality of the accountability process, and the speed at which barriers are escalated. These observations show whether the organization can act when the script stops being convenient.

Which decisions belong in the days 31 to 45 transition?

Days 31 to 45 should move the coordinator from diagnosis into controlled improvement. Select the few changes that remove the largest response dependency. A revised alarm zone, a better radio channel, a staffed command point, a verified rescue route, or a clear contractor interface may improve readiness more than a complete rewrite of the plan.

Use a decision log to show why each change was prioritized. The log should state the hazard or failure condition, the decision owner, the evidence, the temporary protection, and the date for checking effectiveness. This makes resource discussions more precise because leaders can see what remains exposed and why the proposed action matters.

Connect emergency planning to control of work. When an emergency affects a process, a restart, isolation, or temporary repair, the organization needs a disciplined boundary between response urgency and safe authorization. The control-of-work decision gates are especially relevant when production pressure begins to compete with response discipline.

Do not promise that a new checklist will eliminate uncertainty. James Reason’s work on latent failures shows why weak conditions can remain hidden until several defenses align badly. The coordinator’s value is to expose those conditions early and make them visible to the people who can change them.

What should leaders see by day 46?

By day 46, leaders should be able to see response readiness without asking for a long presentation. Show the current scenario map, the open high-consequence gaps, the accountable owners, the overdue decisions, the exercise findings, and the next verification date.

Use evidence that describes capability rather than activity. The number of people who attended a drill is an activity measure. The percentage of critical roles that communicated their decision, reached the correct location, and escalated a barrier within the agreed window is closer to a readiness measure, provided the method and denominator are defined.

Two dates matter in this review. ISO 45001 was published in 2018, and its management-system logic expects organizations to plan, implement, evaluate, and improve processes rather than treat a procedure as a finished control. OSHA’s 29 CFR 1910.38 remains a named regulatory anchor for emergency action planning in covered general-industry settings. Neither reference removes the need for site-specific verification.

Andreza’s experience at multinational scale reinforces the same point. Her work across more than 30 countries required local ownership because a central plan cannot predict every access route, language need, contractor interface, or emergency-service limitation.

How should the final 14 days convert findings into ownership?

Days 47 to 60 should close the transition, not close every action. The coordinator should confirm that each high-priority gap has a named owner, an interim control where needed, a funding or resource path, and a verification date. If an action is not yet complete, its remaining exposure must be visible.

Run a short re-test on the most important changes. Recheck the alarm, the communication path, the command location, the emergency equipment, the accountability process, and the handoff to recovery. A re-test is valuable because it shows whether the change survived contact with the site rather than merely surviving a meeting.

Build a monthly readiness rhythm that includes one field verification, one open-decision review, one exercise or scenario discussion, and one check of external interfaces. Keep the rhythm proportionate. A small site may need a concise monthly review, while a complex operation may need separate process, medical, fire, security, and contractor readiness reviews.

The coordinator should leave the first 60 days with a system that can challenge itself. A response plan is stronger when workers can identify a weak barrier, supervisors can escalate without delay, and leaders can fund the change before the next alarm tests it.

What should a new emergency planning coordinator do next?

A new emergency planning coordinator should spend the first 60 days establishing ownership, verifying field capability, testing decisions, and exposing the gaps that documents conceal. The role is not administrative support for a plan. It is a system of assurance that connects emergency decisions to the work conditions that make those decisions possible.

At PepsiCo, Andreza Araujo led work associated with a 50% reduction in accident ratio in six months. That result is not an emergency-readiness benchmark or a promise for another site. It demonstrates the value of a defined time horizon, visible ownership, and verification that operating decisions changed.

When leaders need to develop this capability, Andreza Araujo brings a practical approach grounded in engineering, creativity, and care. The standard is simple to state, although difficult to fake: the response must work for the people who need it before the organization needs to prove that it works.