Compare project velocity across months of meeting notes

Step 1: Confirm the notebook covers enough historyOneNote

Check that the notebook has meeting notes spanning at least two or three months — a single month of notes won't show a meaningful trend.

Step 2: Ask for the velocity comparisonCopilot

Open Copilot Notebooks against the project's full notebook (not just the most recent section) and ask it to compare across the specific date range you confirmed in step 1, explicitly requesting it cite which meetings back each claim.

Without that instruction it tends to produce a plausible-sounding summary you can't actually trace.

Prompt idea:

Compare our meeting notes from the last three months. What issues keep recurring across multiple meetings, and is our pace on open items improving, flat, or slowing? Cite which meetings support each conclusion.

Step 3: Trace each claim back to its source meetingsOneNote

For every recurring issue or pace claim, open the specific meeting notes it cites and confirm the pattern actually holds — a theme mentioned once shouldn't count as "recurring."

Step 4: Turn confirmed findings into a short trend noteOneNote

Write up the confirmed recurring issues and pace assessment as a short note at the top of the notebook, so the next status update can reference it directly.

Check the work

• Verify each "recurring" issue actually appears in more than one meeting's notes.
• Check that the pace assessment is based on completed items, not just items discussed.
• Confirm no meeting outside the requested date range was pulled into the comparison.

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