The Legal Project Management Process: 8 Steps

Summary

Knowing that legal work should be run as a project is one thing. Knowing what to actually do on Monday morning is another.

The legal project management process is a repeatable loop for running any matter: scope the outcome, plan the stages and tasks, schedule the dates, delegate by role, track progress as work is done, adapt the plan as the matter develops, manage by exception, and fold what you learned back into the template. Run that loop consistently and a matter stops depending on any one person's memory.

You'll learn each step in practical terms — including the two most neglected ones: adapting the plan when the matter surprises you, and managing by exception so your attention lands where it's needed instead of everywhere. (New to the discipline? Start with what legal project management actually means. This guide runs a single matter as a project; for systematising the whole firm's caseload, see the matter management process.)

Step 1 — Scope: define done
Step 2 — Plan: stages and core tasks
Step 3 — Schedule: targets ahead of deadlines
Step 4 — Delegate: by role, with instructions
Step 5 — Track: progress as a by-product
Step 6 — Adapt: re-plan as the matter reveals itself
Step 7 — Manage by exception
Step 8 — Close and learn
Key takeaways

Figure 1 — The legal project management loop. The steps repeat matter after matter; management by exception sits in the middle, watching all of them.

Step 1 — Scope: define done

Before anything goes on a plan, answer two questions: what does "done" look like for this matter, and what has to happen to get there? The deliverables, the client's actual objective, the constraints (limitation dates, funding, the other side). Most scope problems on legal matters aren't caused by complexity — they're caused by nobody ever writing the destination down, so every team member is quietly navigating to a slightly different one.

Step 2 — Plan: stages and core tasks

Break the matter into the stages it will move through — its milestones, the deliverables and deadlines that mark progress — and list the core tasks under each. Two disciplines here:

Don't start from a blank page. If your firm has a workflow for this matter type, apply it — that's the point of having one. (See how to build one your team will use.)
Start light. Capture the tasks that genuinely matter, not every conceivable step. An over-detailed plan overwhelms the team and gets abandoned; a lean framework gets used, and you can add detail where the matter proves it's needed.

Step 3 — Schedule: targets ahead of deadlines

Give every milestone two dates: the hard due date it truly must be met by, and a soft target date ahead of it that the team actually works to. The gap is your buffer — the difference between "we're behind our aim" and "we're in trouble". Anchor task dates to the milestones they serve, so the plan produces a live timeline rather than a list of isolated to-dos. (The full discipline, including what happens when a court date moves, is in legal calendaring and deadline management.)

Step 4 — Delegate: by role, with instructions

Assign each task to a role — paralegal, junior lawyer, admin — rather than a name, and push each task to the most cost-effective role that can competently do it. Delegating by role keeps the plan valid when the team changes, and delegating down appropriately is what makes matters profitable. Then let the instructions travel with the work: a task that carries its own one-line instruction can be picked up by whoever holds that role, without a corridor briefing. That's delegation that survives contact with a busy week.

Step 5 — Track: progress as a by-product

If tracking requires anyone to stop working and report, it will decay within a month. The process only holds if progress is recorded as a by-product of doing the work — the assignee checks off the task, and the matter's position updates by itself. No status meetings, no Friday chasing, no spreadsheet that's three weeks stale. This is what the plan structure in steps 2–4 buys you: because the work is broken into visible tasks and milestones, "where is this matter up to?" is answered by looking, not asking.

Key point: If tracking is a separate job, it dies. Structure the work so that doing it is documenting it.

Step 6 — Adapt: re-plan as the matter reveals itself

Here's the step traditional project management theory underplays and legal work punishes you for skipping: the plan will be wrong, and that's fine — if you adapt it. No plan survives first contact. You learn what a matter really requires once you're inside it: the estate turns out to be contested, the PI claim doesn't settle, the other side changes tack. Adapting means:

Add to the plan mid-matter — chain in the next workflow (the litigation module, the contested-probate module) at the moment the matter reveals it's needed.
Adjust the applied plan on this matter — add, remove, or re-date tasks for the actual circumstances without corrupting the firm's template.
Re-date in one action when a key date moves — a shifted court date should cascade through the downstream timeline, not trigger an afternoon of manual re-diarising.

A plan that can't change quietly stops describing the matter — and then both the plan and the reporting built on it become fiction.

This is the balance legal work demands: waterfall structure across the matter (the staged plan from step 2), agile execution inside each stage. Too repeatable for pure agile, too unpredictable for pure waterfall — so blend them. (More on the blend: building legal workflows.)

Step 7 — Manage by exception

Now the loop pays for itself. With every matter tracked in real time, you don't need to rely on staff to tell you whether they're doing a good job — a vulnerable position, since the people most at risk are often those without the experience to realise they need help. Nor do you need to check in on everyone constantly, which your best people quietly resent. Instead, triage:

Watch the lead indicators. Late tasks make late milestones, and late milestones make late billings — task and milestone slippage is your early warning, months before the financials confirm it.
Spend management time only where the indicators say to. Step in early on matters at risk of missing milestone deadlines; leave the on-track matters — and the A-players running them — alone.
Resource from evidence, not gut feel. The same task data shows workload ahead: when to hire and for what roles, who is keeping up and who is quietly falling behind, which leave requests would leave you skeleton-staffed in a crunch — and when to rest your best people. Sports teams don't play their stars the full 80 minutes; fatigue means injuries and a worse season. With visibility of the year's demand you can send people on a break in the quiet windows, before burnout chooses the timing for you.

Key point: Manage by exception: let the lead indicators pick which matters get your attention, and let the demand curve pick when your people rest.

Step 8 — Close and learn

When the matter closes, spend ten minutes on the question that compounds: what did this matter teach us that the template should know? A task that was missing, an instruction that would have saved a call, a stage that proved unnecessary. Fold it back into the workflow and the whole firm inherits the lesson on the next matter — your process gets a little better with every file, instead of every lesson retiring with the person who learned it.

Key takeaways

Key point: Legal project management is a loop: scope, plan, schedule, delegate, track, adapt, manage by exception, close and learn — run it on every matter and delivery stops depending on memory.

Define done first; most matter chaos is unwritten scope, not complexity.
Plan from a workflow template, and keep it light — core tasks, not every step.
Two dates per milestone: a soft target the team works to, ahead of the hard deadline.
Delegate by role with instructions in the task — delegation that survives staff changes.
Track as a by-product of the work; separate reporting jobs always decay.
Adapt the plan mid-matter — it's the step legal work punishes you for skipping.
Manage by exception: attention to at-risk matters, evidence-based resourcing, deliberate rest.
Close with a lesson folded back into the template, so the firm compounds.

Run the loop in one place

Hivelight is built around exactly this loop — workflows for the plan, roles for the delegation, targets and cascading dates for the schedule, and live tracking with demand forecasting for the manage-by-exception step. Book a demo and walk one of your matters through it.

The Legal Project Management Process: Running a Matter as a Project, Step by Step