Action Plan Template: Columns, Filled-In Example and How to Run It
9 min read ยท 2026-10-25
An action plan template is a one-page table that turns a goal into a list of specific actions, each with one owner, a due date, the resources it needs, a status and a way to check it is done. It answers four questions for everyone on the team: what needs to happen, who does it, by when, and how we will know it worked.
Most action plans fail for the same reasons. The goal is vague, an action belongs to "the team" instead of a person, or nobody looks at the sheet after the kickoff meeting. The template below fixes all three. It starts with a measurable goal and a baseline, gives each action a single owner and a date, and runs on a short weekly review. You also get the exact columns, build steps in Excel or Google Sheets and a filled-in 8-week example.
The roadmap at a glance
Goal: Reach one measurable goal within 8 weeks, with every action owned, dated, done and checked against the baseline. Duration: 8 weeks
Define the goal and baseline (Week 1)
Write one goal that anyone can check, and measure where you stand today.
- Write the goal as a result with a number and a date, such as "cut average first response time on support tickets from 9 hours to 4 hours by the end of week 8".
- Pull the current number from your system of record and write it next to the goal as the baseline.
- Name the sponsor who can unblock decisions and the plan owner who runs the weekly review.
- List what is out of scope, so the plan does not grow every week.
Milestone: A goal statement with a baseline, a target, a date, a sponsor and a plan owner, approved by the sponsor.
Break the goal into actions (Week 1-2)
List every action needed to reach the goal, small enough to finish in two weeks or less.
- Run a 45-minute working session with the people who will do the work and list the causes of the gap.
- Turn each cause into one or more actions that start with a verb, such as "set up an auto-assignment rule for billing tickets".
- Split any action that would take more than two weeks into smaller ones.
- Mark dependencies: which actions cannot start until another one is done.
Milestone: A complete action list where every row starts with a verb and fits in two weeks or less.
Assign owners, dates and resources (Week 2)
Give every action one owner, a realistic due date and the resources it needs.
- Assign one named owner per action. Add helpers in a separate column if needed.
- Set due dates with each owner, not for them, and check them against holidays and other projects.
- Note the resources each action needs: budget approval, tool access, time from another team.
- Write a done criterion for each action, such as "rule live in the help desk and tested on 10 tickets".
Milestone: Every row has an owner, a due date, resources and a done criterion, and every owner has agreed to their dates.
Execute the first wave (Weeks 3-5)
Complete the actions with no dependencies and remove blockers fast.
- Hold a 15-minute weekly review: what is done, what is late, what is blocked.
- Update the status column before the review, not during it.
- Escalate any blocker older than one week to the sponsor.
- Track the goal metric weekly against the baseline.
Milestone: All first-wave actions marked Done with their done criterion met, and the goal metric reported each week.
Execute the second wave and adjust (Weeks 6-7)
Finish the dependent actions and change course if the metric is not moving.
- Start the actions that were waiting on first-wave work.
- Compare the goal metric with where you expected it to be by now.
- Add, drop or change actions based on what the numbers show, and note each change in the sheet.
- Confirm owners still have time, and reassign if someone is overloaded.
Milestone: All planned actions done or formally dropped, with a written reason for each change.
Close and review (Week 8)
Check the result, hand over what must continue and record what you learned.
- Measure the goal metric the same way you measured the baseline.
- Hand any ongoing task to a process owner, such as a weekly report or a new rule to maintain.
- Run a 30-minute retrospective: what helped, what slowed you down, what to repeat.
- Send a short close-out note to the sponsor with the result and the open items.
Milestone: A close-out note with the final metric against the baseline and target, sent to the sponsor in week 8.
The columns your action plan template needs
Put the goal, baseline, target, date, sponsor and plan owner in a small header block above the table, in rows 1 to 4. The table starts below it, one row per action. Keep it to these nine columns. More columns make the sheet harder to update, and a sheet nobody updates is useless.
Number the actions so people can refer to them in meetings ("A7 is blocked"). Keep the order of the rows close to the order of execution, with dependent actions below the ones they depend on.
- ID: A1, A2, A3.
- Action: starts with a verb and describes one deliverable.
- Owner: one person, by name.
- Start date and Due date.
- Depends on: the ID of any action that must finish first.
- Resources needed: budget, tools, access, time from another team.
- Status: Not started, In progress, Blocked, Done.
- Done criterion: how anyone can check it is finished.
- Notes: the latest blocker or decision, one line.
How to build it in Excel or Google Sheets
A spreadsheet is enough for most action plans under 40 rows. The steps below work in Excel and in Google Sheets, with small differences in menu names.
Share the file with edit access for owners and comment access for everyone else. Ask owners to update their own rows before the weekly review, so the meeting is about blockers, not data entry.
- Type the header block in rows 1 to 4 and the nine column titles in row 6.
- Select the table and turn it into a table with Insert > Table in Excel, or keep it as a range with filters on in Google Sheets.
- Add a dropdown to the Status column: Data > Data Validation in Excel, or Data > Data validation in Google Sheets, with the four status values.
- Color the statuses with conditional formatting (Home > Conditional Formatting in Excel, Format > Conditional formatting in Google Sheets): gray for Not started, blue for In progress, red for Blocked, green for Done.
- Add a rule that turns a row's due date red when the date is before TODAY() and the status is not Done.
- Freeze the title row with View > Freeze Panes in Excel, or View > Freeze in Google Sheets, so it stays visible as you scroll.
Example: a filled-in action plan for a support team
Here is the template filled in for a customer support manager whose team takes too long to answer new tickets. Header: goal is to cut average first response time from 9 hours to 4 hours by the end of week 8. Sponsor: head of customer experience. Plan owner: support team lead.
Notice that every action has a single owner and a check anyone can verify. Notice too that the staffing change (A4) depends on the analysis (A1), so it sits lower in the list.
- A1, analyze ticket volume by hour and channel: owner support analyst, due week 2, done when a chart of volume by hour is shared with the team.
- A2, set up auto-assignment rules for the three biggest ticket types: owner help desk admin, due week 3, done when rules are live and tested on 10 tickets.
- A3, write saved replies for the ten most common questions: owner senior support agent, due week 4, done when all ten are in the help desk and reviewed.
- A4, move one agent's shift to cover the morning peak: owner support manager, depends on A1, due week 5, done when the new rota is published.
- A5, add a first response time widget to the team dashboard: owner support analyst, due week 3, done when the widget shows daily numbers.
- A6, review results and adjust rules: owner support team lead, depends on A2 to A5, due week 7, done when changes are logged in the Notes column.
How to run the weekly review
The weekly review is what turns the template into results. Keep it to 15 minutes with the owners of open actions. Sort the sheet by status, with Blocked rows first, then late rows, then rows due this week.
Do not walk through every Done row. Read the goal metric at the start, look at the problems, agree on who does what by when, and write the decision in the Notes column. If a blocker needs someone outside the room, the plan owner takes it to the sponsor the same day.
- Goal metric this week against the baseline and target.
- Blocked actions and who will unblock each one.
- Late actions and the new date, agreed with the owner.
- Actions due next week, to spot problems early.
- Any change to the plan, recorded in the sheet.
How to present it to stakeholders
Stakeholders do not need the full sheet. Give them a one-slide summary: the goal with its baseline and target at the top, the current value of the metric, a simple bar of actions done against total, and the top two blockers with what you need from them.
Use the same layout every time you report, so leaders can compare week to week at a glance. If the metric is not moving even though actions are done, say so and show what you will change. That builds more trust than a page full of green statuses.
Action plan vs project plan
People often use the terms as if they meant the same thing. An action plan is a short list of actions aimed at one goal, usually over weeks. It fits on one sheet and is run by one owner with a short weekly review. A project plan covers a larger piece of work with a defined scope, a budget, phases, a schedule with dependencies, risk management and formal change control.
If your list grows past 40 or 50 actions, involves several teams with their own plans, or needs a budget, you probably need a project plan instead. In that case, the action plan can still live inside it as the to-do list for one workstream.
Common mistakes to avoid
- Writing a vague goal like "improve response times" makes success impossible to check, so add a baseline, a target number and a date.
- Assigning an action to a team or two people means nobody owns it, so give each action exactly one named owner.
- Setting due dates for people instead of with them leads to dates nobody believes, so agree on each date with its owner.
- Writing actions that take two months hides progress until it is too late, so split anything longer than two weeks.
- Marking actions Done without a check lets half-finished work slip through, so write a done criterion for every row.
- Building the plan and never reviewing it lets it go stale in a week, so hold a 15-minute review at the same time every week.
Frequently asked questions
What are the main parts of an action plan?
A measurable goal with a baseline and a target date, a list of specific actions, one owner per action, start and due dates, resources needed, a status and a done criterion. Add a dependency column if some actions must wait for others.
How do I write an action plan step by step?
Write the goal with a number and a date, then measure the baseline. List the actions with the people who will do them, assign one owner and a date to each, and add resources and done criteria. Then review the sheet every week until the goal is met.
What is the best tool for an action plan template?
Excel or Google Sheets is enough for most action plans, because everyone can open them and update their own rows. If your team already runs its work in a tool like Asana, Jira or Smartsheet, build the plan there so updates happen where people already work.
How long should an action plan be?
Short enough that the team can review it in 15 minutes. Most action plans have 5 to 30 actions over a few weeks to a quarter. If it grows much longer, split it by workstream or turn it into a project plan.
What is the difference between an action plan and a to-do list?
A to-do list is a set of tasks, often for one person, with no shared goal. An action plan ties every action to one measurable goal, with an owner, a date, resources and a way to check it is done. It is also reviewed as a team.