Free Project Management Template for Microsoft Planner (Download + Guide)

What should a Microsoft Planner project template contain?

A Planner plan holds exactly three things: tasks, buckets, and labels. Everything else — the timeline, the charts, the assignments — is a view of those three. So the template question becomes: which buckets, which labels, and which task patterns do you reuse on every project?

The answer that holds up in practice is smaller than most teams expect.

Buckets for the workflow. Five buckets cover the stages a task actually moves through: `01 Intake`, `02 Plan`, `03 In Progress`, `04 Waiting`, `05 Done`. The numbering matters more than it looks: Planner sorts buckets alphabetically, so numbers are the only way to keep a sensible left-to-right order.

Labels for work type. Planner gives every task a coloured label palette. Use four: `Client`, `Internal`, `Approval`, `Blocker`. Labels are the closest thing to a custom field on a basic plan, and mixing them with buckets is the most common structural mistake — a label called “In Progress” duplicates a bucket and confuses everyone.

A standard checklist per task type. Planner’s checklist is where a template earns its keep, because it turns “write the campaign brief” into six concrete steps. Keep one checklist per recurring task type, not per task instance.

A priority convention. Planner offers Urgent, Important, Medium, and Low. Most teams use two of them. Decide which two before the first project, because priority is the only built-in field the charts will segment.

An attachments and notes rule. Planner tasks accept files and a notes field, and both rot quickly. The rule that works: the note field holds a link to the source document, never a pasted copy.

That is the template. It fits on an index card, which is the point: Planner’s value is that a new team member can read the board in ten seconds.

How does the template map onto Planner’s plan-and-bucket model?

Every Planner plan is backed by a Microsoft 365 Group, and the plan object you see is a board over that group’s tasks. This matters for the template because the *plan* is the unit you copy, and the group is the unit that controls membership and file storage.

The single most important row is the first. Because Planner’s progress field is limited to Not started, In progress, and Completed, teams that rely on it end up with a board where everything is “In progress” and nothing is informative. Buckets solve this: a task in `04 Waiting` is not a different progress state, it is a different location, and moving the card is the status update.

The second most important row is the last. Planner has no template gallery of its own in the way ClickUp does; the practical template mechanism is Copy plan, available from the plan menu, which creates a duplicate with the same buckets and tasks. That is a genuine template — with known gaps covered below.

How do you build the template in Planner, step by step?

Build the template as a plan called `TEMPLATE — Project Delivery`, keep it in a dedicated group, and give it no real dates. A template with dates is a template that lies.

1. Create the plan from the Planner app or from the Tasks by Planner and To Do tab in Teams. Name it with the `TEMPLATE` prefix so nobody mistakes it for live work.
2. Add the five buckets in numbered order: Intake, Plan, In Progress, Waiting, Done.
3. Add one placeholder task per bucket describing the kind of work that belongs there — for example, “Request received and triaged” in Intake. These placeholders teach the structure faster than any document.
4. Set four labels and name them explicitly: Client, Internal, Approval, Blocker. Rename the label group too, or it stays “Label group 1”.
5. Build the standard checklists on the placeholder tasks: brief approved, asset received, review booked, published, measured.
6. Set the views: Grid for editing, Board for the daily stand-up, Charts for the weekly review, Schedule for dates.
7. Add one milestone task per phase in the Plan bucket, and pin the plan in Teams so it opens in one click.
8. Copy the plan for the first real project, and leave the template untouched from then on.

Step eight is where discipline starts. The template should never carry live work, because the moment it does, copying it copies last month’s leftovers and the drift begins.

How do you copy a plan without inheriting last month’s mess?

Use Copy plan from the plan menu, choose a destination group, and immediately rename the copy to the project name. The copy includes buckets, tasks, assignments, labels, and dates. It does not include attachments, comments, or a reliable history of completed work, and it copies due dates as-is — which is why a template with 2025 dates produces a 2026 project that is already overdue.

Three fixes make copying clean. First, strip all dates from the template and set them only in the copy. Second, delete the placeholder tasks in the copy in one pass, before anyone starts adding work, so no placeholder survives into a status report. Third, keep the template under twenty tasks; a hundred-task template makes every copy a small migration project.

If your team copies plans more than twice a month, the copy step is your real template cost, and it is the first place to look when someone suggests moving to a paid tool with true templates.

What can Planner’s basic plans do without a premium licence?

Basic Planner — the version included in Microsoft 365 Business Basic and Standard — covers tasks, buckets, labels, checklists, attachments, comments, charts, schedule, and the Teams tab. That is a functional project tracker, and for many small teams it is enough.

What it does not cover is the project-controls layer: dependencies between tasks, baselines, goals, sprints, custom fields, critical path, and advanced reporting. Those moved into Planner’s premium tier after Project for the web was retired on 1 August 2025, and they require a premium Planner licence.

The practical consequence for the template is that sequencing is manual. If task B cannot start until A finishes, the basic plan shows two dates and no link; when A slips, someone has to notice and move B. That is fine for a ten-task project and corrosive for a hundred-task one.

What does the template cost in Microsoft Planner in 2026?

The template is free to build. What you pay for is the licence that surrounds it, and the decision is usually between an existing Microsoft 365 plan and one premium Planner seat per project manager.

Prices are published list figures for 2026 on annual commitments, before tax, and they vary by region and agreement.

Example 1: the fifteen-person team already on Microsoft 365. If the team has Business Basic, the Planner template costs $0 extra — 15 × $6 × 12 = $1,080 per year covers mail, Teams, and the plan. Adding premium Planner for three project leads is 3 × $10 × 12 = $360 per year, not fifteen seats. The same fifteen people on a dedicated PM tool at $17 per seat would be 15 × $17 × 12 = $3,060, a difference of $1,980 a year.

Example 2: manual date shuffling as a hidden invoice. Take twenty tasks that depend on each other and no dependency links. If a lead spends five minutes a week nudging dates after each slip, that is 20 × 5 = 100 minutes a week, roughly 80 hours across 48 working weeks. At a $60 loaded rate that is $4,800 a year — thirteen times the $360 premium upgrade. The arithmetic rarely justifies premium for one project, and usually does for five running at once.

Example 3: reporting time. A monthly status pack assembled by hand takes three hours: exporting the chart, chasing updates, formatting. Twelve months is 36 hours. With a clean bucket convention and a saved chart view, the same pack takes 45 minutes, or 9 hours a year — a saving of 27 hours, worth $1,755 at $65 per hour, against a licence cost of zero on Business Basic. Reporting discipline is the cheapest upgrade available.

What are the trade-offs of running projects in Planner?

The advantage is incontestable for Microsoft shops: the plan lives where the team already works, identity is handled by Entra ID, files sit in the group’s SharePoint library, and there is no new vendor, no new invoice, and no new login. Adoption is often the fastest of any tool because nobody has to be persuaded to open Teams.

The cost is expressiveness. One assignee per task means shared ownership becomes a comment. Three progress states mean buckets must carry real meaning. No dependencies on basic plans means sequencing is a human habit. No custom fields means priority and labels are the only segmentation you get.

The second cost is reporting at the edges. Planner charts are good at “how many tasks by bucket” and poor at “is this project healthy”. Anything that compares two plans — a portfolio view, a cross-team capacity view — is outside the product, and people rebuild it in Excel every month.

The third is that Planner is a coordination tool, not a document tool. Project charters, decision logs, and meeting notes belong in OneNote or SharePoint, which means the template spans two products. That is acceptable, but it must be deliberate, or the plan becomes a set of links to nowhere.

What breaks a Planner template after a few months?

Bucket creep. Someone adds `Blocked by Vendor` for one project, and now every plan has a bucket that applies to one supplier. Fix: buckets are capped at five, and additions need the plan owner’s agreement.

Label palette drift. Four labels become eleven, half of them unused, and the board turns into confetti. Fix: rename labels explicitly and delete unused ones each quarter.

Completed tasks piling up. Because Completed is a status and Done is a bucket, tasks end up in both, and the board shows a Done column that is empty while the chart says work is finished. Fix: pick one convention — status for completion, bucket for location — and document it in the plan description.

Copy drift. The template gains a task for one project, and every future copy inherits it. Fix: never edit the template during a live project; queue changes and apply them monthly.

Date rot. Template dates become past dates, and every copy starts overdue. Fix: strip dates from the template entirely.

Ownership ambiguity on shared work. One assignee field, two real owners, and the task is silently owned by nobody. Fix: assign the accountable person and put the collaborator in the task notes, or split the task.

When is Planner the wrong choice?

Planner is the wrong tool when the work needs sequencing that changes weekly, when a portfolio view is a standing requirement, or when the same person must appear as owner on twenty tasks across five plans and you need to see their total load. Basic Planner has no workload view, and premium Planner’s people view answers a narrower question than a resource manager asks.

It is also the wrong choice when the deliverable is a document rather than a stream of tasks. A project plan that lives in prose — scope, assumptions, approvals — belongs in OneNote, where pages and sections fit the shape of the content. The project plan template for OneNote covers that version.

How does Doitify compare for the same template?

Doitify is our product, so treat this as disclosure rather than an independent comparison. It provides projects, tasks, sub-tasks, checklists, owners, due dates, and the coordination layer around them: Kanban, Gantt, calendar, roadmap, workload views, work and performance reports, automations, and import/export, with multiple assignees per task and custom statuses rather than fixed progress states.

The honest summary is that Planner wins on distribution and price for Microsoft-centric teams, and loses on expressiveness. If your project fits five buckets and four labels, Planner is the cheaper correct answer, and switching would buy features you would not use. If your board keeps overflowing its buckets because the workflow has more than five real stages, the constraint is the tool, not the template.

Conclusion

Microsoft Planner rewards a template that respects its shape: five buckets for stages, four labels for work type, checklists for the steps that repeat, and no dates in the master copy. Built that way, a free Microsoft 365 licence runs real projects competently, and the premium tier becomes a decision about dependencies and reporting rather than a default.

Decide in this order: does the workflow fit five buckets, does anything need to be sequenced automatically, and does anyone ask for a cross-project view? Two yeses and premium Planner is worth the $10. One or none, and the free plan with a disciplined copy habit is the better answer — cheaper, already installed, and one fewer system for the team to learn.

If this post on Microsoft Planner project template was helpful, you might also enjoy Project Management Software for Cross-Functional Teams and Program Manager vs Portfolio Manager: Roles Compared.