Writing a Memorandum That Doesn't Waste Everyone's Time
A memorandum is an internal written communication used within an organization to convey policy changes, procedural updates, incident reports, or recommendations. It sits somewhere between a formal letter and a casual email. That ambiguity is where most people mess it up. The standard format has five parts: the header (TO, FROM, DATE, RE), an opening statement of purpose, background context, the body with analysis or details, and a closing with recommended action or next steps. Keep it to one page whenever possible. Anything longer gets read by no one.
Memorandum Example
Here is what a working memo looks like in practice. The TO line lists the audience. The FROM line identifies the author and their role. The DATE field should always include the full date, not just the day. The RE line is the subject header — make it specific enough that someone scanning a filing system can find it later. I see too many memos with RE lines like "Meeting Notes" or "Update," which are useless for retrieval purposes. Write "Request for Q3 Budget Reallocation — Facilities Department" instead. The opening paragraph should state the memo's purpose in the first two or three sentences. Never bury the lead. The person reading this likely has forty minutes and three other things demanding attention. Give them the bottom line immediately, then provide supporting detail afterward. This is the inverted pyramid structure borrowed from journalism, and it works here because busy professionals have the same constraints as editors. The body contains the factual substance. Present data, timelines, and context in a logical sequence. Use numbered or bulleted lists when you have multiple items. Paragraphs should be short — three to four sentences maximum. Walls of text signal that the writer hasn't thought clearly about what they are trying to communicate.
I once spent three weeks trying to get a compliance memo approved that discussed data retention policy changes. The problem was not the content. The problem was that the memo referenced a prior directive by its internal code number rather than its title and date. Anyone outside the original drafting team could not verify the source. I rewrote the entire section to include the full citation — document title, issuing authority, and publication date — along with a link to the original text. The compliance team approved it the same day. That was the difference between a memo that functions and a memo that gets bounced back for revisions. The closing section should specify what action, if any, the reader needs to take. If the memo is informational only, state that explicitly. "For your awareness" or "No action required" saves the recipient from wondering whether they owe a response. If action is needed, include a deadline and specify the format of the required reply. One counter-intuitive thing about memoranda that most people miss: the memo format itself carries institutional weight. Even when the content is routine, sending something as a formal memo rather than an email changes how people treat it. It signals that the matter has been thought through and that the author stands behind the content. That matters in litigation-adjacent environments where documentation trails become evidence. I have seen internal memos used as exhibits in employment disputes simply because they were signed and dated on company letterhead. Email threads do not carry the same gravity in those contexts.
Get the Full Details
Another nuance people overlook is the distribution list. A memo sent to the wrong audience generates more follow-up work than it saves. If the memo concerns a technical specification change, sending it to the entire company creates noise. Send it to the affected departments and cc those who need visibility. Less distribution means fewer clarifying questions, which means less time spent answering them. The main downside of the memorandum format is that it requires more discipline to write well than an email does. People cut corners. They omit the date. They skip the RE line. They write in fragmented prose because they treat it like a chat message with a formal wrapper. The result is a document that fails its primary function: clear, permanent, retrievable communication. When a memo cannot be understood without a follow-up conversation, it has already failed. A practical workaround for the corner-cutting problem is to use a template with mandatory fields. Require the author to fill in every section before the memo can be submitted. Even a simple form that blocks submission until the TO, FROM, DATE, RE, and action-required fields are populated eliminates roughly sixty percent of the poorly constructed memos I encounter. The remaining forty percent usually come from people who treat templates as suggestions rather than requirements, and no automated fix will help with those.
If your organization needs a template, you can find standard formats from the Government Publishing Office, the Harvard Law School library memorandum guide, and various state bar association resources. Many of these are freely available as downloadable documents. The structure across all of them is essentially the same because the format evolved from military and government correspondence standards that predate email by decades. The core logic has not changed. Write the memo as if it might be read five years from now by someone who was not involved in the original discussion. That person might be an auditor, a new manager, or a lawyer. Clarity now prevents confusion later. The time investment is minimal — maybe ten minutes longer than writing a quick email — and the payoff is a document that does its job without requiring revision.
