Roadmap & measurement

The recommended next move, the build order with acceptance criteria, who does what — and the measurement plan: exactly which numbers get pulled from production to prove the claim, or disprove it. The audit is the deliverable; everything below is a separate decision.

Recommended next move

Proceed with build 1 — the document pack. The heaviest step by the firm's own logs, fully template-driven, and the safest: drafts only, every send behind attorney approval. No build is a valid outcome of an audit; here, the measured numbers justify one.

The plan, on one line

1weeks 1–2

The document pack

drafts only — accepted when ten straight cases need no corrections

2weeks 3–6

The full opening

intake to filing, same-day — each step behind its named approver

3only if approved

The out-of-scope finds

demand packages, records, updates — each gets its own audit first

The build order

Each phase is accepted by the firm's own people against a written criterion — not by demo.

weeks 1–2

Build 1 · The document pack

The eight documents drafted from the firm's templates, populated from the intake record, released one by one on the approval screen. Runs in training mode first: drafts produced and compared against what the team writes by hand, nothing released.

2 weeks to live~19 h/mo returned≈ $11k/yrpack 100% drafted, human approves

accepted when the paralegal signs off on ten consecutive cases without correcting a draft

weeks 3–6

Build 2 · The full case opening

Intake structuring, conflict check, retainer with reminders, the research (report ordering, carrier identification, calendar computation), claim-filing preparation, and case assignment join the pack — one step at a time, each behind its named approver.

+4 weekstotals ~88 h/mo returned≈ $55k/yr~65% of the opening automated

accepted when each step passes the same ten-consecutive-cases rule, and a full opening completes same-day on five consecutive cases

separate

Build 3 · Approved out-of-scope items

Demand-package assembly, records chasing, status updates, after-hours intake — each starts with its own map entry (a focused audit of that process), then its own proposal. Nothing here is committed by this document.

per item, after its own auditest. up to ≈ $103k/yr further

starts only on the owner's approval, per item

Who does what

The firm	Analog
Approves each phase against its criterion — and owns every send, every day. Provides the eight templates and confirms them current; one hour a week of the paralegal’s time during training mode.	Does not advance a phase until its criterion is met in writing. Builds inside the firm’s systems, runs training mode, reports the comparison numbers weekly, and fixes what the team corrects.

How we prove it — four numbers, checked weekly

Pulled from Clio and the approval log every week, and compared with what the audit measured (document 02). If the numbers don't improve, everyone sees it.

Human time to open a case5 h 30 m today → 2 h or lessmeasured from review times in the approval log

From signature to a working filetypically 3 days today → the same daymeasured from Clio's own timestamps

How often the team corrects a draftnew measure → falling toward zero, never hiddenevery edit recorded on the approval screen

Problems that slip through silently3 last quarter → zero — every one logged, with its causefrom the blocked-items log

The stop rule: if after build 1 the measured numbers do not hold — hands-on time not falling, corrections not converging — the roadmap stops there, with the firm keeping the working document pack and the data. The numbers decide, not the plan.

← previous06 · Prioritized opportunities next →08 · The build

Prepared by /analog · part of the car-crash case study.
open daily · 24/7 · +1 (786) 370-9416 · hello@slashanalog.com · privacy notice