Module 11: OneNote, Loop, and Copilot Notebooks
Lesson 11.6: Notebook Capstone: Build a Project Brain
Lesson Promise
Design a complete project-brain workflow using OneNote, Loop, Copilot Chat references, and Copilot Notebooks.
Real-World Scenario
A learner must build a reusable project-brain system for a client engagement, course launch, research project, or internal initiative.
Core Concept
The capstone combines note capture, Loop-style collaboration, selected references, notebook scope, source hygiene, decision logs, weekly reviews, and sharing rules.
The goal is not to make Copilot omniscient. The goal is to make project context explicit, current, and reviewable.
A finished project brain includes an intake structure, reference map, prompt pack, maintenance cadence, sensitivity rules, and final review checklist.
Step-By-Step Workflow
- Choose one project and define the decisions the project brain should support.
- Create a note structure for meetings, research, decisions, risks, and tasks.
- Create a reference map for documents, pages, files, links, and chats where available.
- Design notebook prompts for weekly review, source audit, decision log, and next actions.
- Create sharing and sensitivity rules.
- Run a final audit for stale sources, missing references, and unsupported conclusions.
Prompt Lab
Bad Prompt
Build a notebook for my project.
Better Prompt
Build a project-brain workflow with notes, references, decisions, risks, weekly review prompts, and sharing rules.
Expert Prompt
Design a complete project brain for this initiative. Include OneNote capture structure, Loop collaboration page plan, Copilot Notebook reference map, must-use sources, excluded sources, prompt pack, decision log, risk log, weekly review cadence, sharing rules, sensitivity warnings, stale-source audit, and final verification checklist. Do not assume Copilot can access sources I did not add or reference.
Hands-On Exercise
Build the full project-brain blueprint for a safe project and test the weekly review prompt.
Deliverable
A complete project-brain blueprint with note structure, reference map, prompt pack, review cadence, sharing rules, and verification log.
Knowledge Workspace Review Checklist
Common Mistakes
- Treating a notebook as if it can see every file, email, chat, or web page automatically.
- Adding too many weak references instead of curating the few sources that actually matter.
- Letting stale notes, old plans, or unverified links drive current project answers.
- Sharing notebooks without checking linked-file permissions and sensitive content.
- Confusing OneNote notes, Loop pages, Copilot Pages, and Copilot Notebooks as the same experience.
Quiz / Checkpoint
What makes a project brain trustworthy?
It uses explicit sources, current references, decision logs, review cadence, permission checks, and human verification.
Official Sources To Verify
- How Microsoft 365 Copilot Notebooks works
- Get started with Microsoft 365 Copilot Notebooks
- Add references to your Microsoft 365 Copilot Notebook
- Refer to specific files and more in Microsoft 365 Copilot
- Welcome to Copilot in OneNote
- Summarize your OneNote notes with Microsoft 365 Copilot
- Copilot tutorial: Summarize and identify to-do items with Copilot in OneNote
- Loop access via Microsoft 365 subscriptions
- Copilot Chat in Microsoft 365 apps
- What Copilot license do I have
Want your AI product explained to a large AI-native audience?
Kingy AI helps AI companies turn complex products into clear, useful YouTube videos that drive awareness, product understanding, demos, clicks, and search visibility.
