LensReading which lens this session carries.
The catalogueLegalLitigation & DisputesTransactional

Service LG7A

Matter Lifecycle

Runs transactional. Starts when a scheduled window opens. It runs 5,697 times a week across 8 stations. 3 of those stations stop for a person and 5 are done by an agent, 1 of them on the shared spine.

Runs a week

5,697

131 in flight right now.

Stations

8

3 person · 4 agent · 1 spine

Agent share of steps

63%

Autonomy on this service is set at 55% against a ceiling of 58%.

Decisions a person makes

3

Held by VP Litigation.

Touchless

54%

Share of runs that complete without anybody opening them.

Timetable against actual

10.1h

Actual 7.8h, 2.3h under the timetable.

Operations

The lane diagram

Read it left to right.

Person3 stations and 63% of the dwellAgent4 stations and 33% of the dwellShared spine1 station and 4% of the dwell5 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Contract Lifecycle Management
Contract Lifecycle Management
Document and Matter Management
Contract Lifecycle Management
Contract Lifecycle Management
Contract Lifecycle Management
Document and Matter 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

Intake

AgentMatter Intake Agentworkflow4m7m4Contract Lifecycle Management
2

Issue legal hold

GBSMatter Intake Agentgbs49m1h 34m7Contract Lifecycle Management
3

Assemble chronology

AgentDocument Review Agentworkflow2h 53m5h 42m42Document and Matter Management
4

Model exposure

AgentChronology Builder Agentworkflow2h 52m4h 26m24Contract Lifecycle Management
5

Strategy review

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

HumanVP Litigationpolicy2h 8m4h 54m7Contract Lifecycle Management
6

Counsel instruct

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

HumanVP Litigationpolicy4h 44m8h 18m5Contract Lifecycle Management
7

Track

AgentLitigation Orchestratorworkflow1h 25m2h 16m36Document and Matter Management
8

Resolve

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

HumanVP Litigationpolicy6h 43m12h 24m6Contract 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%
5,697 a week is what the estate records.
Decisions handed to agents0 of 3
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates2211 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
77,384.3h
5,697 items at 815 minutes of decision each.
Agent time a week
45,860.9h
483 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 0.8h of headroom.
Stations without a person
63%
3 gates left on 8 stations.
Where an item spends its time
63% waiting on a person
37% in the agent lane
An item now takes 1,298 minutes of worked time end to end against 1,298 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 Matter Lifecycle

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.

8 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

8 stations, nothing waiting, nothing sent back

0 min of 22 hrs

now Intake · Matter Intake Agent · 4 min

As the ledger has it

the same stations, plus 7 categories the estate already counts

0 min of 2.3 days

now Intake · Matter Intake Agent · 4 min

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

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

Attestations on this estate are written against intake items, not against procedures, so a step done off the platform cannot be matched to the attestation that covers it.

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

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

6 of 8 stations attributed here · would write back

Document and Matter Management

iManage · legal · inbound · medium

modeled

2 of 8 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Litigation Orchestrator
That orchestrator’s remit
Owns matter work end to end inside Legal. Runs 3 lines across 20 stations, drains the repeatable share into no shared tower, and holds 6 human gates.
Accountable person
VP Litigation
Sub-function
Litigation & Disputes
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

What this page is and is not

This is a catalogue of the modeled estate.