Standard operating procedure · IT10A · Information Technology

Standard Change

Transactional procedure owned by Change & Release in Information Technology. 7 numbered steps, 0 of them a person deciding and 7 of them agent work … more

Information Technology manual Service view

Procedure code

IT10A

Transactional

Rule versions in force

v1.0 · v2.1 · v5.4

3 governing rules stacked over it

In force since

2025-10-03

Earliest effective date across those rules

Last reviewed

2026-06-28

Latest review date across those rules

Rules approved by

Director, Change Management

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 standard change to one repeatable standard inside Change & Release, part of Information Technology. more

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears close. more

In scope

Every unit of standard change raised inside Change & Release, from the trigger below through to the final step.
7 of the 7 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 7 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

Change Orchestrator

Accountable person

Director, Change Management

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

That team’s remit

Owns change record work end to end inside Information Technology. more

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

Autonomy

87% now · ceiling 89%

Pre-approved standard changes flow through with no human at all. more

The procedure, step by step

7 numbered steps · 0 of them stop for a person

A step is one station on the line. more

No.	Step	Who does it	What happens	System of record	Time on the step	In flight
01	Submit GBSgbs	Change Intake Agent	Change Intake 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.	IT Service Management	4 minstandard 9 min	39
02	Score risk GBSgbs	Change Intake Agent	Change Intake 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.	IT Service Management	1.5 hrsstandard 1.8 hrs	42
03	Conflict check GBSgbs	Change Intake Agent	Change Intake 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.	IT Service Management	1.0 hrsstandard 1.7 hrs	37
04	Auto-approve pre-approved GBSgbs	Change Intake Agent	Change Intake 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.	IT Service Management	57 minstandard 1.2 hrs	17
05	Implement GBSgbs	Change Intake Agent	Change Intake 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.	IT Service Management	2.2 hrsstandard 2.8 hrs	3
06	Verify GBSgbs	Change Intake Agent	Change Intake 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.	IT Service Management	2.4 hrsstandard 4.3 hrs	36
07	Close GBSgbs	Change Intake Agent	Change Intake 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.	IT Service Management	1.1 hrsstandard 1.9 hrs	45

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

Person0 stations and 0% of the dwellAgent0 stations and 0% of the dwellShared spine7 stations and 100% of the dwell0 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

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

speed

worked clock

00:00

allowance clock

00:00

stations cleared

0/7

the happy path, worked time0 min of 9.2 hrs

the same run against its allowance0 min of 14 hrs

Human

decides · 0

Agent

does the work · 0

GBS

shared spine · 7

run log

Nothing has happened yet. more

where the worked time goes9.2 hrs a unit

Shared spine9.2 hrs · 100%0 crossings between lanes

what makes this path viable

The lanes are the recorded lanes. 0 of the 7 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 89% autonomy ceiling and this run sits at 100% unattended, inside it.
1 system is 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. more

what this run is, and what it is not

This is a run, not a forecast. more

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

The second clock is the allowance. more

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

The run reads the station rows only. more

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

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

No break below was chosen. more

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 9.2 hrs

now Submit · Change Intake Agent · 4 min

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 14 hrs

now Submit · Change Intake Agent · 4 min

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

2 counted categories land on this procedure. more

What this run cannot claim

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

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

Roles and responsibilities

3 named parties

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

Party	RACI	Steps	Duty	Escalates to
Change Orchestrator orchestrator	Runs the line	0	Sequences this line, holds its timetable and decides what has to surface to a person. more	Raises to Director, Change Management when a unit falls outside the envelope or confidence drops below the floor.
Change Intake Agent agent A4% autonomy · ceiling A4% 90% clean · 8% overridden	Responsible	7	Runs the repeatable portion of change & release inside the shared transaction spine at spine cost and spine controls.	Escalates to Director, Change Management when the unit falls outside the decision envelope or confidence drops below the floor.
Director, Change Management person	Accountable	0	Accountable for this procedure and for the envelope the agents run inside. more	The end of the escalation path for this line.

Party

RACI

Steps

Duty

Escalates to

Change Orchestrator

orchestrator

Runs the line

Sequences this line, holds its timetable and decides what has to surface to a person. more

Raises to Director, Change Management when a unit falls outside the envelope or confidence drops below the floor.

Change Intake Agent

agent

A4% autonomy · ceiling A4%

90% clean · 8% overridden

Responsible

Runs the repeatable portion of change & release inside the shared transaction spine at spine cost and spine controls.

Escalates to Director, Change Management when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Change Management

person

Accountable

Accountable for this procedure and for the envelope the agents run inside. more

The end of the escalation path for this line.

Decision points and escalation

0 places this procedure stops

This procedure has no decision point. more

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Change & Release.

The rules this procedure runs inside

3 governing rules

Change & Release Decision Envelope

active

IT10-POL-200 · envelope · vv1.0

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

Approved by Director, Change Management · in force 2025-10-03 · reviewed 2026-06-16

Binds Change Intake Agent, Risk Scoring Agent, Change Board Prep Agent, Implementation Verification Agent

Global · EU

Change & Release Evidence Standard

active

IT10-POL-201 · evidence · vv2.1

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

Approved by Director, Change Management · in force 2026-04-28 · reviewed 2026-06-28

Binds Change Intake Agent, Risk Scoring Agent, Change Board Prep Agent, Implementation Verification Agent

LATAM · US

Change & Release Escalation Rule

active

IT10-POL-202 · escalation · vv5.4

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

Approved by Director, Change Management · in force 2025-12-27 · reviewed 2026-06-07

Binds Change Intake Agent, Risk Scoring Agent, Change Board Prep Agent, Implementation Verification Agent

EU · UK · US

Systems this procedure touches

1 named · 0 connected

System attribution is a rule, not a reading. more

System	Vendor	Domain	Criticality	Steps	Connection
IT Service Management	ServiceNow ITSM	itsm	high	7	modeled

0 of the 1 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 1 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

9.2 hrs

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

Touchless

90%

Agent share

100%

A week

1,797

In flight

219

Effort a week

0 human minutes · 551 agent minutes

Volume multiplied by the time on each step. more

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 … more

Gate	What trips it	Who releases it	Clock	Waivable
Privileged access grant approval	Any administrative, root or elevated entitlement	Identity governance and system owner	4 business hours	No
Firewall or network boundary change approval	Any rule affecting segmentation, ingress or egress	Network security lead	1 business day	No
Production database or destructive action approval	Any data-affecting operation in production, including bulk deletion	Data owner and CIO delegate	1 business day	No
Major incident command escalation	Any severity-one incident or suspected compromise	Incident commander	15 minutes	No

Next to it on the same team

Change & Release

Normal Change

IT10B

Emergency Change

IT10C

All of Information Technology

What this document is and is not

These procedures describe the modeled estate. more

Actions

What is waiting on a person

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

151

named approvers appear across the library

Every decision point on every procedure carries a job title, not a queue. more

143

steps in the library hand their unit to another function

A handoff is where a procedure stops being one team’s problem. more

controls exist in the estate, and they belong to no procedure in particular

Controls and exception classes are held estate-wide. more

Operations

What this desk is allowed to start

A surface that only reports is not operable. more

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

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

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 more

Not holding on the record

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