CORE GUIDES READYUK EDITIONOFFICIAL DATA // SOURCE STATUS
GET PREPPED NOWUK PREPAREDNESS // OFFICIAL SOURCES // PRACTICAL GUIDANCE
SOURCE STATUS
OFFICIAL SOURCESCHECK STATUSSTATUS & FRESHNESSGB GRID FREQUENCYCHECK SOURCEELEXON BMRSUK WEATHER WARNINGSCHECK SOURCEMET OFFICEENGLAND FLOOD STATUSCHECK SOURCEENVIRONMENT AGENCYUK OFFICIAL UPDATESLATEST UPDATESSOURCE ATTRIBUTEDMY AREALOCAL INFORMATIONPOSTCODE CHECK
BUSINESS RESILIENCE // OPERATIONS WORKBOOK

MAKE THE PLAN
WORK UNDER PRESSURE.

Keep the practical information that sits behind a continuity plan: controlled contacts and dependencies, a timestamped incident chronology, and short exercises that expose weak assumptions before a real disruption does.

MAINTAIN REGISTERS →OPEN INCIDENT LOGRUN TABLETOP
OPERATIONS WORKBOOK // THIS DEVICELOCAL WORKBOOK // CHECKING…
REGISTER RECORDS0CONTACTS + SUPPLIERS + SYSTEMS
INCIDENT ENTRIES0CURRENT CHRONOLOGY
EXERCISES SAVED0LOCAL TEST RECORDS
RECORDED ACTIONS0FROM EXERCISE RECORDS
01 / CONTROLLED REGISTERS

KEEP THE DETAILS YOU NEED OFF THE MAIN SYSTEM.

These are deliberately small working registers for continuity use. Keep only the information required to contact people, switch suppliers and recover essential systems.

SEED FROM YOUR CONTINUITY PLANCopies existing plan-owner, deputy, critical-supplier and recovery fields into blank register rows. It does not change the plan.
CONTACTS + DEPUTIES

Who needs to be reachable?

SUPPLIERS + THIRD PARTIES

What dependency may need switching?

IT + RECOVERY

What must be restored, by whom?

CONTROL RULE // Keep an offline/exported copy only if your organisation can protect it appropriately. Contacts and operational details can be sensitive even when they do not contain passwords.
02 / INCIDENT CHRONOLOGY

RECORD FACTS, DECISIONS AND ACTIONS.

A simple chronology reduces reliance on memory when conditions are changing. Record what was known at the time, who decided what, and what needs to happen next.

Not recorded
Not recorded
Not recorded
Not recorded
RECORDING RULE // Do not guess. If something is unconfirmed, record it as unconfirmed. Do not write card numbers, CVVs, passwords, recovery codes or other authentication secrets into the chronology.
03 / TABLETOP EXERCISES

TEST THE DECISIONS BEFORE THE INCIDENT.

Choose one failure mode and work through it with the people who would actually make the decisions. The exercise is discussion-led: the objective is to expose assumptions, ownership gaps and recovery dependencies.

ASSESSMENT-LED START
TEST RECORDS // LOCAL TO THIS DEVICEMost recent first
CYBER EXERCISES // GPN's scenario is for continuity decisions, not technical incident-response training. For cyber exercises, use the NCSC's free Exercise in a Box material for structured scenario practice.
PLAN → OPERATE → TEST → IMPROVE

Feed what you learn back into the continuity plan.

Registers, logs and exercises are useful only if the plan changes when assumptions fail. Update recovery order, deputies, switch thresholds and workarounds after each meaningful exercise or incident.

UPDATE CONTINUITY PLAN →VIEW PRINTABLE PLAN
NCSC BUSINESS CONTINUITY ↗NCSC EXERCISE IN A BOX ↗HSE EMERGENCY PROCEDURES ↗BACK TO BUSINESS HUB →