Business Continuity & Incident Response Playbook — Restaurant Template

Purpose and how to use this playbook

This playbook helps your team move quickly and consistently when disruptions threaten service, safety, or revenue. Use it as a living document: copy it for your location, fill in names and phone numbers, run tabletop drills, and convert the checklists into the platform's interactive incident form so every response is recorded.

Scope

Scenarios covered: power outage, supplier failure, food-safety incident (contamination/recall), mass staff absence (call-offs), and IT/POS outage. Each scenario includes: a quick triage checklist, immediate actions, communications templates (staff and guests), an owner/escalation path, and recovery timeline milestones.

Before an incident: preparation checklist

• Assign an Incident Commander (IC) and alternates with clear authority to make operational decisions.
• Create and publish a staff contact list and call tree (names, roles, phone, SMS, Slack/email).
• Maintain current supplier backup options and minimum stock lists for key ingredients.
• Keep emergency supplies onsite (battery lights, credit-card imprint tools, printed menus, basic non-perishable backup ingredients).
• Train staff on basic incident roles and run at least one tabletop drill per quarter.
• Ensure the incident log template is available (digital or printed) and that staff know where to file completed logs.

Core roles & responsibilities

• Incident Commander (IC): leads the response, makes go/no-go decisions, communicates with ownership/head office, and signs off on recovery.
• Operations Lead (Kitchen/Food): manages food safety, menu changes, portioning, and kitchen workflow adjustments.
• Front-of-House Lead: manages guests, communicates wait-times, issues refunds/comp comps per preapproved policy.
• Communications Lead: crafts and sends staff messages, guest-facing notices, and social media/online messages (if required).
• Facilities/IT Support: engages vendors, manages technical fixes, and documents outages and work orders.
• Scribe / Incident Logger: records times, decisions, actions, and messages in the incident log for post-incident review.

Incident log (template fields)

Make sure every incident entry includes these fields:

1. Incident ID
2. Date/time reported
3. Reported by (name & contact)
4. Location
5. Incident type
6. Severity (1–5)
7. Immediate actions taken (who did what, time)
8. Communications sent (audience, channel, time, copy)
9. Owner/escalation (names & times)
10. Time service resumed / recovery time
11. Estimated financial/guest impact
12. Post-incident notes and lessons learned

Recovery timeline template (copy and adapt)

Use these milestone buckets to coordinate actions and set expectations.

• 0–15 minutes (Triage): Confirm safety, assign IC and scribe, stop risky activity, notify on-site staff, secure guests.
• 15–60 minutes (Stabilize): Execute immediate mitigations (switch to generators, pull affected menu items, call backup supplier), notify customers if there will be a delay/closure.
• 1–4 hours (Recover): Restore partial operations where safe, communicate updated ETA for full service, continue log and escalate vendor support as needed.
• 24–72 hours (Restore & Review): Complete full restoration, reconcile sales/inventory impacts, begin post-incident review and corrective actions.

Scenario response checklists

Power outage

Quick triage:

• Confirm outage scope (building, neighborhood, internal breaker?).
• Safety first: ensure hot-holding and cold-holding temperatures; discard food outside safe ranges.
• Turn off sensitive equipment to avoid damage when power returns.

Immediate actions:

1. IC calls landlord/electric utility and documents expected restoration time.
2. Facilities Lead switches to generator if available and safe to do so.
3. Operations Lead discards perishable items above safe temperature and documents quantities.
4. Front-of-House Lead notifies guests of delays and implements reduced menu if needed.

Guest message (short):

We’re experiencing a temporary power outage. For safety we’re pausing full service while we confirm food safety and equipment status. We expect to update you in [ETA]. Thank you for your patience — ask the host about complimentary options if you’re waiting.

Supplier failure (ingredient unavailable or late)

Triage questions: Can we substitute safely? Is there a food-safety risk? How long until supplier fixes it?

1. Purchasing lead contacts primary supplier and documented backups; request ETA and partial shipments.
2. Menu/Operations Lead identifies substitute ingredients or temporary menu changes and updates recipe cards.
3. Communications Lead informs staff and updates POS/menu descriptions to avoid inaccurate orders.

Decision guide (simple):

1. If safe substitute exists and cost/quality acceptable → implement substitute and note change in POS.
2. If no safe substitute and critical to dish → mark item unavailable and inform guests/staff.
3. If supplier cannot deliver within critical window → escalate to regional purchasing manager and consider alternate suppliers or temporary menu.

Food-safety incident (contamination, suspected foodborne illness, recall)

Immediate priorities: protect guests, preserve evidence, isolate suspect product, and notify health authorities when required.

1. Stop serving suspect item(s). Tag and secure all related inventory; photograph labels and lot numbers.
2. Collect guest reports and medical info (if any) and advise them to seek medical attention; provide contact details to public health when required.
3. Notify Health Department and insurer per local rules; follow legal reporting requirements.
4. Communications: be factual, empathetic, and avoid speculation. Use pre-approved template (below) and coordinate with legal if available.
5. Begin internal traceback with supplier, lot numbers, and invoices.

Guest message (sensitive):

We are investigating a reported illness potentially connected with our [menu item]. We take this very seriously. We’ve paused serving the item, are cooperating with public health authorities, and will contact affected guests with updates. Please contact us at [phone/email] if you were affected.

Mass staff absence (call-offs, transport strike)

Quick triage and stabilizers:

1. Operations Lead and IC assess coverage: which roles are missing and which positions are mission-critical.
2. Call tree: IC calls scheduled staff and trained cross-cover staff; offer agreed-upon emergency pay/incentive where policy allows.
3. Prioritize service: move to limited hours or limited menu, reduce floor capacity, or temporarily suspend reservations.

Guest notice (when limiting service):

Due to unexpected staffing shortages, we are operating on a reduced menu and may have longer wait times. We’re sorry for the inconvenience and appreciate your understanding.

IT / POS outage

Protect revenue and guest experience:

1. Switch to offline operations: paper tickets, printed menus, manual payment receipts, and pre-printed gift card/manual credit-card imprint if needed.
2. Notify payment processor and IT vendor; document error codes and times.
3. Communicate to guests (short) and post notice at entrance/hosts station.

Guest message (short):

We’re experiencing a temporary card processing issue. We accept cash and can take cards manually. Thank you for your patience.

Escalation matrix & approvals

Define thresholds that move incidents up the chain: e.g., any food-safety incident involving hospitalization → immediate notification to owner/regional manager and legal; outage expected >2 hours → owner notified; estimated revenue loss > [$X] or more than N tables impacted → escalate.

Post-incident: review & prevention

1. Hold a debrief within 48–72 hours with IC, ops, FOH lead, communications, procurement, and scribe to review timeline, costs, customer impact, and root causes.
2. Create corrective action items with owners and deadlines (e.g., update supplier backup list, revise SOPs, schedule equipment maintenance, retrain staff).
3. Document lessons learned in the central knowledge store and update this playbook where relevant.
4. Run a follow-up drill within 90 days to validate changes.

Templates you can copy

Staff alert (SMS / Slack)

[Restaurante Name] — Incident Alert: [brief description]. Please report to [location] immediately. Contact IC: [name/phone]. Do not share details externally until cleared. — Management

Guest notification (social & website)

We are currently experiencing [brief incident]. For guest safety, we are [action: pausing service / limited menu / temporarily closed]. We will post updates here and at the door. Thank you for your patience. — [Restaurant Name]

Adapting this playbook for your site

Make these practical edits before an incident happens:

• Fill in names and contact numbers for each role and alternate.
• Set thresholds for escalation and the monetary value that triggers owner notification.
• Pre-authorize certain customer remedies (e.g., refunds, comps) so staff can act without delay.
• Identify and agree on acceptable menu substitutions and price/portion changes.

How to make this playbook interactive (recommended)

To improve execution and record-keeping: convert the incident log and scenario checklists into the platform's interactive form so every incident submission is saved with timestamps, owners, and fielded data for later analytics. That enables cross-location dashboards, trend detection (e.g., recurring supplier failures), and searchable incident history.

Final notes

This playbook emphasizes safety, clear roles, swift communication, and learning. Keep it visible, practiced, and updated. Small, practiced responses reduce stress, protect guests, and limit financial loss.