LensReading which lens this session carries.

Standard operating procedure · AD9C · Administration

Live Disruption Response

Transactional procedure owned by Business Continuity in Administration. 6 numbered steps, 2 of them a person deciding and 4 of them agent work …

Procedure code

AD9C

Transactional

Rule versions in force

v2.5 · v5.5 · v2.0

3 governing rules stacked over it

In force since

2024-10-16

Earliest effective date across those rules

Last reviewed

2026-06-28

Latest review date across those rules

Rules approved by

1

Director, Business Continuity

Rule health

2/3

1 under review · 0 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run live disruption response to one repeatable standard inside Business Continuity, part of Administration.

Entry condition

Runs transactional. Starts when a request lands in the queue.

Exit condition

The unit clears stand down, released by Director, Business Continuity.

In scope

  • Every unit of live disruption response raised inside Business Continuity, from the trigger below through to the final step.
  • 4 of the 6 steps, which run without a person present.
  • 2 decisions that stop the line until a named person releases it.

Out of scope

  • Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
  • Work that belongs to another function. This line records no handoff, so nothing leaves it mid-flow.
  • Shared-spine work. This line has none; every step is done inside the function.

Who owns it

Runs the line

Continuity Orchestrator

Accountable person

Director, Business Continuity

The end of the escalation path. Above them sits Administration Chief of Staff for the function.

That team’s remit

Owns continuity plan work end to end inside Administration.

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

58% now · ceiling 60%

Plans and exercises are agentic.

The procedure, step by step

6 numbered steps · 2 of them stop for a person

A step is one station on the line.

No.StepWho does itWhat happensSystem of recordTime on the stepIn flight
01

Detect

Agentworkflow

Business Impact Analysis Agent

Business Impact Analysis Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials1.6 hrsstandard 3.6 hrs37
02

Assess

Agentworkflow

Dependency Mapping Agent

Dependency Mapping Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.IT Service Management1.5 hrsstandard 3.1 hrs30
03

Activate

HumanpolicyDecision

Director, Business Continuity

Releases: Director, Business Continuity

Work stops. Director, Business Continuity reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the continuity plan decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials5.0 hrsstandard 9.1 hrs1
04

Coordinate

Agentworkflow

Exercise Design Agent

Exercise Design Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.Group ERP — Financials33 minstandard 56 min38
05

Communicate

Agentworkflow

Crisis Comms Agent

Crisis Comms Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.IT Service Management16 minstandard 22 min46
06

Stand down

HumanpolicyDecision

Director, Business Continuity

Releases: Director, Business Continuity

Work stops. Director, Business Continuity reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the continuity plan decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials5.8 hrsstandard 9.4 hrs0

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine.

Person2 stations and 74% of the dwellAgent4 stations and 26% of the dwellShared spine0 stations and 0% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
IT Service Management
Group ERP — Financials
Group ERP — Financials
IT Service Management
Group ERP — Financials
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it.

speed
worked clock
00:00
allowance clock
00:00
stations cleared
0/6
the happy path, worked time0 min of 15 hrs
the same run against its allowance0 min of 27 hrs
Human
decides · 2
Agent
does the work · 4
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes15 hrs a unit
Person11 hrs · 74%Agent3.9 hrs · 26%3 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 2 of the 6 stations stop for a person and every one of them still does on this run.
  • Every one of the 2 decisions is still taken by the people who hold them. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 60% autonomy ceiling and this run sits at 26% unattended, inside it.
  • 2 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.
what would have to change

1 of the 2 decisions can be handed over inside the 60% ceiling.

could move to the agent lane
  • 03 Activate — held by Director, Business Continuity, 5.0 hrs a unit
stays with a person
  • 06 Stand down — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.
what this run is, and what it is not

This is a run, not a forecast.

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations.

The second clock is the allowance.

A decision may be handed to the agent lane only if two things hold …

The run reads the station rows only.

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything.

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

This is the same unit on the same stations, breaking.

No break below was chosen.

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

6 stations, nothing waiting, nothing sent back

0 min of 15 hrs

now Detect · Business Impact Analysis Agent · 1.6 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 31 hrs

now Detect · Business Impact Analysis Agent · 1.6 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

3 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Roles and responsibilities

6 named parties

The responsibility grid is assigned by a rule, not lifted from a chart.

PartyRACIStepsDutyEscalates to

Continuity Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Director, Business Continuity when a unit falls outside the envelope or confidence drops below the floor.

Business Impact Analysis Agent

agent

A2% autonomy · ceiling A2%

89% clean · 3% overridden

Responsible1Executes the business continuity step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Business Continuity when the unit falls outside the decision envelope or confidence drops below the floor.

Dependency Mapping Agent

agent

A2% autonomy · ceiling A2%

91% clean · 2% overridden

Responsible1Executes the business continuity step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Business Continuity when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Business Continuity

person

Accountable and responsible2Holds 2 decisions on this line. Accountable to Director, Business Continuity for the decisions held here.

Exercise Design Agent

agent

A2% autonomy · ceiling A2%

97% clean · 6% overridden

Responsible1Executes the business continuity step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Business Continuity when the unit falls outside the decision envelope or confidence drops below the floor.

Crisis Comms Agent

agent

A2% autonomy · ceiling A2%

99% clean · 4% overridden

Responsible1Executes the business continuity step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Business Continuity when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

2 places this procedure stops

03 · Activate

5.0 hrs

Held for a named human when the unit exceeds the continuity plan decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Business Continuity

06 · Stand down

5.8 hrs

Held for a named human when the unit exceeds the continuity plan decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Business Continuity

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Business Continuity.

The rules this procedure runs inside

3 governing rules

Business Continuity Decision Envelope

active

AD9-POL-200 · envelope · vv2.5

Agents in this lane may act without a human when the continuity plan sits inside the stated value, risk and confidence envelope.

Approved by Director, Business Continuity · in force 2026-03-02 · reviewed 2026-05-24

Binds Business Impact Analysis Agent, Dependency Mapping Agent, Plan Maintenance Agent, Exercise Design Agent, Crisis Comms Agent, Recovery Coordination Agent

EU · UK · US

Business Continuity Evidence Standard

under review

AD9-POL-201 · evidence · vv5.5

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path.

Approved by Director, Business Continuity · in force 2025-02-25 · reviewed 2026-06-28

Binds Business Impact Analysis Agent, Dependency Mapping Agent, Plan Maintenance Agent, Exercise Design Agent, Crisis Comms Agent, Recovery Coordination Agent

Global · EU

Business Continuity Escalation Rule

active

AD9-POL-202 · escalation · vv2.0

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires.

Approved by Director, Business Continuity · in force 2024-10-16 · reviewed 2026-05-03

Binds Business Impact Analysis Agent, Dependency Mapping Agent, Plan Maintenance Agent, Exercise Design Agent, Crisis Comms Agent, Recovery Coordination Agent

Global

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical4modeled
IT Service ManagementServiceNow ITSMitsmhigh2modeled

0 of the 2 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 2 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

14.8 hrs

Summed from the time each step sits, standard 26.5 hrs — running at 56% of the standard.

Touchless

59%

Agent share

67%

A week

6,013

In flight

152

Effort a week

653 human minutes · 235 agent minutes

Volume multiplied by the time on each step.

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level …

GateWhat trips itWho releases itClockWaivable

Travel above $5,000

approval

Any itinerary exceeding $5,000 in total costFunction leader1 business dayNo

Security-sensitive itinerary

approval

Travel to any listed destination or any executive protection requirementSecurity and Chief Administrative Officer2 business daysNo

Records disposition

approval

Any deletion, destruction or retention-period changeRecords officer and Legal5 business daysNo

Executive calendar displacement

escalation

Any change that displaces an existing external commitmentExecutive assistant2 hoursNo

What this document is and is not

These procedures describe the modeled estate.

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings.

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from.

Current distribution

2,748 steps

Agent, inside the function1,38951%
Agent, on the shared spine85131%
Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date.