How to Build a Case Law Research Trail

Research that lives only in your head is research nobody can check. Three weeks later you cannot remember which terms you tried, a junior repeats the same searches from scratch, and when a senior asks whether you looked for the obvious contrary authority you have no honest answer. A research trail fixes this by leaving a record of what you searched, what you found, and why you kept or dropped each result. It is the difference between a conclusion someone can rely on and a conclusion they have to redo.

Write the question down before you search

An unwritten question drifts. Before touching a database, state the precise issue, the forum it will be argued in, and the facts that make it live. That framing tells you which court's decisions bind and which merely persuade, and it stops you collecting cases that are interesting but off the point. If the question changes as you read, record that too; a shifted question is a normal part of research, not something to hide.

Log searches as you run them

The value is in the boring detail. For each search worth remembering, capture:

• the database or source consulted
• the exact terms and filters used
• the date you ran it
• how many results you actually reviewed, not just how many were returned

This log is what lets you say, with a straight face, that you searched for the contrary line and either found it or can show where you looked. It also stops two people covering the same ground while a whole line of authority goes unexamined.

Record why each case stays or goes

A list of citations is not a trail. For every case you keep, note the court, the date, the paragraph that matters, and one line on why it helps or hurts. Just as important, note the ones you rejected and the reason: wrong forum, distinguishable facts, superseded by a later ruling. A reviewer learns as much from a well-reasoned exclusion as from an inclusion, and the excluded pile is where opposing counsel usually goes hunting.

Keep source and provenance attached

Save a link or citation that leads back to the original report, not a screenshot floating in a chat. Prefer neutral or reported citations that another lawyer can look up independently, and note where you read the full text rather than a summary. When the trail travels with the matter, the next person can open the actual judgment instead of trusting your paraphrase of it.

Note the case's current standing

A case that supports you today may have been doubted, distinguished, or overtaken by a larger bench. Part of the trail is recording that you checked, and what you found: whether the decision has been followed, whether a later ruling has qualified it, and against which source you confirmed it. Treat citator flags as a reason to open the primary text, not as a verdict you can cite.

Make the trail easy to resume

The test of a good trail is simple: could a colleague pick it up cold and carry on without repeating your steps? That means keeping the searches, the kept and rejected cases, and the open questions in one place tied to the matter, rather than in separate notes and downloads. Keeping the trail and the sources in a single matter workspace, such as Juniorlawyer, spares the next lawyer from rebuilding it.

Close by listing what remains open: authorities not yet verified, a contrary line still to be run down, a point awaiting a senior's view. A trail that names its own loose ends is far more useful than one that pretends to be finished, and it lets whoever reviews the note check every step against the reports themselves.