LensReading which lens this session carries.

Standard operating procedure · IT11A · Information Technology

Monthly Showback

Analytical procedure owned by IT Financial Management in Information Technology. 5 numbered steps, 1 of them a person deciding and 4 of them agent work …

Procedure code

IT11A

Analytical

Rule versions in force

v3.6 · v1.5

2 governing rules stacked over it

In force since

2025-03-10

Earliest effective date across those rules

Last reviewed

2026-07-03

Latest review date across those rules

Rules approved by

1

Director, IT Financial Management

Rule health

0/2

1 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 monthly showback to one repeatable standard inside IT Financial Management, part of Information Technology.

Entry condition

Runs analytical. Starts when a drift signal breaches tolerance.

Exit condition

The unit clears publish.

In scope

  • Every unit of monthly showback raised inside IT Financial Management, from the trigger below through to the final step.
  • 4 of the 5 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.
  • 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

IT Finance Orchestrator

Accountable person

Director, IT Financial Management

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

That team’s remit

Owns cost line 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

66% now · ceiling 88%

Cost attribution and showback are mechanical allocation work that agents do at full granularity.

The procedure, step by step

5 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

Attribute cost

GBSgbs

Cost Attribution Agent

Cost Attribution 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 Management6.6 hrsstandard 8.1 hrs36
02

Allocate to business

GBSgbs

Cost Attribution Agent

Cost Attribution 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 Management10.6 hrsstandard 24.6 hrs30
03

Draft readout

Agentworkflow

Budget Tracking Agent

Budget Tracking 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.5 hrsstandard 3.1 hrs29
04

Owner review

HumanpolicyDecision

Director, IT Financial Management

Releases: Director, IT Financial Management

Work stops. Director, IT Financial 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 cost line decision envelope, when confidence falls below the floor, or when a policy clause is engaged.IT Service Management34.7 hrsstandard 41.8 hrs3
05

Publish

GBSgbs

Cost Attribution Agent

Cost Attribution 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 Management3.8 hrsstandard 5.0 hrs16

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 61% of the dwellAgent1 station and 3% of the dwellShared spine3 stations and 37% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
IT Service Management
IT Service Management
Configuration Management Database
IT Service Management
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/5
the happy path, worked time0 min of 2.4 days
the same run against its allowance0 min of 3.4 days
Human
decides · 1
Agent
does the work · 1
GBS
shared spine · 3
run log

Nothing has happened yet.

where the worked time goes2.4 days a unit
Person35 hrs · 61%Agent1.5 hrs · 3%Shared spine21 hrs · 37%3 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 1 of the 5 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 39% 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, IT Financial Management.

stays with a person
  • 04 Owner review — 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

5 stations, nothing waiting, nothing sent back

0 min of 2.4 days

now Attribute cost · Cost Attribution Agent · 6.6 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 3.6 days

now Attribute cost · Cost Attribution Agent · 6.6 hrs

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

IT Finance Orchestrator

orchestrator

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

Cost Attribution Agent

agent

A4% autonomy · ceiling A4%

93% clean · 6% overridden

Responsible3Runs the repeatable portion of it financial management inside the shared transaction spine at spine cost and spine controls.Escalates to Director, IT Financial Management when the unit falls outside the decision envelope or confidence drops below the floor.

Budget Tracking Agent

agent

A4% autonomy · ceiling A4%

94% clean · 4% overridden

Responsible1Executes the it financial management step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, IT Financial Management when the unit falls outside the decision envelope or confidence drops below the floor.

Director, IT Financial Management

person

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

Decision points and escalation

1 places this procedure stops

04 · Owner review

34.7 hrs

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

Director, IT Financial Management

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside IT Financial Management.

The rules this procedure runs inside

2 governing rules

IT Financial Management Decision Envelope

superseded

IT11-POL-200 · envelope · vv3.6

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

Approved by Director, IT Financial Management · in force 2025-03-10 · reviewed 2026-07-03

Binds Cost Attribution Agent, Showback Agent, Budget Tracking Agent, Vendor Spend Agent, Unit Cost Agent

LATAM · US

IT Financial Management Evidence Standard

under review

IT11-POL-201 · evidence · vv1.5

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

Approved by Director, IT Financial Management · in force 2026-05-19 · reviewed 2026-06-24

Binds Cost Attribution Agent, Showback Agent, Budget Tracking Agent, Vendor Spend Agent, Unit Cost Agent

APAC

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
IT Service ManagementServiceNow ITSMitsmhigh4modeled
Configuration Management DatabaseServiceNow CMDBitsmhigh1modeled

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

2.4 days

Summed from the time each step sits, standard 3.4 days — running at 69% of the standard.

Touchless

71%

Agent share

80%

A week

56

In flight

114

Effort a week

2,082 human minutes · 1,347 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.