How to Write a Memo People Actually Read

A memo is the most misunderstood document in office life. Done well, it is the fastest way to get a decision made, a policy understood, or a project moving: one page, one point, and a reader who knows what to do when they finish. Done badly, it is a wall of text nobody finishes. The difference comes down to one discipline — bottom line up front — and a format that respects the reader's time.

What a memo is actually for

A memo (short for memorandum) is an internal written message that records a decision, announces a change, or asks for action. It is not a chat message, which is for quick back-and-forth, and it is not an email thread, which sprawls. A memo is for the things that need to be findable later: a policy change, a project decision, a procedure, or a summary of what was agreed.

That archival role is why memos still matter in workplaces full of instant messaging. When someone asks, six months later, "When did we decide that?" the memo is the answer. Write it as if a new hire will read it cold in a year — because eventually, one will.

BLUF: bottom line up front

The single most important memo technique is BLUF: put the bottom line in the first paragraph. State the decision, the request, or the news before any background. Readers decide in seconds whether to keep reading, and a memo that opens with three paragraphs of context has already lost most of them.

Compare the two openings. Weak: "Over the past several months, the onboarding team has reviewed a number of processes with an eye toward efficiency, and after considerable discussion, several changes have been identified." Strong: "Starting November 2, all new client accounts use the revised onboarding checklist attached below. The change cuts setup time from four days to two." The second version can be acted on immediately, and the background can follow for anyone who wants it.

The header: To, From, Date, Subject

Every memo opens with the same four header lines, and each one earns its place:

• To: the people who need to act or know. Be specific — a named team or role, not "everyone."
• From: the author, so questions have a destination.
• Date: the date the memo takes effect or is issued, which matters when policies change.
• Subject: a short, specific summary of the point, written as a headline, not a topic. "New client onboarding checklist, effective November 2" beats "Onboarding."

The subject line is doing real work here. It is how the memo gets found in a search six months later, and it is how a busy reader triages their inbox. Spend thirty seconds making it specific.

A structure that works every time

After the header, a reliable memo follows four parts, in this order:

1. Purpose. One or two sentences stating the decision or request. This is the BLUF paragraph.
2. Background (brief). Only the context a reader needs to understand the decision — what changed, and why now. Two or three short paragraphs at most.
3. Action or details. What changes, who does what, and by when. Use a short list, not a paragraph, when there are multiple steps.
4. Closing. One line for questions, naming a person and a way to reach them, and noting any attachments.

Resist the urge to add a fifth section for caveats, history, and edge cases. If an edge case genuinely matters, it belongs in an attachment or a linked procedure, not in the memo itself.

Length rules: one page is the goal

A memo should fit on one page whenever possible, and almost never needs more than two. That limit is a feature, not a constraint: it forces the writer to decide what the point is. If a draft runs to three pages, the problem is rarely that the topic is too big. It is usually that the memo is trying to make three points, and it should be three memos, or one memo with attachments.

Use short paragraphs, headings for the sections above when the memo runs past a page, and bullet points for any list longer than three items. Dense blocks of text are the fastest way to lose a reader who was willing to read the first paragraph.

Tone: direct, neutral, and human

Memo tone should be direct without being blunt, and formal without being stiff. Write in plain language, avoid jargon your readers do not share, and never use a memo to scold a whole team for one person's mistake — that message belongs in a private conversation. When a memo announces an unpopular change, say so plainly, give the reason in one sentence, and say what happens next. Readers accept bad news far more readily than evasive news.

Worked example: a memo that fits on one page

Here is a complete memo using the structure above:

To: Client Onboarding Team
From: Dana Whitfield, Operations Lead
Date: October 26, 2026
Subject: New client onboarding checklist, effective November 2

Purpose: Starting November 2, all new client accounts use the revised onboarding checklist attached below. The change cuts setup time from four days to two.

Background: The old checklist asked for the same tax document twice and routed approvals through two managers. The revised version removes the duplicate request and assigns a single approver per account.

Action: (1) Use the attached checklist for every account opened on or after November 2. (2) Finish accounts already in progress on the old checklist; do not restart them. (3) Send questions to Dana by October 30 so the team can resolve them before launch.

Closing: Questions? Contact Dana Whitfield. Attachment: Revised Onboarding Checklist (1 page).

Every element is there — decision, reason, steps, deadline, contact — in under 200 words. A reader can act on it in two minutes and find it again in a year by searching "onboarding checklist."

When not to write a memo

Not every message deserves memo treatment. Do not write a memo for a quick question (use chat), a sensitive personnel matter (use a private conversation), or a discussion that needs input (use a meeting or a shared document). A memo announces or records; it does not brainstorm. If you need a reply from everyone, you probably need a meeting, not a memo with a long CC list.

Five mistakes that make memos unreadable

• Burying the point. Background before the decision is the most common memo failure, and BLUF fixes it.
• A vague subject line. "Update" and "FYI" tell the reader nothing and make the memo unfindable later.
• Writing for the file, not the reader. A memo padded with legalistic hedging protects no one and convinces no one.
• Mixing three messages into one. One memo, one point. Attachments carry the rest.
• Forgetting the action and deadline. A memo that informs but never says who does what, by when, creates a second round of messages to clarify it.

Frequently asked questions