Write a Legal Memo That Survives Partner Review
The most common way a first memo draft fails isn't bad analysis. It's a weak point that only surfaces when a partner asks the obvious question three paragraphs before the conclusion, costing a full review cycle that a more honest first draft would have avoided. An associate who spends real hours building a strong affirmative case can lose most of that credibility in one meeting if the partner's first question is the exact weakness the memo never mentioned.
Warning
A memo that only presents your strongest argument isn't more persuasive. It just means someone else finds the weak point instead of you, later, when it's more expensive to fix.
The best memo isn't the one with no weaknesses. It's the one that names its weakest point before anyone has to ask.
Why a blank page makes this worse
Starting a memo from nothing tends to produce whichever structure comes to mind first, which is usually the strongest argument, expanded at length, with the counterargument mentioned briefly near the end if at all. That ordering feels natural to write and reads as evasive to a reviewer who already suspects there's a weak spot. An experienced partner reading a memo on a non-compete's enforceability already knows, before reading a word, that the missing geographic limit is going to be the hardest part of the analysis, and a memo that buries that issue reads as either naive or evasive, neither of which is the impression an associate wants to leave.
Before: draft the strongest argument first, add a brief counterargument paragraph near the end, submit for review.
After: draft issue, brief answer, and analysis together, with the counterargument built into the analysis itself, then ask directly what the single weakest part of the position is before anyone else finds it.
A process for a memo that holds up under review
- 1
State the issue and key facts before asking for analysis
Give Claude the actual question presented and the facts that matter, including the ones that cut against your position. Leaving out unfavorable facts produces analysis that doesn't hold up once a reviewer adds them back in.
- 2
Ask for the standard structure: issue, brief answer, facts, analysis, conclusion
A memo missing one of these sections reads as incomplete regardless of how strong the analysis inside it is. Asking for the full structure up front avoids a second pass just to add what's missing.
- 3
Ask Claude to isolate the single weakest part of the position
Not "what are the risks" in general, which invites a hedge-everything answer, but specifically which single point a skeptical reader would push on first.
- 4
Revise the analysis around that weak point directly
Once it's named, address it in the memo itself rather than hoping the reviewer doesn't notice. A memo that raises and answers its own hardest question reads as more, not less, confident.
Here's a prompt that starts the process:
We need a memo on whether our client's non-compete is enforceable under Texas law, given a 2-year term and no geographic limit. Structure it as issue, brief answer, facts, analysis, and conclusion, and flag the weakest part of our position before I ask.
”For a memo going to a partner who's reviewed similar issues before, it's worth asking Claude to note explicitly how this fact pattern differs from the typical case, since a partner's first instinct is often to compare against precedent they already know well, and a memo that anticipates that comparison reads as more thoroughly considered.
This partner has reviewed several non-compete enforceability memos before. Note explicitly how this fact pattern, specifically the missing geographic limit, differs from the more typical case where geography is defined, since that's likely to be their first point of comparison.
”
Inside Claude Tutorial
Naming the weakest point before anyone else does is transferable.
Surfacing the hardest question in your own argument, instead of hoping it goes unnoticed, is useful in any kind of structured written analysis. The app has a full lesson on this exact pattern.
Handling the weak point once it's named
Naming the weak point is only useful if the memo actually addresses it, rather than mentioning it and moving on. A memo that flags its own weakness and then doesn't engage with it substantively has done half the job, and the half it skipped is the more important one.
Tip
Ask Claude to draft the counterargument as if it were being made by opposing counsel, then respond to that version directly in the memo. Responding to a real, specific version of the opposing argument reads as far more credible than a generic "some may argue" paragraph.
Draft the strongest version of the counterargument, as if you were opposing counsel arguing the non-compete is unenforceable due to the missing geographic limit, then write our response to that specific argument for the memo.
”If the counterargument turns out to be genuinely strong, it's worth asking directly whether the memo's overall conclusion should shift, rather than writing a response that technically addresses the point while quietly holding onto the original recommendation regardless of how persuasive the counterargument actually is.
Having drafted opposing counsel's strongest argument, be honest: does it meaningfully weaken our position, or does our response genuinely hold up? If it weakens our position more than the current brief answer reflects, say so directly.
”Keeping the brief answer honest
The brief answer at the top of the memo is often the only part a busy partner reads closely on a first pass, which makes it the easiest place for a hedge to hide an actual weakness.
Common mistake
Writing a brief answer so qualified it doesn't actually commit to a position. "It depends" is rarely wrong, but it isn't useful either. Ask Claude for a brief answer that takes a real position and states the confidence level plainly, rather than hedging around every variable.
Rewrite the brief answer to state our actual recommended position clearly in the first sentence, then note the confidence level and the one factor most likely to change the outcome.
”Continue reading
- Turning Deposition Notes into a Clear Case Summary: building the factual record a memo like this often draws on.
- Reviewing Contracts with Claude Without Missing the Risky Clause: the same habit of naming what's missing, applied to a document instead of an argument.