LensReading which lens this session carries.

Standard operating procedure · AD6A · Administration

Classify to Dispose

Transactional procedure owned by Records & Information Management in Administration. 7 numbered steps, 2 of them a person deciding and 5 of them agent work …

Procedure code

AD6A

Transactional

Rule versions in force

v2.4 · v5.1 · v1.0

4 governing rules stacked over it

In force since

2025-07-04

Earliest effective date across those rules

Last reviewed

2026-06-22

Latest review date across those rules

Rules approved by

1

Chief Records Officer

Rule health

4/4

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 classify to dispose to one repeatable standard inside Records & Information Management, part of Administration.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears certificate.

In scope

  • Every unit of classify to dispose raised inside Records & Information Management, from the trigger below through to the final step.
  • 5 of the 7 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.
  • The 3 steps carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Records Orchestrator

Accountable person

Chief Records Officer

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

That team’s remit

Owns record set 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

57% now · ceiling 68%

Classification and retention are automatable.

The procedure, step by step

7 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

Ingest

Agentworkflow

Classification Agent

Classification 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 — Financials23 minstandard 29 min35
02

Classify

GBSgbs

Classification Agent

Classification 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 — Financials1.6 hrsstandard 2.9 hrs19
03

Apply retention

GBSgbs

Classification Agent

Classification 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 — Financials40 minstandard 56 min39
04

Hold check

HumanpolicyDecision

Chief Records Officer

Releases: Chief Records Officer

Work stops. Chief Records Officer 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 record set decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials7.4 hrsstandard 17.6 hrs6
05

Disposition approve

HumanpolicyDecision

Chief Records Officer

Releases: Chief Records Officer

Work stops. Chief Records Officer 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 record set decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials1.2 hrsstandard 2.3 hrs5
06

Execute

GBSgbs

Classification Agent

Classification 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 — Financials1.0 hrsstandard 2.1 hrs34
07

Certificate

Agentworkflow

Records Policy Agent

Records Policy 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 Management31 minstandard 44 min35

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 67% of the dwellAgent2 stations and 7% of the dwellShared spine3 stations and 25% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
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/7
the happy path, worked time0 min of 13 hrs
the same run against its allowance0 min of 27 hrs
Human
decides · 2
Agent
does the work · 2
GBS
shared spine · 3
run log

Nothing has happened yet.

where the worked time goes13 hrs a unit
Person8.7 hrs · 67%Agent54 min · 7%Shared spine3.3 hrs · 25%4 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 2 of the 7 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 68% autonomy ceiling and this run sits at 33% 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

Nothing moves. 33% of the worked time already runs unattended and the owning team is held to a 68% ceiling, so the next decision cannot be handed over until somebody raises that ceiling.

stays with a person
  • 04 Hold check — Handing this over would put 191% of the worked time in the unattended lane, past the 68% ceiling this team is held to.
  • 05 Disposition 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

7 stations, nothing waiting, nothing sent back

0 min of 13 hrs

now Ingest · Classification Agent · 23 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 40 hrs

now Ingest · Classification Agent · 23 min

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

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

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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

Roles and responsibilities

4 named parties

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

PartyRACIStepsDutyEscalates to

Records Orchestrator

orchestrator

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

Classification Agent

agent

A2% autonomy · ceiling A2%

97% clean · 8% overridden

Responsible4Runs the repeatable portion of records & information management inside the shared transaction spine at spine cost and spine controls.Escalates to Chief Records Officer when the unit falls outside the decision envelope or confidence drops below the floor.

Chief Records Officer

person

Accountable and responsible2Holds 2 decisions on this line. Accountable to Chief Records Officer for the decisions held here.

Records Policy Agent

agent

A2% autonomy · ceiling A2%

92% clean · 10% overridden

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

Decision points and escalation

2 places this procedure stops

04 · Hold check

7.4 hrs

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

Chief Records Officer

05 · Disposition approve

1.2 hrs

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

Chief Records Officer

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Records & Information Management.

The rules this procedure runs inside

4 governing rules

Records & Information Management Decision Envelope

active

AD6-POL-200 · envelope · vv2.4

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

Approved by Chief Records Officer · in force 2025-07-04 · reviewed 2026-05-31

Binds Classification Agent, Retention Schedule Agent, Disposition Agent, Privacy Redaction Agent

EU · UK

Records & Information Management Evidence Standard

active

AD6-POL-201 · evidence · vv5.1

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

Approved by Chief Records Officer · in force 2025-10-24 · reviewed 2026-05-12

Binds Classification Agent, Retention Schedule Agent, Disposition Agent, Privacy Redaction Agent

APAC

Records & Information Management Escalation Rule

active

AD6-POL-202 · escalation · vv1.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 Chief Records Officer · in force 2026-04-13 · reviewed 2026-05-06

Binds Classification Agent, Retention Schedule Agent, Disposition Agent, Privacy Redaction Agent

APAC

Records & Information Management Autonomy Ceiling

active

AD6-POL-203 · ceiling · vv5.1

The ceiling for this lane is 68 on the platform scale.

Approved by Chief Records Officer · in force 2026-03-01 · reviewed 2026-06-22

Binds Classification Agent, Retention Schedule Agent, Disposition Agent, Privacy Redaction Agent

EU · UK

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical6modeled
IT Service ManagementServiceNow ITSMitsmhigh1modeled

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

12.8 hrs

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

Touchless

71%

Agent share

71%

A week

2,484

In flight

173

Effort a week

519 human minutes · 250 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.