LensReading which lens this session carries.

Standard operating procedure · RO7B · Revenue Growth Management

Cancellation Processing

Transactional procedure owned by Renewals & Churn Ops in Revenue Growth Management. 6 numbered steps, 1 of them a person deciding and 5 of them agent work …

Procedure code

RO7B

Transactional

Rule versions in force

v3.7 · v3.6

2 governing rules stacked over it

In force since

2024-12-18

Earliest effective date across those rules

Last reviewed

2026-05-01

Latest review date across those rules

Rules approved by

1

Director, Renewal Operations

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 cancellation processing to one repeatable standard inside Renewals & Churn Ops, part of Revenue Growth Management.

Entry condition

Runs transactional. Starts when an upstream system posts an event.

Exit condition

The unit clears final bill.

In scope

  • Every unit of cancellation processing raised inside Renewals & Churn Ops, from the trigger below through to the final step.
  • 5 of the 6 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 hands off to sales, information-technology, finance and does not follow the unit there.
  • 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

Renewal Ops Orchestrator

Accountable person

Director, Renewal Operations

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

That team’s remit

Owns renewal record work end to end inside Revenue Growth Management.

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

Autonomy

85% now · ceiling 88%

Auto-renewal and cancellation processing are contractual mechanics that run touchless.

The procedure, step by step

6 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

Receive notice

Agentworkflow

Renewal Calendar Agent

Renewal Calendar 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.Customer Relationship Management15 minstandard 20 min43
02

Verify terms

GBSgbs

Renewal Calendar Agent

Renewal Calendar 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 Management1.7 hrsstandard 3.5 hrs35
03

Save attempt

HumanpolicyDecision

Director, Renewal Operations

Releases: Director, Renewal Operations

Work stops. Director, Renewal Operations 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 renewal record decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Hands off to salesCustomer Relationship Management6 minstandard 7 min2
04

Process

GBSgbs

Renewal Calendar Agent

Renewal Calendar 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 Management2.2 hrsstandard 3.8 hrs33
05

Deprovision

Agentworkflow

Cancellation Agent

Cancellation 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-technologyEnterprise Data Warehouse1.6 hrsstandard 2.5 hrs33
06

Final bill

GBSgbs

Renewal Calendar Agent

Renewal Calendar 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 financeCustomer Relationship Management1.6 hrsstandard 2.2 hrs35

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 1% of the dwellAgent2 stations and 26% of the dwellShared spine3 stations and 73% of the dwell5 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Enterprise Data Warehouse
Customer Relationship 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/6
the happy path, worked time0 min of 7.4 hrs
the same run against its allowance0 min of 12 hrs
Human
decides · 1
Agent
does the work · 2
GBS
shared spine · 3
run log

Nothing has happened yet.

where the worked time goes7.4 hrs a unit
Person6 min · 1%Agent1.9 hrs · 26%Shared spine5.4 hrs · 73%5 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 6 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 88% autonomy ceiling and this run sits at 99% 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, Renewal Operations.

stays with a person
  • 03 Save attempt — 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

6 stations, nothing waiting, nothing sent back

0 min of 7.4 hrs

now Receive notice · Renewal Calendar Agent · 15 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 21 hrs

now Receive notice · Renewal Calendar Agent · 15 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

Renewal Ops Orchestrator

orchestrator

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

Renewal Calendar Agent

agent

A4% autonomy · ceiling A4%

99% clean · 1% overridden

Responsible4Runs the repeatable portion of renewals & churn ops inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Renewal Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Renewal Operations

person

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

Cancellation Agent

agent

A4% autonomy · ceiling A4%

92% clean · 3% overridden

Responsible1Executes the renewals & churn ops step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Renewal Operations when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

1 places this procedure stops

03 · Save attempt

6 min

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

Director, Renewal Operations

Handoffs out of this procedure

Step 03 Save attempt passes the work to sales.

Step 05 Deprovision passes the work to information-technology.

Step 06 Final bill passes the work to finance.

The rules this procedure runs inside

2 governing rules

Renewals & Churn Ops Decision Envelope

active

RO7-POL-200 · envelope · vv3.7

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

Approved by Director, Renewal Operations · in force 2024-12-18 · reviewed 2026-04-30

Binds Renewal Calendar Agent, Auto-renewal Agent, Downgrade Processing Agent, Cancellation Agent

APAC

Renewals & Churn Ops Evidence Standard

active

RO7-POL-201 · evidence · vv3.6

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

Approved by Director, Renewal Operations · in force 2025-05-13 · reviewed 2026-05-01

Binds Renewal Calendar Agent, Auto-renewal Agent, Downgrade Processing Agent, Cancellation Agent

EU · UK

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Customer Relationship ManagementSalesforce Sales Cloudcrmcritical5modeled
Enterprise Data WarehouseSnowflakeanalyticscritical1modeled

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

7.4 hrs

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

Touchless

90%

Agent share

83%

A week

2,542

In flight

181

Effort a week

6 human minutes · 439 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

Quote above $250,000

approval

Any quote exceeding $250,000 total contract valueDeal desk4 business hoursNo

Margin below floor

approval

Any configuration priced beneath the published margin floorDeal desk and Finance1 business dayNo

Territory change affecting 10+ sellers

approval

Coverage change touching more than 10 quota-carrying sellersSVP Revenue Growth Management3 business daysNo

Commission variance above 2%

escalation

Calculated payout deviating more than 2% from modeled expectationFinance controller2 business daysNo

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.