Building a project management system in Notion is achievable. The previous post in this series showed you exactly how to do it. But building it well — with the right database architecture, the right relations, the right views for every phase of a project lifecycle, and documentation that lets a team member pick it up without training — takes significant time. Time that most project managers and business owners do not have when a project is already in motion.
The Project Management with AI template exists to close that gap. This is a full review of what it contains, how it is structured, and whether it is the right starting point for your team.
The Problem With Starting From Scratch
When you build a project management system from a blank Notion page, you make architecture decisions under time pressure. You create a tasks database and then realise later it needs a Phase property. You add the Phase property and then realise your views need to be reorganised around it. You add a risk register three weeks into the project because a stakeholder asked for one, and it does not connect to the tasks database because you did not anticipate needing that relation when you first set things up.
Every late-addition change to a database structure requires updating views, relations, and rollups that were built around the old structure. The system accumulates debt. By the end of the project it works, but it is patched and improvised rather than designed.
A well-designed template starts from the full picture — every database that a project lifecycle needs, with every relation already connected — so the architecture is right from day one.
What the Template Covers
The template covers five project phases: Discovery and Initiation, Planning, Execution and Monitoring, and Closure. Each phase has its own section with the databases and documents relevant to that stage. The full template includes 30+ databases, pages, and document templates across all phases — all connected through a central Projects hub.
Phase 1 — Discovery and Initiation
The Discovery phase includes a Business Requirements Document template, a Project Charter page, a Stakeholder Identification database, and an initial Risk Identification database. Each of these is a structured Notion page with AI prompts built into callout blocks — you paste the prompt into your AI tool of choice, get a draft output, and paste the result into the relevant section.
The BRD template is the most detailed component in this phase. It covers project background, business drivers, scope definition, functional and non-functional requirements, assumptions, constraints, and approval sign-off. The structure mirrors the BRD format used by professional project managers, adapted for Notion’s page format. It is a working document template, not just a checklist.
Phase 2 — Planning
The Planning phase is the most database-heavy section. It includes a full Project Task Tracking database with Board, Timeline, and filtered views per phase. A Resource Estimation database links team members to tasks and calculates estimated hours and cost automatically through Rollups. A Budget Tracker covers every cost category with Planned versus Actual tracking. A Project Schedule database with start and end dates feeds the Timeline view, producing a Gantt-style project schedule directly in Notion.
The Stakeholder Communication Plan — often one of the most poorly managed aspects of project planning — is a database with each stakeholder, their preferred communication channel, frequency, and the team member responsible for managing that relationship. A filter shows only stakeholders due for communication this week.
Phase 3 — Execution and Monitoring
This is where the daily work happens. The Execution phase adds a Meeting Minutes database linked to the task database (action items from meetings become tasks automatically), a Change Request Log for scope changes, a Quality Assurance Checklist database, and an Issue Log that distinguishes issues — problems that have occurred — from risks, which are problems that might occur.
The Status Report template is a highlight of this phase. It is a recurring page template inside the Meetings database — a structured weekly status report with sections for progress summary, completed milestones, current risks and issues, budget summary (pulling rollup data from the budget database), and next week’s plan. Fill in the narrative sections and the numbers populate automatically from the connected databases.
Phase 4 — Closure
Project closure is the phase most teams rush or skip entirely. The template includes a Project Closure Report template, a Lessons Learned database (one entry per lesson, tagged by phase and category), a Final Budget Reconciliation view (automatically comparing planned to actual across all budget line items), and a Project Archive checklist ensuring documentation is complete before the project is closed.
The Lessons Learned database is particularly valuable over time. After five or six projects, the accumulated lessons — tagged by project type, phase, and category — become a searchable knowledge base for how this team works and what it has learned. It is the kind of institutional knowledge that usually lives in people’s heads and leaves when they do.
Where AI Comes In
The AI component of the template is not a Notion AI subscription feature — it is a set of structured prompts embedded directly into the template pages as callout blocks. Each prompt is written to generate a specific output: a first draft of a BRD section, a risk identification brainstorm for a specific project type, a stakeholder analysis for a given industry, a status report narrative based on project data you provide.
You copy the prompt, add your project-specific context, paste it into any AI tool — ChatGPT, Claude, Gemini — and get a draft that fits the template structure. The output goes back into the corresponding section of the Notion template. It is AI assistance embedded into a workflow rather than bolted on as an afterthought.
The Database Architecture
The central hub is the Projects database. Every other database relates back to it: Tasks, Risks, Budget, Stakeholders, Meetings, Change Requests, Issues, and Resources all have Relation properties pointing to Projects. The Projects database has Rollup properties pulling completion percentages, risk counts, issue counts, budget variance, and stakeholder counts from all connected databases simultaneously.
Opening a project record shows the complete project picture — every metric from every database — on a single page. That is the value of the relational architecture: information does not need to be gathered and assembled manually. It is already assembled, always current, and accessible in one click.
Who This Template Is For
This template is for professional project managers, business owners managing multiple workstreams, and consultants running client projects who want a serious Notion PM system without spending two to three weeks building it from scratch. It is deliberately more comprehensive than most people need for a single simple project — it is designed for people who run projects professionally and need a system that covers edge cases they will eventually encounter.
It is not the right starting point for a solo freelancer managing their own task list, or for a team that has never used Notion before. Both of those cases are better served by simpler templates — the free Everyday Life template for the solo user, and the Freelance Management System for the freelancer.
How to Get Started With It
After duplicating the template, spend the first thirty minutes reading through the user manual — a dedicated page inside the template that explains each section, the database connections, and the recommended order for setting things up. Do not delete sample data until you have read the manual. The sample data shows the template working correctly, which is the most useful reference you have for understanding what it is supposed to do.
Then set up the Team Members section with your actual team. Configure the Projects database with your real projects. Add tasks to the first active project. From that point, use the template for one full project cycle before making any structural changes — a complete project run is the best way to learn which parts you use heavily and which parts need customisation for your specific workflow.
What You Get That You Could Not Build Quickly Yourself
Three things distinguish this template from a self-built system. The first is the BRD, charter, status report, and closure report document templates — professionally structured project documents that take significant time to design well and that most self-built Notion PM systems skip entirely.
The second is the Rollup architecture on the Projects database — eight separate Rollup and Formula properties pulling data from eight connected databases simultaneously, all calculating correctly and updating automatically. Building that correctly from scratch without errors requires significant experience with Notion’s database system.
The third is the AI prompt library — forty prompts covering every document in the template, each written to produce output that fits the template structure. Writing good AI prompts for structured project management documents is a skill in itself, and having them pre-written for the specific structure you are using saves considerable iteration time.
The Project Management with AI template is available at createdigitaltools.com. It is a one-time purchase with lifetime updates — as Notion adds new features, the template is updated to use them. If you are running projects professionally and want a Notion system that covers the full lifecycle, this is the template to start with.
Disclosure: This post contains affiliate links. If you sign up for Notion through the links in this post, we may earn a small commission at no extra cost to you. The Project Management with AI template is our own product and we have an obvious financial interest in it — but everything written above reflects how the template actually works.
0 Comments