What Is a Work Plan? How to Write One, With Examples and a Free Template
The Coavon team · · 16 min read
A work plan is a short document that sets out what a piece of work should achieve and how it will get done: the goals, the deliverables, the tasks, who does each one, the dates, the resources and budget, and the risks. It turns an idea (“we need a new website”, “we need more leads this quarter”) into something a team can start on Monday and check on every week. Work plans are used for projects, for a team's work over a month, quarter or year, and for one person's own work.
This guide covers what a work plan is for, what goes in one, how it differs from a project plan and an action plan, the main types, how to write one in seven steps, and three complete examples. If you just want the layout, download the free work plan template for Word and Excel.
Short on time? Jump to what goes in a work plan, how to write one, the project example or the free template.
What is a work plan?
A work plan answers five questions about a piece of work before it starts:
- What are we trying to achieve? The goals, with a measure and a date.
- What will we deliver? The things that will be finished or handed over.
- Who does what, and by when? The tasks, each with one owner and a due date.
- What do we need? People, suppliers, tools and money.
- What could go wrong? The main risks, and what you will do about each.
That is the whole idea. A work plan for a small project can fit on one page; one for a funded program or a client engagement might run to five. What makes it a plan rather than a wish list is that every part is specific enough to check: a number, a name, a date.
Work plan or workplan?
Both spellings are used and mean the same thing. Work plan (two words) is the more common in everyday business writing and is what most style guides would expect. Workplan (one word) is common in government, nonprofit and grant documents, and some funders ask for it by that name. Pick one and use it consistently. You may also see it called a work schedule, a plan of work or a program plan.
What is the purpose of a work plan?
A work plan exists to get everyone agreeing on the same thing before time and money are spent, and to give you something to check progress against afterwards. In practice it does five jobs:
- Gets agreement up front. The person paying for the work, the people doing it and anyone affected all sign off on the same goals, scope and dates.
- Makes ownership clear. Every task has one name next to it, so nothing falls between two people.
- Shows whether you are on track. With dates and milestones written down, “how is it going?” has a factual answer.
- Surfaces problems early. Writing down resources and risks often shows that the plan needs more time, more money or fewer goals, before anyone has started.
- Makes the work repeatable. A good plan for a website project, a quarterly campaign or a client onboarding becomes the starting point for the next one.
Funders, clients and managers also ask for work plans so they can see how a team intends to use their money or time. A grant application, a consulting proposal or a request for budget often includes one.
What goes in a work plan?
Most work plans have the same eight parts. Small plans can merge some of them; larger ones expand each into its own section.
| Part | What it says | Example |
|---|---|---|
| Summary | What the plan covers and why now, in two or three sentences | Replace our six-year-old website, which does not work well on phones, before the spring campaign |
| Goals | What you want to achieve, each with a measure, a target and a date | Contact form enquiries from about 15 to 30 a month by June |
| Scope and deliverables | What is and is not included, and what will be finished or handed over | Nine pages, new copy and redirects; online booking is out of scope |
| Tasks and timeline | Each task with one owner, a start date, a due date and a status | Write and edit the page copy: copywriter, 1 to 19 February |
| Milestones | The key dates that show the work is on track | Designs approved by 3 February |
| Resources and budget | People, suppliers, tools, materials and money, and who approves spending | Agency $9,000, copywriter $1,800, photos $300 |
| Risks and constraints | What could go wrong and what you will do; the fixed limits you work within | Content arrives late: one named owner per page and a weekly reminder |
| Roles and communication | Who does what, how progress is reported and who approves changes | Weekly update every Friday; the operations director approves changes |
Grant and nonprofit work plans often add objectives and activities (the same idea as goals and tasks, in funder language), outputs and outcomes (what you produce, and the change it makes), and an evaluation section saying how results will be measured and reported. If a funder gives you a format, use theirs.
Goals, deliverables and tasks: the difference
These three are the parts people mix up most, and the plan is much easier to follow when they are kept apart:
- A goal is the result you want: “more enquiries from the website”. It is measured, not ticked off.
- A deliverable is something you finish and hand over: “a live website with nine pages”. It is either done or not.
- A task is an action someone takes to produce a deliverable: “write the copy for the services pages”. It starts with a verb and has one owner.
A plan with only goals has no way to start. A plan with only tasks can be finished in full and still miss the point. You need all three, linked: tasks produce deliverables, and deliverables move the goals.
Work plan vs project plan vs action plan
These terms overlap and people use them loosely. Here is how they usually differ:
| Work plan | Project plan | Action plan | |
|---|---|---|---|
| Covers | A project, or a team or person’s work over a period | One project, start to finish | The steps to reach one goal or fix one problem |
| Length | One to five pages | Often longer, with several supporting plans | Often one page or a table |
| Main focus | What, who, when, with what and what could go wrong | Scope, schedule, budget, quality, risk, communication and change control | Actions, owners and dates |
| Typical use | Small and mid-sized projects, quarterly team plans, grants, personal plans | Large or formal projects, often run by a project manager | After a review, an audit or a goal-setting meeting |
In a small business the line between a work plan and a project plan is thin, and the two names are often used for the same document. A work plan becomes a full project plan when you add things like a schedule baseline, formal change control and separate plans for quality, procurement or communication. An action plan is usually smaller than either: it is the task list without the budget, scope and risks around it.
Two other documents are sometimes confused with a work plan. A business plan describes the whole business (market, model, finances) over several years; a work plan describes one piece of work. A work breakdown structure (WBS) is a diagram or outline that splits deliverables into smaller pieces; it is often the first step in writing the task list of a work plan, not a replacement for it.
Types of work plans
The parts stay the same, but the level of detail changes with what the plan covers and how far ahead it looks.
| Type | Covers | Typical length | How detailed the tasks are |
|---|---|---|---|
| Project work plan | One project with a start and an end | Two to five pages | Every task, with dates |
| Weekly work plan | One person or team for a week | Half a page | Every task, by day |
| Monthly work plan | A team or person for a month | One page | Main tasks, by week |
| Quarterly work plan | A team for three months | One to three pages | Main tasks and a milestone for each month |
| Annual or yearly work plan | A team, department or organization for a year | Two to five pages | Goals and milestones only; tasks go in the quarterly plans |
| Individual or personal work plan | One person’s work and development | One page | Main tasks and learning goals |
The further ahead a plan looks, the less detail it should hold. Tasks planned twelve months out rarely survive the first quarter, so annual plans set goals and milestones and leave the tasks to shorter plans underneath. A weekly work plan is the opposite: little more than a task list for the week, usually taken from the monthly or project plan above it.
How to write a work plan in 7 steps
These steps work for any type of plan. For a one-page plan, each step might take five minutes; for a funded project, a day or two.
1. Write the summary and goals
Start with why. In two or three sentences, say what the plan covers, why it matters now and what will be different when it is done. Then write two to four goals. Each goal needs a measure, a target and a date; without all three, nobody can tell whether it was reached.
| Vague goal | Clear goal |
|---|---|
| Improve the website | Contact form enquiries from about 15 to 30 a month by June |
| Get faster at support | Every customer email answered within one working day by the end of March |
| Grow the newsletter | 1,500 subscribers by 30 September, from 900 today |
| Learn the new system | Run month-end close in the new accounting system without help by May |
If you can only write a vague goal, that is useful to know: the work probably needs a short discovery phase before it needs a plan.
2. Set the scope
Write down what the plan covers and, just as important, what it does not. The out of scope line is the one that saves arguments later. If the website project does not include online booking, say so now, before someone assumes it does and is disappointed in week ten.
3. List the deliverables, then break them into tasks
List the things you will finish or hand over, then break each one into tasks. Write every task as an action that starts with a verb, small enough that one person can finish it in a few days to two weeks. If a task would take longer, split it.
| Unclear task | Clear task |
|---|---|
| Website copy | Write and edit the copy for the nine pages |
| Testing | Test every page on a phone, a tablet and three browsers |
| Marketing | Send the launch email to the customer list |
| Onboarding | Book the new hire’s first-week meetings with each team lead |
4. Give every task an owner and dates
Put one name, or one job title, next to every task. Two names usually means nobody. Then add a start date and a due date, working back from any fixed date (a launch, an event, a funding deadline). Note which tasks must wait for others; the copywriter cannot start until the page list is agreed. Add a status column (Not started, In progress, Waiting, Done) so the plan can be updated in seconds each week.
When you place the dates, leave some slack. Plans almost always run longer than expected, and a plan with no spare time in it is late the moment anything slips. For more on building a realistic schedule, including how to estimate and how to find the critical path, see our guide to project scheduling.
5. Add milestones, resources and budget
Pick three to six milestones: dates that, if hit, tell you the plan is on track, such as designs approved, content complete, ready for testing and launch. Then list the resources: the people (and how much of their time), suppliers, tools and materials, with a cost against each and a total. Say who approves spending.
This is the step that most often changes the plan. When the time and money are written down next to the goals, it is common to find they do not add up, and the honest fix is to drop a goal, move a date or ask for more, now rather than halfway through.
6. Write down the risks and constraints
List the three or four things most likely to knock the plan off course. For each, note how likely it is, how much it would hurt, and what you will do: either something that makes it less likely, or what you will do if it happens. Then list the constraints, the fixed limits the plan must work within, such as a hard launch date, a budget cap or a person who is only free part-time.
| Weak risk entry | Useful risk entry |
|---|---|
| Delays | Content arrives late. Name one owner per page on day one, send a weekly reminder, and build with placeholder text so the build is not held up. |
| Budget | The agency quote rises if pages are added. New page requests go on a phase 2 list unless the sponsor approves them. |
| Staff | The copywriter is free only in February. Agree the page list by 29 January so writing can start on 1 February. |
7. Agree how you will track it, then get it approved
Decide when progress will be reported (for example, a written update every Friday), which meeting checks it, and who approves changes to scope, dates or budget. Then share the plan with the people doing the work and the person paying for it, adjust it with their comments and get it signed off.
After that, the plan is a living document. Update the status of each task every week, and when something big changes, change the plan and its version number rather than quietly working around it. A plan that is three weeks out of date is worse than none, because people will trust it.
Work plan example 1: a project work plan
A small company is replacing its website. The marketing manager owns the plan; an outside agency designs and builds the site; a freelance copywriter writes the pages; the operations director approves the budget and any changes. The project runs for 12 weeks, from 11 January to 2 April 2027. The business, people and amounts are made up.
Goals: contact form enquiries from about 15 to 30 a month by June 2027; the marketing team can make routine changes without the agency; launch by 29 March within $11,100.
Scope: home page, five service pages, about, contact and news; new copy; redirects from old addresses; analytics. Out of scope: online booking and payments (a phase 2 decision in May), photography, and moving the email system.
Tasks and timeline (as of 25 January):
| Task | Owner | Start | Due | Status |
|---|---|---|---|---|
| 1. Agree goals, budget and the list of pages | Marketing manager | 11 Jan | 15 Jan | Done |
| 2. Collect content from each team | Marketing manager | 18 Jan | 5 Feb | In progress |
| 3. Design the home page and two inner pages | Agency designer | 18 Jan | 29 Jan | In progress |
| 4. Review and approve the designs | Operations director | 1 Feb | 3 Feb | Not started |
| 5. Write and edit the page copy | Copywriter | 1 Feb | 19 Feb | Not started |
| 6. Build the site | Agency developer | 4 Feb | 5 Mar | Not started |
| 7. Set up redirects from old pages | Agency developer | 1 Mar | 12 Mar | Not started |
| 8. Test on phones, tablets and browsers | Marketing assistant | 15 Mar | 24 Mar | Not started |
| 9. Fix the issues found in testing | Agency developer | 22 Mar | 26 Mar | Not started |
| 10. Launch, check analytics and train the team | Marketing manager | 29 Mar | 2 Apr | Not started |
Milestones: designs approved 3 February; content complete 19 February; ready for testing 12 March; site live 29 March.
Budget: agency design and build $9,000 (fixed price, paid in three parts); copywriter $1,800; stock photos $300; the marketing manager's time, about one day a week. Total $11,100, approved by the operations director.
Risks: content arrives late (high likelihood, high impact: one owner per page, weekly reminder, build with placeholder text); old links break after launch (medium, high: redirect list from analytics, top 50 old addresses checked on launch day); the project grows (medium, medium: new requests go on a phase 2 list).
Communication: a written update every Friday; 30 minutes every Tuesday with the agency; the operations director approves any change to scope, dates or budget.
Notice what makes it work: every goal has a number and a date, the out-of-scope line heads off the obvious extra requests, every task has exactly one owner, and every risk comes with something the team will actually do. The complete version, with deliverables, roles and sign-off, is the filled-in example in the work plan template.
Work plan example 2: a quarterly team work plan
A three-person marketing team at a small software company plans its second quarter (April to June 2027). A quarterly plan looks further ahead than a project plan, so it holds goals, the main pieces of work and a milestone for each month, and leaves the day-to-day tasks to the team's weekly planning.
| Goal | Main work | Owner | Milestone |
|---|---|---|---|
| Trial sign-ups from search up from about 120 to 180 a month by 30 June | Publish eight guides on topics customers ask about; refresh the four oldest | Content lead | Four guides live by 15 May |
| Newsletter from 900 to 1,500 subscribers by 30 June | Add a sign-up offer to every guide; run one webinar a month | Marketing manager | First webinar held 22 April |
| Case study for each of our three main customer types | Interview six customers; write and approve three case studies | Marketing assistant | Interviews done by 30 April |
Resources: the three team members; a freelance designer for about ten hours a month; webinar software already paid for. Budget: $2,400 for design and $600 for small paid promotions. Risks: customers slow to agree to interviews (ask eight to get six; offer a small thank-you); the product launch in May pulls the team away for two weeks (guides front-loaded into April).
Review: the team checks progress against the goals every other Monday and writes a one-paragraph summary at the end of each month. Anything not started by mid-May is either cut or moved to the third-quarter plan, not squeezed in.
Work plan example 3: an individual work plan
An individual work plan sets out one person's main work and learning for a period. Managers often write one with a new hire for their first 90 days, or with any team member as part of an annual review. Here is one for a new office manager at a 20-person firm, starting on 1 March 2027.
| Period | Goals | Main tasks | Support needed |
|---|---|---|---|
| Days 1 to 30 | Learn how the office runs and who to ask | Meet each team lead; shadow the outgoing office manager for two weeks; list every recurring task and when it happens | Introductions from the managing director; access to the shared calendar and supplier list |
| Days 31 to 60 | Run day-to-day office work without help | Take over supplier orders, room bookings and new-starter set-up; write a checklist for each | Weekly 30-minute check-in with the managing director |
| Days 61 to 90 | Improve one process | Pick the most frustrating recurring task, suggest a better way, and run it for a month | Budget of up to $500 for any tool needed |
How progress is checked: a short check-in every week for the first month, then every other week; a review at day 90 against the three goals. A personal work plan stays deliberately short. Its job is to make expectations clear on both sides, not to track every task.
A work plan template you can use
Our free work plan template has everything above, ready to fill in. There are three Word versions and an Excel tracker:
- Detailed: summary, goals, scope, deliverables, tasks and timeline, milestones, resources and budget, risks, roles and communication, and sign-off. Best for projects with a budget or an approver.
- Simple, one page: goal, deliverables, a task table, resources, risks and how you will track it. Best for small pieces of work, monthly or quarterly plans and personal plans.
- Filled-in example: the website project from example 1, complete.
- Excel tracker: the task list with status and priority drop-downs, days left, overdue dates in red and a progress count. It also opens in Google Sheets.
Every part to change is in brackets and highlighted in the Word files, so none is missed. The Word versions open in Google Docs too.
If you only need the bare outline, copy this:
- Summary: what this covers and why now.
- Goals: goal, measure, target, date (two to four of them).
- Scope: in scope; out of scope.
- Deliverables: what will be finished or handed over, with an owner and due date for each.
- Tasks: task, owner, start, due, status.
- Milestones: three to six key dates.
- Resources and budget: item, cost, total, who approves.
- Risks: risk, likelihood, impact, what you will do; plus constraints.
- Communication: when updates are posted, which meeting checks progress, who approves changes.
Common work plan mistakes
- Goals with no number or date. “Improve customer service” can never be finished or failed. Add a measure, a target and a date.
- Tasks owned by a team. “Marketing to write the copy” means nobody in particular. Put one person or one role on every task.
- No out-of-scope line. Without it, the plan quietly grows until the original dates no longer make sense.
- Too much detail too far ahead. Daily tasks planned six months out waste time and will be wrong. Plan the near term in detail and the far term in milestones.
- No slack. A schedule with every day accounted for is late the first time anything slips.
- Risks with no response. Listing “delays” as a risk does not help. Write what would cause the delay and what you will do about it.
- Written once, never updated. A plan nobody updates stops being trusted within a month. Set a weekly time to update the status.
- Kept somewhere nobody looks. A plan in an email attachment is forgotten by the second week. Keep it, or at least its task list, where the team already works.
How to keep a work plan on track
Writing the plan is the easy part. These habits keep it useful once the work has started:
- Update it weekly, in a set slot. Ten minutes on a Friday to update every task's status is enough for most plans.
- Report against the milestones, not just the tasks. “Designs approved on time, content one week late” tells a sponsor more than a list of ticks.
- Change the plan when reality changes. Move dates, drop goals or ask for more resources openly, and record what changed and why.
- Keep a list for later. Good ideas that arrive mid-plan go on a “next time” list instead of into this plan.
- Review it at the end. Note what took longer than planned and why. The next plan's estimates will be better for it.
Work plan software: when a document is not enough
A document is the right place to agree a work plan: it is easy to read, comment on and sign off. It is a poor place to run one, because every update means someone editing a file, and nobody gets reminded when a task is due.
Once a plan is agreed, many teams move the task list into a project tool and keep the document for the goals, scope, budget and risks. In Coavon, each deliverable can be a section in a Flow project and each task a Flow task with its owner, dates and status, and milestones mark the key dates. Owners are reminded as tasks come due, and on Pro and Business you can see the plan on a timeline, link tasks that wait on each other and post a weekly status update (On track, At risk or Off track). Business adds goals that projects report against, which suits quarterly and annual work plans. The plan document itself can live in Docs beside the project. Flow has no budget tracking of its own (you can add a cost to each task as a number field), so keep the budget table in the plan or your accounts.
If you are choosing a tool, our comparison of project management software for 2027 covers Coavon and eight others, with prices for small teams.
Frequently asked questions
What is a work plan?
A work plan is a short document that sets out what a piece of work should achieve and how it will get done: the goals, deliverables, tasks, who does each one, the dates, the resources and budget, and the risks. It is used for projects, for a team’s work over a month, quarter or year, and for one person’s work.
How do I create a work plan?
Write a short summary and two to four goals with a measure, target and date; set the scope, including what is out of scope; list the deliverables and break them into tasks; give every task one owner and dates; add milestones, resources and budget; write down the main risks and constraints; agree how progress will be tracked; then get it approved and update it every week.
How do I write a simple work plan?
On one page, write the goal with a number and a date, the deliverables, a table of tasks with an owner and due date for each, the resources you need, the two or three main risks, and how and when you will check progress. The simple version of our free work plan template has exactly these sections.
Is it a work plan or a workplan?
Both are correct and mean the same thing. Work plan, as two words, is more common in business writing. Workplan, as one word, is common in government, nonprofit and grant documents. Use whichever your organization or funder uses, and use it consistently.
What are the main parts of a work plan?
A summary, goals, scope and deliverables, tasks and timeline, milestones, resources and budget, risks and constraints, and roles and communication. Grant work plans often add objectives and activities, outputs and outcomes, and an evaluation section.
What is the difference between a work plan and a project plan?
They overlap a lot and the names are often used for the same document. A work plan sets out what will be done, by whom, by when and with what, and is used for projects and for ongoing work over a period. A project plan covers one project and is often more formal, adding things like a schedule baseline, change control and separate quality or communication plans.
What is the difference between a work plan and an action plan?
An action plan is usually smaller: a list of actions, owners and dates to reach one goal or fix one problem. A work plan adds the goals with their measures, the scope, the deliverables, the resources and budget, and the risks around that list.
What is the purpose of a work plan?
To get everyone agreeing on the goals, scope, owners and dates before time and money are spent, and to give a clear way to check progress afterwards. It also surfaces problems early, such as too little time or money, and gives you a starting point for the next similar piece of work.
What is an example of a work plan?
A 12-week plan to replace a company website, with goals (such as doubling contact form enquiries by June), a scope that leaves out online booking, ten tasks each with one owner and dates, four milestones, a budget of $11,100, three risks with responses, and a weekly update every Friday. This guide also includes a quarterly marketing team plan and a 90-day plan for a new hire.
How long should a work plan be?
As short as it can be while still answering what, who, when, with what and what could go wrong. A personal or monthly plan often fits on one page. A plan for a funded project or a client engagement may run to four or five pages.
How often should a work plan be updated?
Update the status of each task every week, and update the plan itself, with a new version number and date, whenever something big changes, such as a goal, a deadline, the budget or who is doing the work.
Who writes a work plan?
Usually the person who will own the work, such as a project lead, team manager or the individual for a personal plan, with input from the people doing the tasks. It is then reviewed and approved by whoever is paying for the work or responsible for its result.