Copilot Pages: Turn Shared Drafts Into Recorded Decisions

Use Copilot Pages to turn a response into a shared draft that colleagues can edit and refine together. Keep proposals distinct from approvals, then deliberately record the decisions and follow-up work people confirm.

A tool like fenbs can keep that selected work record available to supported connected assistants after the drafting session ends. It does not synchronize Copilot Pages or import the chat behind a page. This guide covers the review and handoff loop within our AI at work library.

How do you create a useful page from a Copilot response?

1. Start with a bounded request, such as a draft project brief for colleagues to review. Provide the source material you are authorized to use.
2. Use the response’s Edit in Pages option to add it to a new or existing page, following the controls available in your account.
3. Give the page a descriptive title and an obvious review status. Separate proposed choices from facts that already have approval.
4. Check the initial content before sharing it. Remove unsupported claims and identify questions reviewers actually need to answer.

Microsoft’s Copilot Pages getting-started guide↗ (opens in a new tab) describes creating a page from a chat response and editing it alongside Copilot Chat. It also links the current access requirements. Check those details if your account shows different controls.

A useful first page invites a specific review. Instead of asking colleagues to improve everything, ask whether the project goal is correct, whether the proposed scope is complete, and which unresolved choice blocks progress. A shorter page with those questions can be easier to approve than a polished document with an unclear purpose.

What should a collaborative draft include?

Build the page around the decision people need to make. Start with the purpose, then give enough source context to evaluate the proposal. Put open questions where reviewers will see them, rather than hiding uncertainty in a closing paragraph.

• Purpose: What outcome is the draft trying to support?
• Known facts: Which source-backed details can reviewers rely on?
• Proposed choices: What are people being asked to approve or change?
• Open questions: Which missing answer prevents a sound decision?
• Next work: What would happen if the proposal were accepted?

For example, suppose a small studio is preparing a client onboarding guide. The page can hold alternative wording and reviewer suggestions. It should make clear whether collecting a new client detail is only proposed or has already been approved by the person responsible for that process.

For help generating the draft itself, see Copilot for writing at work. This page focuses on what happens once a draft becomes something several people are editing and relying on.

How do you share a page without losing the review boundary?

Use the page’s Share controls and choose the intended audience. Microsoft’s Copilot Pages sharing guide↗ (opens in a new tab) explains sharing a page link or a component that colleagues can work with. It says collaborators can contribute to the page without accessing the Copilot chat session behind it.

That distinction matters for the reader. They may see the draft without the caveats or source discussion in your chat. Put the source references and material review questions in the page itself, wherever the audience is permitted to receive them.

Before sharing, check for private information copied from source material. A page intended for a broad project group should not accidentally include details from a restricted conversation. Ask a reviewer to confirm they can open the page and the sources they need, then explain what kind of feedback you want.

When does an edited paragraph become an agreed decision?

An edit shows that content changed. It does not, by itself, establish who had authority to approve it or whether the team accepted it. Choose a clear human review point for changes that affect scope, commitments, or standing instructions.

In the onboarding example, a colleague might simplify a paragraph describing requested client information. The wording can be useful without authorizing a change to the process. Ask the responsible person to confirm that choice, then preserve what was approved separately from the evolving draft.

fenbs Decisions and rules keeps a person’s confirmed choice with its reason and related work, so a connected assistant does not have to infer approval from the latest wording.

What should you carry from a page into follow-up work?

Select the details that change what happens next: the approved choice, who made it, the reason, a source link, and the remaining tasks. Preserve unresolved questions too. A clean handoff can say the guide’s outline is accepted while its privacy wording still needs a review.

Keep the page as the place for continued drafting. Manually transfer selected decisions and task context into fenbs when you need a shared work record across supported assistants. Do not copy the entire page just to make it appear in another tool; duplicated drafts can disagree without anyone noticing.

For documentation-specific review and maintenance, see Copilot for documentation work. For broader distinctions between Microsoft assistant experiences, the Microsoft Copilot agents guide provides the separate overview.

How to do this with fenbs

1. Create a free account, then add the project whose shared draft you are reviewing.
2. Manually save the page link and the selected context the kanban board’s members may receive. Explain which parts remain draft material.
3. Record each confirmed choice in Decisions and rules, naming the person who decided and the reason. Keep unanswered approval questions open.
4. Add the agreed follow-up tasks and their plans. Connect a supported assistant from Integrations if you want it to read the selected record before working.
5. Save Where we left off with the next review step, outstanding checks, and anything waiting on a person.

fenbs is not the right fit for live document coediting or automatic synchronization with Copilot Pages. Use Pages for the collaborative draft and fenbs when you need confirmed decisions and task progress to remain available across supported AI apps.

How do you prevent later edits from quietly changing the agreement?

When a later edit affects an approved choice, ask whether the person responsible accepts the change. Preserve the earlier decision and record a replacement when people make one. Do not overwrite the history of why the team chose the original approach.

Before the next session, check that the page and work record still describe the same approved direction. Our AI handoff guide covers saving the remaining work; Copilot instructions examples can help you ask an assistant to keep proposals separate from approvals.

The practical test is whether another colleague can tell what is ready to use, what still needs a decision, and where to start. If they have to reconstruct that from the drafting conversation, add those missing details before calling the review complete.