How Legal Memorandum Formatting Actually Works in Practice
I still get requests from junior associates who treat the legal memo layout like it's a creative writing exercise. It isn't. It's a document format built for one purpose: letting someone who hasn't read the file pull out the answer in under two minutes. The difference between a memo that gets read and one that gets forwarded to someone else usually comes down to structure, not substance. The standard memo layout has five components arranged in a specific order. The heading comes first with the to, from, date, and re lines. Then a brief statement of the question presented. Followed by the answer. Then the statement of facts. Then the discussion. This order isn't arbitrary. Partners read from the bottom up sometimes, but they almost always check the answer section before anything else. If the answer isn't there or isn't clear, they stop reading.
Building a Functional Legal Memo Layout
Start with the heading block. I see people waste fifteen minutes formatting this when it should take thirty seconds. The to line goes to the assigning partner or attorney. The from line is you. The date is the date of completion, not the date you start drafting. The re line should be a single line that describes the legal issue, not a case caption. Write something like "Whether a non-compete survives assignment of a commercial lease under California law" instead of just "Non-compete Issue." The question presented section is where most memos fail. Keep it to two or three sentences maximum. Frame it as a specific legal question that can be answered yes or no with supporting reasoning. I had a case last year where a senior associate wrote a seven-sentence question that actually contained two separate questions, a factual scenario, and a hint at the desired outcome. The partner who read it marked it up in red and wrote "pick one and move on." When the question is bloated, the answer section becomes unfocused and the discussion drags. The answer section deserves more space than you think it does. One paragraph. Direct. Then the IRAC breakdown in the discussion. Never bury your conclusion behind a wall of procedural history. I've seen memos where the answer was a single sentence hidden inside a three-paragraph introduction. That defeats the entire purpose of the format.
The facts section should be neutral. No arguments disguised as facts. If you need to argue a point, put it in the discussion. I remember a memo I reviewed where someone wrote "the defendant negligently failed to secure the premises" in the facts section. That's not a fact. That's a legal conclusion. The reader shouldn't encounter that until the analysis. I corrected it to "the defendant did not install the security gate required by the building code and did not post warning signs" and moved the negligence argument to the discussion. Saved me from having to flag it three separate times during review. The discussion section follows IRAC but with a practical adjustment. Lead with the controlling authority before you state the rule. Most junior writers state the rule abstractly, then cite the case. Start with the case, then extract the rule. It grounds the analysis immediately. I use a rule-by-rule structure when there are multiple elements. For a breach of contract claim, I don't write one long paragraph covering all four elements. I break it into four subsections. Each one gets its own italicized topic sentence that states what that element requires under the cited authority. This makes it easy to check whether an element was actually addressed. Counterarguments belong in the discussion, not as an afterthought. If you can see a strong opposing position forming while you're researching, address it head-on. A memo that ignores counterarguments reads like advocacy disguised as analysis. I once had a memo come back with a single note from a partner: "you didn't even try to argue the other side." The issue was straightforward, but the citation to a dissenting opinion in a closely split case made it worth discussing. Addressing it upfront actually strengthened the memo because it showed the reader you'd done the work.
Get the Full Details
For the citation format, stick to Bluebook if your firm requires it. Otherwise, use your jurisdiction's standard. Inconsistency in citation style within a single memo is more distracting than any minor formatting error. I use a quick reference check where I scan every parenthetical to make sure the reporter volume and page number match the case name. A wrong citation doesn't just look sloppy. It forces the reader to verify it, which breaks their reading flow and plants doubt about the rest of your research.
When the Standard Layout Doesn't Work
Not every memo fits the IRAC model cleanly. Complex regulatory issues with overlapping statutes often need a thematic structure instead of an elemental one. I had a memo last quarter dealing with a healthcare compliance question where the relevant regulations weren't organized by legal element at all. They were organized by obligation type: licensing, record-keeping, reporting, and enforcement. Forcing that into IRAC made the discussion repetitive and hard to follow. I restructured it around those four obligation categories and wove the legal analysis into each one. The partner who reviewed it said it was the clearest memo he'd read on the topic in six months. Length is another place where the standard format creates problems. Some firms want thirty-page memos. Some want five. The content doesn't change, only the level of detail in the discussion. I've learned to calibrate based on the reader. A memo for a senior partner who handles this type of work routinely gets less procedural background and more direct analysis. A memo for a partner who is encountering the issue for the first time needs more setup. I typically add two or three sentences of context per major point when the audience is unfamiliar with the area. The biggest limitation of the legal memo layout is that it assumes the writer knows the answer. When you're genuinely uncertain, the format can make you sound more confident than you actually are. I've seen associates write memos that read like they've resolved an issue when the case law is still developing or split across circuits. The structure pushes you toward a definitive answer. If the authority is unclear, state that uncertainty explicitly in the answer section. Don't let the format force a conclusion you don't support. I usually add a sentence like "the current state of authority does not yield a single clear answer" right after the direct response when that's the case. It's better to flag it than to let the partner draw their own conclusion from an overly polished memo.
Pedagogical memos or training documents often use a modified layout. These include a brief background section before the question presented, especially when the reader needs context about a factual scenario they haven't encountered. The background section should be no longer than one paragraph and should only include facts necessary to understand the legal issue. Extra case background belongs in the discussion where it supports the analysis. File naming is part of the layout workflow even though it isn't in the document itself. I name every memo with the date, the core issue, and a version number. Something like "20250115_noncompete_assignment_CA_v2.docx." It sounds mundane but it saves significant time when you're searching through a shared drive six months later. I've wasted more time looking for a memo because someone named it "Memo_0314_final_revised_updated.docx" than I care to admit. The legal memo layout is a tool, not a template you fill in blindly. Understanding why each section exists in its current position lets you adapt it when the situation calls for it. Most of the time, though, the standard structure is the right choice because it's what every reader in your firm already knows how to navigate efficiently. Deviating from it without a reason costs time for everyone who has to read it afterward.
