Jump to section
You gave the file to your paralegal on Monday. By Wednesday you had rewritten most of it, and by Friday you were quietly wondering why you bothered. If that loop feels familiar, the problem usually is not the paralegal. It is how the work left your hands in the first place.
Delegation is a skill, and it is one most of us were never taught. Law school trains you to be personally accountable for every comma. That instinct keeps clients safe, but it also makes handing work off feel like a small act of negligence. It is not. Done well, delegation is how a small firm stops being capped at the size of one lawyer's calendar.
Why lawyers hold on too long
There are three honest reasons we hover. The first is fear: if it goes out with your name on it and it is wrong, that is your problem at the law society, not theirs. The second is speed: in the moment, doing it yourself is genuinely faster than explaining it. The third is the quiet one, that we like being the person who knows how everything works.
All three are real. None of them survive contact with a growing practice. The fear is managed by review, not by refusing to delegate. The speed advantage evaporates the second a task recurs, because the tenth time you explain something is far cheaper than the tenth time you do it yourself. And the last reason is worth sitting with, because it is usually the true one.
Note. Delegation is not the same as abdication. You keep the professional obligation for the work product. What you are handing over is the doing, not the responsibility.
Scope the outcome, not the keystrokes
The most common delegation failure is describing the steps instead of the result. "Pull the corporate records and put them in a folder" tells someone what to type. It does not tell them what you actually need, which might be a clean chronology of the ownership changes for a share purchase closing.
When you scope by outcome, you give the person room to solve the problem in a way you might not have thought of, and you give yourself a clear thing to check against. Compare the two framings:
| Keystroke framing | Outcome framing |
|---|---|
| Draft the affidavit of documents | Produce an affidavit of documents that lists everything relevant and privileged, ready for my review by Thursday noon |
| Enter the invoice | Get this matter billed and out the door before month end, with disbursements reconciled |
| Call the registry | Confirm the filing deadline and put it in the matter with a reminder, so nothing slips |
The outcome column is not longer because it is fussier. It is longer because it carries the definition of done. When done is defined, a person can tell whether they are finished. When it is not, they hand it back early and nervous, and you fill the gap by taking over.
The handoff that prevents rework
A good handoff takes about ninety seconds and saves hours. It has four parts, and you can say them out loud or drop them in a task.
- The outcome. What finished looks like, in one sentence.
- The why. One line of context. People who understand the purpose make better small decisions when the instructions run out, which they always do.
- The guardrails. The deadline, the format, and the two or three things that would make you wince if they went wrong. Not everything, just the landmines.
- The check-in. When you want to see it, and how much of it. "Send me the first section by end of day" beats silence followed by a finished product built on a wrong assumption.
That last point is where most rework hides. If a task will take a paralegal two days, a five minute check on the first afternoon costs almost nothing and catches wrong-direction work before it compounds. You are not checking the work. You are checking the direction.
The tenth time you explain something is far cheaper than the tenth time you do it yourself. The real math of delegation
Reviewing without redoing the work
Here is the trap. You get the draft back, you see a phrasing you would not have used, and your pen starts moving. Forty minutes later you have a document that is now yours, and a paralegal who has learned nothing except that their version was not good enough.
Review against the outcome, not against how you would have done it. Ask a blunt question before you touch anything: is this wrong, or is it just different? If it is wrong, mark it and say why, so the correction sticks next time. If it is merely different and still meets the standard, leave it. Your goal is work that is correct and defensible, not work that is indistinguishable from your own hand.
Tip. When you do correct something, give the rule, not just the fix. "Change this date" teaches nothing. "Always cite the limitation period from the governing statute, not the client's memory" teaches a habit that saves you the next twenty times.
Keeping the whole file, the deadlines, the notes, and the version history in one place makes this kind of review far less painful, which is a big part of why firms move their matters into a single system like A1 CMS rather than chasing versions through email.
Growing what you trust them with
Trust is not a switch, it is a ladder. You do not hand a new paralegal a contested motion on day one, and you do not keep them on document coding for three years either. The move is to widen the scope in deliberate steps and to notice when someone has earned the next rung.
A simple way to track it: for each type of work, decide whether the person does it under close review, does it and reports back, or simply owns it and tells you if something is off. When a task moves from the first category to the second, you have both gained hours. Onboarding sets the initial scope of this, and it is worth being intentional about that early stretch. Our piece on the first thirty days covers how to structure it, and if you are still building the team, hiring your first legal assistant is the place to start.
Start with one recurring task this week. Scope it by outcome, brief it in ninety seconds, and set a single check-in before the deadline. When it comes back, ask whether it is wrong or just different, and let the different stand. Do that a dozen times and something changes: you stop being the bottleneck in your own practice, and the person you hired starts to look like the investment they always were.
