An action memo is a short document that turns a decision, meeting, or project discussion into clear next steps. Use the blank action memo template below to record the purpose, key decisions, task owners, deadlines, and follow-up details in one place.
What an Action Memo Is
An action memo is a practical record of what needs to happen after a discussion or decision. It explains the situation briefly, states the outcome or direction, and assigns specific work to named people or roles. Its main job is to help readers understand what was agreed and what they should do next.
The term is used in different settings, so there is no single required format. A team may use an action memo after a planning meeting, while a project lead may use one to communicate a decision and its implementation steps. In either case, the memo should be concise enough to scan and detailed enough that a person who missed the conversation can follow the commitments.
An action memo is not simply a transcript or a list of everything people discussed. It filters the discussion down to relevant context, decisions, actions, owners, and timing. It may link to fuller notes or supporting documents, but it should still make the immediate responsibilities understandable on its own.
When to Use an Action Memo
Use an action memo when a decision needs to be carried out by one or more people, especially if responsibilities could otherwise be unclear. It is useful after a meeting, at a project handoff, when a team agrees on a change in process, or when a manager needs to communicate a plan to people who were not in the room.
It is less useful for a casual conversation with no meaningful follow-up, or when an existing project tracker already records the decision, owner, and due date in a clear and accessible way. Avoid creating a second record that will quickly become inconsistent. In that case, a short message pointing people to the existing source of truth may be enough.
- After a meeting: capture decisions and tasks while the discussion is fresh.
- For a handoff: give the receiving person context, open questions, and next steps.
- For a change: explain what is changing, when it takes effect, and who is responsible for implementation.
- For a follow-up: check progress against previously agreed tasks and record revisions.
Action Memo Template
| Memo information | Details |
|---|---|
| Subject or title | |
| Date prepared | |
| Prepared by | |
| Audience | |
| Purpose | |
| Background or context | |
| Decision or agreed direction | |
| Open questions or dependencies | |
| Next review or follow-up date |
| Action or deliverable | Owner | Due date | Status | Notes or dependency |
|---|---|---|---|---|
How to Fill It Out
Start with a specific subject line that tells readers what the memo concerns. A phrase such as “Website review: approved changes and next steps” is more useful than “Meeting notes.” Add the date and the intended audience so a saved or forwarded copy still has basic context.
- State the purpose. In one or two sentences, explain why the memo exists and what readers need to know or do.
- Give only useful background. Include the relevant problem, prior commitment, or constraint. Leave out discussion that does not affect the decision or the work ahead.
- Write the decision plainly. Identify what was agreed, who made or confirmed the decision if that matters, and any important limits. If there is no final decision, say what remains unresolved rather than implying agreement.
- Break work into observable actions. Describe a result someone can complete, such as “Send the revised agenda to the group,” rather than “Follow up.” Split work into separate rows when different people own different outcomes.
- Name one accountable owner for each action. Other contributors can be listed in the notes, but a clear primary owner reduces the risk that everyone assumes someone else will act.
- Set a usable deadline and status. Use a calendar date where possible. If timing depends on another task, record that dependency as well as the expected date or checkpoint.
- Review before sharing. Check names, dates, wording, and whether the actions reflect what participants actually agreed. Invite correction if the memo is meant to confirm a group decision.
Not every memo needs every field. For a small task, the context and action table may be enough. For a decision with several stakeholders, record the rationale, dependencies, and next review date so that later readers can understand why the work is proceeding as described.
Filled-In Sample
Sample — fictional details: A team has agreed to update the orientation checklist before a new staff group begins. The memo might state that the current checklist has outdated room instructions and that the team approved a revised version for the next orientation cycle. The action table could include: “Update room instructions,” owner: “Mina Patel,” due date: “May 12,” status: “In progress,” notes: “Confirm the room number with the facilities contact.” A second row could say: “Review the revised checklist,” owner: “Jordan Lee,” due date: “May 15,” status: “Not started,” notes: “Review after the room detail is confirmed.”
This sample is deliberately modest: it names an outcome, an owner, a date, and a dependency. It does not claim the work is finished or turn an unresolved detail into a decision. In a real memo, use the names and dates that apply, and make clear if a date is proposed rather than agreed.
Writing an Action Memo People Can Use
Put the most important information near the top. Readers should be able to find the decision and their own responsibilities without searching through a long account of the meeting. A short opening summary can answer three questions: what happened, what was decided, and what happens next.
Use direct, concrete language. “Prepare a one-page draft of the revised checklist” gives a clearer finish line than “Work on the checklist.” If a task contains several steps, either list the steps in the notes or create separate actions with owners and dates. Avoid vague status labels unless the team has agreed what they mean; “waiting for room confirmation” is more informative than “blocked.”
Include enough context to prevent a task from being misunderstood, but do not make the memo a substitute for a full project plan. If a reader needs more detail, identify the relevant document or point of contact. Use consistent date formats, define unfamiliar abbreviations, and avoid assigning an action to a group when one person can be named as accountable.
Common Problems and How to Prevent Them
- Actions have no owner. Assign one accountable person or role to each action. If responsibility is genuinely shared, name a coordinator who will track completion.
- Deadlines are missing or ambiguous. Replace “soon” or “next week” with a clear date, or specify the event that determines timing. If the date is tentative, label it as such.
- The memo records discussion but not the outcome. Summarize the relevant context, then state the decision or explicitly identify what is still open.
- People confuse a proposal with an agreement. Mark suggestions as proposed and decisions as approved or agreed only when that reflects what happened.
- The document becomes a second, outdated tracker. Choose one place for current task status. If the memo is a snapshot, include its date and point readers to the maintained tracker when one exists.
- Too much background buries the request. Move detailed history to an attachment or linked record, while keeping the reason for the action in the memo.
A memo can document work, but it cannot create agreement that did not occur. When recipients need to confirm responsibilities or a decision is still being reviewed, say so directly and provide a way to respond. If a memo touches legal, tax, medical, or personal financial-planning decisions, use it only to record process and ask a qualified professional for advice.
Action Memo vs. Meeting Minutes and Decision Memo
Meeting minutes usually preserve a broader record of a meeting: attendees, topics, discussion summaries, and decisions. An action memo is narrower and emphasizes execution. It may be based on minutes, but it should not reproduce every agenda item if readers mainly need to know the commitments.
A decision memo generally helps someone evaluate options and make a choice. It may compare alternatives, explain trade-offs, and recommend a course of action before approval. An action memo more often communicates what will happen after a direction has been selected. In practice, one document can serve both purposes if it clearly separates the recommendation, the decision, and the resulting tasks.
An action-item list is narrower still: it tracks tasks, owners, and deadlines, usually with little context. Use a list when the team already understands the background and only needs a progress record. Choose a memo when readers also need to understand why the tasks exist, what was decided, or how the actions fit together.
Sharing and Following Up
Send the memo to the people who need to act, approve, or stay informed. Make the intended audience explicit rather than distributing it broadly by default. If someone is assigned an action, give that person a practical opportunity to flag an incorrect owner, deadline, or description before the task becomes overdue.
For follow-up, review the action table at the agreed checkpoint. Update statuses in the designated record, note changed deadlines, and record new decisions separately from the original ones so readers can distinguish the initial plan from later changes. Close completed actions clearly; do not leave them marked as in progress simply because the memo remains stored for reference.
Keep the memo easy to retrieve alongside related project records. If the plan changes, communicate the update to affected people and identify which version or status is current. A memo that is accurate when issued can become misleading if it is circulated later without a date or explanation of subsequent changes.
Frequently Asked Questions
What should an action memo include?
An action memo generally includes a subject, date, purpose, relevant context, decision or agreed direction, and a list of actions with owners and due dates. Add dependencies, status, or a follow-up date when they help readers carry out or track the work.
How long should an action memo be?
There is no fixed length. Keep it as short as possible while preserving the context needed to understand the decision and complete the actions. A routine follow-up may fit on one page; a complicated handoff may need more detail or a reference to supporting material.
Who writes an action memo?
Usually the meeting facilitator, project lead, decision owner, or person responsible for coordinating follow-up prepares it. The important point is that someone is responsible for recording and sharing the agreed information, and that affected people can correct misunderstandings.
Is an action memo the same as meeting minutes?
No. Minutes usually summarize a broader meeting record, while an action memo focuses on decisions and what must happen next. An action memo can be prepared from minutes, or it can be the only record needed for a short discussion.
Can I use an action memo for a project?
Yes. It can communicate a project decision, handoff, or group of near-term tasks. For ongoing project tracking, use the memo alongside a maintained task record or tracker rather than relying on an old memo as a live status report.