Business Continuity Runbook Template for Plant Disruptions

Purpose and scope

This runbook helps plants and cross‑functional teams react, stabilize, and recover production after major disruptions (plant outage, flood, fire, severe weather, major supplier failure, cyber incident, etc.). It is designed to be concise, testable, and rehearsal‑ready so teams can act with clarity under pressure. Keep a printed laminated copy in the control room and ensure digital copies are accessible to incident participants.

When to activate

• Immediate safety threat (injury, fire, hazardous release) — activate now.
• Plant stoppage affecting critical lines or >30% of daily capacity.
• Key supplier failure expected to disrupt deliveries within 48 hours.
• Regulatory event, major quality hold, or cyber‑security incident impacting operations.

Incident activation flow (quick reference)

1. Ensure safety and stop work on affected equipment if needed (Safety Lead).
2. Plant Manager / Shift Lead declares incident and activates the runbook.
3. Incident Commander (IC) appointed and initial 15‑minute briefing held (IC, Plant Manager, Ops Recovery Lead, Maintenance Lead, Supply Chain Lead, Safety, Communications, IT, Customer Liaison).
4. Establish incident channel (phone bridge/Teams/Slack) and set communication cadence (15 min for first hour, then hourly or as needed).
5. Execute immediate response checklist (see below) and document all actions in the incident log.
6. Escalate to site leadership or enterprise crisis team according to thresholds (customer impact, >8 hours downtime, safety/regulatory exposure).

Roles and responsibilities (brief)

• Incident Commander (IC): Owns the incident, convenes briefings, makes prioritization decisions, and communicates status to executive stakeholders.
• Plant Manager: Site authority for resources, safety, and plant operations.
• Operations Recovery Lead: Coordinates production recovery steps, line restarts, staffing and temporary capacity shifts.
• Maintenance Lead: Diagnoses, isolates, and repairs equipment; coordinates external service contractors.
• Supply Chain Lead: Manages suppliers, alternative sourcing, inventory allocations, and customer delivery plans.
• Safety/Environmental Lead: Ensures safe work, regulatory notifications, and permits.
• Communications Lead: Crafts internal and external messages; maintains the communication tree.
• IT/Data Lead: Preserves and recovers digital systems, ensures data capture and integrity.
• Customer Liaison: Notifies affected customers, manages expectations and recovery commitments.

Owner matrix for core recovery steps

Immediate response checklist (0–2 hours)

• Ensure people are safe — implement evacuation or medical if required.
• Isolate affected equipment and lockout/tagout (LOTO) if mechanical/electrical fault.
• Preserve evidence for quality/regulatory investigation (photos, sensors, logs).
• Start an incident log (time, person, actions taken) — store centrally.
• Notify core incident team and start communication bridge.
• Perform quick impact assessment: lines affected, SKUs impacted, raw materials at risk, expected downtime estimate.
• Assign owners for immediate containment, repair triage, and supplier outreach.

Stabilize and recover checklist (2–72 hours)

• Prioritize SKUs for recovery (see prioritized SKU guidance below).
• Identify alternate production options: reroute to other lines, run overtime, shift mixes, contract manufacturers.
• Contact alternate suppliers and confirm lead times, minimums, expedited shipping.
• Plan staged restarts with quality checks at each stage (first‑article, sample inspections).
• Communicate transparent status to customers with realistic delivery windows.
• Track costs and approvals for overtime, repairs, external contractors.

Prioritized SKUs — quick method

Prioritize SKUs by combining business impact and recoverability:

1. Customer criticality (contract penalties, key accounts, next‑day commitments).
2. Revenue contribution (top % of revenue).
3. Inventory buffer (days of finished goods or raw material on hand).
4. Alternate routability (can it be made on another line/plant quickly?).

Use a simple RRI score (Risk = Customer criticality × Revenue × Inability to reroute). Create a short table listing top 10 SKUs to restore first and owners responsible.

Alternative production & supplier options (practical examples)

• Internal: shift reallocation, convert low‑priority lines, temporary overtime, split production across shifts.
• External: activate pre‑qualified contract manufacturers; use regional plants in the enterprise; leverage trusted co‑packers.
• Supply: use alternate approved suppliers, authorized distributors, or expedited air freight for critical components.
• Customer: offer partial shipments, temporary product substitutions, or shipment date extensions with discounts where appropriate.

Communication templates (copy, personalize, send)

Internal alert (short):
Subject: [INCIDENT] {Plant} — {Short description} — {Date/Time}
Body: We have declared an incident affecting {area/line}. Safety is our priority — all are to follow instructions from supervisors. IC: {Name}. Incident channel: {bridge/room}. Next update at {time}.

Customer notification (short):
Subject: Production delay notice — {SKU} — {Plant}
Body: We are experiencing a disruption at {Plant}. Impact: expected delay for {SKU(s)}. We are activating recovery plans and expect to provide a firm update by {time}. Contact: {Customer Liaison name/email}.

Supplier request (sample):
Subject: Urgent supply request — {Part} — {Plant}
Body: We need confirmation of capacity for expedited supply of {part/qty} by {date}. Please confirm lead time and earliest ship date. Contact: {Supply Chain Lead}.

Incident log & documentation

Maintain an incident log with timestamped entries: who did what, decisions made, costs authorized, restoration steps, quality hold actions, and customer communications. Keep photos, sensor data, and test results attached. This log supports regulatory reporting and the after‑action review.

Testing, drills and cadence

• Tabletop drill: quarterly for core incident scenarios with cross‑functional participation.
• Full scale exercise: annually, including supplier participation when practical.
• Validate contact tree and supplier alternatives every 6 months.
• After each real incident, hold an after‑action review within 7 days and publish a short improvement plan.

After‑action review checklist

• What happened (timeline)?
• What went well / what failed?
• Root cause hypotheses and immediate fixes.
• Permanent corrective actions, owners, and due dates.
• Update the runbook and supplier lists based on lessons learned.

Quick attachments & resources (placeholders)

• Contact tree: emergency numbers for internal leads, key suppliers, service contractors, insurance, and local authorities.
• Pre‑qualified alternate suppliers & contract manufacturers list.
• Line start/stop checklists and first‑article test forms.
• LOTO and safety checklists.

How to keep this runbook useful

Designate an owner (Business Continuity Coordinator) to update this runbook after drills or real incidents, verify contacts quarterly, and maintain alternate supplier agreements. Treat the runbook as a living tool — short, actionable, and rehearsed.