A M Water Services Limited — Integrated Management System

APP_17 · Disaster Recovery & Business Continuity Plan

Reference
APP_17
Issue
5
Issue date
28 September 2026
Owner
Sean Ashton (HSQE Consultant)
Approved by
Aaron Mason, Managing Director
Review
1 June 2027
ISO
9001 6.1 · 9001 8.1 · 14001 8.2 · 45001 8.2
Status as at
27/09/2026
How A M Water Services would keep operating, or recover, if a disruption breaches one of the five impact thresholds. Eight worst-case scenarios, each with the assumption it rests on, the recovery timeframe and the strategy.
8Continuity scenarios
5Impact thresholds
4Critical services
3Activities completed
4Activities planned
RefScenario and assumptionTypeEscalates fromRecovery timeframe

The document

Purpose

This plan sets out how A M Water Services Limited would keep operating, or recover, where a disruption breaches one of the five impact thresholds below. AMWS is a single-site water-services contractor of around twenty people with two Directors, one office and a small fleet, and the plan is sized to that. It follows the FSB Insurance Service business continuity template, which is written for businesses of this size.

Two tiers, and where each is held

Tier 1 — immediate response
minutes to hours
APP_16 Emergency Preparedness & Response, which holds the response matrix, the key emergency contacts and the office emergency arrangements
Tier 2 — business continuity
hours to weeks
This plan, where a disruption has breached or is likely to breach one of the impact thresholds

APP_16 takes precedence while anyone is at risk. Continuity decisions wait until the scene is safe.

Impact tolerance

An impact is unacceptable when it would stop AMWS achieving its long-term objectives, and would require the business to be run differently in order to survive. Anything below these thresholds is managed in normal operations or under APP_16.

Impact typeAn unacceptable impact is
FinancialAn uninsured loss that AMWS could not absorb from reserves without standing down crews or reducing headcount
ReputationSuspension or removal from a water company framework, or a client withholding work pending assurance
ProductionEmergency call-outs or framework jobs not delivered for more than one week
HumanA fatality, or a specified injury under RIDDOR, to an operative, a subcontractor or a member of the public
RegulatoryA prohibition notice, Environment Agency enforcement, or loss of certification or SSIP registration, such that AMWS cannot work on the frameworks

This plan is invoked when any of these thresholds has been breached or is likely to be. That test is also the reason a scenario appears in the table above and the reason others do not.

Critical services and recovery timeframes

A critical service is one whose loss threatens the continuity of the business.

ServiceRequired recovery timeframeProcesses it relies on
Emergency call-out response to water company clients4 hoursOne crew, one vehicle, one mobile phone, the client's job instruction
Making safe an open excavation or live siteImmediateAny two operatives; signing, lighting and guarding stock
Framework job delivery3 working daysCrews, plant, materials, RAMS from the Van Packs portal
Payroll5 working daysBank access and the payroll records; the accountant can run it under the standing arrangement

Activity tracker

ActivityDescriptionStatusDate planned or completed
Production and authorisationPlan rebuilt on the FSB template and approved by the DirectorsCompleted28/09/2026
Exercise — key-person absenceDesktop exercise, Managing Director unavailable for 5+ working daysCompleted17/03/2026
Exercise — key-person absenceDesktop exercise, Site Supervisor unavailable for 5+ working days. Closed CAR-2026-005Completed26/05/2026
Exercise — loss of the officeDesktop exercise, Northampton office unusablePlannedQ4 2026
Exercise — systems recoveryDocumented restore test proving the backup procedure. APP_07 action 18, Sean AshtonPlanned31/03/2027
TrainingDirectors and Site Supervisor briefed on their role in this planPlannedQ4 2026
ReviewAnnual review of this planPlanned01/06/2027

Records of each exercise are held in the APP_16 testing log.

Roles

RoleCompetencies requiredWhat the role doesPrimaryDeputy
Director in chargeBusiness and customer knowledge; authority over financial, customer and HSQE decisionsDecides whether to invoke this plan; assesses the impact against the thresholds; directs the response; communicates with clients, the insurer and the regulators; decides when normal operation has resumedAaron Mason, Managing DirectorLeanne Mason, Director — Finance/Admin
Operational recoverySite and plant knowledge; NRSWA and water-hygiene competence; supervises crewsRe-prioritises crews, vehicles and plant; makes open excavations and live sites safe; arranges hire or subcontract cover; briefs operativesJason May, Site SupervisorAaron Mason, Managing Director

Escalation between the primary and the deputy is a phone call. No further command structure is needed for a business of this size, and the deputising arrangement has been exercised twice, on 17/03/2026 and 26/05/2026.

Sean Ashton (Onyx Operations, HSQE Consultant) advises on any decision touching health, safety, environmental or regulatory risk, and on any statutory notification. He holds no operational authority.

Emergency response

Where to go. For the office premises, the assembly points and the evacuation route are in RA_HO_17 Fire Safety Management and SOP 8.15 Fire. On site, the muster arrangement is in the job RAMS.

Who to call. The internal numbers, the utility emergency lines and the statutory bodies — Environment Agency, HSE, ICO, Action Fraud — are held once, in the Key emergency contacts section of APP_16. They are not repeated here, so there is one list to keep current. Escalate to Aaron Mason, or to Leanne Mason if Aaron is unavailable.

Crisis management

Organise. Mobilise the roles above and deputise where the primary is unavailable. Record the decisions taken and the times they were taken.

Command centre. Adopt one of the following, in order.

OptionWhere
The Northampton office01604 763641
A Teams callWhere the office is unusable or the Directors cannot travel

Crisis agenda. Use this to structure each meeting, and minute it.

  1. Organise. Assign the roles and deputise where the primary is absent.
  2. Assess the damage and test the impact against the five thresholds.
  3. Select the best-fit scenario from the table above and check which of its assumptions hold.
  4. Agree the response, the priorities and the timeframes. Adapt the strategy to what has actually happened.
  5. Communicate, in the order set out below.
  6. Engage professional support where it is needed — insurer, solicitor, accountant, IT provider.
  7. Agree when the group next meets.

Stakeholders and communication.

StakeholderWhat they rely on from usWho tells themWhen
The client whose job is affectedWhat has happened, the effect on their programme, when they will next hear from usAaron MasonWithin 4 hours of the decision to invoke
Other clients with live jobsWhether their work is affected, including when the answer is noAaron or Leanne MasonWithin 24 hours
Operatives and crewsWhether to work, where to go, what has changedJason May, WhatsApp Works groupImmediately, and before the next shift starts
Subcontractors and suppliersWhether to attend, deliver or stand downLeanne MasonWithin 24 hours
Insurer or brokerNotification of the eventAaron MasonWithin 4 hours where a claim is likely
HSE or the Environment AgencyStatutory notification where the trigger is metSean Ashton with Aaron MasonTo the statutory deadline — RIDDOR timescales, or immediately for a pollution incident
ICOWhere a notifiable personal-data breach has occurredSean AshtonWithin 72 hours (POL_HSQE_30 Section 8)
Alcumus ISOQAROnly where the disruption affects certificationSean AshtonBefore the next scheduled contact

Business recovery

Apply these steps, then take the strategy from the scenario table above.

  1. Assess the situation and select the best-fit scenario. Check which of the assumptions hold and what follows from those that do not.
  2. Read the strategy for that scenario and adapt it to the circumstances.
  3. Brief everyone involved, and change the instructions to operatives where the adaptation requires it.
  4. Review as the situation develops.

IT service continuity

SystemHow it is hostedWho relies on itWorkaroundRecovery processRecovery timeTested
Microsoft 365 — email, Teams, OneDriveBy the supplier, software as a serviceAll staffMobile phones for calls; WhatsApp Works group for the crew cascadeWait for supplier recovery. Provider backup is the primary backup, POL_HSQE_30 Section 41 dayNo — APP_07 action 18, Sean Ashton, 31/03/2027
IMS and Van Packs portalsStatic sites, cloud-hosted, versioned in the build sourceOperatives for RAMS and work packs; Directors; auditorsWork packs are carried in the vans in hard copyRebuild and redeploy from the versioned source1 dayYes — rebuilt from source at each issue
XeroBy the supplier, software as a serviceLeanne Mason and the accountantInvoices held and entered when the service returns; payroll run by the accountant under the standing arrangementWait for supplier recovery1 weekNot applicable — no AMWS-side recovery step
WhatsApp Works groupBy the supplier, on operatives' mobilesOperatives and the Site SupervisorDirect calls from the contact list in APP_16Wait for supplier recovery1 dayYes — the phone fallback is in routine use

Contacts

Held once, in the Key emergency contacts section of APP_16: internal numbers, the utility emergency lines for Anglian Water, Affinity Water, Cadent Gas, UK Power Networks and Openreach, and the statutory bodies. Checked at the standing weekly Director and HSQE call.

Supplier contacts are on APP_19 Approved Supplier Register. Operative contact details are held by Leanne Mason.

Responsibilities

RoleResponsibility
Aaron Mason
Managing Director
Decides whether to invoke this plan, directs the response, and approves this document
Leanne Mason
Director — Finance/Admin
Deputises as Director in charge; handles the supply chain, payroll and the insurer during a disruption
Jason May
Site Supervisor
Operational recovery: crews, vehicles, plant and making sites safe
Sean Ashton
HSQE Consultant
Advises on health, safety, environmental and regulatory decisions and on statutory notification; maintains this plan and the exercise programme

How this document is approved

Approved by Aaron Mason as Managing Director. Reviewed annually, after any activation for a real incident, after each desktop exercise, and whenever the risk profile changes — a new contract, a new operation, or a change of personnel in a key role. The outcome of any activation is an input to the annual Management Review.

Related documents

Revision history

IssueDateApproved byChange
101/06/2024Aaron Mason, DirectorInitial issue.
230/09/2025Aaron Mason, DirectorReviewed following IA202512 Emergency Preparedness (0 NC, 0 OBS). Scenario framework introduced; test log restructured.
301/06/2026Aaron Mason, DirectorReviewed in line with the 2026 internal audit cycle — IA202612 Emergency Preparedness (19/05/2026, 0 NC, 0 OBS). Restructured to a 12-scenario format; invocation threshold set at disruption exceeding 24 hours; two-tier model formalised with APP_16. CAR-2026-005 closed via the Q2 2026 desktop exercise, Site Supervisor absence, 26/05/2026.
409/09/2026Aaron Mason, DirectorBusiness impact analysis added, with prioritised activities and a recovery objective for each. Communication during a disruption added.
528/09/2026Aaron Mason, DirectorRebuilt on the FSB Insurance Service business continuity template, which is written for single-site businesses of this size. Impact tolerance now sets the test — five thresholds, and a disruption is a continuity event when it breaches one, which is what decides whether a scenario belongs in this plan. Critical services reduced to the four whose loss threatens the business, with one recovery timeframe each in place of two figures for each of eight activities. Scenarios reduced from twelve to eight: loss of IT service and cyber incident separated, because one is waited out and the other is contained and may be notifiable; severe weather managed in normal operations under APP_16; key-person absence consolidated to one scenario covering all three named roles. Roles reduced to two, each with a primary and a deputy. Recovery strategies now name the risks they answer on APP_05 and the alternatives on APP_19. IT service continuity added, with the hosting, the workaround, the recovery process and whether the recovery has been tested for each system. Contacts held once in APP_16 rather than duplicated. The ISO 22301 coverage map is withdrawn: AMWS is not certified to it and is not seeking to be, and this plan answers Clauses 6.1 and 8.1 of ISO 9001 and Clause 8.2 of ISO 45001 and ISO 14001 through APP_02.
Generated from the controlled source on the AMWS IMS portal. Issue 5, 28 September 2026. Uncontrolled when printed.