LensReading which lens this session carries.

Standard operating procedure · HR4A · Human Resources

Manager Support Case

Transactional procedure owned by HR Business Partnering in Human Resources. 5 numbered steps, 1 of them a person deciding and 4 of them agent work …

Procedure code

HR4A

Transactional

Rule versions in force

v5.9 · v1.4

2 governing rules stacked over it

In force since

2024-11-15

Earliest effective date across those rules

Last reviewed

2026-07-14

Latest review date across those rules

Rules approved by

1

VP HR Business Partnering

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 manager support case to one repeatable standard inside HR Business Partnering, part of Human Resources.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears resolve.

In scope

  • Every unit of manager support case raised inside HR Business Partnering, 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 1 step carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

HRBP Orchestrator

Accountable person

VP HR Business Partnering

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

That team’s remit

Owns case work end to end inside Human Resources.

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

Autonomy

57% now · ceiling 58%

Tier-1 policy questions are fully agentic.

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

Intake

Agentworkflow

Manager Query Agent

Manager Query 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.Core HR and Payroll2.3 hrsstandard 4.0 hrs0
02

Classify

Agentworkflow

Org Health Signal Agent

Org Health Signal 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.Recruiting and Applicant Tracking46 minstandard 1.5 hrs6
03

Tier-1 answer

GBSgbs

Manager Query Agent

Manager Query 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.Core HR and Payroll1.8 hrsstandard 2.3 hrs21
04

Judgment review

HumanpolicyDecision

VP HR Business Partnering

Releases: VP HR Business Partnering

Work stops. VP HR Business Partnering 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 case decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Core HR and Payroll5.5 hrsstandard 10.7 hrs4
05

Resolve

Agentworkflow

Restructure Modeling Agent

Restructure Modeling 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.Workforce Management1.6 hrsstandard 2.5 hrs15

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 46% of the dwellAgent3 stations and 39% of the dwellShared spine1 station and 15% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Core HR and Payroll
Recruiting and Applicant Tracking
Core HR and Payroll
Core HR and Payroll
Workforce 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 12 hrs
the same run against its allowance0 min of 21 hrs
Human
decides · 1
Agent
does the work · 3
GBS
shared spine · 1
run log

Nothing has happened yet.

where the worked time goes12 hrs a unit
Person5.5 hrs · 46%Agent4.6 hrs · 39%Shared spine1.8 hrs · 15%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 58% autonomy ceiling and this run sits at 54% unattended, inside it.
  • 3 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 VP HR Business Partnering.

stays with a person
  • 04 Judgment 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 12 hrs

now Intake · Manager Query Agent · 2.3 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 25 hrs

now Intake · Manager Query Agent · 2.3 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

4 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

5 named parties

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

PartyRACIStepsDutyEscalates to

HRBP Orchestrator

orchestrator

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

Manager Query Agent

agent

A2% autonomy · ceiling A2%

96% clean · 4% overridden

Responsible2Runs the repeatable portion of hr business partnering inside the shared transaction spine at spine cost and spine controls.Escalates to VP HR Business Partnering when the unit falls outside the decision envelope or confidence drops below the floor.

Org Health Signal Agent

agent

A2% autonomy · ceiling A2%

93% clean · 5% overridden

Responsible1Watches hr business partnering continuously. Escalates to VP HR Business Partnering when the unit falls outside the decision envelope or confidence drops below the floor.

VP HR Business Partnering

person

Accountable and responsible1Holds 1 decision on this line. Accountable to VP HR Business Partnering for the decisions held here.

Restructure Modeling Agent

agent

A2% autonomy · ceiling A2%

95% clean · 8% overridden

Responsible1Authors positions on hr business partnering. Escalates when two options sit inside the confidence band and the evidence cannot separate them.

Decision points and escalation

1 places this procedure stops

04 · Judgment review

5.5 hrs

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

VP HR Business Partnering

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside HR Business Partnering.

The rules this procedure runs inside

2 governing rules

HR Business Partnering Decision Envelope

active

HR4-POL-200 · envelope · vv5.9

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

Approved by VP HR Business Partnering · in force 2025-01-31 · reviewed 2026-07-14

Binds Manager Query Agent, Case Intake & Triage Agent, ER Case Prep Agent

Global

HR Business Partnering Evidence Standard

active

HR4-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.

Approved by VP HR Business Partnering · in force 2024-11-15 · reviewed 2026-06-28

Binds Manager Query Agent, Case Intake & Triage Agent, ER Case Prep Agent

EU · UK

Systems this procedure touches

3 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Core HR and PayrollWorkday HCMhcmcritical3modeled
Recruiting and Applicant TrackingGreenhousehcmmedium1modeled
Workforce ManagementNICE WFMservicemedium1modeled

0 of the 3 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 21.0 hrs — running at 57% of the standard.

Touchless

57%

Agent share

80%

A week

650

In flight

46

Effort a week

332 human minutes · 384 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

Candidate rejection on substantive assessment

approval

Any rejection based on capability judgment rather than administrative criteriaHiring manager2 business daysNo

Offer terms and compensation

approval

Any offer, compensation change or exception to the published bandHR business partner and compensation lead2 business daysNo

Performance or disciplinary action

approval

Any rating, performance plan, disciplinary step or terminationManager and HR business partner3 business daysNo

Adverse-impact testing

oversight

Monthly outcome testing across all agent-supported selection processesCHRO and employment counselMonthlyNo

Next to it on the same team

HR Business Partnering

All of Human Resources

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.