Turn a project's OneNote notes into a formal charter and risk register

Step 1: Make sure the notebook is reasonably completeOneNote

Scan back through the notebook's meeting sections and check that the major decisions, scope discussions, and risks raised over the project's life are actually captured somewhere — Copilot can only draft from what's written down, so a notebook with gaps produces a charter and risk register with the same gaps, silently.

Step 2: Ask for the charter, status, and risk register togetherCopilotClaude

Doing all three from the same notebook in one pass keeps them consistent with each other, rather than drafting separately and reconciling later.

Prompt idea:

Using the notes in this project notebook, draft: a one-page project charter (objective, scope, stakeholders), a current status summary, and a risk register listing each identified risk with a proposed mitigation.

Step 3: Validate the risk register especially closelyWord

Risks mentioned in passing during a meeting aren't the same as risks the team has actually assessed — confirm each one is real before it goes in a formal register.

Step 4: Share drafts with the project team before finalizingWord

The notebook captures what was said, not necessarily what everyone meant — a quick team review catches misinterpretations early.

Check the work

• Confirm every listed risk was actually discussed as a real risk, not a passing comment.
• Check the charter's scope and objective against what stakeholders actually agreed to.
• Have at least one other project team member review before treating any of these as final.

Source: NBold, "OneNote + Microsoft 365 Copilot Notebooks: Build Living Project Playbooks" (2026)