Running projects with Microsoft 365 Copilot
Build a project hub and AI notebook in about an hour, then run a 20 minute weekly update that keeps it accurate.
How to set up a project so Copilot gives real answers, not guesses.
What it does
Copilot has no memory of your project. It only answers well when your status, decisions and actions live in one place instead of scattered across email, chat and someone's head. This guide shows how to build that place, and how to keep it accurate week after week. It is for anyone running a rollout, a system change or a policy update without a project manager title, inside a company Microsoft 365 tenant. You set up a single project code, one hub, a task list and a curated set of sources, so Copilot works from the same information you and your team already use. What makes it different from a blank page is that every step is spelled out: the naming rules, the hub pages, the status board columns, the prompts to run, and the weekly routine that keeps the whole thing honest. It also includes a setup checklist and a table of common mistakes to avoid.
What is inside
- The five principles that stop projects becoming untraceable
- A hub page map: overview, status board, decision log, risks, meeting notes
- The nine status board columns and what each one is for
- Four ready to use Copilot prompt templates
- A weekly six step routine to keep the hub current
- A setup checklist and a table of common mistakes
Who it is for
- Someone coordinating a rollout, system change or policy update without a project manager title
- A project lead who wants the work to survive a handover without them
- Anyone using Copilot for project status who gets thin, generic answers