A research memo that sits unread usually failed at the briefing stage, not the research stage. Knowing how to brief legal research properly is a skill most fee earners never had to learn explicitly, because in-house juniors absorb it informally over months of trial and error. Delegating research externally makes the gap visible immediately, since a poorly scoped brief produces a technically correct but practically useless memo.
What makes a research brief usable?
A specific question, not a general topic. “Does a particular clause survive termination under these facts” produces a usable memo. “Research termination clauses” does not, a distinction covered further in the legal research support article. The difference isn’t pedantic; it’s the difference between a memo that answers the actual question keeping a fee earner up at night and one that surveys the general area without landing anywhere useful.
Fee earners who are good at delegating research tend to write the brief the way they’d want the answer phrased. If the honest version of the question is “can I rely on X in front of this particular judge,” that’s the question that should go in the brief, not a broader restatement of the legal area.
Why does narrow scope produce better results when learning how to brief legal research?
A tightly scoped question allows genuinely thorough research within it. A broad topic forces a choice between depth and breadth, and usually neither serves the fee earner well. Ten hours spent on a narrow, well-defined question produces something usable. Ten hours spread across a broad topic produces a competent survey that still leaves the fee earner to do the hard part themselves.
This is counterintuitive to fee earners used to giving juniors latitude to “look into” something. Latitude works when the junior already understands the matter’s context deeply; it works far less well the first time a piece of research is delegated externally, before that shared context exists.
What should be included in the brief itself?
The specific facts, the question that needs answering, and the format the answer needs to take to be useful, whether a short memo or a fuller note, following the same principles set out in the article on briefing outsourced work generally. A brief that includes the relevant facts up front saves a round trip of clarifying questions before the research can even start.
It’s also worth stating explicitly what the memo will be used for: a client-facing explanation reads very differently from an internal note weighing litigation risk, even when the underlying research question is identical. Naming the audience in the brief does more to shape a usable memo than almost any other single instruction.
What goes wrong when a brief is too vague?
The researcher has to guess at scope, and guesses tend to be conservative, producing a broader, shallower memo than the fee earner actually needed. The fee earner then has to either accept a memo that doesn’t quite answer the question, or send it back for a second pass, which costs more time than a tighter brief would have taken to write in the first place.
This is the single most common reason a delegated research task disappoints on the first attempt. It’s rarely a research quality problem; it’s almost always a scoping problem that a slightly more specific brief would have prevented.
How does this connect to supervision and sign-off?
A clear brief also makes review faster, since the fee earner reviewing the memo already knows exactly what question it was answering and can check the answer against that question directly, rather than having to first work out what was actually being asked. This ties into the same instruction-and-review discipline covered in the article on how firms document supervision to satisfy an SRA inspection, since a well-briefed piece of research leaves a cleaner paper trail of what was asked and what was delivered.
A fee earner who learns how to brief legal research well tends to find review takes a fraction of the time it used to, simply because there’s no ambiguity left to resolve at the review stage.
Does this change for urgent, same-day research requests?
The principle holds even more under time pressure, not less. A vague brief sent urgently produces a vague memo returned urgently, which then needs correcting under even more time pressure. A specific, narrow question, even dashed off quickly, gives a researcher the best chance of returning something usable on the first pass, which matters most exactly when there’s no time for a second one.
According to the Law Society’s guidance on legal research practice, well-scoped instructions are consistently identified as the single biggest factor in research turnaround quality, ahead of the researcher’s experience level. That holds whether the researcher sits down the corridor or works through an outsourced arrangement.
How does this differ from briefing document drafting or bundle preparation?
Research briefs carry more ambiguity risk than drafting or bundling instructions, because the output is analytical rather than mechanical. A bundling instruction, covered in the article on common mistakes in trial bundling, has a fairly fixed structure to aim for. A research question doesn’t, which is exactly why scope has to be defined explicitly rather than left implicit.
The same discipline applies across other categories of delegated work, from legal drafting to disclosure review, but research is where a vague brief does the most damage, since there’s no template to fall back on if the question itself isn’t clear.
What does a well-briefed research request actually save a fee earner?
Time on the review end, not just the research end. A memo that answers the right question the first time needs a quick sign-off rather than a rewrite, freeing the fee earner to spend that time on the client-facing work only they can do, the same principle behind embedded paralegal support more broadly. Over a run of matters, this compounds significantly, since every well-scoped brief avoids a second round trip that a vague one would have required.
Firms that get this right tend to build a small internal habit around it: a one-line question, the key facts, and the intended use of the answer, sent as a matter of course rather than reconstructed from scratch each time, an approach that pairs naturally with the packages on the Pricing page built around exactly this kind of recurring structured work.
Is there a risk in over-specifying the brief?
Some, though it’s a far smaller risk than under-specifying one. A brief that pins down the question too rigidly can occasionally miss a related issue a broader instruction might have surfaced. The fix isn’t to loosen the question back into a general topic, it’s to add a short second line flagging any adjacent issue worth a brief mention, while keeping the primary question narrow. This gets the best of both without reintroducing the scope problem that made the topic-based brief unusable in the first place.
Have a research question that needs a straight answer?
We’ll assign a dedicated paralegal to your matter for 7 days, no charge, so you can see how a well-briefed memo comes back before deciding anything.
Confidential · No obligation · Typically a 20-minute call
Frequently Asked Questions
How long should a legal research brief be?
Usually short. A specific question and the relevant facts matter far more than length; a few clear sentences outperform a long, unfocused brief.
Should the brief include the fee earner’s own view of the likely answer?
It can help, provided it’s flagged as a starting hypothesis rather than the expected conclusion, so the research isn’t unintentionally steered.
What is the most common mistake fee earners make when learning how to brief legal research?
Describing a topic instead of a question, which leaves the researcher to guess at scope rather than answer something specific.
