TaskbyTask.Practical AI guides for work
Microsoft 365 Copilot · Practical walkthrough

Use Copilot Pages to turn one good answer into something your team can edit

You get an answer from Copilot that is most of the way there, then paste it into an email where it dies. Two colleagues hold the missing facts. A Copilot Page gives them somewhere to add them.

Task by Task13 min read + practice
A shared ceramic relief with removable curved tiles, an empty bay and sculpting tools.

What you'll make

one shared Copilot Page holding a short brief, with its gaps marked “To confirm”, an empty owner column for colleagues to fill, and a deliberate choice of who can see it.

What you'll need

a work or school account with SharePoint or OneDrive storage (Pages doesn’t need a paid Microsoft 365 Copilot licence, though your organisation’s settings still apply), a few notes you’re allowed to share with the intended readers, and about 20 minutes.

Example result.

Supplier onboarding: draft decision brief
Decision needed: can supplier setup begin once both checks finish?
Established: bank-detail verification incomplete; contract review
  in progress.
Open: when can finance and procurement confirm? (To confirm)
Next step: ask both functions for an update. Owner: ____

1. Get one answer worth keeping

Sign in to Microsoft Copilot and paste your notes with this prompt:

Draft a short internal brief for [audience] about [decision or task].
Use only the notes below. Use these sections: Decision needed;
Established facts; Open questions; Next steps, with an empty owner
column. Keep dates, figures and conditions. Mark anything missing as
"To confirm". Do not invent owners or deadlines. Keep it under 350
words.

NOTES: [your notes]

[audience] is who will edit the page; [decision or task] is what it’s for; [your notes] are pasted with their source names.

Why this works: a brief that arrives with plausible names already filled in has to be argued with before anyone can use it. The blank owner column invites the people who know to fill it in.

What you should see: four short sections, with the gaps marked and the owners left empty.

2. Move the answer to a Page

Below the response, select the pencil button, Edit in Pages. The Page opens beside the chat. Select the title and rename it straight away, with its status: “Supplier onboarding: draft decision brief”. The default title is what makes a page unfindable in a fortnight.

Why this works: the page becomes the shared object; your chat stays yours.

What you should see: the brief in an editable page beside the conversation, with a clear title.

3. Edit each part the right way

You have three ways to change a Page, and they fail differently:

  • Type directly for facts: a wrong date, a name, a figure. Nothing else is at risk.
  • Highlight text and select Ask Copilot for wording in one passage.
  • Ask Copilot Chat for structure: a new section, a different order.

Microsoft’s own warning is the one to remember: “If you ask Copilot Chat to update your page, some content from earlier conversations might be removed.” Treat every Chat edit as a rewrite of the whole page and read it all afterwards. For a passage you care about, highlight it and use:

Rewrite only the highlighted text. Keep every date, name, figure and
condition exactly as written. Make it shorter and remove any sentence
that states a conclusion the rest of the page does not support. Do
not add anything new.

Why this works: the narrower the route, the less there is to recheck. Structure through Chat, wording through a selection, facts by hand.

What you should see: the edited passage changed and everything else exactly as it was.

4. Share the page deliberately

Before sharing, remove anything the recipients shouldn’t receive. Then select Share in the upper-right corner. Copy link gives colleagues access to that one page, which opens in Loop. Copy component lets you paste it into Teams, Outlook or OneNote, where edits update the page in real time. Either way, recipients get the page without your Copilot chat session.

Why this works: the page is what you’re handing over, so it should contain only what this audience should see.

What you should see: colleagues able to open and edit the page, and nothing on it you’d mind them reading.

Check the result

  • Every date, figure and condition on the page appears in your notes.
  • “To confirm” items are still visible after every edit.
  • Owners are real agreements, not suggestions.
  • The opening decision and the next steps still agree.

The usual failure: a Chat edit or a quick colleague edit quietly changes what the page says. A condition disappears in a rewrite, or someone types a completion date with no source. Spot it by reading the whole page after any Chat edit, and asking where each new date came from. To catch what moved:

Compare this page with the notes below. List every date, condition
and open question from the notes that is missing or changed on the
page, and any new date on the page that the notes do not contain.
Do not edit the page.

NOTES: [your original notes]

Type back anything missing yourself. If a lot has gone, open the page’s version history and restore an earlier version.

Worked example: a supplier onboarding brief

Fictional example. The notes:

Operations: we need a decision on whether to begin supplier setup.
Finance: bank-detail verification is incomplete.
Procurement: contract review is in progress. No completion date agreed.
Manager: do not begin setup until finance and procurement confirm.

The first page matched the example result. Then the category manager asked Chat to “add a section of questions for the supplier”. The new section was good, but the rewrite dropped the manager’s condition from Decision needed. The comparison prompt listed it as missing, and she typed it back in.

After sharing, a procurement colleague typed “Contract review done 14 Oct” into Established. There was no source for it yet, so she moved it to Open as “Contract review: procurement says 14 Oct, To confirm in writing”, and the finance colleague added their own owner name to the bank-detail step.

What mattered:

  1. Read after every Chat edit. The new section was right and the rewrite still lost a condition.
  2. A colleague’s edit is a claim too. A date typed into a shared page needs the same source as one in the notes.
  3. The owner column did its job. People filled in their own names; nobody had to argue with a guessed one.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Build one page from several conversations

To add an answer from an older chat, select Chat in the left navigation, open the conversation, select the Pages icon at the bottom of the response, then Add to recent page and pick your page. Two conversations about the same supplier will contradict each other somewhere, so before tidying, ask Copilot to list conflicting dates, figures and statuses with both passages, and not to choose between them.

Decide what leaves the page

When the page is settled, you can convert it to a Word document or PowerPoint. Before converting, check by hand: does every date, figure and name come from a source you can point to; is every “To confirm” either confirmed or still visible; are the owners real agreements? Do that pass yourself, because a last automated tidy is exactly the edit most likely to smooth “To confirm” into a statement.

Know where Pages struggles

Microsoft lists the current limits: Pages works mainly with Microsoft 365 content; layout and advanced formatting are limited; Copilot’s responses may not reflect several people’s simultaneous edits until the page is refreshed; and big pages with lots of embedded content can be slow. A page four people have edited and Copilot has rewritten twice will also drift in tone, so decide early who does the final read.

Sources

Optional analytics

With your permission, Google Analytics uses cookies to measure visits and which guides people read. It stays off until you accept. Use Analytics choices in the footer to change your choice. Rejecting after accepting refreshes this page. Privacy details.