How to Maintain a Legal Research Update Log

The dangerous memo is not the wrong one; it is the one that was right last year. A partner reuses a note written for an earlier matter, unaware that a later ruling or an amendment has since shifted the ground, and the firm advises on a position that no longer holds. Research decays quietly. An update log is the antidote: a running record of when a note was last verified, what changed, and what is still open, so nobody has to guess whether a two-year-old conclusion can still be trusted.

Give every memo a header that ages

A research note should announce its own shelf life. At the top, record the question it answers, the scope it covers, who owns it, and the date it was last checked against current sources. A reader glancing at that header should be able to tell in seconds whether the note is fresh enough to rely on or overdue for review. A memo without a last-checked date is a memo asking to be trusted blindly.

Log changes, do not overwrite them

When you revisit a note, resist the urge to silently edit the conclusion. Instead, append a dated entry that records:

• what prompted the review, such as a new decision, an amendment, or a change in the facts
• which authorities you re-examined
• what changed in the analysis, and what held firm
• who made the update

Keeping the earlier reasoning visible lets a reviewer see why a position was revised rather than wondering whether it was ever considered. The history is part of the advice.

Decide what triggers a review

Not every note needs constant attention, so set clear triggers. A memo should be revisited when the facts or forum change, when it is about to be reused in a new matter, or when a development touches the authorities it rests on. For a matter that runs for months, schedule periodic checks rather than trusting that someone will remember. The point is to make review a routine, not a lucky accident.

Watch the moving parts, not the whole world

You cannot re-research everything on every pass, so target the parts that move. Note which statutory provisions, notifications, and leading cases the conclusion depends on, and confirm their current standing when you review. A decision may have been distinguished or overtaken; a provision may have been amended or newly notified. Check each load-bearing authority against a current primary source rather than assuming the note captured it once and for all.

Separate what is settled from what is provisional

An honest log distinguishes the parts of a note you have verified from the parts that rest on assumption or await confirmation. Mark clearly where a conclusion is firm, where it depends on facts still to be confirmed, and where a point remains genuinely open. That separation tells the next reader exactly how much weight the note can bear and where they still need to look.

Keep the log where the matter lives

An update log helps only if it travels with the note and the matter, not in a personal folder that leaves with the person who wrote it. Keep the memo, its sources, and its revision history together, tied to the matter, so anyone picking it up sees both the current position and how it got there. A workspace that keeps a matter's notes and their history in one place makes this far easier than stitching together scattered drafts.

When you next hand a memo on, close with a short line: last checked on this date, these authorities confirmed, this point still open. That single sentence turns a static document into a living one, and it lets whoever relies on it verify the position against current sources instead of trusting that it aged well.