How the advisory team should use OneNote and Copilot Notebooks — to turn scattered notes, PDFs, meeting transcripts, and reference documents into a scoped, queryable, shareable project brain. Six distinct OneNote AI surfaces, six advisory workflows, and the single feature that changes how research-heavy engagements are run.
Before the features, the reframe. OneNote on its own is a container for notes. Copilot Notebooks turn a curated collection of project material into a scoped AI workspace. The shift isn't cosmetic — it changes what "capturing project context" means.
Most consultants have used OneNote for years as a glorified scratchpad. Meeting notes in one section, reference snippets in another, action items scattered through. The content is there, but nobody ever goes back to find anything. On a typical project the accumulated notes are a graveyard — real context buried in chronological order with no way to query it.
"Copilot Notebooks are AI-powered workspaces for a project or topic built on your reference materials — bringing together your work context behind a project in one place for you, your team members, and Copilot to collaborate on."
What's structurally different about Copilot Notebooks — compared to every other Copilot surface in this playbook — is scoped grounding. In Word, Excel, PowerPoint, Outlook, and Teams, Copilot reasons over your whole Microsoft Graph (every email, file, meeting you have access to) plus sometimes the open web. That breadth is useful but it also introduces noise: the model has too many possible sources and picks whichever seems relevant. In a Copilot Notebook, Copilot reasons only over the references you've added to that notebook. Nothing else. No web grounding. No cross-tenant leaks. Just your curated material.
Three specific shifts that this scoping enables:
Old pattern: project context is scattered across SharePoint folders, Teams chats, OneNote sections, email threads, PDFs downloaded to OneDrive. New pattern: one notebook per project. Add every relevant reference as a link (not a copy). Copilot treats the whole collection as a single knowledge base.
Old pattern: receive a 100-page regulatory document, read it once, hope you remember the right sections when they come up weeks later. New pattern: add the document to the project notebook. Three weeks later when the topic comes up, ask the notebook what it says — get an answer grounded in the specific document, with citations.
Old pattern: project context lives in each team member's head, with partial overlap in emails and files. Key people leaving the project = meaningful loss of institutional memory. New pattern: the shared Copilot Notebook is the institutional memory. New joiners query it to onboard. Leavers' knowledge persists in the curated references.
For Arup advisory specifically — where engagements routinely span 5-15 reference documents (client RFP, past proposals, research briefs, stakeholder maps, technical standards, meeting transcripts) — this is the single biggest time-saver in the whole stack for research-heavy work. Everything else in the playbook (Word, Excel, PowerPoint, Outlook, Teams) is about producing outputs. Copilot Notebooks are about holding the context that those outputs depend on.
"Copilot in OneNote" and "Copilot Notebooks" are related but structurally different. OneNote Copilot is Summarise/Rewrite on your own notes. Copilot Notebooks is a grounded AI workspace. Both useful; different tools for different jobs.
Microsoft has given two genuinely different products almost the same name. The advisory team will waste hours confused by this if not addressed head-on. Here's the distinction, clearly.
Your long-established notes container. Pages organised into sections, sections into notebooks. You type, paste, draw, embed things. Copilot in OneNote operates on this content.
A curated portfolio of references that Copilot reasons over. Not where you take notes — where you gather material Copilot should know about.
The two play complementary roles. OneNote Notebooks are where you create content — your own notes, meeting captures, rough thinking. Copilot Notebooks are where you gather the content Copilot needs to help you with a project — which can absolutely include a pointer to your OneNote notebook as one of its references.
A sensible Arup pattern: one OneNote notebook per consultant (your personal notes across all engagements, organised by section per project), and one Copilot Notebook per engagement (the curated project brain, shared with the team, referencing both your OneNote section for that engagement and the external documents). That way your capture layer and your AI-grounded research layer each do what they're good at without overlap.
Copilot Notebooks has stricter prerequisites than most other Copilot surfaces. Three checks up front save the team from discovering constraints mid-engagement.
1. Licence check. Copilot Notebooks requires both a Microsoft 365 Copilot licence (the paid enterprise add-on, not Pro alone) and a SharePoint or OneDrive service plan on the same account. The SharePoint/OneDrive requirement is because notebooks are stored there — without it, you can't create a notebook at all. Most Arup M365 accounts have both by default, but check before training the team.
2. Reference curation discipline. The notebook is only as good as the references you add. Four rules:
3. Custom instructions — the underused lever. Every Copilot Notebook supports custom instructions that shape how Copilot responds to all prompts in that notebook. This is the most underused setting. Useful defaults for an Arup advisory notebook:
Always respond as if briefing a senior Arup advisory consultant. Use professional, neutral tone. When answering, cite the specific reference document each claim comes from. Flag where references disagree. Identify gaps where the notebook doesn't contain enough material to answer confidently. For any recommendations, structure as: Recommendation / Rationale / Evidence / Caveats. Do not invent facts not present in the references.
Set once per notebook; applies to every prompt from every team member. Think of it as the notebook's system prompt.
Day one of a new engagement. Instead of reading ten documents in sequence over three hours, spend thirty minutes building a Copilot Notebook. You'll have better context after the build than most consultants would have after a day of reading.
Not everything needs to live in a Copilot Notebook. For rough in-meeting notes, half-formed thoughts, quick captures — OneNote is still the right place. But Copilot in OneNote turns those rough captures into structured team outputs in minutes.
One specific move worth building into every consultant's habit: after any meeting where you took notes (with or without Teams Recap), extract action items into a task list immediately. The prompt is trivial — "Extract every action item from these notes as a task list with owner and due date where I mentioned one. Flag items where the owner is unclear" — but the discipline of doing it reliably means nothing falls through the cracks. Copy the output to Planner, Microsoft To Do, or Teams tasks.
Quick rewrite trick: select rough notes from a client call that need to go into an internal briefing email. Right-click → Rewrite with Copilot. Adjust for professional tone and concision. Paste into the email. The round-trip from OneNote capture to Outlook-ready prose takes under a minute.
The feature almost no-one uses. Generate a podcast-style narrated summary of your project references; listen on the Tube, on a walk, while cooking. Absorb context without reading. For advisory consultants with heavy reading loads, this is transformative.
1. Client annual report + industry regulations. You're advising a rail authority. Build a notebook with: their annual report, the latest Office of Rail and Road policy update, three relevant industry briefs, and any past Arup work for adjacent clients. Generate Audio Overview. Listen on the train to the client meeting. You arrive with the context in your head.
2. RFP response prep. Three days to respond to an RFP. Build a notebook with the RFP, client's strategy document, two past Arup responses for similar clients, and the research pack. Generate Audio Overview. Listen that evening, sleep on it. Next morning you have a structural sense of the proposal shape before drafting a word.
3. New technology domain. Team needs to get up to speed on hydrogen infrastructure for a bid. Build a notebook with 6-8 reference reports. Generate Audio Overview. Everyone on the team listens during their commute. The team aligns to the same framing without a single meeting.
Set notebook-level custom instructions before generating Audio Overview to shape the output: "Use professional tone appropriate for a senior consultant. Focus on strategic implications rather than technical details. Highlight where Arup's capabilities would be relevant." The voices will adjust their conversation accordingly.
The team needs to get up to speed on a new technology, framework, or client domain. Traditional approach: everyone reads everything (or more realistically, nobody reads everything). Notebook approach: one person curates, everyone queries. One hour of work unlocks the whole team.
Curation is the value-add. Picking the 6-10 best sources matters more than picking 50 merely-relevant ones. The senior person's judgement on "what should the team read first" is the knowledge transfer that Copilot amplifies. A typical upskilling notebook might include:
Once the notebook is shared, team members:
The team alignment emerges because everyone is drawing from the same curated set of references, rather than each consultant reading different articles they found independently.
One more useful move: use the notebook's Word generation to produce a 2-page team briefing document summarising the topic from the references. Saves consultants who prefer reading over listening. Distribute alongside the shared notebook.
The step beyond individual Copilot Notebooks. Share the engagement notebook to a Microsoft 365 Group — the group membership drives access, so as consultants rotate on and off the engagement, their access updates automatically. The notebook becomes the institutional memory.
Sensible pattern:
Shared Copilot Notebooks work best with a designated owner — usually the engagement manager or workstream lead. The owner's job:
The payoff step. Generate a Word document or PowerPoint presentation directly from a Copilot Notebook — with Copilot grounded on all the references you've curated. The deliverable drafts itself in the context of everything you've built.
In Part VII (Word workflow) we covered /filename references — up to 20 files. In a Copilot Notebook, you can ground on up to 300 files, plus SharePoint folders, plus whole OneNote notebooks, all already curated for relevance. The quality of the draft is dramatically better because:
All the principles from Parts V (PowerPoint) and VII (Word) still apply. Specify audience, tone, length, structure. Ask for an outline first; approve; then ask for sections. Don't let Copilot invent anything not in the references. Flag gaps with comments rather than guesses. The advantage here is you've already done the curation work — the prompt itself can be shorter because the context is already in the notebook.
Six use cases, six tools, one table.
| Your scenario | Use this | Surface | Time |
|---|---|---|---|
| Day 1 of a new engagement with 5+ source docs | Build Copilot Notebook | M365 Copilot app | ~30 min |
| Rough meeting notes → team-shareable summary | Copilot in OneNote · structured summary | OneNote app | ~5 min |
| Absorb research while commuting | Audio Overview | Copilot Notebook | ~10-15 min passive |
| Team needs to learn a new regulatory framework | Shared notebook + Study Guide + Audio | M365 Group share | ~1 hour build |
| New consultant joining the engagement | Shared notebook onboarding prompt | Shared notebook | ~15 min for them |
| Extract action items from meeting notes | Copilot in OneNote · action extract | OneNote pane | ~30 sec |
| Client briefing document from research | Notebook → Word agent | Copilot Notebook | ~30-60 min |
| Weekly engagement catch-up | Shared notebook · "what's new?" | Shared notebook | ~2 min |
| Project-state overview before a client meeting | Overview page + refresh | Copilot Notebook | ~3 min |
| Summarise a single page of your own notes | Copilot in OneNote · select + Summarise | OneNote pane | ~30 sec |
| Map stakeholder relationships on a complex project | Mind map from Copilot Notebook | Copilot Notebook | ~5 min |
| Self-test your understanding of a new topic | Quiz + flash cards from Notebook | Copilot Notebook | ~15 min |
Patterns from advisory teams adopting OneNote and Copilot Notebooks. Almost every bad outcome maps to one of these.