Pages, Notebooks, and Suite WorkflowsIntermediate12 min

OneNote, Loop, and Whiteboard

Choose OneNote for notes, Loop for a shared draft, and Whiteboard for ideas on a canvas. Keep each result tied to its source and check it before use.

What you'll learn

  • Match a task to OneNote, Loop, or Whiteboard by its working object
  • Ground a prompt in a specific page, note set, or board
  • Separate confirmed, tentative, open, and generated information
  • Audit generated content before you keep it

Before you start

On this page

One colleague has meeting notes that need to become a task list. Another is working in a brief the team edits together. A third has twenty ideas scattered across a canvas. Copilot can help in each case, but the right app depends on the material already in front of you.

Start with the thing you're working on

Name the working object and what you need from it:

You're starting with... Use To produce...
Existing notes on a page OneNote A summary, task list, plan, rewrite, or outline
Shared page content a team develops Loop An evidence-bounded draft or concise orientation
Loose ideas on a canvas Whiteboard More ideas, themes, or a board summary

OneNote reshapes notes you've already written. Loop holds a draft the group develops together. Whiteboard helps with ideas and their spatial arrangement. Meeting notes headed for a task list belong in OneNote. Ideas that need clustering belong in Whiteboard.

Include the app and the source in the instruction. "Summarize this" could point almost anywhere. "Summarize the notes on this OneNote page" and "Summarize the ideas on this Whiteboard" define two different sources. The wording also tells the next person exactly what Copilot used.

Name the app, every time

Put the application and the source in the prompt itself: "the notes on this OneNote page," "the ideas on this board." It removes the single most common ambiguity and makes your result reproducible for the next reader.

One change can point you to another app

A workshop team has put twenty onboarding ideas on a canvas and wants to see possible groups before choosing what to pursue. Whiteboard fits because the ideas are spatial, and the team can inspect the clusters together.

If the starting material were meeting notes and the result needed to be a task list, use OneNote. If the ideas were settled and the team now had to co-edit a sponsor update, use Loop. Let the work in front of you determine the app.

Limit the prompt to one object

Here, grounding means telling Copilot to use one page, one set of notes, or one board. A useful prompt specifies:

  1. The allowed source (this OneNote page).
  2. What must not be inferred (don't invent owners or dates).
  3. How missing information should appear (write "Not stated").
  4. The output you want (sections, a table, an outline).

The Goal, Context, Source, and Expectations structure from Prompting 101 still applies. For a project plan, the goal is the plan, the context is an employee-onboarding pilot, and the source is this OneNote page. In the expectations, ask for phases, tasks, owners, dependencies, and open questions, with "Not stated" for anything absent from the notes.

Keep the source state visible

Once you've limited the prompt to one object, mark four kinds of information:

  • Confirmed: explicitly stated in the source.
  • Tentative: suggested, proposed, or under consideration.
  • Open: a required fact or decision the source doesn't provide.
  • Generated structure: a theme, sequence, or agenda Copilot created to organize the material.

Generated structure deserves special attention. If Copilot groups ideas under a theme, that doesn't show the team agreed with the grouping. Label it "proposed" or "suggested structure" until people confirm it.

Loop and Whiteboard need different reviews

The source rule stays the same, while the material changes.

In Loop, you may be working from a shared status brief or a decision log. Copilot can draft a "Decision needed" section that sets out the decision, options, evidence, and missing information. It shouldn't make the decision or assign an owner for the team. A collaborator still needs to review the draft.

Whiteboard deals with ideas on a canvas. Keep any ideas Copilot adds separate from the originals and label them clearly. When it groups existing ideas, count them before and after. Every original should still be present, and the themes remain tentative until the team agrees.

OneNote does more than summarize

OneNote's Copilot can do more than summarize and list tasks. Ask it to rewrite a paragraph for a new audience while preserving every date, name, requirement, and degree of certainty. Compare the rewrite with the original sentence by sentence. If a fact changes or a caveat softens, treat that as an error. For an outline, label the proposed order as a draft until the agenda is settled. Copilot can reshape and reorganize your notes. It cannot add a fact, an owner, or a certainty the notes didn't already carry.

Summarize a OneNote page cleanly· onenote
Bad example

Summarize this OneNote page and pull out the important points.

Good example

Summarize the notes on this OneNote page in five bullets, then list confirmed decisions, action items, risks, tentative suggestions, and open questions under separate headings. Use only this page, and write "Not stated" for anything missing. Don't invent a room, an owner, or a date.

Why this works: A structured summary that keeps suggestions out of the decisions list and leaves genuine gaps visible.

Extract a task list you can verify· onenote
Bad example

Make a task list from these notes with owners and deadlines.

Good example

Extract the action items from these notes into a table with columns Action, Owner, Deadline, Status in source, and Evidence. Use "Not stated" for a missing owner or deadline, and don't turn a suggestion or an unresolved need into an assigned task.

Why this works: A task table whose Evidence column lets you confirm each row against a source line. "find a room" remains an open need because no one is assigned.

Draft a "Decision needed" block in Loop· loop
Bad example

Write a decision section from this Loop page.

Good example

Draft a "Decision needed" section from the content on this Loop page. State the decision, the options, the supporting evidence, and the information still missing. Use only the page, don't infer an owner, and don't make the decision for the team.

Why this works: A crisp decision block the team can act on, with the missing pieces named and no owner or verdict Copilot invented.

Group Whiteboard ideas without faking consensus· other
Bad example

Group these Whiteboard ideas into the best themes.

Good example

Organize the ideas on this Whiteboard into themes. Preserve every original idea, give each theme a short name, and label the grouping tentative. Do not treat any theme as an agreed decision. List any ideas you add separately as "Copilot suggestions."

Why this works: A themed board where all your original ideas survive, generated additions are labeled, and no cluster is presented as something the team approved.

Run one audit before you keep it

For each factual line, find the source line that supports it. Count the owners, dates, and original ideas in the source, and confirm the output adds none. Keep tentative material separate, and label every generated theme as proposed. If a first pass already looks clean, add an "Evidence" column instead of accepting it outright.

Run the same audit in every app

Save the source, prompt, and first output. For each factual statement, note the source line that supports it. Count the owners, dates, and original board ideas in the source, then check that the output added none. Tentative material should remain separate from confirmed material, and every generated theme, sequence, or wording should be marked as proposed.

Consider a Loop sponsor update that says, "The onboarding guide is ready to launch, and Sam owns final approval." The page only says the first draft is complete, and it doesn't name a final-approval owner. The corrected update says "the first draft is complete" and "final-approval owner: Not stated." The revised copy is just as readable, but its claims now match the source.

A clean-looking first pass still benefits from an Evidence column. Ask Copilot to name the source line behind each row. The result is easier for the next person to check. Files, Planner, and Cross-App Workflows extends the same practice across OneDrive, SharePoint, and Planner.

Try it yourself

Audit a flawed first pass

The fastest way to build the habit is to break a bad summary. Here are the source notes and a deliberately flawed Copilot summary. Notes: "Workshop date: 18 August. Audience: new team leads. Need two facilitators. Room is not confirmed. Include a hands-on exercise. Accessibility review is pending." Flawed summary: "The workshop will be held on 18 August in Room 204. Alex and Morgan will facilitate. The accessibility review is due on 10 August."

  1. 01

    List every person, date, room, and decision the notes actually state.

  2. 02

    Read the flawed summary and mark each claim against your list.

    Hint: Three claims in the summary have no support in the notes.

  3. 03

    Flag the inventions: Room 204 (the notes say the room is unconfirmed), Alex and Morgan (no facilitator names appear), and the 10 August due date (the review is only "pending").

  4. 04

    Rewrite the summary so every fact traces to the notes, turning each invention into "Not stated" or an open question.

  5. 05

    Add an Evidence column naming the source line for each retained fact.

A corrected summary with zero invented facts, gaps labeled "Not stated," and an Evidence column that makes every claim checkable.

Key takeaways

  • Choose the surface by working object. OneNote transforms notes, Loop drafts shared content, Whiteboard groups ideas.
  • Name the app and the source in every prompt. "Summarize this" is ambiguous. "Summarize the notes on this OneNote page" is not.
  • Keep confirmed, tentative, open, and generated information separate, and label anything Copilot organizes "proposed," not "approved."
  • A theme or agenda Copilot generates is not proof the team agreed to it.
  • Run one audit before keeping any output. Every claim should trace to a source line, and nothing new should be invented.

Check your understanding

  1. 1. Twenty ideas sit on a canvas and need grouping into themes before the team decides what to pursue. Which surface fits?

  2. 2. You ask Copilot to group board ideas into themes, and it labels the result an "approved plan." What's wrong?

  3. 3. What makes a prompt in OneNote, Loop, or Whiteboard "grounded"?

  4. 4. A OneNote summary files "Find a room" under Action items, but the notes only say "we still need a room." How should it be classified?

  5. 5. Your first-pass summary already looks correct. What's the best next step?

Frequently asked questions

Terms used in this lesson

working object
The raw material you start from (notes, shared page content, or ideas on a canvas), which decides the right surface.
grounding
Restricting Copilot to a specific page, note set, or board and defining how missing information should appear.
generated structure
A theme, sequence, or agenda Copilot creates to organize material. It is a proposal that still needs approval.
audit
The check you run before keeping output: tracing each claim to a source line and confirming nothing was invented.

Further reading