Why this matters
What “OneNote project management” actually means
OneNote is the tool people reach for when their organisation already has Microsoft 365 and adding another piece of project software requires a procurement cycle. So OneNote project management is, for most people, “the project work I’d do in Asana if I could buy Asana.” The templates that work in OneNote are the ones that respect what OneNote actually is: a hierarchical notebook where each page can have free-form text, embedded files, and tables. The templates that don’t work are the ones that try to make OneNote into a kanban board or a Gantt chart.
The 2026 reality is that OneNote got a tighter integration with Microsoft Planner and To Do during the recent Microsoft 365 update. That changes the calculus for some templates: where you used to need a custom kanban-in-OneNote, you can now embed a Planner board on a OneNote page and get the kanban for free. We’ll cover where that integration helps and where you still want a OneNote-native template.
This piece is the umbrella for the OneNote project space. For deeper coverage on specific shapes, our pieces on project dashboards, meeting templates, and using OneNote for project management go into the specifics.
The shapes
Four template shapes that cover real project work
| Shape | Best for | OneNote-native or ported? |
|---|---|---|
| Project overview | Projects with a definable scope, owners, dates | Native (single page or section) |
| Kanban / task tracking | Sprint-shaped work, parallel tasks | Better via embedded Planner |
| Meeting notes | Decisions, owners, follow-throughs | Native, table-heavy template |
| Project dashboard | Status reporting, multi-project overview | Native, multi-section structure |
The cleanest mental model: one notebook per project, sections for “Overview,” “Meetings,” “Decisions,” and “References.” Pages within those sections hold the per-meeting notes, per-decision rationale, and reference materials. The kanban shape doesn’t fit cleanly into OneNote’s hierarchy, which is why most kanban-in-OneNote templates feel awkward; they’re forcing a board metaphor onto a notebook that wants to be a notebook.
Picks
Six OneNote project management templates that earn their place
Built-in OneNote project overview template
OneNote ships with a “Project Overview” page template (Insert → Page Templates → Business). It’s plain, it’s free, and it does the basic thing: project name, owner, dates, scope, deliverables, status. Most “OneNote project template” posts on the internet are repackaging this with prettier headers. For new projects where you haven’t built a custom shape yet, start here. Customise as you learn what your team actually fills in.
Auscomp Kanban for OneNote (free)
Auscomp’s free Kanban template is the most-respected community-made template for OneNote. Three-column kanban (To Do, In Progress, Done) within a OneNote page; tasks are bullet-list items moved by drag. Useful for solo or small-team work where you don’t want to spin up a Planner board. Limitation: doesn’t scale past a dozen tasks per board.
Meeting notes (custom, table-based)
The strongest custom template you can build in OneNote is a meeting-notes layout with these blocks: meeting title and date at the top, attendees as a tag list, agenda items as a numbered list, decisions table (decision, owner, deadline), action items table (item, owner, due date, status). Save as a template via Insert → Page Templates → Save current page as template. Our meeting template piece covers the field structure.
Project dashboard (multi-section)
For project portfolios (multiple parallel projects), a dashboard section that lists each project’s name, owner, status, and current blockers earns its place. The structure is one section per project plus an “All Projects” overview section that links to the per-project sections. Updating the overview section once a week takes 10 minutes and gives you a portfolio-level view without leaving OneNote. See our project dashboard piece for layout.
Embedded Microsoft Planner board (the integration win)
Since the 2025 Microsoft 365 update, you can embed a Planner board directly in a OneNote page (Insert → Online Video / File → Planner). The board lives in Planner and renders in OneNote; updates to either reflect in both. This replaces the need for kanban-in-OneNote for any team that has Planner access. Not every Microsoft 365 license includes Planner, so this won’t work for every reader.
Premium Etsy bundles (mixed quality)
Etsy sellers ship paid OneNote project bundles in the $20 to $40 range, usually with project overview, kanban, meeting notes, dashboard, and CRM templates. Quality varies. The good ones save 4 to 6 hours of template-building time and look polished. The bad ones look polished and break OneNote’s structure (overuse of fixed-width tables, embedded images that don’t render on mobile). Check buyer reviews and confirm mobile rendering before paying.
OneNote project management templates work best when they respect the notebook hierarchy. Templates that try to make it a kanban board fight the tool.What we found
When to skip
When OneNote is the wrong tool for project management
OneNote starts losing the comparison against dedicated tools at three thresholds. First, when the team is more than five or six people, because OneNote’s collaboration is good for parallel-page editing and bad for real-time conflict resolution; collaborators step on each other’s edits in ways that Asana or Monday don’t. Second, when sprint-shaped work outweighs reference-shaped work, because OneNote isn’t a kanban or sprint tool natively (the Planner integration helps, but a pure Planner-or-Jira workflow is cleaner). Third, when reporting matters: OneNote has no native reporting, no burndown charts, no automatic status rollups.
OneNote stays the right tool when the project is reference-heavy (many documents, many decision logs, many meetings to capture), when the team is small (two to five people), and when the organisation already pays for Microsoft 365. For solo project work, OneNote is genuinely competitive with Notion and Obsidian; the notebook hierarchy is more intuitive than Notion’s database-first structure for many users.
Common mistakes
Three template traps to avoid
Looks like a feature
- “50+ templates in one bundle.”
- Heavy use of fixed-width tables for layout.
- Templates that recreate Trello or Asana inside OneNote.
Why it isn’t
- You’ll use 4 of 50; pay for category coverage instead.
- Fixed tables break on mobile and don’t reflow; OneNote was built for free-form, not grid-locked layouts.
- Better to embed Planner than to fake a kanban; the recreated kanban is always slower.
The verdict
How we’d structure project work in OneNote
For most project work in OneNote, the structure that holds up is: one notebook per project, four sections (Overview, Meetings, Decisions, References), built-in project-overview template on the Overview page, custom meeting-notes template applied to each new page in Meetings, decisions captured as a single rolling page in Decisions, references stored as embedded files in References. If you have Planner access, embed a board in the Overview page for task tracking. If you don’t, use a single page with a checklist for tasks; don’t try to recreate a kanban.
That structure takes about an hour to set up and survives multi-month projects without the template needing major surgery. It’s the structure we wish more “OneNote project template” posts pushed; the field is currently dominated by elaborate single-page templates that try to do everything at once and fail the moment a project lasts longer than a month.
OneNote will keep evolving alongside Microsoft 365 in 2026; the Loop integration is expected to deepen, and the Planner-OneNote bridge will likely add more bidirectional sync. We’ll update this guide when the integrations shift. Tell us in the comments which OneNote project structure has actually held up for your team. Six-month-old templates teach more than two-week-old screenshots.
FAQ
If yours isn’t above, drop the question in the comments and we’ll add it.
People also ask