Skip to content
Writing Style Library

Memo

A formal internal document that puts a decision or policy on the record for a group, with a TO/FROM/DATE/RE header.

Memo

Section titled “Memo”

A memo is a formal internal document that puts a decision, policy, or position on the record for a group within an organization. Its defining hallmark is the structured header - TO, FROM, DATE, RE - which signals to the reader that this is not a conversational message but a formal statement intended for filing and future reference. A memo is written to be retrieved and re-read weeks or months after it was issued, not acted on by a single named recipient before the next meeting.

The register of a memo is institutional. It addresses the group as a whole, not a specific person with a specific task. This makes the memo the right format when a policy needs to be officially stated, when a decision needs to sit on the record so that future team members can find it, or when an announcement carries enough weight that it should exist as a standalone document outside of any email thread or chat channel. A well-written memo does not ask for a reply; it puts something in writing so there is no ambiguity about what was decided or communicated.

Unlike an email - a message optimized for the inbox scan, leading with a specific action request to named recipients - a memo is a standalone document that states something for the record and addresses the group as a whole. Email can carry action requests, FYIs, broad announcements, and durable records; the memo differs by being a formal standalone internal document with a TO/FROM/DATE/RE header, written to be filed and consulted outside an inbox thread. This distinction matters when choosing the format: if the document needs a reply or requires a named person to act, use an email. If the document needs to exist as an authoritative record that the organization can point to, use a memo.

Memos are typically 200 to 600 words. The opening line of the body should state the purpose directly below the header - no preamble. Supporting context follows, and a closing statement of what the memo establishes or confirms completes the document. Because a memo is read for reference rather than for action, its structure should favor clarity and retrievability over urgency cues.

Canonical template

Section titled “Canonical template”
TO: [Recipient group, team, or department]
FROM: [Author name and title]
DATE: [Date]
RE: [Topic - what this memo puts on record]


[Opening: one to two sentences stating the decision, policy, or position being established]


[Body: the context, rationale, or supporting detail the reader needs to understand the record]


[Closing: a statement confirming what this memo establishes or makes official]

When to use

Section titled “When to use”

Putting a policy decision on the record for a team or department, announcing an organizational change that needs to exist as a retrievable standalone document, formally communicating a position that future members or stakeholders will need to find, documenting a decision reached in a meeting so it exists outside of anyone’s notes, communicating to a group when no reply is expected or required.

When not to use

Section titled “When not to use”

When a reply is expected from a specific person (use email instead), when the communication calls for back-and-forth dialogue (use a meeting or a chat channel), when the audience is external to the organization (use a letter or a formal announcement).

Pairs well with

Section titled “Pairs well with”

executive, direct-communicator, matter-of-fact, candid, executive-summary

Often confused with

Section titled “Often confused with”

email: Email is a business inbox message whose subject line carries the summary and whose body is optimized for quick scanning, whether the message is an FYI, announcement, durable record, or action request. A memo is designed for the opposite purpose: it addresses the group as a whole, puts a decision or policy on the record for future reference, and does not prompt a reply. When a document needs a named person to act on it before a deadline, use email. When an organization needs an authoritative record to file and retrieve, use a memo.

Tells

Section titled “Tells”
  • A structured header - TO, FROM, DATE, RE - that identifies the document as a formal internal record
  • The RE line names the decision, policy, or position being put on record, not a task or a question
  • The body opens immediately below the header, stating the purpose in the first sentence without preamble
  • Group-addressed: the TO field names a role, team, or department, not a specific individual with a task
  • No call to action or reply requested - the document closes with a statement of record, not an ask
  • A formal institutional register that expects filing and future retrieval, not an inbox response
  • Self-contained: the document assumes no conversational history and no prior thread

Anti-patterns

Section titled “Anti-patterns”
  • Writing a memo when the communication needs a specific recipient to act - with a deadline, an approval request, or a named owner - That is better handled as an email: the inbox format can route a named action, owner, approval, or deadline directly to recipients; a memo addresses the group as a whole and puts something on the record, so using it for a targeted ask buries the action request inside a document-style header that signals reference, not response.
  • Opening the body with background or pleasantries instead of stating the decision or policy in the first sentence - A memo is read for reference: readers return to it to confirm what was decided. If the decision is buried in paragraph three, the memo fails at its one job.
  • Treating the TO/FROM/DATE/RE header as optional or decorative - The header is what makes a memo a memo; without it, the document is unclassified prose that loses the formal-record signal and cannot be efficiently filed or retrieved.

Failure modes

Section titled “Failure modes”
  • Bureaucratic inflation - the institutional formality of the memo overdone tips into impenetrable ceremony: every sentence is passive, hedged, and wrapped in official-speak until the actual decision is lost inside the form - State the decision plainly in the first body paragraph; formality lives in the header structure, not in circumlocution throughout the text.
  • Scope creep into treatise - the for-the-record register overdone turns one memo into a comprehensive document that tries to address every related nuance, caveat, and edge case until no one reads it fully - One memo documents one decision or policy; if multiple topics need documenting, write separate memos or restructure the content as a dedicated policy document.

Instruction

Section titled “Instruction”
Write as a memo. Begin with the structured header: TO (recipient group or role), FROM (author
name and title), DATE, and RE (the topic - what this memo puts on record). Open the body
immediately below the header with one to two sentences stating the decision, policy, or position
being established - no preamble. Follow with the context or rationale the reader needs to
understand the record. Close with a statement of what this memo confirms or establishes. Address
the group as a whole, not a specific individual with a task. Do not include a call to action or
request a reply - the memo states something for the record. Maintain a formal institutional
register; expect the document to be filed and retrieved, not replied to.

Template

Section titled “Template”

See the Memo template.

Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Executive, Direct Communicator, Matter of Fact, Candid, Executive Summary

Avoid with

Section titled “Avoid with”

Confessional, Reverent, Playful

Often confused with

Section titled “Often confused with”

Email

Examples

Section titled “Examples”

TO: Platform Engineering Team FROM: Maya Chen, Engineering Manager, Platform DATE: Monday, June 23 RE: Adoption of async-first standups as standing practice

This memo confirms that async-first standups are now standing practice for the Platform team. The 30-day trial that began May 19 is concluded, and the synchronous 9am Pacific standup will not return to the calendar.

The trial was a response to three problems recorded in ADR-0014. The 9am Pacific slot fell at 9:30pm for our India-based engineers, who attended at 3.2 of 5 sessions against 4.6 for US-based engineers. The meeting produced roughly four minutes of content that changed anyone’s behavior out of a fourteen-minute average. And verbal status left no record, which cost the team real time on three occasions last quarter when someone reworked a problem that had already been solved and discussed out loud. The trial replaced the meeting with a written update in #team-standup - posted by 10am local time, three fields, blockers routed by direct @mention.

The results held. On-time posting climbed from 78 percent in Week 1 to 85.5 percent by Week 2 and stayed near that level for the rest of the trial. Median time from @mention to substantive reply was 18 minutes, well inside the old pattern of blockers waiting until the afternoon for a response. India-based engineers posted every weekday for the first time in this team’s history. Two problems flagged mid-trial - posts running long, and on-call triage taking longer than the 10-minute target - were resolved with the three-bullet ceiling introduced at the Thursday working session; splitting the on-call rotation was considered and was not needed. Priya Raman reviewed the trial data ahead of the Day 30 review on June 19, and no objection was raised to making the format permanent.

This memo establishes the async standup format documented in docs/playbook.md as the Platform team’s default practice, effective immediately. The Thursday working session continues on its existing schedule. Team members joining after May 19 are expected to read docs/playbook.md as part of onboarding. No further trial review is scheduled; the format will be revisited only if a future retrospective surfaces a specific problem it cannot handle.