Flood Incident Playbook for Multi-Site Teams: 24 Hours Before, During, and After a Warning

TL;DR

• Build a single chain of command and per-site owners before you need them; flood warnings can have short lead times, so speed comes from preparation. [1]
• Treat early signals (official alerts, outlooks, rising levels, severe weather) as your trigger to pre-activate site actions and comms, even if flooding is only “possible”. [1][3][7]
• Run a simple “ops room” rhythm during warnings: one source of truth, time-stamped decisions, and clear instructions to sites, suppliers and customers. [10][12][16]
• Plan for gaps: some flood types can happen fast and may not have advance warnings (nation-dependent), so your plan must not rely on a single channel. [2][7]
• Prioritise life safety and utility isolation; follow emergency services instructions and avoid floodwater. [1][12]
• In recovery, control re-entry, document damage, and manage health risks (PPE, electrical safety, contamination) before restarting operations. [5][6][16]

Why multi-site teams need a flood incident playbook

Multi-site operations don’t fail during floods because teams “don’t care”. They fail because work is distributed, decision-making is unclear, and warning lead times can be short.

A solid playbook makes three things true across your whole portfolio:

1. Every site knows who is in charge (and who can make which call)
   Flood response collapses when site teams wait for head office and head office waits for “more certainty”. A playbook defines escalation, permissions (e.g., shutting down operations), and a minimum information pack per site. [4][13]

2. Your response is consistent, even when information isn’t
   Flood warnings are typically issued for defined areas, and being inside an area does not automatically mean a specific building will flood. Portfolio teams need a standard way to convert “area warning” into “site action”. [19]

3. You can act at speed without improvising
   In England, the Environment Agency “usually” issues flood alerts 2–12 hours before flooding and flood warnings 30 minutes–2 hours before flooding. Even if your organisation gets more notice sometimes, you should design for tight windows. [1]

This is also business continuity flooding in practice: protecting people, preventing avoidable damage, and keeping critical services running or recovering quickly. Government business guidance explicitly recommends having a flood plan, checking flood insurance and business interruption cover, ensuring prevention products work, including impacts on staff in H&S assessments, and agreeing flood contingency plans with suppliers and customers. [4]

UK warning context: what changes at each stage

Research summary (triangulated from UK sources)

The following points are supported across multiple authoritative sources and are the “spine” of the playbook:

• Three main warning levels are used across Great Britain (Flood Alert, Flood Warning, Severe Flood Warning), issued by the national agencies and described consistently by the Met Office and the agencies themselves. [1][7][14][13]
• Lead times can be short, especially when warnings escalate; treat warnings as operational triggers rather than “information-only”. [1]
• Coverage and flood type limitations exist, and they differ by nation:
  • England: you cannot get flood warnings for surface water (‘flash’) flooding via the Get Flood Warnings service. [2]
  • Wales: NRW notes its warning service covers ~90% of properties at risk from main rivers or the sea, and explicitly flags flood sources it does not warn for (including surface water and small watercourses) that can occur quickly and locally. [7]
• Safety and recovery guidance is consistent: follow emergency services, avoid floodwater, isolate utilities only when safe, and manage contamination and electrical hazards during clean-up and re-entry. [1][5][6][12][16]
• Insurers want evidence: contact your broker/insurer early, take photos, and keep records to support claims and cashflow (including interim payments). [16][6]

Who issues warnings (nation-aware)

For day-to-day operational response, you should treat these agencies as the “official warning owners”:

• England: Environment Agency (EA) flood warnings and alerts. [15]
• Wales: Natural Resources Wales (NRW) flood warnings and alerts. [15]
• Scotland: Scottish Environment Protection Agency (SEPA) flood warnings and alerts. [15]

Northern Ireland uses different services; GOV.UK points organisations to NI Direct flood maps for risk checking. [2][3]

UK flood warning stages and typical lead times

You will see these stages across agency services (wording varies slightly by nation and channel):

• Flood Alert: flooding is possible; prepare now. EA guidance notes flood alerts are usually issued 2–12 hours before flooding (where possible). [1]
• Flood Warning: flooding is expected; act now. EA guidance notes flood warnings are usually issued 30 minutes–2 hours before flooding. [1]
• Severe Flood Warning: danger to life and significant disruption; act now and be ready to evacuate. [1][7]

Operational implication: your “24 hours before” actions can’t wait for a Flood Warning. Your plan should pre-activate earlier (alerts/outlooks/severe weather/rising levels). [1][7]

What warnings do (and don’t) cover

A resilient portfolio plan assumes you may face flooding with limited warning:

• England: the Get Flood Warnings service does not provide warnings for surface water (flash) flooding. [2]
• Wales: NRW notes it does not warn for some sources including surface water and small watercourses, which can happen very quickly and be localised. [7]
• Scotland: SEPA flood mapping includes surface water risk, and SEPA guidance highlights considering other sources like overloaded drainage systems and groundwater. [13]
• For England, GOV.UK also notes that if you want to know about surface water flooding locally, you may need to contact your local council. [3]

Evidence grading used in this playbook

To keep actions practical, each recommendation is tagged:

• Essential — widely supported by official guidance and low-regret for most sites. [1][4][6][7][12][16]
• Recommended — good support, but depends on site type, criticality, and feasibility. [4][13][16]
• Optional — useful for specific sectors, higher-risk sites, or mature programmes; do if it fits. [13]

The flood incident playbook

Before the timeline, set these foundations. They prevent 80% of avoidable chaos.

Core roles (keep it lightweight)

Minimum structure for multi-site teams:

• Incident Lead (Gold / Strategic): sets priorities, approves closures, owns external escalation.
• Operations Lead (Silver / Tactical): runs the playbook, allocates resources, maintains the “source of truth”.
• Site Leads (Bronze / Operational): execute site actions, report status, manage contractors on the ground.
• H&S / Compliance: re-entry controls, staff safety, evidence and reporting. (Include flood impacts in H&S assessments.) [4]
• Comms Lead: staff/customer/supplier comms and updates. (Agree flood contingency plans with suppliers and customers.) [4]
• Finance / Insurance Liaison: insurer contact, evidence pack, cost tracking, claims support. [4][16]

Minimum per-site “site pack”

Use a consistent template for every location. SEPA’s regulated-site guidance and SEPA public advice both point to practical items to include: contact lists, maps of key shut-off points, triggers, and procedures. [13][12]

Include:

• Site address + access notes + what “closed” means for this site
• Key contacts (site lead, landlord/managing agent, security, utilities, critical suppliers) [12][13]
• Map/photo of service shut-off points and where flood protection equipment is stored [1][13]
• Critical assets list (plant rooms, comms rooms, hazardous materials, stock)
• Minimum safe shutdown steps + time required (especially for industrial/regulated sites) [13]
• Evidence checklist (photos, logs, invoices, time sheets) [6][16]

Your incident log (don’t skip it)

You don’t need bureaucracy; you need defensible, time-stamped facts.

Record:

• Warning stage, area, and time received/seen [1]
• Decisions and who approved them
• Site status updates and photos [16]
• Safety actions (utilities isolated, evacuation, closures) [1][5][6]
• Costs incurred, contractor attendance, and business interruption notes [4][16]

The flood incident playbook

24 hours before: preparedness actions

Trigger to start this phase (portfolio-wide):
Start “T‑24” when any of the following occur for any site cluster: Flood Alert issued, elevated outlooks, severe weather expected, known vulnerable locations, rising river/sea levels, or when local guidance suggests fast-onset risk (e.g., surface water in Wales). [1][3][7]

Objective: buy time. You’re reducing decision latency, not “waiting for certainty”.

People and governance

• Essential: Confirm the incident lead + on-call rota for the next 48 hours; publish a single escalation route (Teams/Slack channel + phone fallback).
• Essential: Assign each site a named Site Lead and deputy, and confirm they can be contacted 24/7 if needed. (SEPA explicitly notes business flood plans should include staff contact lists.) [12]
• Recommended: Decide in advance what triggers: (a) site closure, (b) moving stock/vehicles, (c) isolating power, (d) evacuation. (SEPA recommends trigger points and allocated tasks in the flood plan.) [13]

Information and monitoring (multi-site flood monitoring)

• Essential: Verify official channels for each nation:
  • England: Check for flooding (warnings/alerts, levels, and 5‑day risk). [3]
  • Wales: NRW flood warnings, levels and 5‑day risk tools (and note NRW’s stated limitations for surface water/small watercourses). [7]
  • Scotland: SEPA live flooding info/Floodline plus the Scottish Flood Forecast for earlier national-level indication. [13][20]
• Essential: Confirm that all sites that can be registered are registered for warnings, and that distribution lists are current.
  • England supports organisation accounts and reporting for locations and contacts via the Get Flood Warnings service. [10]
  • Wales allows you to sign up for more than one location. [22]
  • Scotland guidance for regulated sites explicitly reminds organisations to register all vulnerable sites, not just head office. [13]
• Recommended: Run a 15-minute portfolio triage:
  • Which sites are in warning areas?
  • Which sites are operationally critical?
  • Which sites have “no message available” or limited coverage? (England specifically flags not all locations have flood messages.) [11]

Site readiness (physical measures)

• Essential: Confirm flood prevention products and warning systems function properly (and fix what you can now). [4]
• Essential: Pre-position flood protection equipment and install it where appropriate once trigger thresholds are met. (Official guidance repeatedly references putting flood protection equipment in place.) [1][7][12]
• Recommended: Move high-value portable items and critical documents away from at-risk areas. [1][12][7]
• Recommended: Move vehicles out of flood risk areas where possible. [12]
• Optional (regulated / industrial / high-risk sites): Review whether hazardous activities should be paused if flooding is predicted; SEPA notes suspending hazardous activities may be necessary due to flood impacts on emergency response. [13]

Business continuity and comms

• Essential: Confirm insurance position: flood damage + business interruption + lost revenue. [4]
• Recommended: Pre-alert key suppliers and customers of potential disruption and confirm alternative routes/delivery plans (government business guidance explicitly recommends agreeing flood contingency plans). [4]
• Recommended: Draft two messages now:
  • Internal: “If you’re scheduled on site X tomorrow, do not travel until you receive a go/no‑go update.”
  • External (customers/tenants): “We’re monitoring official flood warnings and may restrict access; updates at [time cadence].”
    (SEPA explicitly advises businesses to tell staff, customers and suppliers not to travel into the flood area when flooding is forecast.) [12]

Evidence to capture (start now):

• Screenshot/record of warnings and timing per site cluster [1][3]
• Confirmed contact lists and duty rota [12][10]
• Photos of installed protection equipment (time-stamped) [1][7][12]

During warning: live response actions

Trigger to start this phase:
A Flood Warning or Severe Flood Warning is issued for any site, or site conditions indicate flooding is imminent (even if official messages lag). [1][7]

Objective: protect life, prevent avoidable damage, maintain decision clarity.

Life safety and access control

• Essential: Follow emergency services instructions; Severe Flood Warning messaging emphasises danger to life and readiness to evacuate. [1][7]
• Essential: Stop non-essential travel into affected areas; avoid floodwater. (Both GOV.UK and SEPA advise not walking/driving through floodwater.) [1][12]
• Essential: Restrict access to sites at risk (lockdown/closure decision owned by the Incident Lead; executed by Site Leads).

Utilities and shutdown

• Essential: If safe, turn off gas/electric/water as part of site protection actions. [1][7][12]
• Essential: Do not use electrical appliances if flooding is impacting the site (SEPA). [12]
• Recommended: For critical sites, use the “minimum safe shutdown” procedure from the site pack, including time-to-shutdown and dependencies (SEPA regulated-site guidance highlights the need to understand shutdown time and impacts on utilities and safety-critical equipment). [13]

Operating rhythm (keep it boring)

• Essential: Run one source of truth:
  • portfolio status board (site: green/amber/red),
  • last update time,
  • current warning stage,
  • next decision checkpoint.
• Recommended: Set a fixed cadence (e.g., hourly) to refresh:
  • official warning status,
  • site lead updates,
  • road/access impacts,
  • supplier status.
    (For England, organisation users can pull live warnings reports via Get Flood Warnings service reporting.) [10]

Communications

• Essential: Issue clear instructions per site (open/closed/essential staff only) with next update time.
• Recommended: If you have tenants/customers on site, push a single consistent message and a single escalation contact.
• Recommended: If sites are in Scotland/Wales, mirror communications to reflect local agency terminology and links (NRW/SEPA). [7][12]

Evidence logging (for insurance + audit)

• Essential: Take photos/video when safe and document damage and conditions (ABI recommends photos; UKHSA notes taking photos and keeping records where possible). [16][6]
• Essential: Track costs, disruption, and mitigation measures for business interruption claims. [4][16]

First 24 hours after: recovery and review

Trigger to start this phase:
Warnings are removed or the peak has passed for the site cluster, and the Incident Lead declares transition to recovery.

Objective: safe re-entry, controlled restart, documented learning.

Controlled re-entry and safety

• Essential: Confirm it’s safe to return with emergency services where relevant; GOV.UK guidance is explicit on checking safety before returning. [5]
• Essential: Do not turn on water, gas or electricity until checked by utilities/qualified engineers; GOV.UK is explicit on this point. [5]
• Essential: Treat floodwater as potentially contaminated; UKHSA notes floodwater can contain sewage, harmful pollutants or contaminants and recommends protective clothing and hygiene measures. [6]
• Recommended: Arrange electrical checks before re-energising equipment; UKHSA advises calling a registered electrician to assess wiring/equipment affected by flooding. [6]

Damage assessment and claims

• Essential: Contact broker/insurer early; ABI advises this and notes insurers will advise what evidence is needed. [16]
• Essential: Build an “evidence pack” per site:
  • photos,
  • incident log,
  • contractor invoices,
  • stock loss records,
  • downtime notes,
  • accounts evidence (ABI notes this supports interim payments and cash flow). [16]
• Recommended: If the building is badly damaged, coordinate access and stripping-out via insurer/loss adjuster and appointed contractors (ABI). [16]

Operational restart

• Essential: Verify critical systems (power, HVAC, comms, security) before reopening.
• Recommended: Reopen in phases:
  • Phase 1: safety + security,
  • Phase 2: critical operations,
  • Phase 3: full service.
• Optional: Where you can, use recovery to “build back better” through resilience upgrades, but only after immediate safety and drying needs are managed (ABI notes drying/disinfecting processes can be lengthy depending on damage). [16]

Review (close the loop)

• Essential: Debrief within 72 hours:
  • What triggered action too late?
  • Which sites lacked clear owners?
  • Which comms worked/didn’t?
  • Where did monitoring/coverage gaps appear? [2][7][11]
• Recommended: Update site packs and contact lists immediately while memory is fresh. (Government business guidance emphasises planning and preparedness.) [4]

Decision matrix by warning stage

Warning stage (GB)	What it means (official)	Multi-site trigger	Actions (people / sites / comms)	Evidence / outputs
Flood Alert	Flooding is possible; prepare now. EA notes alerts are usually 2–12 hours before flooding. [1]	Any portfolio site enters alert area OR early outlook suggests elevated risk. [1][20][7]	Essential: activate on-call + confirm site leads. [4][12] Essential: check official status + levels. [3][7] Recommended: pre-position barriers, move vehicles/docs. [1][12]	Screenshot warning status + timestamps. [1] Confirmation of contact lists + rota. [12]
Flood Warning	Flooding is expected; act now. EA notes warnings are usually 30 mins–2 hours before flooding. [1]	Trigger site closure/limited access thresholds; begin minimum safe shutdown where needed. [1][13]	Essential: restrict access; issue clear “do not travel” comms. [12][1] Essential: install protection equipment; isolate utilities if safe. [1][7][12] Recommended: coordinate suppliers/tenants; log decisions. [4][16]	Incident log; photos; contractor actions; cost tracking. [6][16]
Severe Flood Warning	Danger to life and significant disruption; act now and be ready to evacuate. [1][7]	Immediate life-safety escalation; executive visibility.	Essential: follow emergency services; evacuate if required; call 999 if in immediate danger. [1][7] Essential: stop all non-essential activity/travel into area. [1][12]	Time-stamped decisions, evacuation status, welfare checks, safety confirmations. [1][6]
Warning removed / stand down	Official warnings lifted; risk may persist locally. Use judgement and site checks. [5][6][7]	Transition to recovery once safe; controlled re-entry.	Essential: confirm safe return; do not re-energise utilities until checked. [5][6] Essential: start insurer process + evidence pack. [16][6] Recommended: phased reopening + debrief. [4]	Recovery checklist, inspection records, insurer correspondence, lessons learned. [4][16]

Practical checklist for operations teams

Use this as a one-page “grab list” for incident leads and site leads.

Preparedness (before escalation)

• All sites have a named Site Lead + deputy and 24/7 contact method. [12]
• Each site has a site pack: shut-off points, protection equipment location, minimum safe shutdown steps. [13][1]
• Insurance confirmed: flood + business interruption + lost revenue. [4]
• Flood prevention products checked and functional. [4]
• Supplier/customer contingency agreed for key services. [4]
• Monitoring in place for each nation (EA/NRW/SEPA official sources). [15][3][7][13]
• Sites registered for warning messages where available; distribution lists tested. [10][22][13]
• Plan accounts for coverage gaps (surface water / fast onset). [2][7][3]

Live response (during warnings)

• Single source of truth created (portfolio status board) and update cadence set. [10]
• Access restrictions issued per site (go/no-go for staff, tenants, contractors). [12]
• Flood protection equipment deployed where safe and appropriate. [1][7][12]
• Utilities isolated only if safe and as per procedure. [1][7][12]
• Staff instructed to avoid floodwater and follow emergency services. [1][12]
• Evidence captured: photos (when safe), logs, timestamps, costs. [16][6]

Recovery (first 24 hours after peak)

• Safe to return confirmed; re-entry controlled. [5]
• Utilities checked by qualified engineers before restoring. [5][6]
• PPE and hygiene controls in place during clean-up. [6]
• Insurer/broker contacted; evidence pack assembled. [16][6]
• Phased reopening plan agreed; comms to customers/tenants issued. [4]
• Debrief scheduled; site packs updated. [4]

Common mistakes to avoid

• Treating a Flood Alert as “FYI only” — official guidance frames it as a preparation trigger. [1][7]
• Building your plan around long lead times — warnings can be issued close to flooding, and some flood types happen fast. [1][2][7]
• Assuming warnings exist for every site — England explicitly notes some locations won’t have flood messages available. [11]
• No per-site owner — “someone will handle it” doesn’t scale beyond a few locations. (SEPA emphasises allocating tasks and having contact lists.) [13][12]
• Re-entry too early — GOV.UK and UKHSA stress safe return and utilities checks. [5][6]
• Weak evidence — insurers need photos and records; cashflow can depend on it. [16][6]

How FloodWatch supports this workflow (without replacing official guidance)

FloodWatch is a visibility and monitoring tool, not a forecast provider or an emergency service. It helps multi-site teams execute a flood warning response plan with fewer gaps and less manual checking.

Where it fits in the playbook:

• Portfolio view: see all sites and their current official warning status in one place (England/Wales/Scotland). [15]
• Multi-site monitoring: reduce the need to hop between different agency pages and formats; keep a consistent “source of truth” during incidents. [3][7][13]
• Alerts and exports: route the right warning to the right owner; export status updates for reporting and contractors.
• AI briefs: generate short, plain-English incident briefs for ops leaders (grounded in the official warning data FloodWatch is monitoring).
• Audit trail support: make it easier to keep time-stamped records, screenshots, and site-level notes that align with insurer evidence needs. [16][6]

Subtle next steps:

• Try a postcode demo to see how official warnings look for one location.
• Upload a site list to map your portfolio and assign owners.
• Start portfolio monitoring so you can pre-activate before escalation.

FAQ

What’s the difference between a Flood Alert and a Flood Warning?

A Flood Alert means flooding is possible and you should prepare; a Flood Warning means flooding is expected and you should act now. GOV.UK also provides typical lead times for the EA stages (alerts usually 2–12 hours; warnings usually 30 minutes–2 hours), but lead times can vary. [1]

Do flood warnings cover surface water (flash) flooding?

Not always. In England, the Get Flood Warnings service states you cannot get flood warnings for surface water (flash) flooding. In Wales, NRW explicitly notes it doesn’t warn for some sources including surface water and small watercourses, which can happen quickly and locally. Always build local triggers and don’t rely on a single channel. [2][7]

Who issues flood warnings in each UK nation?

In Great Britain: EA (England), NRW (Wales), and SEPA (Scotland). [15] GOV.UK points Northern Ireland organisations to NI Direct for flood risk information. [2][3]

What evidence should we keep for insurance and compliance?

At minimum: time-stamped photos, a clear incident log of decisions and actions, and records of costs and business interruption impacts. ABI advises taking photos and gathering accounts evidence to support claims and interim payments; UKHSA guidance also references taking photos and keeping records where possible. [16][6]

When is it safe to turn power and gas back on after flooding?

GOV.UK guidance says do not turn on water, gas or electricity until utilities or a qualified engineer has checked they are safe. UKHSA also recommends electrical assessment by a registered electrician if wiring/equipment may have been affected. [5][6]

References

1. Flood alerts and warnings: what they are and what to do (GOV.UK)
2. Get flood warnings by text, phone or email (GOV.UK)
3. Check for flooding (GOV.UK)
4. Business flood plan checklists (GOV.UK)
5. What to do after a flood (GOV.UK)
6. How to recover from flooding (UKHSA guidance via GOV.UK)
7. What to do in a flood (Natural Resources Wales)
8. Access our data, maps and reports (Natural Resources Wales Open Data/APIs)
9. Environment Agency Real Time flood-monitoring API reference
10. Reports: guidance for professional users of the Get flood warnings service (GOV.UK)
11. Adding locations: guidance for professional users of the Get flood warnings service (GOV.UK)
12. Before, during and after a flood (SEPA Beta)
13. Flooding guide for regulated sites (SEPA Beta)
14. Flood warnings guide (Met Office)
15. About our services (Flood Forecasting Centre, GOV.UK)
16. Advice for businesses affected by flooding (Association of British Insurers)
17. Local resilience forums: contact details (GOV.UK)
18. Flooding emergency planning: Responses (Local Government Association)
19. Flood maps FAQs (SEPA Beta)
20. Scottish Flood Forecast FAQs (SEPA Beta)
21. Scottish Flood Forecasting Service (Met Office)
22. Sign up to receive flood warnings (Natural Resources Wales)