How to Write a Memo: Structure, Format, and Examples
TL;DR: The essentials of writing a memo
- A memo is an internal document. Use it to inform a team, department, or whole organization about a decision, policy change, or action they need to take.
- Every memo opens with a four-line header: TO: the recipients, FROM: the sender, DATE: written in full, and SUBJECT: a specific description of the topic.
- The body has three parts. Open with a one-sentence purpose statement. Follow with the context and details. Close with the action items or next steps.
- Memos are formal but concise. One page is the target. Avoid contractions, keep sentences short, and get to the point in the first line.
- Memos do not use salutations ("Dear Ms. Smith") or complimentary closings ("Sincerely"). Both belong to formal letters, not memos.
- Six types cover most business needs: announcement, request, confirmation, directive, update, and response.
Learning how to write a memo is one of the most useful business writing skills you can develop. Memos are the format businesses reach for when they need to inform a team about a decision, direct a group to take a specific action, or document something for the internal record. Unlike email, which ranges from a two-line message to a multi-paragraph explanation, memos have a defined structure that makes them predictable to read and easy to file. Unlike formal letters, they skip the salutation and closing conventions because they travel inside the organization rather than out to a client, agency, or government body.
This guide covers what a memo is and when to send one instead of an email or a formal letter. It walks through the five elements that make up the standard memo structure. It covers six of the most common memo types with full worked examples. It includes guidance on tone and register, common mistakes to avoid, and a side-by-side comparison of memos, formal letters, and business email. If you are writing a memo for the first time or refreshing your skills for a new role, working through the sections in order will give you the full picture. If you are looking for a specific example, jump to the "Six Common Types of Memos" section.
What Is a Memo?
A memo, short for memorandum, is a written communication used inside an organization. It travels from one person or department to a defined internal audience: a team, a department, a division, or the whole organization. The purpose is to inform recipients about a specific matter and, in most cases, to request or direct specific action. Memos are used to announce policy changes, communicate decisions, provide project updates, document conversations, deliver instructions, and record internal actions that need to be preserved.
Memos have three characteristics that distinguish them from other business writing. First, they are internal. A memo is written for people inside the organization, not for clients, customers, vendors, or external partners. Second, they are structured. Every memo opens with the same four-line header (TO, FROM, DATE, SUBJECT) and follows a predictable body structure that makes the purpose visible on the first read. Third, they are formal but concise. The register is professional and the writing is direct. Most memos fit on a single page. Longer memos usually indicate that the writer has not yet decided what is essential.
When to Send a Memo vs. an Email vs. a Formal Letter
The choice between a memo, an email, and a formal letter depends on the audience, the formality required, and whether the communication needs to be filed as an official record. Each format has a role that the other two do not fill well.
Send a memo when the communication is internal, when the recipient is a group rather than an individual, and when the content needs a structured format for filing or reference. A memo is also the right choice when the information should carry the weight of a formal internal document rather than a routine message. Policy changes, procedural updates, project status reports for leadership review, and directives from management are the kinds of communications that benefit from memo format. A memo signals to recipients that the content is official, structured, and worth reading carefully.
Send an email for routine communications, quick questions, informal updates between individuals, and any message where the content does not need to be filed as an official document. Email is the default for day-to-day workplace communication. It is faster, less formal, and easier to reply to. The tradeoff is that email is easy to overlook in a busy inbox, so a memo can be the better choice when you need the recipient to actually notice and act on the content.
Send a formal letter when the recipient is external to the organization, when the correspondence needs to follow traditional business letter conventions with a salutation and closing, and when a paper record is expected. Job applications, complaint letters to external companies, letters to government agencies, recommendation letters for external opportunities, and legal correspondence all belong to the formal letter format. For a full guide on formal letter structure and conventions, see our article on how to write a formal letter.
The Standard Structure of a Memo
Every memo contains the same five structural elements. The consistency of this structure is one of the format's practical advantages: recipients know where to look for what they need. If you have to write a memo for the first time or in a new organization, following this structure will make your memo read as professional and predictable.
1. The header block
Every memo opens with a four-line header. Each line begins with a bold label followed by the information: TO, FROM, DATE, and SUBJECT. The header block appears at the top of the memo, above the body, and is separated from the body by one blank line. Some organizations add a CC line for people who should receive a copy but are not primary recipients. The four required fields are the same across almost every organization.
The TO line names the primary recipients. Use titles and department where relevant: "All Marketing Team Members," "Members of the Compensation Committee," "Regional Sales Managers." The FROM line names the sender, including title. The DATE line uses the full date, written out to avoid the American vs. British ambiguity of numeric formats. "March 15, 2026" or "15 March 2026" is unambiguous. The SUBJECT line is specific and descriptive. "Q1 Budget Review" is better than "Budget." "Updated Expense Report Procedure Effective April 1" is better than "New Procedure." A specific subject line helps recipients understand the memo's purpose at a glance and helps the memo get filed correctly later.
2. The opening statement
The first paragraph of a memo states the purpose in one or two sentences. Do not open with pleasantries, background, or general context. The reader should know why the memo was written by the end of the first sentence. A strong opening reads like: "Effective April 1, 2026, our expense report procedure will change" or "This memo confirms the compensation committee's decisions from the March 12 meeting." A weak opening reads like: "As you know, we have been discussing changes to our procedures for some time."
3. The body: background and details
The middle of the memo provides the context, details, and evidence the reader needs to understand and act on the opening statement. This section may be one paragraph for a short memo or two to four paragraphs for a longer one. Present the information in a logical order: background first, then specific details, then the reasoning that supports what follows. Use bullet points or numbered lists when the content is naturally a list. Avoid burying the important information in the middle of a long paragraph where the reader might miss it.
4. Action items or next steps
The closing section states what the recipient should do after reading the memo. Be specific. "Please submit your Q2 budget proposals by April 10" is better than "Please respond as soon as possible." "Team leads should meet with their reports individually before the end of the month to communicate the change" is better than "Please make sure your teams are informed." Vague action items are the most common weakness in memos and lead to memos being read without any follow-up.
5. The closing (optional)
Some memos end with a brief closing line offering contact information for questions, thanking recipients, or acknowledging their patience with a difficult change. This is optional and should be one sentence at most. Memos do not use complimentary closings such as "Sincerely" or "Best regards" the way formal letters do, and they do not include a signature line. The sender's name and title appear in the FROM line at the top, which serves the same identifying purpose.
Attachments (when applicable)
When a memo references supporting documents, list the attachments at the bottom with the label "Attachments:" or "Encl:" followed by the names of the documents. This lets recipients confirm they received everything the memo referenced. For memos sent by email, attachments are typically added to the email itself and mentioned in the memo body rather than in a separate attachment line.
Six Common Types of Memos with Worked Examples
Different situations call for different types of memos. The structural elements above stay the same. The body content and tone vary based on the purpose. Six types cover almost every internal business need. The examples below are complete worked memos, formatted the way an editor would expect to see them.
Type 1: Announcement memo
An announcement memo informs recipients about a change, decision, or new initiative. The tone is neutral and informative. The opening states what is being announced. The body provides the context and specifics. The closing states what the recipients need to do.
TO: All Regional Managers
FROM: David Bennett, Director of Operations
DATE: March 15, 2026
SUBJECT: Updated Remote Work Policy Effective April 1
Effective April 1, 2026, our remote work policy will change. Employees currently working remotely full-time will move to a hybrid schedule requiring three days per week in the office. The policy applies to all non-field roles across all regions.
This change follows the six-month review completed by the operations committee in February. The review found that in-person collaboration on complex projects continues to produce measurably better outcomes than remote-only work, particularly for cross-functional initiatives. The three-day requirement gives teams predictable overlap time while preserving the flexibility that remote work provides on the other two days.
Regional managers should meet with each direct report individually before March 25 to communicate the change and to work out which three days in the office best suit the team's operational rhythm. Please submit your team schedules to HR by March 28 for review before the April 1 effective date. Contact me directly with any questions about implementation.
Type 2: Request memo
A request memo asks recipients for information, resources, or action. The tone is professional and clear about what is needed and when. The opening states the request. The body explains the context. The closing states the specific deadline and any format requirements.
TO: Department Heads
FROM: Priya Iyer, Chief Financial Officer
DATE: March 15, 2026
SUBJECT: Q3 Budget Input Requested by April 10
Please submit your Q3 budget input for the fiscal year 2026-2027 planning cycle by April 10, 2026. The finance team will consolidate department submissions and prepare the Q3 forecast for executive review at the April 22 leadership meeting.
Each department should submit projections for headcount, operating expenses, capital requests, and any anticipated one-time costs. Use the standard template attached to this memo. If your department is planning any significant initiatives that will affect Q3 spending (new hires, technology investments, expansion projects), please include a one-paragraph summary describing the initiative and its expected budget impact.
Send completed submissions to me and to Chen Zhu in the finance team. Contact Chen with any questions about the template or the required categories. If the April 10 deadline creates a genuine conflict, let me know before the end of this week so we can adjust.
Type 3: Confirmation memo
A confirmation memo documents a decision, conversation, or agreement so there is a written record. It is often written after a meeting to confirm what was decided and who is responsible for what. The tone is factual and specific. The opening states what is being confirmed. The body lists the decisions or agreements in order. The closing typically invites correction if anything is captured incorrectly.
TO: Compensation Committee Members
FROM: Rachel Okoro, Head of Human Resources
DATE: March 15, 2026
SUBJECT: Confirmation of Decisions from March 12 Compensation Meeting
This memo confirms the decisions reached at the compensation committee meeting on March 12, 2026. Please review the summary below and let me know by March 20 if any item has been recorded incorrectly.
The committee approved a merit increase pool of 3.2 percent of total base salary for the fiscal year 2026-2027 cycle, to be allocated by managers based on the performance calibration completed in February. The committee also approved a market adjustment budget of $180,000 to address specific roles identified as below-market in the annual compensation review. The market adjustments will be processed with the merit cycle and communicated to affected employees at the same time.
The committee deferred the decision on the retention bonus program for senior engineering roles. Rachel will circulate an updated proposal with revised eligibility criteria before the next scheduled meeting on April 9.
Contact me directly with any corrections or questions.
Type 4: Directive memo
A directive memo instructs recipients to do something specific, often in a specific way. The tone is clear and action-oriented. The opening states what recipients must do. The body provides the specific procedures, deadlines, and requirements. The closing identifies the point of contact for questions.
TO: All Employees
FROM: James Callahan, Chief Operating Officer
DATE: March 15, 2026
SUBJECT: New Expense Report Procedure Effective April 1
All expense reports submitted on or after April 1, 2026, must follow the new procedure described below. The previous procedure will no longer be accepted after that date.
Three changes take effect on April 1. First, all expense reports must be submitted through the new Concur system rather than the previous spreadsheet template. Employees will receive Concur login credentials by March 25, along with a training video covering the submission process. Second, receipts for expenses over $25 must be uploaded as attachments in Concur. Paper receipts are no longer accepted, and expenses over $25 without receipts will not be reimbursed. Third, expense reports must be submitted within 30 days of the expense date. Reports submitted more than 30 days after the expense date will require director approval before reimbursement.
Team leads should confirm that every direct report has received their Concur credentials by March 27. Contact Michael Hastings in finance for questions about the procedure or for help completing your first submission.
Type 5: Update or progress memo
An update memo informs leadership or a project team about the status of an ongoing initiative. The tone is factual and structured. The opening states the current status. The body provides specific progress against milestones, budget, and timeline. The closing identifies risks and any decisions needed from the recipients.
TO: Executive Leadership Team
FROM: Sofia Lundberg, Program Director
DATE: March 15, 2026
SUBJECT: ERP Migration Project: March Progress Update
The ERP migration project remains on schedule for the July 1, 2026, go-live date. The March milestones have been completed on time and within budget. Two risks have been identified that warrant executive attention.
Progress against March milestones. Data mapping for the finance and procurement modules was completed on March 8, one day ahead of schedule. User acceptance testing for the finance module began March 10 and is currently 60 percent complete against a March 22 target. The training material development for department leads is on track for the April 5 completion date. Budget expenditure through March is $2.1 million against a planned $2.3 million, running 8.7 percent under plan.
Risks and open items. First, the integration with the legacy CRM system is proving more complex than the vendor initially estimated. We are working with the vendor to determine whether the July 1 go-live can still be met or whether a two-week delay may be needed. A decision on this is expected by March 25. Second, three key users on the procurement testing team have flagged availability conflicts with the April testing schedule due to competing project commitments. I will circulate a proposed resolution to the sponsors by March 20.
Type 6: Response memo
A response memo replies to a question, request, or previous memo. The tone matches the original: professional, factual, and focused on the specific matter raised. The opening identifies what the memo is responding to. The body provides the response. The closing states any follow-up needed.
TO: Priya Iyer, Chief Financial Officer
FROM: Marcus Delacroix, Head of Engineering
DATE: March 15, 2026
SUBJECT: Engineering Q3 Budget Input, Response to March 8 Memo
This memo responds to your March 8 request for Q3 budget input for the fiscal year 2026-2027 planning cycle. Engineering's Q3 projections and initiative summary are provided below. Full detail is in the attached budget template.
Projected headcount for Q3 is 47, an increase of 5 from Q2. The additional roles are three senior engineers for the platform team and two site reliability engineers to support the ERP migration go-live. Operating expenses are projected at $1.85 million, up from $1.62 million in Q2, primarily reflecting the headcount increase and a $60,000 increase in cloud infrastructure costs tied to the ERP migration testing environment. Capital requests total $240,000, covering laptop replacements for the platform team and updated development workstations for two engineering labs.
Two initiatives will have significant Q3 budget impact. First, the ERP migration go-live in July will require approximately $180,000 in engineering effort during Q3, most of which is already reflected in the headcount and operating expense projections above. Second, the platform team plans to migrate our authentication service to a new vendor during Q3, requiring approximately $95,000 in one-time transition costs. A separate memo on the authentication migration will follow by March 25.
Contact me directly with questions about any of the projections.
Tone and Register in Memos
The tone of a memo is professional, direct, and impersonal. Memos are workplace documents rather than personal correspondence, and the writing should reflect that. Several specific practices distinguish the memo register from casual writing.
Use complete sentences and standard grammar. Sentence fragments and abbreviations that would be acceptable in a text message or informal email are inappropriate in a memo. Write in full sentences and use standard punctuation throughout.
Avoid contractions. Traditional memo register avoids contractions. Write "do not" rather than "don't," "will not" rather than "won't," and "cannot" rather than "can't." Contemporary business writing has loosened this convention somewhat for internal memos to colleagues, but the safer default is to spell out contractions.
Get to the point in the first sentence. Memos are read quickly. The first sentence should tell the reader what the memo is about. Do not open with background, pleasantries, or extended context. If the memo needs context, provide it in the second paragraph.
Use bullet points and numbered lists when appropriate. When the content is naturally a list (steps in a procedure, items in a decision, milestones in a project), format it as a list. This makes the memo faster to read and reduces the risk that a reader will miss an item buried in a paragraph.
Avoid emotional language. Memos should be factual and neutral. Even when the content is difficult (a layoff announcement, a policy change that will be unpopular, a critical performance issue), the writing should be measured. Emotional or defensive language undermines the writer's authority.
Be specific about actions and deadlines. Vague language such as "as soon as possible" or "in the near future" invites the reader to interpret the deadline loosely. Use specific dates and specific actions. "Submit your response to me by 5 PM on March 25" is stronger than "Please respond soon."
Common Mistakes to Avoid
Certain mistakes come up across most memos that need editing. The list below covers the ones flagged most often during professional review.
Vague subject lines. "Budget," "Update," and "Announcement" are not subject lines. They are one-word topics. A useful subject line identifies the topic and the specific matter within it: "Q3 Budget Input Requested by April 10." A specific subject line helps recipients understand the memo's purpose at a glance and helps the memo get filed correctly.
Burying the purpose. The most common structural problem in memos is opening with background or context and stating the purpose halfway through. The reader should know why the memo was written by the end of the first sentence. If the memo needs background, put it in the second paragraph, not the first.
Using a memo when an email would do. Not every internal communication needs to be a memo. A quick question, a routine update, or an informal request between two colleagues can and usually should be an email. Memos should be reserved for communications where the format adds value: policy changes, official decisions, directives, and formal internal records.
Vague action items. "Please respond as soon as possible" is a weak close. Every memo that requires action from the recipient should specify what action, from whom, and by when. If the memo does not require action, it should say so explicitly so recipients know they only need to read and file it.
Adding a salutation or complimentary closing. Memos are not letters. Do not begin with "Dear Team," and do not end with "Sincerely" or "Best regards." The FROM line at the top identifies the sender. The memo ends after the action items or the brief optional closing line.
Length beyond one page without a reason. Most memos should fit on one page. Longer memos are justified when the content genuinely requires the additional length: a project status update with several substantive sections, a confirmation memo listing many decisions from a long meeting, a directive with detailed procedures. If the memo runs longer than one page for any other reason, edit for concision before sending.
Formatting inconsistencies. Every memo in an organization does not have to look identical, but any single memo should be internally consistent. Use the same font, the same header format, the same paragraph spacing, and the same list style throughout. Inconsistencies signal that the memo was drafted quickly and reviewed carelessly.
Sending it to the wrong distribution list. The most consequential mistake in memo writing is sending confidential or sensitive information to a broader distribution than intended. Before hitting send on any memo, verify the TO line against the intended audience. This is particularly important for compensation, personnel, and strategic decisions.
Memos vs. Formal Letters vs. Email: When to Use Each
The three formats overlap in some ways but serve distinct purposes. The table below highlights the differences that matter when you are deciding which format to use.
| Feature | Memo | Formal Letter | |
|---|---|---|---|
| Primary use | Internal communication with a defined audience | External formal correspondence | Everyday communication, internal or external |
| Audience | Team, department, or organization | Individual or organization outside your own | Anyone |
| Header | TO, FROM, DATE, SUBJECT block | Sender's address, date, recipient's address | System-generated: To, From, Date, Subject |
| Salutation | None | "Dear Ms. Smith:" or "Dear Sir or Madam," | "Hi Sarah," or "Dear Ms. Smith," (varies) |
| Complimentary closing | None | "Sincerely," or "Yours faithfully," + signature | "Thanks," "Best," "Regards," or none |
| Typical length | One page | One page | A sentence to several paragraphs |
| Register | Formal but concise | Highly formal | Varies from casual to formal |
| Filed as record | Usually yes | Usually yes | Sometimes |
The quick rule: internal and structured, use a memo. External and traditional, use a formal letter. Anything else, use email. For the full formal letter format including block and modified block layouts, salutation and closing conventions, and worked examples across six letter types, see our article on how to write a formal letter.
Editor World's Business Document Editing Service
Editor World provides professional editing for business documents including memos, formal letters, business proposals, RFP responses, executive communications, and internal reports. Every edit reviews structure, tone, clarity, grammar, and consistency, with British or American conventions applied based on your audience. Every editor is a native English speaker from the United States, the United Kingdom, or Canada. No AI tools are used at any stage. Editors are matched to your document by discipline and can apply the specific tone your audience expects.
For memos, formal letters, business proposals, and internal communications, see our business document editing service. For final-pass review of near-final documents before distribution, see our professional proofreading service. For a companion guide on formal external correspondence, see our article on how to write a formal letter. Browse editors by expertise at editorworld.com/editors and message any editor directly before submitting to discuss the tone and audience your memo needs to reach.
Frequently Asked Questions
What is a memo and when should I write one?
A memo, short for memorandum, is a written communication used inside an organization to inform a team, department, or wider group about a matter and, in most cases, to request or direct a specific action. Memos are used to announce policy changes, communicate decisions, provide project updates, document conversations, deliver instructions, and record internal actions that need to be preserved. Send a memo when the communication is internal, the recipient is a group, and the content needs a structured format for filing. Memos are also right when the information should carry the weight of a formal internal document rather than a routine message.
What is the standard structure of a memo?
Every memo contains five structural elements. First, the header block: four lines labeled TO, FROM, DATE, and SUBJECT. Second, the opening statement, which states the memo's purpose in the first sentence. Third, the body, which provides background, details, and evidence in two to four paragraphs. Fourth, the action items or next steps, which specify what recipients should do and by when. Fifth, an optional closing line offering contact information or acknowledgment. Memos don't use salutations or complimentary closings the way formal letters do.
What is the difference between a memo and an email?
A memo is a structured internal document with a defined format (TO, FROM, DATE, SUBJECT header block followed by an opening statement, body, and action items). An email is a flexible communication format that ranges from a two-line message to a multi-paragraph explanation. Memos are appropriate for policy changes, official decisions, directives, project status reports, and communications that need to be filed as internal records. Email is the default for routine communications, quick questions, informal updates, and any message that doesn't need to be filed as an official document.
What is the difference between a memo and a formal letter?
A memo is an internal document for people inside an organization. A formal letter is an external document for people outside the organization such as clients, government agencies, or legal counterparts. Memos open with a TO/FROM/DATE/SUBJECT header block and skip both the salutation and the complimentary closing. Formal letters open with the sender's address, date, and recipient's address, followed by a salutation such as "Dear Ms. Smith," and end with a complimentary closing such as "Sincerely" followed by a signature. Both are formal, but the structural conventions differ substantially. See our formal letter guide for the full letter format.
How long should a memo be?
Most memos should fit on a single page. The body typically runs three to five paragraphs and 300 to 500 words. Longer memos are justified when the content genuinely requires additional length, such as project status updates with several substantive sections, confirmation memos listing many decisions from a long meeting, or directives with detailed procedures. If a memo runs longer than one page for any other reason, edit for concision before sending. Length beyond what the content requires signals that the writer hasn't yet decided what is essential.
Should I use bullet points in a memo?
Yes, when the content is naturally a list. Steps in a procedure, items in a decision, milestones in a project, or components of a directive read faster as bullets or numbered lists than as prose. Use lists when they make the content easier to scan and absorb. Avoid using lists for content that reads naturally as prose, since a memo made entirely of bullet points can feel choppy and unfocused. The right balance is prose for context and reasoning, lists for enumerable specifics.
Do memos need a signature?
No. Memos don't require a signature. The sender's name and title appear in the FROM line at the top of the memo, which serves the same identifying purpose that a signature serves in a letter. Some organizations add the sender's initials in handwriting next to the FROM line as a mark of authorization for paper memos, but this is a stylistic choice rather than a requirement. Memos sent electronically (as PDF attachments or in the body of an email) typically have no signature at all.
How do I address a memo to multiple recipients?
The TO line can name a group, a list of individuals, or a combination. For a group, use a descriptive label: "All Regional Managers," "Members of the Compensation Committee," "Q3 Budget Task Force." For a small list of named individuals, list them by name in the TO line. For a large or complex distribution, name the primary audience in the TO line and use a CC line for secondary recipients. When a memo is sent to different audiences with different actions expected, some writers include a subheading or callout at the top of the body to make each audience's action clear.
Content reviewed by the Editor World editorial team. Editor World was founded in 2010, has been BBB A+ accredited since 2010, has edited over 140 million words for more than 8,000 clients in over 65 countries, and is recommended by the Boston University Economics Department, the University of San Diego, the University of Michigan, UCLA, the University of Missouri, and other institutions. Multiple Gold and Bronze Stevie Award winner. 5.0 / 5 Google Reviews and 5.0 / 5 Facebook Reviews. 4.9 / 5 average editor rating. Less than 5% of applicants are accepted as editors. Native English editors from the United States, the United Kingdom, and Canada. No AI tools are used at any stage. Page last reviewed November 2026.