LensReading which lens this session carries.

Standard operating procedure · GB1C · AI GBS & Global Business Services

Time & Absence Cycle

Transactional procedure owned by H2R Control Tower in AI GBS & Global Business Services. 6 numbered steps, 1 of them a person deciding and 5 of them agent work …

Procedure code

GB1C

Transactional

Rule versions in force

v5.0 · v4.7

2 governing rules stacked over it

In force since

2024-09-17

Earliest effective date across those rules

Last reviewed

2026-06-06

Latest review date across those rules

Rules approved by

1

Tower Lead, Hire-to-Retire

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 time & absence cycle to one repeatable standard inside H2R Control Tower, part of AI GBS & Global Business Services.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears feed payroll.

In scope

  • Every unit of time & absence cycle raised inside H2R Control Tower, 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 records no handoff, so nothing leaves it mid-flow.
  • 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

Hire-to-Retire Tower Orchestrator

Accountable person

Tower Lead, Hire-to-Retire

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

That team’s remit

Owns payroll transaction work end to end inside AI GBS & Global Business Services.

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

Autonomy

78% now · ceiling 91%

The tower processes at scale with deterministic rules.

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

Collect

GBSgbs

Employee Lifecycle Agent

Employee Lifecycle 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.Group ERP — Financials1.4 hrsstandard 2.3 hrs36
02

Validate

GBSgbs

Employee Lifecycle Agent

Employee Lifecycle 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.Group ERP — Financials52 minstandard 1.2 hrs35
03

Policy check

GBSgbs

Employee Lifecycle Agent

Employee Lifecycle 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.Group ERP — Financials20 minstandard 32 min32
04

Exception review

HumanpolicyDecision

Tower Lead, Hire-to-Retire

Releases: Tower Lead, Hire-to-Retire

Work stops. Tower Lead, Hire-to-Retire 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 payroll transaction decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Group ERP — Financials7.2 hrsstandard 8.5 hrs2
05

Approve

GBSgbs

Employee Lifecycle Agent

Employee Lifecycle 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.Group ERP — Financials3.0 hrsstandard 5.8 hrs30
06

Feed payroll

GBSgbs

Employee Lifecycle Agent

Employee Lifecycle 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.Group ERP — Financials22 minstandard 25 min45

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 54% of the dwellAgent0 stations and 0% of the dwellShared spine5 stations and 46% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
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/6
the happy path, worked time0 min of 13 hrs
the same run against its allowance0 min of 19 hrs
Human
decides · 1
Agent
does the work · 0
GBS
shared spine · 5
run log

Nothing has happened yet.

where the worked time goes13 hrs a unit
Person7.2 hrs · 54%Shared spine6.0 hrs · 46%2 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 91% autonomy ceiling and this run sits at 46% unattended, inside it.
  • 1 system is 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 Tower Lead, Hire-to-Retire.

stays with a person
  • 04 Exception 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

6 stations, nothing waiting, nothing sent back

0 min of 13 hrs

now Collect · Employee Lifecycle Agent · 1.4 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 18 hrs

now Collect · Employee Lifecycle Agent · 1.4 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

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

3 named parties

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

PartyRACIStepsDutyEscalates to

Hire-to-Retire Tower Orchestrator

orchestrator

Runs the line0Sequences this line, holds its timetable and decides what has to surface to a person. Raises to Tower Lead, Hire-to-Retire when a unit falls outside the envelope or confidence drops below the floor.

Employee Lifecycle Agent

agent

A4% autonomy · ceiling A4%

95% clean · 6% overridden

Responsible5Runs the repeatable portion of h2r control tower inside the shared transaction spine at spine cost and spine controls.Escalates to Tower Lead, Hire-to-Retire when the unit falls outside the decision envelope or confidence drops below the floor.

Tower Lead, Hire-to-Retire

person

Accountable and responsible1Holds 1 decision on this line. Accountable to Tower Lead, Hire-to-Retire for the decisions held here.

Decision points and escalation

1 places this procedure stops

04 · Exception review

7.2 hrs

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

Tower Lead, Hire-to-Retire

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside H2R Control Tower.

The rules this procedure runs inside

2 governing rules

H2R Control Tower Decision Envelope

active

GB1-POL-200 · envelope · vv5.0

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

Approved by Tower Lead, Hire-to-Retire · in force 2024-10-14 · reviewed 2026-05-02

Binds Employee Lifecycle Agent, Payroll Run Agent, Time & Absence Agent, Benefits Administration Agent, Case Deflection Agent, Exception Triage Agent

US · Canada

H2R Control Tower Evidence Standard

active

GB1-POL-201 · evidence · vv4.7

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

Approved by Tower Lead, Hire-to-Retire · in force 2024-09-17 · reviewed 2026-06-06

Binds Employee Lifecycle Agent, Payroll Run Agent, Time & Absence Agent, Benefits Administration Agent, Case Deflection Agent, Exception Triage Agent

EU · UK

Systems this procedure touches

1 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Group ERP — FinancialsSAP S/4HANAledgercritical6modeled

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

13.2 hrs

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

Touchless

87%

Agent share

83%

A week

7,344

In flight

180

Effort a week

430 human minutes · 360 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

Autonomy level increase

approval

Any move of an agent or workflow to a higher autonomy bandBusiness owner and risk5 business daysNo

New data class processing

approval

Any service processing a data class not already approvedRisk and privacy officer5 business daysNo

Outsourcing or service removal

approval

Any material operating-model, sourcing or service-portfolio changeGBS executive committee10 business daysNo

Agent recertification

oversight

Quarterly evaluation of every agent against its published certification criteriaAgent governance boardQuarterlyNo

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.