LensReading which lens this session carries.

Standard operating procedure · FI10C · Finance

Cost Structure Position

Judgment procedure owned by Cost & Profitability in Finance. 5 numbered steps, 1 of them a person deciding and 4 of them agent work …

Procedure code

FI10C

Judgment

Rule versions in force

v5.9 · v3.1 · v1.2 · v1.7

4 governing rules stacked over it

In force since

2025-02-04

Earliest effective date across those rules

Last reviewed

2026-08-11

Latest review date across those rules

Rules approved by

1

Director, Profitability Analytics

Rule health

4/4

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 cost structure position to one repeatable standard inside Cost & Profitability, part of Finance.

Entry condition

Runs judgment. Starts when a leadership team frames the question.

Exit condition

The unit clears cfo ratify, released by Director, Profitability Analytics.

In scope

  • Every unit of cost structure position raised inside Cost & Profitability, 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.
  • Shared-spine work. This line has none; every step is done inside the function.

Who owns it

Runs the line

Profitability Orchestrator

Accountable person

Director, Profitability Analytics

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

That team’s remit

Owns analysis work end to end inside Finance.

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

Autonomy

55% now · ceiling 84%

Allocation and margin modeling are mechanical and run 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

Frame

Agentstrategy

Cost Allocation Agent

Cost Allocation Agent performs this step unattended at the strategy 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 Warehouse33.9 hrsstandard 2.9 days36
02

Model options

Agentstrategy

Product Margin Agent

Product Margin Agent performs this step unattended at the strategy 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 Warehouse31.7 hrsstandard 42.2 hrs28
03

Draft position

Agentstrategy

Customer Profitability Agent

Customer Profitability Agent performs this step unattended at the strategy 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 Warehouse31.4 hrsstandard 2.2 days21
04

Challenge

Agentstrategy

Cost-to-Serve Agent

Cost-to-Serve Agent performs this step unattended at the strategy 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 Warehouse23.6 hrsstandard 2.2 days1
05

CFO ratify

HumanpolicyDecision

Director, Profitability Analytics

Releases: Director, Profitability Analytics

Work stops. Director, Profitability Analytics 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 analysis decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials3.5 daysstandard 7.0 days3

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 41% of the dwellAgent4 stations and 59% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Enterprise Data Warehouse
Enterprise Data Warehouse
Enterprise Data Warehouse
Enterprise Data Warehouse
Group ERP — Financials
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 8.5 days
the same run against its allowance0 min of 16.0 days
Human
decides · 1
Agent
does the work · 4
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes8.5 days a unit
Person3.5 days · 41%Agent5.0 days · 59%1 crossing 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 84% autonomy ceiling and this run sits at 59% 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, Profitability Analytics.

stays with a person
  • 05 CFO ratify — 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 8.5 days

now Frame · Cost Allocation Agent · 34 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 8.6 days

now Frame · Cost Allocation Agent · 34 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

2 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

6 named parties

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

PartyRACIStepsDutyEscalates to

Profitability Orchestrator

orchestrator

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

Cost Allocation Agent

agent

A4% autonomy · ceiling A4%

95% clean · 9% overridden

Responsible1Runs the repeatable portion of corporate services inside the shared transaction spine at spine cost and spine controls.Escalates to Director, Corporate Services when the unit falls outside the decision envelope or confidence drops below the floor.

Product Margin Agent

agent

A3% autonomy · ceiling A3%

97% clean · 1% overridden

Responsible1Executes the cost & profitability step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Profitability Analytics when the unit falls outside the decision envelope or confidence drops below the floor.

Customer Profitability Agent

agent

A3% autonomy · ceiling A3%

94% clean · 4% overridden

Responsible1Executes the cost & profitability step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Director, Profitability Analytics when the unit falls outside the decision envelope or confidence drops below the floor.

Cost-to-Serve Agent

agent

A3% autonomy · ceiling A3%

92% clean · 1% overridden

Responsible1Executes the service analytics step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Head of Service Analytics when the unit falls outside the decision envelope or confidence drops below the floor.

Director, Profitability Analytics

person

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

Decision points and escalation

1 places this procedure stops

05 · CFO ratify

3.5 days

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

Director, Profitability Analytics

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Cost & Profitability.

The rules this procedure runs inside

4 governing rules

Cost & Profitability Decision Envelope

active

FI10-POL-200 · envelope · vv5.9

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

Approved by Director, Profitability Analytics · in force 2025-05-18 · reviewed 2026-05-14

Binds Cost Allocation Agent, Product Margin Agent, Customer Profitability Agent, Cost-to-Serve Agent, Driver Analysis Agent

Global

Cost & Profitability Evidence Standard

active

FI10-POL-201 · evidence · vv3.1

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

Approved by Director, Profitability Analytics · in force 2026-03-23 · reviewed 2026-08-11

Binds Cost Allocation Agent, Product Margin Agent, Customer Profitability Agent, Cost-to-Serve Agent, Driver Analysis Agent

APAC

Cost & Profitability Escalation Rule

active

FI10-POL-202 · escalation · vv1.2

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, Profitability Analytics · in force 2025-02-04 · reviewed 2026-05-08

Binds Cost Allocation Agent, Product Margin Agent, Customer Profitability Agent, Cost-to-Serve Agent, Driver Analysis Agent

EU · UK

Cost & Profitability Autonomy Ceiling

active

FI10-POL-203 · ceiling · vv1.7

The ceiling for this lane is 84 on the platform scale.

Approved by Director, Profitability Analytics · in force 2025-02-12 · reviewed 2026-04-25

Binds Cost Allocation Agent, Product Margin Agent, Customer Profitability Agent, Cost-to-Serve Agent, Driver Analysis Agent

EU · UK · US

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Enterprise Data WarehouseSnowflakeanalyticscritical4modeled
Group ERP — FinancialsSAP S/4HANAledgercritical1modeled

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

8.5 days

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

Touchless

40%

Agent share

80%

A week

5

In flight

89

Effort a week

4,988 human minutes · 7,231 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

Payment above $100,000

approval

Any single payment or batch exceeding $100,000Controller and treasurer4 business hoursNo

Nonstandard journal entry

approval

Any entry outside the approved recurring library, including estimates and reservesController1 business dayNo

New or changed bank details

approval

Any change to supplier or employee banking informationTreasury and supplier master owner2 business daysNo

External disclosure or board forecast

approval

Any external report, statutory filing or board-committed forecastCFO3 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.