LensReading which lens this session carries.

Standard operating procedure · LG5B · Legal

Regulator Submission

Transactional procedure owned by Regulatory Affairs in Legal. 6 numbered steps, 2 of them a person deciding and 4 of them agent work …

Procedure code

LG5B

Transactional

Rule versions in force

v2.1 · v5.0 · v3.0 · v4.8

4 governing rules stacked over it

In force since

2025-05-28

Earliest effective date across those rules

Last reviewed

2026-08-11

Latest review date across those rules

Rules approved by

1

VP Regulatory Affairs

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 regulator submission to one repeatable standard inside Regulatory Affairs, part of Legal.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears log.

In scope

  • Every unit of regulator submission raised inside Regulatory Affairs, from the trigger below through to the final step.
  • 4 of the 6 steps, which run without a person present.
  • 2 decisions that stop 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

Regulatory Affairs Orchestrator

Accountable person

VP Regulatory Affairs

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

That team’s remit

Owns regulatory item work end to end inside Legal.

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

Autonomy

64% now · ceiling 68%

Horizon scanning and impact mapping are continuous and agentic.

The procedure, step by step

6 numbered steps · 2 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

Assemble

Agentworkflow

Horizon Scanning Agent

Horizon Scanning 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.Contract Lifecycle Management2.0 hrsstandard 4.6 hrs17
02

Draft

Agentworkflow

Impact Assessment Agent

Impact Assessment 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.Document and Matter Management2.6 hrsstandard 3.3 hrs6
03

Counsel review

HumanpolicyDecision

VP Regulatory Affairs

Releases: VP Regulatory Affairs

Work stops. VP Regulatory Affairs 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 regulatory item decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Contract Lifecycle Management3.9 hrsstandard 6.8 hrs0
04

Officer sign

HumanpolicyDecision

VP Regulatory Affairs

Releases: VP Regulatory Affairs

Work stops. VP Regulatory Affairs 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 regulatory item decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Contract Lifecycle Management2.8 hrsstandard 3.6 hrs0
05

Submit

Agentworkflow

Change Implementation Agent

Change Implementation 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.Contract Lifecycle Management2.4 hrsstandard 4.1 hrs33
06

Log

Agentworkflow

Regulatory Stance Agent

Regulatory Stance 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.Document and Matter Management1.0 hrsstandard 1.8 hrs27

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.

Person2 stations and 46% of the dwellAgent4 stations and 54% of the dwellShared spine0 stations and 0% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Contract Lifecycle Management
Document and Matter Management
Contract Lifecycle Management
Contract Lifecycle Management
Contract Lifecycle Management
Document and Matter 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 15 hrs
the same run against its allowance0 min of 24 hrs
Human
decides · 2
Agent
does the work · 4
GBS
shared spine · 0
run log

Nothing has happened yet.

where the worked time goes15 hrs a unit
Person6.7 hrs · 46%Agent8.0 hrs · 54%2 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 2 of the 6 stations stop for a person and every one of them still does on this run.
  • Every one of the 2 decisions is still taken by the people who hold them. The happy path is that each one is released first time, not that it is skipped.
  • The owning team is held to a 68% autonomy ceiling and this run sits at 54% 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

Nothing moves. 54% of the worked time already runs unattended and the owning team is held to a 68% ceiling, so the next decision cannot be handed over until somebody raises that ceiling.

stays with a person
  • 03 Counsel review — Handing this over would put 92% of the worked time in the unattended lane, past the 68% ceiling this team is held to.
  • 04 Officer sign — 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 15 hrs

now Assemble · Horizon Scanning Agent · 2.0 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 34 hrs

now Assemble · Horizon Scanning Agent · 2.0 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.

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

Regulatory Affairs Orchestrator

orchestrator

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

Horizon Scanning Agent

agent

A2% autonomy · ceiling A2%

97% clean · 6% overridden

Responsible1Executes the regulatory affairs step it owns, posts its evidence, and hands the unit to the next stage.Escalates to VP Regulatory Affairs when the unit falls outside the decision envelope or confidence drops below the floor.

Impact Assessment Agent

agent

A2% autonomy · ceiling A2%

93% clean · 7% overridden

Responsible1Executes the privacy & data protection step it owns, posts its evidence, and hands the unit to the next stage.Escalates to Data Protection Officer when the unit falls outside the decision envelope or confidence drops below the floor.

VP Regulatory Affairs

person

Accountable and responsible2Holds 2 decisions on this line. Accountable to VP Regulatory Affairs for the decisions held here.

Change Implementation Agent

agent

A2% autonomy · ceiling A2%

89% clean · 2% overridden

Responsible1Executes the regulatory affairs step it owns, posts its evidence, and hands the unit to the next stage.Escalates to VP Regulatory Affairs when the unit falls outside the decision envelope or confidence drops below the floor.

Regulatory Stance Agent

agent

A2% autonomy · ceiling A2%

96% clean · 13% overridden

Responsible1Authors positions on regulatory affairs. Escalates when two options sit inside the confidence band and the evidence cannot separate them.

Decision points and escalation

2 places this procedure stops

03 · Counsel review

3.9 hrs

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

VP Regulatory Affairs

04 · Officer sign

2.8 hrs

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

VP Regulatory Affairs

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Regulatory Affairs.

The rules this procedure runs inside

4 governing rules

Regulatory Affairs Decision Envelope

active

LG5-POL-200 · envelope · vv2.1

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

Approved by VP Regulatory Affairs · in force 2025-12-18 · reviewed 2026-07-05

Binds Horizon Scanning Agent, Impact Assessment Agent, Submission Drafting Agent, Regulator Correspondence Agent, Change Implementation Agent

EU · UK

Regulatory Affairs Evidence Standard

active

LG5-POL-201 · evidence · vv5.0

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

Approved by VP Regulatory Affairs · in force 2025-07-04 · reviewed 2026-08-11

Binds Horizon Scanning Agent, Impact Assessment Agent, Submission Drafting Agent, Regulator Correspondence Agent, Change Implementation Agent

Global

Regulatory Affairs Escalation Rule

active

LG5-POL-202 · escalation · vv3.0

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 VP Regulatory Affairs · in force 2026-04-03 · reviewed 2026-07-19

Binds Horizon Scanning Agent, Impact Assessment Agent, Submission Drafting Agent, Regulator Correspondence Agent, Change Implementation Agent

LATAM · US

Regulatory Affairs Autonomy Ceiling

active

LG5-POL-203 · ceiling · vv4.8

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

Approved by VP Regulatory Affairs · in force 2025-05-28 · reviewed 2026-05-16

Binds Horizon Scanning Agent, Impact Assessment Agent, Submission Drafting Agent, Regulator Correspondence Agent, Change Implementation Agent

Global

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Contract Lifecycle ManagementIcertislegalhigh4modeled
Document and Matter ManagementiManagelegalmedium2modeled

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

14.7 hrs

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

Touchless

66%

Agent share

67%

A week

7,243

In flight

83

Effort a week

401 human minutes · 479 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

Any external legal communication

approval

Every communication leaving the enterprise on a legal matterNamed lawyerSame dayNo

Contract above $250,000

approval

Contract value above $250,000 or nonstandard indemnity, unlimited liability or IP transferGeneral Counsel delegate2 business daysNo

Settlement or regulator filing

approval

Any settlement, filing or regulator submissionGeneral CounselCase dependentNo

Citation and provenance audit

oversight

Every agent-produced document with external authority citationsCitation Verifier plus lawyer sign-offPre-releaseNo

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.