How to Write a Memo: Structure, Examples, and Review Workflow

To write a clear memo, identify the audience and purpose first. Then give readers the key message, supporting context, and any required action, including its owner and deadline. Use a header with TO, FROM, DATE, and a specific SUBJECT. For example, a memo about an office access change should identify affected teams, state when the change starts, explain what employees need to do, and link to the authoritative instructions.

A memo is a concise internal document for communicating information, decisions, or required action. Formats vary by organization, and there is no universal one-page limit. This guide shows you how to choose the right format, structure the message, compare three memo types, and review a memo before sending it.

The same principles also apply when an AI-assisted workflow prepares a draft. Treat the draft as a controlled document that requires source information, validation, ownership, and approval before distribution.

Decide whether the message needs a memo

Choose a format based on the communication job. A memo works well for an internal announcement, decision, or instruction that affects multiple people, has an effective date or required action, or should be easy to retrieve later. Email or chat usually suits a lighter, conversational exchange. A report is better for detailed evidence or analysis, an agenda sets out a planned discussion, and meeting minutes record what happened.

These are practical distinctions, not universal rules. A policy notice may be delivered as a memo, but the approved policy itself should remain in its designated system of record. Link to that record rather than treating the memo as the authoritative policy.

Use a six-part structure readers can scan

1. Header: Include TO, FROM, DATE, and SUBJECT. TO can name a person, team, or controlled recipient group. FROM should identify the author and, where useful, the role. Name the topic and add an effective date when it helps, such as “Office access changes starting December 7.” Avoid vague subjects such as “Update.”
2. Purpose: State the point in one or two sentences. Tell readers whether you are informing them, recording a decision, or asking them to act.
3. Context: Explain what is changing or needed, why it matters, and who is affected. Use short paragraphs and bullets when they make details easier to scan.
4. Action or conclusion: State what the reader must do, who is responsible, and the deadline. If no action is required, say so. Give readers a contact for questions.
5. References: List attachments or source documents separately. Link to a long policy instead of copying it in full.
6. Review: Check facts, then clarity, then length. Left alignment, single spacing, and space between paragraphs are useful layout options, subject to your organization’s style.

Write the message around its decision or action

Put the main point before the background. These adaptable formulas can help you get started:

• Informational: Starting [date], [change] because [reason].
• Action required: [Situation]. Please [specific action] by [deadline].

Separate what has been decided from what is still being considered. For a policy change, identify the previous rule when readers need it, the new rule, who is affected, the effective date, and a link to the approved policy. Keep the memo date, approval date, distribution date, and policy effective date distinct.

For a request, name the action, responsible audience, and deadline. “Please respond” is not enough if readers need to submit a form, confirm a schedule, or complete a particular task. Before sending, verify names, dates, policy details, links, and recipient scope. Then remove wording that readers do not need to understand the decision or act.

Choose the example that matches the memo’s job

Use these original outlines to plan the content. Replace the illustrative details with verified organizational facts and route policy language to its authorized owner.

Memo type	Use it for	Must make clear	Typical next step
Company update	Operational news affecting a group	What is changing, who is affected, and when	Prepare for the change or share questions
Policy change	A formal rule or procedure change	Old rule, new rule, effective date, and policy link	Follow the approved policy from its effective date
Progress report	A project or initiative status update	Completed work, blockers, owners, and next steps	Complete or escalate the next action

Company update memo

Illustrative outline: Subject: “Office access changes starting December 7.” Open with the change and start date. Identify affected teams, summarize practical implications such as which entrance to use, and link to the facilities instructions. The operations or communications owner should confirm the audience and instructions before sending. If the facilities source has no confirmed start date, hold the memo and ask its owner to resolve the date rather than guessing.

Policy change memo

Illustrative outline: Subject: “Travel policy: lodging receipts required from January 1.” State the previous rule, the approved new rule, the reason if authorized, who is affected, and the link to the policy record. The policy owner approves the wording. If the effective date in the draft conflicts with the approved policy, return the draft to the policy owner instead of distributing it.

Progress report memo

Illustrative outline: Subject: “Onboarding redesign status, week ending November 13.” Summarize completed work, work in progress, blockers, and next steps with owners and deadlines. The project lead confirms the status. If a blocker has no owner or an action has no agreed deadline, label it unresolved and ask the project lead to assign or confirm the follow-up.

Zapier’s article links to Google Docs copy links for a company update memo, a policy change memo, and a progress report memo. Access may require Google sign-in. The editable files could not be independently inspected, so treat them as starting points rather than verified approval or workflow templates. See the source article for its writing guidance and examples.

If drafting is automated, separate the draft from distribution

An AI-assisted workflow can organize approved notes into a draft, but it should not decide whether a policy is authorized or publish content merely because drafting succeeded. Zapier MCP connects compatible AI clients to configured tools in connected apps. It is a connection layer, not automatic fact-checking, memo approval, or duplicate prevention. The MCP quickstart documents setup and general tool use. Exact triggers and actions vary by app, so check the current app documentation before designing a workflow.

A practical design starts with a source record in the organization’s system of record, such as an approved announcement form or a dated project status record. An authorized owner confirms that the source is ready. The AI client can summarize supplied content into structured draft fields; deterministic checks validate required fields and allowed values; a human reviewer approves the draft; then a configured app action saves or distributes the approved version. The destination might be a document repository, email, or team channel, but the selected app must support the exact action required.

For example, the following is an illustrative draft contract, not a Zapier-published schema:

{
  "memo_id": "memo-announcement-284-v1",
  "memo_revision_id": "memo-announcement-284-v1-r1",
  "generation_run_id": "run-2026-11-13-001",
  "source_record_id": "announcement-284",
  "memo_type": "company_update",
  "to": "Operations and Facilities",
  "from": "Internal Communications",
  "subject": "Office access changes starting 2026-12-07",
  "effective_date": "2026-12-07",
  "required_action": null,
  "action_owner": null,
  "action_deadline": null,
  "source_references": [
    "https://intranet.example/announcements/284"
  ],
  "approver": "Operations owner",
  "status": "needs_review"
}

The separate identifiers preserve the row grain: one logical memo, one revision, and one generation attempt. If the memo cites several documents, store each citation as a related source record rather than using one unstable flattened key. If the memo is delivered to several destinations, use a separate distribution record for each destination and keep delivery attempts separate from the logical distribution.

Use simple rules for known requirements: allow only approved memo types, require a source ID and recipient, validate dates, and require an approver for a policy change. Use AI for summarizing notes or organizing draft sections, not for inventing missing facts. If a required field is absent or sources conflict, route the draft to its named owner instead of sending it.

To handle duplicate events, define a stable key for the declared record grain. A proposed key for one memo revision is source_system + source_record_id + memo_type + version. A proposed key for one distribution is memo_revision_id + destination_type + destination_id + distribution_version. A read-then-create check alone can race if two runs happen together. Where concurrent runs are possible, enforce uniqueness in the destination database or use a transactional upsert if that system supports one. Keep generation_run_id separate from memo_id so retries and revisions do not become indistinguishable.

Connected-app permissions, tool scope, sensitive-data handling, and review controls determine whether a workflow is appropriate. Use least-privilege access and require human approval for policy, legal, employee-sensitive, or externally visible content. The Zapier app documentation and app directory can help identify available applications, but directory presence does not prove that a particular app supports the exact trigger, field, action, or plan needed.

For help translating a reviewed process into connected-app steps, see Zapier automation consulting. For a bounded AI drafting role with human review, see AI agent consulting.

Final memo review: check facts, audience, and follow-through

Do not distribute a memo when its audience, source, dates, required action, or approval is missing or contradictory. Return it to the named author or source owner for correction. If delivery fails, the workflow or communications owner should use the approved manual route and retain the final version.

The goal is not to make every internal message formal. It is to make important communication clear, actionable, and easy to retrieve. Whether you write the memo manually or prepare a structured draft with connected tools, the final responsibility remains with the authorized owner who verifies the facts and approves the message.