Legal Workflow Fundamentals and Process Mapping
This domain tests whether you can model legal work as a repeatable process rather than a set of personal habits. Expect questions on map types, levels of detail, roles and handoffs, and the gap between the documented process and the work actually performed.
Core concepts
- A process converts a trigger into a defined outcome; a procedure documents one part of it.
- A workflow adds roles, decision points, inputs, outputs, systems, and service levels to the process view.
- Common maps: flowcharts, swimlane diagrams (one lane per role or system), SIPOC (suppliers, inputs, process, outputs, customers), and value-stream maps that separate value-adding time from waiting time.
- Map the as-is state before designing the to-be state; capture exceptions and rework loops because they usually drive delay and cost.
- Define start and end triggers, handoffs, decision criteria, and a measure for each step.
Worked example
A firm maps new-matter opening. The as-is flowchart shows intake email, conflict search, partner approval, engagement letter, and matter number. A swimlane view reveals that conflict searches wait in a shared inbox for up to two days. Because the delay sits at a handoff rather than inside a task, the fix is a routing rule with a named owner, not faster typing. The to-be map adds a four-business-hour service level and an escalation path.
Traps
Presenting an ideal process as the as-is state; drawing an org chart and calling it a workflow; omitting exception paths; leaving maps unversioned; measuring activity volume instead of cycle time.