Standard operating procedure · RO4A · Revenue Growth Management

Order-to-Provision

Transactional procedure owned by Booking & Order Management in Revenue Growth Management. 7 numbered steps, 0 of them a person deciding and 7 of them agent work … more

Revenue Growth Management manual Service view

Procedure code

RO4A

Transactional

Rule versions in force

v4.5 · v1.4

2 governing rules stacked over it

In force since

2025-09-26

Earliest effective date across those rules

Last reviewed

2026-07-27

Latest review date across those rules

Rules approved by

Director, Order Management

Rule health

2/2

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 order-to-provision to one repeatable standard inside Booking & Order Management, part of Revenue Growth Management. more

Entry condition

Runs transactional. Starts when a scheduled window opens.

Exit condition

The unit clears close. more

In scope

Every unit of order-to-provision raised inside Booking & Order Management, 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 hands off to finance, information-technology and does not follow the unit there.
The 5 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

Order Management Orchestrator

Accountable person

Director, Order Management

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

That team’s remit

Owns order work end to end inside Revenue Growth Management. more

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

Autonomy

82% now · ceiling 91%

Straight-through order processing is the point of the shared-services spine. 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	Receive order GBSgbs	Order Validation Agent	Order Validation 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.	Customer Relationship Management	1.9 hrsstandard 3.8 hrs	18
02	Validate GBSgbs	Order Validation Agent	Order Validation 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.	Customer Relationship Management	2.0 hrsstandard 2.4 hrs	33
03	Credit check GBSgbs	Order Validation Agent	Order Validation 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.Hands off to finance	Customer Relationship Management	54 minstandard 1.6 hrs	20
04	Book GBSgbs	Order Validation Agent	Order Validation 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.	Customer Relationship Management	1.7 hrsstandard 2.5 hrs	38
05	Trigger provisioning Agentworkflow	Backlog Agent	Backlog 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.Hands off to information-technology	Customer Relationship Management	1.8 hrsstandard 3.2 hrs	37
06	Confirm to customer GBSgbs	Order Validation Agent	Order Validation 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.	Customer Relationship Management	1.1 hrsstandard 1.9 hrs	39
07	Close Agentworkflow	Order Management Orchestrator	Order Management 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.	Enterprise Data Warehouse	2.6 hrsstandard 4.5 hrs	17

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 dwellAgent2 stations and 36% of the dwellShared spine5 stations and 64% of the dwell3 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Customer Relationship Management

Enterprise Data Warehouse

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

the same run against its allowance0 min of 20 hrs

Human

decides · 0

Agent

does the work · 2

GBS

shared spine · 5

run log

Nothing has happened yet. more

where the worked time goes12 hrs a unit

Agent4.3 hrs · 36%Shared spine7.6 hrs · 64%3 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 91% 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. 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 12 hrs

now Receive order · Order Validation Agent · 1.9 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 17 hrs

now Receive order · Order Validation Agent · 1.9 hrs

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

3 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

5 named parties

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

Party	RACI	Steps	Duty	Escalates to
Order Management 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, Order Management when a unit falls outside the envelope or confidence drops below the floor.
Order Validation Agent agent A4% autonomy · ceiling A4% 99% clean · 3% overridden	Responsible	5	Runs the repeatable portion of booking & order management inside the shared transaction spine at spine cost and spine controls.	Escalates to Director, Order Management when the unit falls outside the decision envelope or confidence drops below the floor.
Backlog Agent agent A4% autonomy · ceiling A4% 94% clean · 4% overridden	Responsible	1	Executes the booking & order management step it owns, posts its evidence, and hands the unit to the next stage.	Escalates to Director, Order Management when the unit falls outside the decision envelope or confidence drops below the floor.
Order Management Orchestrator agent A3% autonomy · ceiling A4% 90% clean · 8% overridden	Responsible	1	Owns the booking & order management lane end to end. more	Escalates to Director, Order Management when the unit falls outside the decision envelope or confidence drops below the floor.
Director, Order 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.

Decision points and escalation

0 places this procedure stops

This procedure has no decision point. more

Handoffs out of this procedure

Step 03 Credit check passes the work to finance.

Step 05 Trigger provisioning passes the work to information-technology.

The rules this procedure runs inside

2 governing rules

Booking & Order Management Decision Envelope

active

RO4-POL-200 · envelope · vv4.5

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

Approved by Director, Order Management · in force 2026-01-25 · reviewed 2026-04-29

Binds Order Validation Agent, Credit Check Agent, Provisioning Trigger Agent, Order Exception Agent, Backlog Agent

Global

Booking & Order Management Evidence Standard

active

RO4-POL-201 · evidence · vv1.4

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

Approved by Director, Order Management · in force 2025-09-26 · reviewed 2026-07-27

Binds Order Validation Agent, Credit Check Agent, Provisioning Trigger Agent, Order Exception Agent, Backlog Agent

Global · EU

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading. more

System	Vendor	Domain	Criticality	Steps	Connection
Customer Relationship Management	Salesforce Sales Cloud	crm	critical	6	modeled
Enterprise Data Warehouse	Snowflake	analytics	critical	1	modeled

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

11.9 hrs

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

Touchless

91%

Agent share

100%

A week

2,101

In flight

202

Effort a week

0 human minutes · 717 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
Quote above $250,000 approval	Any quote exceeding $250,000 total contract value	Deal desk	4 business hours	No
Margin below floor approval	Any configuration priced beneath the published margin floor	Deal desk and Finance	1 business day	No
Territory change affecting 10+ sellers approval	Coverage change touching more than 10 quota-carrying sellers	SVP Revenue Growth Management	3 business days	No
Commission variance above 2% escalation	Calculated payout deviating more than 2% from modeled expectation	Finance controller	2 business days	No

Next to it on the same team

Booking & Order Management

Order Exception

RO4B

Backlog Review

RO4C

All of Revenue Growth Management

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