Legal Memos That Non-Lawyers Can Actually Act On

The average legal memo has two audiences. The first is the lawyer who requested it, or who will review it before it goes further. The second is everyone else — the CEO who will decide whether to proceed, the board member who will vote on the transaction, the regulator who will determine whether the company's position is defensible, the operations manager who needs to know what the legal constraint actually means for next Tuesday's work. The second audience is usually larger, usually has more decision-making authority, and is almost never the one legal writing is optimized for.

This is a structural problem, not a quality problem. Lawyers are trained to write for legal audiences: courts that need every qualification stated, opposing counsel who will exploit any gap, appellate reviewers who will read every sentence precisely. The writing skills that serve those audiences — exhaustive qualification, careful hedge-stacking, precise use of defined terms — are precisely the skills that make legal memos unreadable to the business leaders they're meant to inform.

The Plain Writing Act of 2010 requires federal agencies to use clear government communication that the public can understand and use. Its application to legal writing within government agencies is direct. Its lessons for private-sector legal communication are equally direct, even where they are not required: a memo that the reader cannot understand and use has not done its job, regardless of its legal precision.

The Verdict-First Problem

The most common structural failure in legal memos written for business audiences is the buried conclusion. Legal writing training often emphasizes building toward a conclusion — presenting the facts, the applicable law, the analysis, and then the conclusion. This structure serves an audience that wants to follow the reasoning and assess it step by step. It does not serve a CEO reading at 6:45 a.m. before a board meeting.

Research on how executives read documents is consistent: readers in high-decision-load environments use the first two paragraphs to determine whether a document is worth reading in full. A memo that opens with background and statute citations has already lost most of its non-lawyer audience before it reaches the conclusion they actually needed.

The fix is the BLUF structure — Bottom Line Up Front. The first paragraph of a legal memo written for a mixed audience should state: what the legal question is, what the answer is, and what the reader needs to do with it. Everything that follows is support for that conclusion. A reader who needs to take action has what they need immediately. A reader who wants to understand the reasoning can read on.

How Courts and Regulators Actually Read Legal Documents

Lawyers often assume that the precision appropriate for court filings is also appropriate for internal legal memos and business communications. This assumption confuses two different reading environments with very different consequences for imprecision.

Federal courts, including the Supreme Court, have repeatedly emphasized that legal briefs should be clear, direct, and accessible. Chief Justice Roberts, writing in 2021 guidance on brief quality, noted that the most effective advocates present complex legal arguments in plain terms that the court can grasp quickly. The clerks who do initial brief screening read under significant time pressure; a brief that cannot be summarized by a first-year clerk is a brief that has already failed its first audience test.

Regulatory agencies face similar reading constraints. The SEC's Plain Writing Initiative, launched under the Plain Writing Act, specifically requires that regulatory filings be written in clear, concise language. The FDA's guidance on drug labeling uses readability standards drawn from educational testing research. These agencies are not asking for less precise documents — they are asking for documents whose precision is expressed in accessible language, because their staff who must act on the documents are not always attorneys.

The practical lesson is that legal precision and accessible language are not opposites. The confusion arises from legal training that equates complexity of language with rigor of analysis. A memo can be legally airtight and written in plain English. The analysis drives the rigor; the language carries it.

Legalese and Why It Undermines the Memo's Actual Purpose

Legalese — defined terms stacked in Latin phrases, passive constructions that obscure agency, sentences that span multiple subclauses — serves a specific purpose in documents where every word is being read by a trained reader looking for gaps. In memos written for general business audiences, legalese produces the opposite effect: it signals authority without delivering it, and it forces non-lawyer readers to either guess at meaning or stop reading.

Professor Richard Wydick's plain language research, consolidated in his widely used text Plain English for Lawyers, identifies several specific legalese patterns that consistently reduce comprehension without adding precision:

• Nominalizations — converting verbs to nouns ("make a determination" instead of "determine") that add syllables while removing the sentence's action word
• Throat-clearing preambles — opening sentences with "It is important to note that" or "As a preliminary matter" before the actual point
• Multiple negatives — "not unlikely to be considered non-compliant" instead of "probably violates"
• Latin terms with English equivalents — "inter alia" (among other things), "ab initio" (from the beginning), "mutatis mutandis" (with necessary changes) used in documents where plain English would serve equally well

Each of these patterns has a place in specific legal contexts. None of them belong in the first three paragraphs of a memo addressed to a CFO who needs to decide whether to close a transaction by Friday.

Undefined Terms and the Hidden Reading Failure

Legal documents rely on defined terms for precision — a "Material Adverse Effect" in a merger agreement has a precise contractual meaning that differs from the ordinary meaning of those words. Defined terms are necessary and appropriate in contracts, where they will be read by counsel and where the definition controls the outcome.

In advisory memos and business communications, undefined terms create a different problem: readers who encounter a term they don't understand will either guess at its meaning or skip the sentence. Neither outcome serves the memo's purpose. A memo advising on HIPAA compliance that uses "covered entity," "business associate agreement," and "protected health information" without explanation is a memo that will not drive compliant behavior in the operations team that reads it.

The solution is not to avoid defined terms — it is to define them on first use in plain language. "A business associate agreement (a contract that governs how your vendor handles patient data on your behalf)" takes one parenthetical and transforms a term of art into an actionable concept.

Hedge Stacking: Precision That Reads as Evasion

Legal writers hedge because legal analysis is inherently probabilistic — law is fact-dependent, jurisdictionally variable, and subject to interpretation. Appropriate hedging is part of honest legal advice. Hedge stacking — accumulating multiple qualifications in a single sentence or paragraph — is a different problem: it is accurate hedging that reads as evasion.

The practical consequence is that a memo full of hedge stacks produces no decision. A general counsel who tells the CEO "the proposed arrangement may be subject to regulatory challenge under certain circumstances depending on how the relevant agency interprets the applicable standard" has given the CEO no basis for decision. A GC who says "this arrangement is likely to be challenged by the FTC under its current enforcement posture; based on comparable enforcement actions, I estimate a 40% probability the challenge succeeds; here are the steps that reduce that risk" has given the CEO something to act on.

The plain language movement in legal writing, documented extensively in the work of Bryan Garner and the Plain Language Action and Information Network (PLAIN), specifically addresses hedge stacking as a readability failure. The guidance is consistent: state your best assessment directly, then explain the conditions under which it might be wrong. Do not stack the conditions before the assessment.

The GC-to-CEO Memo: What Works

The memos that drive executive action share a structure that is almost universal among effective legal communicators:

1. One-sentence bottom line — the legal conclusion in plain language
2. One-sentence consequence — what it means for the decision being made
3. Recommended action — specifically what the reader should do, by when, and who else needs to be involved
4. Key facts that drive the analysis — the two or three facts that most significantly affect the legal conclusion
5. Primary risks and conditions — what would change the analysis and how significant those risks are
6. Full analysis — for readers who want the reasoning, available but not required to reach the conclusion

This structure serves every reader simultaneously. The executive who reads only paragraphs one through three has enough to make a decision. The board member who reads through the risks section has a complete picture of the legal landscape. The in-house lawyer who reads the full analysis can assess the reasoning. The document does not require any of these readers to read the sections intended for other audiences.

Regulatory Submissions and Plain Language Requirements

The plain language requirement is increasingly explicit in regulatory contexts. The Plain Writing Act of 2010 requires all federal agencies to use plain writing in documents that "are necessary for obtaining any federal government benefit or service or filing taxes, provide information about any federal government benefit or service, or explain to the public how to comply with a requirement the federal government administers or enforces." This scope covers an enormous range of compliance documents and regulatory submissions.

The Office of the Federal Register's Document Drafting Handbook provides specific guidance on plain language requirements for regulatory text, including active voice, short sentences, common words, and tables or lists for complex material. These requirements apply to regulatory submissions and agency correspondence, not just to agency-authored documents — meaning that comments, petitions, and filings addressed to federal agencies benefit from the same plain language treatment.

Agencies that receive comments on proposed rules are staffed by analysts who read dozens of public comments in condensed review periods. A comment that states its legal argument clearly in the first paragraph, provides specific statutory and regulatory citations in the second, and places detailed technical support in an appendix is a comment that gets read and understood. A comment that requires the analyst to excavate the argument from 15 pages of background has a significantly lower probability of influencing the rulemaking record.

What Expert Readers Actually Notice

Lawyers and legal analysts reading a memo or legal document for expert purposes are primarily looking for two things: the quality of the analysis and the quality of the authority. They are not primarily assessing the writing, but poor writing creates friction that makes the analysis harder to evaluate.

A memo with a strong legal analysis buried in passive constructions and hedge stacks will receive a lower assessment of its analytical quality than the same analysis written clearly. This is not a bias — it reflects the real-world difficulty of separating the quality of an argument from the clarity with which it is presented. When the presentation creates friction, the reader's cognitive resources are spent on parsing the language rather than evaluating the reasoning.

The specific patterns that flag a memo's quality problems to expert readers are the same ones that cause non-lawyer readers to disengage: buried conclusions, undefined terms of art, sentences that require re-reading, and qualifications that precede rather than follow the point they qualify. An expert reader can work through these obstacles. A business reader will not.