Copilot Notebook
Masterclass

You've been using Copilot wrong. Not badly - just incompletely. Most people treat Copilot like a search engine: ask a question, get an answer, close the window, start over tomorrow with zero context. That's Copilot Chat. It's useful, but it's the shallow end.

Think of Notebook as a scoped AI workspace. You add references - Word docs, Excel files, PowerPoint decks, meeting transcripts, PDFs - and set instructions. Every conversation within that Notebook draws only from those sources. No cross-contamination from other chats. No web results mixed in. Just your data, answered precisely.

The "project brain" mental model

One Notebook per major initiative. Your Q2 strategy. Your product launch. Your compliance audit. Your onboarding program. Each gets a dedicated AI that knows everything about that project and nothing else. This is the deep work layer of Copilot.

Without context, Copilot draws from its training data. You get Wikipedia-quality responses - factually reasonable but useless for your specific project, your organisation, your situation. This is why most people feel underwhelmed by AI at work.

Grounding, explained simply

When you add references to a Notebook, Copilot doesn't just "know about" your files. It restricts its answers to only those sources. This technique is called RAG (Retrieval-Augmented Generation), but all you need to know is: your files become the AI's only source of truth.

What you can add as references

Up to 100 references per Notebook. Meeting transcripts from Teams are also supported.

This card is hands-on. If you have your laptop open, do this right now. You'll have a working project Notebook before you finish reading.

The average knowledge worker sits in 15+ meetings per week. Decisions get buried. Action items get lost. Nobody remembers what was agreed three Tuesdays ago. This is where Notebook transforms from "nice to have" to "can't live without."

How it works

After any Teams meeting, the transcript is available in your M365 ecosystem. Add it to the relevant Notebook as a reference. Do this consistently and something powerful happens: cross-meeting intelligence.

Ready-to-use meeting prompts

Click to copy any prompt directly into your Notebook.

Generate a decision log from all meetings in this notebook, formatted as a table with Date, Decision, Owner, and Status columns.

List all action items mentioned across these meetings, grouped by person responsible. Include the meeting date where each was assigned.

Create a weekly status report for my manager based on this week's meeting transcripts and project documents. Include: key accomplishments, decisions made, risks flagged, and next steps.

Compare what was committed in the first meeting with what was reported in the most recent meeting. Flag any gaps between commitments and actual progress.

Your budget lives in an Excel file. Your project plan is a Word doc. The risk register is another spreadsheet. The vendor proposal is a PDF. Comparing data across these sources manually takes hours. Notebook does it in seconds.

Drop everything in one Notebook

Add the Excel file, the Word doc, the PDF, the PowerPoint deck. Copilot can now see across all of them simultaneously and answer questions that span multiple sources. No VLOOKUP. No pivot tables. No INDEX MATCH. Just plain English.

What you can ask

Compare the budget forecast in the Q2 spreadsheet with the actual spend reported in the finance summary. Where are the biggest variances? Present as a table.

Which risks in the risk register are addressed by the mitigation plan in the project document, and which ones have no coverage? List unaddressed risks with severity.

Summarise the key findings from all consultant reports in this notebook. Highlight where they agree and where they disagree. Present recommendations that appear in at least two reports.

Audio overviews are just one of several Quick Create features inside Notebooks. But they're the standout: Copilot generates a podcast-style audio summary of your Notebook's content. Two AI voices discuss the key points, draw connections, and highlight insights - like having two analysts brief you on your project while you drive to work.

Customisation options (2026)

Use cases that actually save time

In Chat, you say "write formally" and it forgets by next session. In Notebook, your instructions persist across every single conversation. Set them once, benefit forever. This is what turns a generic AI into a specialist consultant.

Instructions by role

Click any role to see the instruction template.

Always respond as if briefing a project sponsor. Include timeline impacts and resource implications. Flag risks proactively. Use tables for any data. Keep responses under 500 words unless I ask for detail.

Focus on regulatory compliance implications. Reference specific standards mentioned in the reference documents. Highlight gaps between policy and practice. Always cite the source document and section.

Keep responses concise - bullet points preferred. Lead with the business impact. Skip technical implementation detail unless I ask. Highlight decisions that need my input.

Write in Australian English. Use a warm, professional tone. Avoid jargon. Format for readability with headers and short paragraphs. Match the voice and style of our existing published content.

Everything you've learned so far, applied. Each workflow includes the problem, the Notebook setup, and a ready-to-use prompt you can copy right now.

Based on all references in this notebook, generate a project status update for this week. Include: (1) Key accomplishments since last update, (2) Current blockers or risks, (3) Upcoming milestones in the next 2 weeks, (4) Decisions needed. Format as a 1-page executive summary.

I have a meeting with [stakeholder/team] in 30 minutes about [topic]. Based on the references in this notebook, create a prep brief: key discussion points, unresolved items from previous meetings, data points I should have ready, and potential questions I should be prepared for.

Compare [Document A] with [Document B]. Create a table showing: what's covered in both, what's in A but not B, and what's in B but not A. Highlight the most significant gaps and recommend actions to address them.

Generate a briefing document for [Name/Role] who is joining this project for the first time. Include: project background (2 paragraphs), current status, key decisions made so far, open items, and their specific responsibilities. Write for someone with [executive/technical/operational] level of detail.

Create a structured onboarding guide for a new team member joining [team/project]. Organise by: (1) Team overview and key contacts, (2) Current projects and priorities, (3) Key processes and where to find them, (4) Common questions and answers, (5) First-week checklist. Base everything on the reference documents in this notebook.