LensReading which lens this session carries.

Standard operating procedure · GB5C · AI GBS & Global Business Services

Off-catalog Demand

Transactional procedure owned by Service Catalog & Intake in AI GBS & Global Business Services. 4 numbered steps, 1 of them a person deciding and 3 of them agent work …

Procedure code

GB5C

Transactional

Rule versions in force

v4.2 · v3.7 · v5.3

3 governing rules stacked over it

In force since

2025-03-12

Earliest effective date across those rules

Last reviewed

2026-08-07

Latest review date across those rules

Rules approved by

1

Head of Service Catalog

Rule health

2/3

0 under review · 1 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 off-catalog demand to one repeatable standard inside Service Catalog & Intake, part of AI GBS & Global Business Services.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears feed catalog backlog.

In scope

  • Every unit of off-catalog demand raised inside Service Catalog & Intake, from the trigger below through to the final step.
  • 3 of the 4 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

Catalog & Intake Orchestrator

Accountable person

Head of Service Catalog

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

That team’s remit

Owns service request work end to end inside AI GBS & Global Business Services.

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

Autonomy

83% now · ceiling 90%

Intake and routing are pure classification.

The procedure, step by step

4 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

Detect

Agentworkflow

Catalog Definition Agent

Catalog Definition 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.Enterprise Data Warehouse28 minstandard 1.1 hrs25
02

Assess

Agentworkflow

Demand Intake Agent

Demand Intake 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.4 hrsstandard 2.8 hrs21
03

Route or refuse

HumanpolicyDecision

Head of Service Catalog

Releases: Head of Service Catalog

Work stops. Head of Service Catalog 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 service request decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials3.1 hrsstandard 6.5 hrs3
04

Feed catalog backlog

Agentworkflow

Routing Agent

Routing 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.Core HR and Payroll1.9 hrsstandard 3.9 hrs13

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 45% of the dwellAgent3 stations and 55% 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
Enterprise Data Warehouse
Group ERP — Financials
Group ERP — Financials
Core HR and Payroll
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/4
the happy path, worked time0 min of 6.9 hrs
the same run against its allowance0 min of 14 hrs
Human
decides · 1
Agent
does the work · 3
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes6.9 hrs a unit
Person3.1 hrs · 45%Agent3.8 hrs · 55%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 4 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 90% autonomy ceiling and this run sits at 55% unattended, inside it.
  • 3 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 Head of Service Catalog.

stays with a person
  • 03 Route or refuse — 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

4 stations, nothing waiting, nothing sent back

0 min of 6.9 hrs

now Detect · Catalog Definition Agent · 28 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 12 hrs

now Detect · Catalog Definition Agent · 28 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

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

5 named parties

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

PartyRACIStepsDutyEscalates to

Catalog & Intake Orchestrator

orchestrator

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

Catalog Definition Agent

agent

A4% autonomy · ceiling A4%

97% clean · 2% overridden

Responsible1Runs the repeatable portion of service catalog & intake inside the shared transaction spine at spine cost and spine controls.Escalates to Head of Service Catalog when the unit falls outside the decision envelope or confidence drops below the floor.

Demand Intake Agent

agent

A4% autonomy · ceiling A4%

93% clean · 7% overridden

Responsible1Executes the service catalog & intake step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Head of Service Catalog when the unit falls outside the decision envelope or confidence drops below the floor.

Head of Service Catalog

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Head of Service Catalog for the decisions held here.

Routing Agent

agent

A4% autonomy · ceiling A4%

97% clean · 8% overridden

Responsible1Runs the repeatable portion of service catalog & intake inside the shared transaction spine at spine cost and spine controls.Escalates to Head of Service Catalog when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

1 places this procedure stops

03 · Route or refuse

3.1 hrs

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

Head of Service Catalog

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Service Catalog & Intake.

The rules this procedure runs inside

3 governing rules

Service Catalog & Intake Decision Envelope

active

GB5-POL-200 · envelope · vv4.2

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

Approved by Head of Service Catalog · in force 2026-02-05 · reviewed 2026-06-22

Binds Catalog Definition Agent, Demand Intake Agent, Eligibility Agent, Routing Agent, Entitlement Agent

EU · UK · US

Service Catalog & Intake Evidence Standard

superseded

GB5-POL-201 · evidence · vv3.7

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

Approved by Head of Service Catalog · in force 2025-07-22 · reviewed 2026-08-07

Binds Catalog Definition Agent, Demand Intake Agent, Eligibility Agent, Routing Agent, Entitlement Agent

APAC

Service Catalog & Intake Escalation Rule

active

GB5-POL-202 · escalation · vv5.3

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 Head of Service Catalog · in force 2025-03-12 · reviewed 2026-05-31

Binds Catalog Definition Agent, Demand Intake Agent, Eligibility Agent, Routing Agent, Entitlement Agent

EU · UK

Systems this procedure touches

3 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical2modeled
Enterprise Data WarehouseSnowflakeanalyticscritical1modeled
Core HR and PayrollWorkday HCMhcmcritical1modeled

0 of the 3 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

6.9 hrs

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

Touchless

90%

Agent share

75%

A week

8,124

In flight

62

Effort a week

186 human minutes · 226 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

Autonomy level increase

approval

Any move of an agent or workflow to a higher autonomy bandBusiness owner and risk5 business daysNo

New data class processing

approval

Any service processing a data class not already approvedRisk and privacy officer5 business daysNo

Outsourcing or service removal

approval

Any material operating-model, sourcing or service-portfolio changeGBS executive committee10 business daysNo

Agent recertification

oversight

Quarterly evaluation of every agent against its published certification criteriaAgent governance boardQuarterlyNo

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.