LensReading which lens this session carries.

Standard operating procedure · LG9B · Legal

Privacy Impact Assessment

Transactional procedure owned by Privacy & Data Protection in Legal. 7 numbered steps, 2 of them a person deciding and 5 of them agent work …

Procedure code

LG9B

Transactional

Rule versions in force

v5.8 · v4.4 · v4.8

4 governing rules stacked over it

In force since

2025-06-15

Earliest effective date across those rules

Last reviewed

2026-07-22

Latest review date across those rules

Rules approved by

1

Data Protection Officer

Rule health

3/4

1 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 privacy impact assessment to one repeatable standard inside Privacy & Data Protection, part of Legal.

Entry condition

Runs transactional. Starts when a threshold is crossed.

Exit condition

The unit clears register.

In scope

  • Every unit of privacy impact assessment raised inside Privacy & Data Protection, from the trigger below through to the final step.
  • 5 of the 7 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.
  • 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

Privacy Orchestrator

Accountable person

Data Protection Officer

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

That team’s remit

Owns privacy case 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

61% now · ceiling 70%

Subject requests are located and assembled autonomously against a statutory clock.

The procedure, step by step

7 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

Trigger

Agentworkflow

Data Subject Request Agent

Data Subject Request 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.8 hrsstandard 4.9 hrs9
02

Scope

Agentworkflow

Processing Register Agent

Processing Register 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.2 hrsstandard 2.3 hrs21
03

Draft assessment

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.Contract Lifecycle Management1.3 hrsstandard 3.0 hrs27
04

Privacy review

HumanpolicyDecision

Data Protection Officer

Releases: Data Protection Officer

Work stops. Data Protection Officer 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 privacy case decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Contract Lifecycle Management7.4 hrsstandard 11.0 hrs5
05

Mitigations

Agentworkflow

Breach Triage Agent

Breach Triage 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.1 hrsstandard 2.1 hrs2
06

Sign

HumanpolicyDecision

Data Protection Officer

Releases: Data Protection Officer

Work stops. Data Protection Officer 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 privacy case decision envelope, when confidence falls below the floor, or when a policy clause is engaged.Contract Lifecycle Management5.2 hrsstandard 10.9 hrs5
07

Register

GBSgbs

Data Subject Request Agent

Data Subject Request 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.Contract Lifecycle Management2.9 hrsstandard 6.3 hrs37

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 57% of the dwellAgent4 stations and 29% of the dwellShared spine1 station and 13% of the dwell4 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
Document and Matter Management
Contract Lifecycle Management
Contract Lifecycle 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/7
the happy path, worked time0 min of 22 hrs
the same run against its allowance0 min of 40 hrs
Human
decides · 2
Agent
does the work · 4
GBS
shared spine · 1
run log

Nothing has happened yet.

where the worked time goes22 hrs a unit
Person13 hrs · 57%Agent6.4 hrs · 29%Shared spine2.9 hrs · 13%4 crossings between lanes
what makes this path viable
  • The lanes are the recorded lanes. 2 of the 7 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 70% autonomy ceiling and this run sits at 43% 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

1 of the 2 decisions can be handed over inside the 70% ceiling.

could move to the agent lane
  • 04 Privacy review — held by Data Protection Officer, 7.4 hrs a unit
stays with a person
  • 06 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

7 stations, nothing waiting, nothing sent back

0 min of 22 hrs

now Trigger · Data Subject Request Agent · 2.8 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 41 hrs

now Trigger · Data Subject Request Agent · 2.8 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

Privacy Orchestrator

orchestrator

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

Data Subject Request Agent

agent

A2% autonomy · ceiling A2%

90% clean · 3% overridden

Responsible2Runs the repeatable portion of privacy & data protection inside the shared transaction spine at spine cost and spine controls.Escalates to Data Protection Officer when the unit falls outside the decision envelope or confidence drops below the floor.

Processing Register Agent

agent

A2% autonomy · ceiling A2%

95% 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.

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.

Data Protection Officer

person

Accountable and responsible2Holds 2 decisions on this line. Accountable to Data Protection Officer for the decisions held here.

Breach Triage Agent

agent

A2% autonomy · ceiling A2%

95% clean · 1% 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.

Decision points and escalation

2 places this procedure stops

04 · Privacy review

7.4 hrs

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

Data Protection Officer

06 · Sign

5.2 hrs

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

Data Protection Officer

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Privacy & Data Protection.

The rules this procedure runs inside

4 governing rules

Privacy & Data Protection Decision Envelope

active

LG9-POL-200 · envelope · vv5.8

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

Approved by Data Protection Officer · in force 2025-09-27 · reviewed 2026-06-03

Binds Data Subject Request Agent, Processing Register Agent, Impact Assessment Agent, Vendor Data Terms Agent, Breach Triage Agent

LATAM · US

Privacy & Data Protection Evidence Standard

under review

LG9-POL-201 · evidence · vv4.4

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

Approved by Data Protection Officer · in force 2025-06-15 · reviewed 2026-06-27

Binds Data Subject Request Agent, Processing Register Agent, Impact Assessment Agent, Vendor Data Terms Agent, Breach Triage Agent

EU · UK · US

Privacy & Data Protection Escalation Rule

active

LG9-POL-202 · escalation · vv4.8

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 Data Protection Officer · in force 2026-01-09 · reviewed 2026-07-22

Binds Data Subject Request Agent, Processing Register Agent, Impact Assessment Agent, Vendor Data Terms Agent, Breach Triage Agent

Global · EU

Privacy & Data Protection Autonomy Ceiling

active

LG9-POL-203 · ceiling · vv4.8

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

Approved by Data Protection Officer · in force 2026-02-10 · reviewed 2026-05-28

Binds Data Subject Request Agent, Processing Register Agent, Impact Assessment Agent, Vendor Data Terms Agent, Breach Triage Agent

US · Canada

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading.

SystemVendorDomainCriticalityStepsConnection
Contract Lifecycle ManagementIcertislegalhigh5modeled
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

21.9 hrs

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

Touchless

72%

Agent share

71%

A week

1,057

In flight

106

Effort a week

756 human minutes · 559 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

Next to it on the same team

Privacy & Data Protection

All of Legal

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.