LensReading which lens this session carries.

Standard operating procedure · AD4B · Administration

Correspondence Triage

Transactional procedure owned by Executive Support in Administration. 6 numbered steps, 1 of them a person deciding and 5 of them agent work …

Procedure code

AD4B

Transactional

Rule versions in force

v4.1

2 governing rules stacked over it

In force since

2024-10-07

Earliest effective date across those rules

Last reviewed

2026-07-07

Latest review date across those rules

Rules approved by

1

Chief of Staff, Corporate

Rule health

2/2

0 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 correspondence triage to one repeatable standard inside Executive Support, part of Administration.

Entry condition

Runs transactional. Starts when an upstream system posts an event.

Exit condition

The unit clears send.

In scope

  • Every unit of correspondence triage raised inside Executive Support, from the trigger below through to the final step.
  • 5 of the 6 steps, which run without a person present.
  • 1 decision that stops 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

Executive Support Orchestrator

Accountable person

Chief of Staff, Corporate

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

That team’s remit

Owns executive request 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

68% now · ceiling 74%

Scheduling and briefing prep are near-fully agentic.

The procedure, step by step

6 numbered steps · 1 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

Receive

Agentworkflow

Calendar Optimization Agent

Calendar Optimization 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 — Financials2.6 hrsstandard 5.3 hrs9
02

Classify

Agentworkflow

Briefing Pack Agent

Briefing Pack 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 Management8 minstandard 13 min15
03

Route

Agentworkflow

Travel Coordination Agent

Travel Coordination 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 — Financials2.6 hrsstandard 4.2 hrs3
04

Draft response

Agentworkflow

Correspondence Triage Agent

Correspondence Triage 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 Management29 minstandard 44 min19
05

Approve

HumanpolicyDecision

Chief of Staff, Corporate

Releases: Chief of Staff, Corporate

Work stops. Chief of Staff, Corporate 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 executive request decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials7.7 hrsstandard 10.7 hrs4
06

Send

Agentworkflow

Stakeholder Map Agent

Stakeholder Map 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 — Financials56 minstandard 1.1 hrs26

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.

Person1 station and 53% of the dwellAgent5 stations and 47% of the dwellShared spine0 stations and 0% of the dwell2 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
IT Service Management
Group ERP — Financials
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 22 hrs
Human
decides · 1
Agent
does the work · 5
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes15 hrs a unit
Person7.7 hrs · 53%Agent6.8 hrs · 47%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 6 stations stop for a person and every one of them still does on this run.
  • Every one of the 1 decision is still taken by the person who holds it. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 74% autonomy ceiling and this run sits at 47% 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

One decision, held by Chief of Staff, Corporate.

stays with a person
  • 05 Approve — 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 Receive · Calendar Optimization Agent · 2.6 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 16 hrs

now Receive · Calendar Optimization Agent · 2.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

2 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

7 named parties

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

PartyRACIStepsDutyEscalates to

Executive Support Orchestrator

orchestrator

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

Calendar Optimization Agent

agent

A3% autonomy · ceiling A3%

92% clean · 7% overridden

Responsible1Executes the executive support step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Chief of Staff, Corporate when the unit falls outside the decision envelope or confidence drops below the floor.

Briefing Pack Agent

agent

A3% autonomy · ceiling A3%

89% clean · 5% overridden

Responsible1Executes the executive support step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Chief of Staff, Corporate when the unit falls outside the decision envelope or confidence drops below the floor.

Travel Coordination Agent

agent

A3% autonomy · ceiling A3%

99% clean · 3% overridden

Responsible1Executes the executive support step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Chief of Staff, Corporate when the unit falls outside the decision envelope or confidence drops below the floor.

Correspondence Triage Agent

agent

A3% autonomy · ceiling A3%

90% clean · 4% overridden

Responsible1Executes the executive support step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Chief of Staff, Corporate when the unit falls outside the decision envelope or confidence drops below the floor.

Chief of Staff, Corporate

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Chief of Staff, Corporate for the decisions held here.

Stakeholder Map Agent

agent

A3% autonomy · ceiling A3%

94% clean · 5% overridden

Responsible1Executes the executive support step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Chief of Staff, Corporate when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

1 places this procedure stops

05 · Approve

7.7 hrs

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

Chief of Staff, Corporate

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Executive Support.

The rules this procedure runs inside

2 governing rules

Executive Support Decision Envelope

active

AD4-POL-200 · envelope · vv4.1

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

Approved by Chief of Staff, Corporate · in force 2026-07-04 · reviewed 2026-07-07

Binds Calendar Optimization Agent, Briefing Pack Agent, Travel Coordination Agent, Correspondence Triage Agent, Action Tracking Agent, Stakeholder Map Agent

APAC

Executive Support Evidence Standard

active

AD4-POL-201 · evidence · vv4.1

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

Approved by Chief of Staff, Corporate · in force 2024-10-07 · reviewed 2026-05-10

Binds Calendar Optimization Agent, Briefing Pack Agent, Travel Coordination Agent, Correspondence Triage Agent, Action Tracking Agent, Stakeholder Map Agent

EU · UK

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.5 hrs

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

Touchless

75%

Agent share

83%

A week

4,287

In flight

76

Effort a week

464 human minutes · 406 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

Next to it on the same team

Executive Support

All of Administration

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.