An action plan turns a goal into work someone is actually going to do. It lists each step, who owns it, when it’s due, and how you’ll know it’s finished — which is the difference between a decision and an outcome. The free templates below are editable MS Word files, and beneath them you’ll find a worked example, how to break a goal into steps small enough to schedule, and the technique that reveals an impossible plan before you commit to it.
What Makes an Action an Action
Four things, and a row missing any of them will still be sitting there in three months:
- A verb and a specific object. “Improve communication” isn’t an action; “circulate a weekly one-page update to all site staff” is. If you can’t picture someone doing it, it isn’t written yet.
- One named owner. Not a team, not two people, not “everyone.” Shared ownership of an action is the single most reliable way to ensure nobody starts it.
- A date. A specific one. “ASAP,” “ongoing,” and “Q3” are all ways of not committing, and they all produce the same result.
- A “done when.” The condition that ends the action. Without it, “work on the supplier review” can run for a year and never finish.
An action plan where the owner column reads “Team” and the date column reads “ongoing” is a wish list with gridlines. The columns are the plan; the rest is formatting.
Breaking a Goal Into Actions
Most action plans fail at this step rather than at execution. A goal like “reduce customer complaints by half” is real but unworkable — nobody can do it on Tuesday.
The way through is a single repeated question: what has to be true before this can happen?
Reduce complaints by half ? complaints have to be understood first ? so someone has to categorise the last six months of them ? which needs the complaint log exported ? which needs access from IT. Four questions in, you have an action a named person can complete this week: request reporting access from IT — D. Ferreira — by 3 October.
Keep asking until each answer is something one person can finish in a week or less. Anything longer than that is a project pretending to be an action, and it will show no progress at every review until it’s broken down.
Work Backwards From the Deadline
The most useful scheduling habit on this page, and it takes ten minutes.
Instead of starting at today and working forward, start at the fixed end date and schedule in reverse: the last action before it, then the one before that, allowing realistic time for each. Keep going until you reach the present.
Two things happen. You discover the actions nobody had thought about — the approval that takes two weeks, the lead time on an order, the fact that half your team is away in August. And you often discover that the plan requires you to have started three weeks ago, which is uncomfortable but far better learned now than in November.
If backwards scheduling shows the deadline can’t be met, you have three options and only three: cut the scope, add resource, or move the date. Discovering that early is what the exercise is for.
Action Plan Example
|
ACTION PLAN | Goal: cut average first response time from 19 hours to under 8 by 31 December Owner: D. Ferreira | Reviewed fortnightly, Mondays 09:30 |
|||||
| # | Action | Owner | Due | Done when | Status |
|---|---|---|---|---|---|
| 1 | Export and categorise six months of tickets by query type | M. Chen | 3 Oct | Categorised list circulated | Done |
| 2 | Write template replies for the top 10 query types | A. Bello | 17 Oct | 10 replies live in the helpdesk | In progress |
| 3 | Agree and publish a triage rota (needs #1) | D. Ferreira | 24 Oct | Rota published, team briefed | In progress |
| 4 | Obtain dashboard reporting access from IT Requested 2 Sep, chased twice — escalating to IT Manager |
R. Silva | 10 Oct | Live response-time report visible | Blocked |
| 5 | Train two new agents on the triage process (needs #3) | A. Bello | 7 Nov | Both handling tickets unsupervised | Not started |
| 6 | Measure response time against target and report | D. Ferreira | 5 Dec | Result reported to the board | Not started |
| 6 actions · 1 done · 2 in progress · 2 not started · 1 blocked — needs IT, raised 22 Sep | |||||
Three features to copy. Every action has a “done when”, so finishing isn’t a judgement call. Dependencies are marked in the action text — #3 needs #1, #5 needs #3 — so it’s visible that a delay early on moves everything after it. And the blocked row says what it’s waiting for and who from, which is the only kind of blocked entry worth having.
Free Action Plan Templates in MS Word
Each template below is editable in Word. Fill in the goal at the top first — every action underneath should be traceable back to it.
Action Plan with Owners and Deadlines
The layout shown above — numbered actions with owner, due date, completion criteria, and status, plus a goal statement at the head.
Simple Action Plan Template
A lighter goal-and-steps format without status tracking — for personal goals and short pieces of work.
Click on this download button and acquire this Action Plan Template.
Click on this download button and acquire this Action Plan Template.
Click on this download button and acquire this Action Plan Template.
Click on this download button and acquire this Action Plan Template.
Click on this download button and acquire this Action Plan Template.
Click on this download button and acquire this Action Plan Template.
Click on this download button and acquire this Action Plan Template.
Click on this download button and acquire this Action Plan Template.
Dependencies and Resources
Mark what blocks what. Actions rarely stand alone — you can’t train people on a process that hasn’t been written. Note dependencies in the action text or in a column, because a dependency you haven’t spotted is a delay you’ll discover at the worst moment. The actions with the most things depending on them are the ones to watch most closely.
Name what each action needs. Money, a person’s time, an approval, a piece of equipment, access to a system. An action requiring something nobody has arranged isn’t going to happen, however firmly it’s dated — and writing the requirement down is usually what triggers someone to arrange it.
Watch for actions that depend on people outside the plan. Action 4 in the example above is blocked by IT, who never agreed to the deadline and aren’t in the meeting. Those rows slip more than any others, so build in more time and start them earlier than feels necessary.
Reviewing It
- Set the review date before you finish writing the plan. Fortnightly suits most; weekly when things are moving quickly. A plan with no review is a document, not a plan.
- Go through every row, including the finished ones. It takes fifteen minutes and it’s the only thing that makes owners’ commitments real.
- Deal with blocked items first. They’re the reason the meeting exists — everything else is reporting.
- Re-date rather than letting dates rot. An action three weeks past its due date, still showing the original date, tells you nothing. Agree a new date, or agree it isn’t happening.
- Close actions explicitly rather than deleting the row. The completed list is the record of what the plan achieved.
- Add new actions as they emerge. No plan survives contact with the work, and one that never gains rows is one nobody is using.
Day-to-day, individual actions become entries on a task list; upward, progress against the plan belongs in a status report.
Corrective Action Plans
A distinct use with stricter requirements. A corrective action plan — sometimes a CAPA — is written after something has gone wrong: an audit finding, a failed inspection, a customer complaint, a safety incident, or a nonconformity raised against a management standard.
It differs from an ordinary action plan in three ways:
- It must address the cause, not just the symptom. The standard distinction is between a correction — fixing the immediate problem, such as replacing the faulty batch — and a corrective action, which stops it recurring. A plan containing only corrections will be rejected by any competent auditor.
- It needs a documented root cause. Not a guess, and not “human error,” which is where weak investigations stop. Our root cause analysis templates cover the methods.
- It requires verification of effectiveness. An action isn’t closed when it’s done; it’s closed when someone has checked, after a stated interval, that the problem hasn’t come back. Build that check in as its own dated action with its own owner.
Include the finding reference, the date raised, who raised it, and the deadline you’ve been given — auditors and regulators track against their own reference, and a plan that doesn’t quote it creates work for everyone.
Frequently Asked Questions
What is an action plan?
A document listing the specific steps needed to reach a goal, each with a named owner, a due date, and a definition of what “done” looks like. It’s the bridge between deciding something and it actually happening.
What should an action plan include?
The goal at the top, then numbered actions with an owner, a due date, completion criteria, status, and any dependencies or resources required. A review date and cadence should be agreed before the plan is finished.
How do I turn a goal into actions?
Keep asking “what has to be true before this can happen?” until each answer is something one person can finish within a week. Anything larger is a project rather than an action, and it will show no progress at every review until it’s broken down.
What is the difference between an action plan and a project plan?
An action plan lists what needs doing, who’s doing it, and by when. A project plan adds scheduling detail — phases, durations, resource allocation, and critical path. For most goals, an action plan is enough.
Why should I schedule backwards from the deadline?
Because it shows whether the plan is possible. Starting at the end date and working back surfaces the approvals, lead times and absences nobody had accounted for — and if it shows you needed to start three weeks ago, that’s far better known now than in November.
What is a corrective action plan?
A plan written in response to a problem — an audit finding, incident, or complaint — that addresses the underlying cause rather than just the symptom, documents a root cause, and includes a dated check that the fix actually worked.
How often should an action plan be reviewed?
Fortnightly for most plans, weekly during intensive periods. Go through every row, deal with blocked items first, and re-date anything that has slipped rather than leaving an expired date on the page.
Pete Smith is a Business Management graduate and a passionate advocate for practical, accessible resources that empower professionals and entrepreneurs to succeed. With a strong foundation in organizational strategy and operational efficiency, Pete combines academic knowledge with real-world insights to simplify complex business processes. He is the creator behind a growing online platform dedicated to offering free, high-quality documents, templates, and actionable tips designed to save time and improve productivity.