The legal memorandum is the workhorse document of legal practice and law school writing courses. Unlike a brief filed with a court, a memo is an internal document that provides an objective analysis of a legal issue. Its purpose is to inform — not persuade — and that distinction shapes every aspect of how you write it. A supervising attorney relies on your memo to understand the strengths and weaknesses of a client's position, so accuracy and candor are paramount.
Most law school legal writing courses introduce the office memorandum in the first semester, and the skills it develops — issue identification, rule synthesis, analogical reasoning, and counterargument analysis — form the backbone of legal analysis. The standard organizational framework is IRAC (Issue, Rule, Application, Conclusion) or its more refined cousin CREAC (Conclusion, Rule, Explanation, Application, Conclusion), which front-loads your answer for busy readers.
The single most important quality of a legal memo is intellectual honesty. You must address unfavorable authority head-on rather than ignoring it. A memo that presents only the favorable side of an argument is worse than useless — it gives the attorney a false sense of confidence that can lead to embarrassment in court or bad advice to a client.
Document Structure
Heading
Identify the memo's author, recipient, date, and subject matter at a glance.
Use the standard format: TO, FROM, DATE, RE. The RE line should be specific enough that the reader can identify the client and issue without reading the memo. For example: 'RE: Johnson v. ABC Corp. — Whether email constitutes written notice under Section 4.2 of the lease agreement.'
Question Presented
Frame the precise legal question your memo answers.
Write this as a single sentence that weaves together the legal standard and the key facts. The 'under-does-when' format works well: 'Under [legal standard], does [legal question] when [key facts]?' Keep it to one to three sentences maximum.
Brief Answer
Give the reader your bottom-line conclusion up front.
Start with a direct answer (Probably yes / Probably no / It depends) followed by 2-4 sentences explaining why. This section exists for the busy partner who may not read beyond the first page. Make sure it tracks your Question Presented exactly.
Statement of Facts
Present all legally relevant facts in a neutral, chronological narrative.
Include both favorable and unfavorable facts. Write in past tense and present the facts as a story — do not use bullet points or legal jargon. Include only facts you actually use in the Discussion section; if a fact does not appear in your analysis, it does not belong in your Statement of Facts.
Discussion
Analyze the legal issue using IRAC or CREAC structure.
This is the core of your memo. State the governing rule, explain it using case illustrations, apply it to your facts, and address counterarguments. Use topic sentences that advance your analysis. Each paragraph should have a clear purpose. Use headings and subheadings for complex analyses.
Conclusion
Summarize your analysis and provide a practical recommendation.
The conclusion should be 1-2 paragraphs. Restate your answer, briefly summarize the key reasons, and note any significant uncertainties or additional information that could change the analysis. If appropriate, suggest next steps.
Do's and Don'ts
Do
- Front-load your analysis — put your conclusion at the beginning of each IRAC section, not just at the end
- Address counterarguments and unfavorable authority directly in your Discussion section
- Use case illustrations that are factually analogous to your client's situation
- Write clear topic sentences that signal where your analysis is going
- Include pinpoint citations for every legal proposition
- Proofread for Bluebook citation errors — they undermine your credibility
Don't
- Do not advocate — a memo is objective analysis, not a persuasive brief
- Do not ignore unfavorable cases or facts — address them and explain why they may not control
- Do not write a 'book report' that summarizes cases one by one without synthesizing the rule
- Do not use conclusory analysis — show your reasoning, do not just state your conclusion
- Do not include facts in the Statement of Facts that never appear in the Discussion
- Do not use first person ('I think') — the analysis should speak for itself
Before & After Examples
Before
Under the mailbox rule, the acceptance was effective. In Adams v. Lindsell, the court held that acceptance is effective upon dispatch. Here, the plaintiff mailed the acceptance on March 1. Therefore, the acceptance was effective on March 1.
After
The acceptance was likely effective upon mailing on March 1 under the mailbox rule. Under the common law, an acceptance is effective upon proper dispatch, even before the offeror receives it. Adams v. Lindsell, 106 Eng. Rep. 250 (K.B. 1818). In Adams, the court held that a letter of acceptance created a binding contract when posted, not when received, because placing the risk of postal delay on the offeree would make contract formation impractical. Here, the plaintiff deposited a properly addressed and stamped acceptance letter on March 1 — three days before the offer's March 4 expiration. Like the acceptance in Adams, the plaintiff's letter was properly dispatched to the correct address with adequate postage. However, Defendant may argue that the email sent on March 2 revoking the offer was effective before the letter arrived. This argument likely fails because under the mailbox rule, a properly dispatched acceptance takes precedence over a subsequently communicated revocation.
The improved version uses CREAC structure (conclusion first), includes a case illustration with factual parallels, applies the rule to the specific facts, and addresses a counterargument. The weak version is conclusory — it states the rule and conclusion without showing the analytical work.
Before
Question Presented: Is our client liable for negligence?
After
Question Presented: Under Illinois negligence law, is a commercial property owner liable for injuries sustained by a business invitee who slipped on a wet floor near the entrance when the owner had constructive notice of the hazardous condition for approximately forty-five minutes but had not placed warning signs or mats?
The improved version incorporates the jurisdiction, the specific legal standard, the parties' relationship, and the critical facts. The vague version provides no useful information and could apply to any negligence case in any jurisdiction.
Before
In Smith v. Jones, the court found the defendant liable. In Brown v. White, the court also found liability. Therefore, our client is probably liable too.
After
Courts consistently impose liability where a property owner has constructive notice of a hazardous condition and fails to take reasonable remedial steps. In Smith v. Jones, 450 N.E.2d 123 (Ill. App. 2003), the court held a grocery store liable when an employee was aware of a spill for over thirty minutes but failed to place cones or clean the area. Similarly, in Brown v. White, 512 N.E.2d 456 (Ill. App. 2008), liability attached where security camera footage showed a puddle near the entrance for approximately one hour during business hours. Here, the surveillance footage establishes that the wet floor condition existed for at least forty-five minutes during peak hours, placing our client's situation squarely within the range where Illinois courts have found constructive notice sufficient to establish a breach of duty.
The improved version synthesizes a rule from multiple cases, provides factual details from each case illustration, and draws explicit parallels to the client's situation. The weak version merely lists case outcomes without explaining why they are relevant or how they connect to the facts at hand.
Common Mistakes to Avoid
Writing a 'case dump' that summarizes cases individually instead of synthesizing a coherent rule from multiple authorities
Omitting counterarguments — a memo that only presents one side is not objective analysis
Using conclusory application that states a conclusion without showing the analytical reasoning
Including unnecessary background facts that never appear in the Discussion section
Failing to use IRAC/CREAC structure, resulting in disorganized analysis that is hard to follow
Writing an overly broad Question Presented that does not incorporate the specific facts of the case
Neglecting to address the standard of proof or burden of persuasion when it matters to the analysis