LensReading which lens this session carries.

Standard operating procedure · AD3C · Administration

Duty of Care Response

Transactional procedure owned by Travel & Expense in Administration. 5 numbered steps, 0 of them a person deciding and 5 of them agent work …

Procedure code

AD3C

Transactional

Rule versions in force

v1.3 · v3.3 · v1.5

3 governing rules stacked over it

In force since

2024-11-04

Earliest effective date across those rules

Last reviewed

2026-07-05

Latest review date across those rules

Rules approved by

1

Director, Travel & Expense

Rule health

3/3

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 duty of care response to one repeatable standard inside Travel & Expense, part of Administration.

Entry condition

Runs transactional. Starts when a scheduled window opens.

Exit condition

The unit clears confirm safe.

In scope

  • Every unit of duty of care response raised inside Travel & Expense, from the trigger below through to the final step.
  • 5 of the 5 steps, which run without a person present.
  • No decision on this line stops for a person; it runs end to end without one.

Out of scope

  • Anything outside the envelope set by the owning team. With no gate on this line, an out-of-envelope unit is refused rather than held.
  • Work that belongs to another function. This line records no handoff, so nothing leaves it mid-flow.
  • The 1 step carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Travel & Expense Orchestrator

Accountable person

Director, Travel & Expense

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

That team’s remit

Owns expense report 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

77% now · ceiling 92%

The single most automatable process in Administration.

The procedure, step by step

5 numbered steps · 0 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

Disruption signal

Agentworkflow

Policy Check Agent

Policy Check 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.1 hrsstandard 1.5 hrs31
02

Locate travelers

Agentworkflow

Booking Optimization Agent

Booking 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.IT Service Management25 minstandard 39 min42
03

Contact

Agentworkflow

Receipt Extraction Agent

Receipt Extraction 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 — Financials3.0 hrsstandard 3.6 hrs14
04

Rebook

GBSgbs

Traveler Duty-of-Care Agent

Traveler Duty-of-Care Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, 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 — Financials3.0 hrsstandard 6.4 hrs45
05

Confirm safe

Agentworkflow

Duplicate & Fraud Agent

Duplicate & Fraud 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 10 min6

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.

Person0 stations and 0% of the dwellAgent4 stations and 61% of the dwellShared spine1 station and 39% 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
Group ERP — Financials
IT Service Management
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/5
the happy path, worked time0 min of 7.7 hrs
the same run against its allowance0 min of 12 hrs
Human
decides · 0
Agent
does the work · 4
GBS
shared spine · 1
run log

Nothing has happened yet.

where the worked time goes7.7 hrs a unit
Agent4.7 hrs · 61%Shared spine3.0 hrs · 39%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 0 of the 5 stations stop for a person and every one of them still does on this run.
  • There is no decision point on this procedure, so nothing was waived to make the run clean.
  • The owning team is held to a 92% autonomy ceiling and this run sits at 100% 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

This procedure stops for nobody.

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

5 stations, nothing waiting, nothing sent back

0 min of 7.7 hrs

now Disruption signal · Policy Check Agent · 1.1 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 13 hrs

now Disruption signal · Policy Check Agent · 1.1 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

7 named parties

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

PartyRACIStepsDutyEscalates to

Travel & Expense Orchestrator

orchestrator

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

Policy Check Agent

agent

A2% autonomy · ceiling A4%

90% clean · 16% overridden

Responsible1Holds the rules that bind every other agent in travel & expense. Escalates on any decision that would breach a live policy version, with the clause cited.

Booking Optimization Agent

agent

A4% autonomy · ceiling A4%

94% clean · 7% overridden

Responsible1Executes the travel & expense step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Travel & Expense when the unit falls outside the decision envelope or confidence drops below the floor.

Receipt Extraction Agent

agent

A4% autonomy · ceiling A4%

99% clean · 4% overridden

Responsible1Executes the travel & expense step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Travel & Expense when the unit falls outside the decision envelope or confidence drops below the floor.

Traveler Duty-of-Care Agent

agent

A4% autonomy · ceiling A4%

94% clean · 2% overridden

Responsible1Runs the repeatable portion of travel & expense inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Travel & Expense when the unit falls outside the decision envelope or confidence drops below the floor.

Duplicate & Fraud Agent

agent

A4% autonomy · ceiling A4%

96% clean · 4% overridden

Responsible1Executes the travel & expense step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Travel & Expense when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Travel & Expense

person

Accountable0Accountable for this procedure and for the envelope the agents run inside. The end of the escalation path for this line.

Decision points and escalation

0 places this procedure stops

This procedure has no decision point.

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Travel & Expense.

The rules this procedure runs inside

3 governing rules

Travel & Expense Decision Envelope

active

AD3-POL-200 · envelope · vv1.3

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

Approved by Director, Travel & Expense · in force 2025-09-08 · reviewed 2026-04-24

Binds Booking Optimization Agent, Receipt Extraction Agent, Duplicate & Fraud Agent, Reimbursement Agent, Traveler Duty-of-Care Agent

Global · EU

Travel & Expense Evidence Standard

active

AD3-POL-201 · evidence · vv3.3

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

Approved by Director, Travel & Expense · in force 2024-11-04 · reviewed 2026-07-05

Binds Booking Optimization Agent, Receipt Extraction Agent, Duplicate & Fraud Agent, Reimbursement Agent, Traveler Duty-of-Care Agent

Global

Travel & Expense Escalation Rule

active

AD3-POL-202 · escalation · vv1.5

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, Travel & Expense · in force 2025-02-20 · reviewed 2026-06-03

Binds Booking Optimization Agent, Receipt Extraction Agent, Duplicate & Fraud Agent, Reimbursement Agent, Traveler Duty-of-Care Agent

EU · UK

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical3modeled
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

7.7 hrs

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

Touchless

87%

Agent share

100%

A week

2,839

In flight

138

Effort a week

0 human minutes · 461 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.