LensReading which lens this session carries.

Standard operating procedure · IT10B · Information Technology

Normal Change

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

Procedure code

IT10B

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

1

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

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears close.

In scope

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

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.

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.

The procedure, step by step

7 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

Submit

Agentworkflow

Change Intake Agent

Change 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.Configuration Management Database43 minstandard 59 min4
02

Score risk

Agentworkflow

Risk Scoring Agent

Risk Scoring 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 Management2.3 hrsstandard 4.8 hrs39
03

Assemble evidence

Agentworkflow

Conflict Detection Agent

Conflict Detection 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.Configuration Management Database1.7 hrsstandard 3.2 hrs43
04

Change board approve

HumanpolicyDecision

Director, Change Management

Releases: Director, Change Management

Work stops. Director, Change Management 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 change record decision envelope, when confidence falls below the floor, or when a policy clause is engaged.IT Service Management4.5 hrsstandard 5.6 hrs3
05

Implement

Agentworkflow

Implementation Verification Agent

Implementation Verification 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 Management1.9 hrsstandard 2.3 hrs36
06

Verify

Agentworkflow

Change Policy Agent

Change 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.Configuration Management Database1.3 hrsstandard 2.3 hrs18
07

Close

Agentworkflow

Change Orchestrator

Change Orchestrator 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 Management19 minstandard 32 min25

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 35% of the dwellAgent6 stations and 65% 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
Configuration Management Database
IT Service Management
Configuration Management Database
IT Service Management
IT Service Management
Configuration Management Database
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 20 hrs
Human
decides · 1
Agent
does the work · 6
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes13 hrs a unit
Person4.5 hrs · 35%Agent8.2 hrs · 65%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 7 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 89% autonomy ceiling and this run sits at 65% 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 Director, Change Management.

stays with a person
  • 04 Change board 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 Submit · Change Intake Agent · 43 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 18 hrs

now Submit · Change Intake Agent · 43 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

8 named parties

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

PartyRACIStepsDutyEscalates to

Change Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. 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

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

Risk Scoring Agent

agent

A3% autonomy · ceiling A3%

92% clean · 9% overridden

Responsible1Executes the technical debt step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Engineering Effectiveness when the unit falls outside the decision envelope or confidence drops below the floor.

Conflict Detection Agent

agent

A4% autonomy · ceiling A4%

90% clean · 17% overridden

Responsible1Watches change & release continuously. Escalates to Director, Change Management when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Change Management

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Director, Change Management for the decisions held here.

Implementation Verification Agent

agent

A4% autonomy · ceiling A4%

95% clean · 7% overridden

Responsible1Executes the change & release step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Change Management when the unit falls outside the decision envelope or confidence drops below the floor.

Change Policy Agent

agent

A2% autonomy · ceiling A4%

95% clean · 5% overridden

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

Change Orchestrator

agent

A3% autonomy · ceiling A4%

91% clean · 14% overridden

Responsible1Owns the change & release lane end to end. Escalates to Director, Change Management when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

1 places this procedure stops

04 · Change board approve

4.5 hrs

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

Director, Change Management

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.

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.

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.

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

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
IT Service ManagementServiceNow ITSMitsmhigh4modeled
Configuration Management DatabaseServiceNow CMDBitsmhigh3modeled

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

12.7 hrs

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

Touchless

92%

Agent share

86%

A week

7,302

In flight

168

Effort a week

271 human minutes · 493 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

Privileged access grant

approval

Any administrative, root or elevated entitlementIdentity governance and system owner4 business hoursNo

Firewall or network boundary change

approval

Any rule affecting segmentation, ingress or egressNetwork security lead1 business dayNo

Production database or destructive action

approval

Any data-affecting operation in production, including bulk deletionData owner and CIO delegate1 business dayNo

Major incident command

escalation

Any severity-one incident or suspected compromiseIncident commander15 minutesNo

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.