How to Delegate a Legal Research Task

A senior says "look into whether we can get an injunction here" and turns to the next fire. Two days later the junior returns forty pages on the general principles of injunctions, none of which addresses the specific difficulty in this matter, because the difficulty was never named. The junior did not fail; the brief did. Research goes wrong at the point of delegation far more often than at the point of execution, and the fix costs the senior five minutes of precision at the start.

State the question narrowly

"Research injunctions" produces a textbook. "Can we obtain an interim injunction restraining the sale when our client is a subsequent purchaser without possession" produces an answer. The tighter the question, the more useful the research, because the junior spends their time on the actual problem instead of surveying a field. If you cannot state the question in a sentence, the thinking that would let you state it is precisely what you have not yet done, and doing it before you delegate saves everyone the detour.

Give the facts the answer turns on

Legal questions rarely have context-free answers. The facts that change the result, who holds possession, when the cause of action arose, which agreement governs, what relief the client actually wants, must travel with the question. Otherwise the junior either researches every branch of the tree or, worse, invents the missing facts to make the question tractable. Supply the material facts and flag which ones are still uncertain, so the research can note where the answer depends on a fact yet to be confirmed.

Name the forum and the deadline

The law that matters is the law that binds this court. Specify the forum, because the position may differ across High Courts and the applicable procedure changes with it. And state a real deadline tied to the matter, so the junior can calibrate depth. A note needed for a conference tomorrow warrants a different effort from a memo underpinning a filing next month. Ambiguity about time produces either a rushed answer or an over-engineered one.

Say what the output should look like

Decide before you delegate what you want back:

• A short opinion with a bottom-line answer, or a full memo with reasoning?
• Primary sources cited to the paragraph, with the passages relied on?
• Contrary authority surfaced, not just the cases that help?
• The open questions the research could not close, stated honestly?

A junior who knows the expected shape of the answer produces something you can use. One left to guess produces something you have to reshape.

Agree when to stop and ask

The most expensive research failure is a junior who, hitting a gap, fills it with an assumption rather than a question. Set the rule at the outset: if a material fact is missing, if the authorities conflict in a way that changes the answer, or if the question turns out to be the wrong one, stop and come back. A five-minute clarification beats two days spent answering a question you did not mean to ask. Keeping the brief and the working notes in a shared matter space, as tools like Juniorlawyer provide, makes those check-ins quick rather than a fresh explanation each time.

Review the reasoning, not just the conclusion

When the research comes back, test how the answer was reached, not only what it says. Ask the junior to show the controlling authority and walk through why it applies. This catches the confident but wrong answer, and it teaches the junior that research is judged on its sources and reasoning, not on arriving at the conclusion the senior seemed to want. A brief that begins with a precise question and ends with a checked chain of reasoning is worth ten that begin with "look into this."