Legal Cycle Time & Bottleneck Reporting
How to measure where legal work slows down and how long it stays stalled — the metric that points most directly at where process, not people, needs attention.
Cycle time tells you how long something takes. Bottleneck reporting tells you why. Together, they turn a general sense that "things feel slow" into a specific answer about where, and for how long, work is actually stuck.
Why This Pairing Matters
Cycle time alone can mislead. An average masks the difference between work that moves consistently and work that's fast most of the time but occasionally stalls for weeks. Bottleneck reporting is what surfaces that second pattern, which the average alone would hide.
What to Measure
Stage-Level Cycle Time
How long work spends at each step — intake, review, approval, execution — rather than only total time start to finish.
Time in Current Stage
How long an item has been sitting at its current step right now, which flags what's stalled before it becomes overdue.
Bottleneck Frequency
How often work stalls at a specific stage, which points to whether a delay is occasional or a structural pattern.
Distribution, Not Just Average
The spread of cycle times across all matters of a type, so outliers don't get smoothed away by an average.
The core issue
An average cycle time of five days can describe a process where everything takes five days, or one where most things take two and a few take three weeks. Those are different problems with different fixes.
From Measurement to Action
Identify the stage
Break total cycle time down by stage to see specifically where time accumulates, rather than treating the whole process as one block.
Look for the pattern
Determine whether delay at that stage is consistent, occasional, or tied to a specific matter type, team, or approver.
Distinguish capacity from process
A stage that stalls because of volume needs a different fix than one that stalls because the process itself is unclear.
Set a threshold for escalation
Define how long something can sit at a stage before it should surface to someone, rather than waiting for a report to catch it later.
Report on what's currently stuck, not just what already finished
Historical cycle time tells you what happened. A live view of what's currently sitting past its expected stage duration tells you what to act on today.
Where This Fits in the Reporting Model
Cycle time and bottleneck data are among the core KPI categories tracked across the department, and they belong on the operational view of any dashboard. This is also where reporting connects most directly back to the coordination work covered in the Workflow Automation Hub's escalation management content.
Cycle time tells the department something is slow. Bottleneck reporting tells it exactly where to look next.