LensReading which lens this session carries.
The catalogueLegalCommercial AdvisoryTransactional

Service LG2C

Precedent Library Build

Runs transactional. Starts when an upstream system posts an event. It runs 7,699 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 1 of them on the shared spine.

Runs a week

7,699

96 in flight right now.

Stations

5

1 person · 3 agent · 1 spine

Agent share of steps

80%

Autonomy on this service is set at 63% against a ceiling of 64%.

Decisions a person makes

1

Held by Associate General Counsel, Commercial.

Touchless

65%

Share of runs that complete without anybody opening them.

Timetable against actual

2.9h

Actual 3.3h, 0.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 37% of the dwellAgent3 stations and 40% of the dwellShared spine1 station and 23% 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
Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Operations

Every station in order

The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Mine advice

AgentQuestion Triage Agentworkflow2h 32m4h 41m19Contract Lifecycle Management
2

Cluster

AgentPrecedent Retrieval Agentworkflow2h 40m4h 49m15Document and Matter Management
3

Draft standard

AgentRisk Framing Agentworkflow9m18m25Contract Lifecycle Management
4

Counsel approve

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

HumanAssociate General Counsel, Commercialpolicy5h 1m11h 44m7Contract Lifecycle Management
5

Publish

GBSAdvice Drafting Agentgbs3h 5m4h 50m30Contract Lifecycle Management

Operations

Run it

Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through.

Move something
Demand100%
7,699 a week is what the estate records.
Decisions handed to agents0 of 0
This service has at most one gate, so there is nothing to hand over without removing the last human decision.
People on the gates1104 people
Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.
Agent speed100%
100% is the dwell the estate records today.
Person time a week
38,623.3h
7,699 items at 301 minutes of decision each.
Agent time a week
64,928.2h
506 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 16.7h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
37% waiting on a person
63% in the agent lane
An item now takes 807 minutes of worked time end to end against 807 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.
What this model is, on Precedent Library Build

The simulation is arithmetic on the estate, not a queueing model.

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking.

5 stations, walked twice

Once clean, once with the categories the estate counts

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 13 hrs

now Mine advice · Question Triage Agent · 2.5 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 19 hrs

now Mine advice · Question Triage Agent · 2.5 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 …

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

2 systems attributed

0 of 2 returning records

The system register

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

4 of 5 stations attributed here · would write back

Document and Matter Management

iManage · legal · inbound · medium

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Commercial Advisory Orchestrator
That orchestrator’s remit
Owns advisory matter work end to end inside Legal. Runs 3 lines across 18 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
Accountable person
Associate General Counsel, Commercial
Sub-function
Commercial Advisory
Shared spine tower
Not on the shared spine
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Advisory RequestLG2ADeal Structure ReviewLG2B

What this page is and is not

This is a catalogue of the modeled estate.