Business flood plan checklist: turn GOV.UK guidance into an operational runbook

A business flood plan checklist is only useful if it turns into clear decisions at the right time, for the right people, across the right locations. GOV.UK provides an excellent checklist of what to include in a business flood plan — but many organisations stop at “a document” rather than building an operational runbook that teams can actually use under pressure.

This post shows how to translate GOV.UK’s checklist into a practical runbook structure, with a focus on roles, communications, critical assets, and suppliers.

What GOV.UK is really telling you to build

GOV.UK’s business flood plan checklist is effectively asking for two things:

A plan that triggers action (clear trigger points, what happens next, and what changes if conditions worsen)
A plan that stands up operationally (contacts, responsibilities, site details, data protection, and compliance)

Your goal isn’t a long report — it’s a runbook that a duty manager can open and use in minutes.

The operational runbook structure (what to include)

1) One page: purpose, scope, and authority

Keep the front page tight:

Which sites and teams the plan covers
Who owns the plan and who can activate it
Which official information sources you rely on (and where to find them)
Where the latest version of the plan is stored (and how to access it out of hours)

2) Roles and responsibilities (make this unambiguous)

GOV.UK recommends making a person (or group) responsible for managing a flood emergency, including decision-making and contacting relevant people.

Turn that into named roles (use job roles, not just individuals):

Incident Lead (Duty Manager): owns decisions and escalation
Site Owner(s): confirms local conditions and impacts
Facilities Lead: buildings, access, utilities coordination (info + contacts)
IT/Data Lead: systems continuity, access, data protection coordination
Comms Lead: internal updates (and customer/supplier comms where needed)
Supplier Liaison: contractors, logistics, emergency storage/supplies

Tip: add a simple “if unavailable, deputy is…” line for each role.

3) Triggers and escalation (write the “when X happens, do Y” rules)

GOV.UK suggests defining trigger points that make sense for your plan (example: “water in the car park”), and stating what happens at those trigger points.

Make this operational by writing 3–6 triggers per site, such as:

Official alert/warning issued for the site’s area
Loss of site access routes (roads/bridges) affecting operations
Flooding observed on site grounds (reported by site owner or facilities)
Utilities disruption risk (based on site-specific knowledge)
Customer/staff disruption threshold (e.g. can’t operate safely or legally)

For each trigger, define:

Owner: who assesses it
Decision: what gets escalated (and to whom)
Record: what must be logged (timestamp, source, decision)

Keep it short and consistent across sites.

4) Communications tree (who to contact, how, and in what order)

A runbook lives or dies on contactability.

Build two lists:

Internal contacts: duty rota, site owners, facilities, IT, H&S, comms
External contacts: building services, utilities, insurers, key suppliers, landlords/managing agents, local council (where relevant)

Include:

Out-of-hours numbers
Shared inboxes/phone numbers (not only individuals)
Preferred channels (phone / email / Teams / Slack)

5) Site annex: “everything someone would need if they’ve never been there”

GOV.UK suggests including a description or map of emergency routes and points, security procedures, and shut-off points for gas/electric/water (plus any emergency power source).

For each site, create a single annex containing:

Site address + access notes
Site map / floor plan references (where stored)
Key locations (utilities shut-off points, comms rooms, plant rooms) as information
Security procedures that may need activation during disruption
Critical areas (stock, refrigeration, hazardous/restricted areas — as applicable)
Photos of key points (helpful for remote support)

Keep this as site intelligence, not step-by-step physical instructions.

6) Critical assets and priorities (what matters most, in order)

Make prioritisation explicit for operations:

Critical equipment and dependencies
Stock categories (especially time-sensitive or regulated)
Single points of failure (one server room, one loading bay, one access route)
“Can we operate elsewhere?” (alternate locations / remote operating mode)

This turns the flood plan into a business continuity tool, not just a safety document.

7) Data and information (protect operations, records, and evidence)

GOV.UK highlights safe storage of data and information and moving important documents somewhere they won’t be damaged.

Translate that into:

Where critical documents live (digital + physical)
Backup and recovery contacts/process ownership
“Minimum systems required” to operate for 24–72 hours
How teams access the runbook if primary systems are down

8) Suppliers and customers (pre-agree the contingencies)

GOV.UK recommends agreeing flood contingency plans with suppliers/customers and contract management, plus planning for business continuity.

Capture:

Priority supplier list with account references and escalation contacts
Alternate suppliers for critical categories
Logistics plan: deliveries, collections, waste management, cold chain (if relevant)
Emergency support options (storage, supplies, specialist contractors)

The goal: you don’t start negotiating for the first time during disruption.

9) Compliance and governance (make it procurement-friendly)

GOV.UK notes you should understand relevant regulations and legislation (e.g. health and safety, liability, environmental management, financial management).

Add a short governance section:

Which internal policies apply (H&S, environmental, incident management)
Who approves major decisions (and thresholds)
What must be documented for audit/insurance

Make it workable for multi-site estates (portfolio rule)

If you operate multiple locations, keep:

One consistent runbook format across sites
One central portfolio view (sites, owners, priority, status)
Site annexes that hold local specifics

This prevents each site doing its own thing — and makes escalation predictable.

Call to action

Download our Business Flood Plan Runbook Template to get:

A ready-to-fill runbook structure
A site annex format you can replicate across locations
A contacts + suppliers worksheet you can hand to operations teams

(Template available via floodwatch.uk.)

Useful links

GOV.UK — Business flood plan checklists: https://www.gov.uk/government/publications/preparing-your-business-for-flooding/business-flood-plan-checklists
GOV.UK — Get flood warnings by text, phone or email: https://www.gov.uk/get-flood-warnings
GOV.UK — Flood alerts and warnings (definitions): https://www.gov.uk/guidance/flood-alerts-and-warnings-what-they-are-and-what-to-do
GOV.UK — Check for flooding: https://www.gov.uk/check-flooding

Business flood plan checklist: turn GOV.UK guidance into an operational runbook