We need Copilot proofreading in Word with Track Changes — and one shared prompt for the whole org. Is that possible?

You’re asking for two sensible things at once: edits people can audit, and one house style so every team isn’t reinventing the proofreading prompt. Practitioner threads keep hitting the same snag — Chat agents chat about the document, while the edit you actually want happens inside Word.

Here’s what’s going on. Learn’s Copilot release notes (2 June 2026) say the default chat experience with Copilot in Word can edit the document directly. Users can turn that experience off if they prefer. Microsoft’s wording is that Copilot-made changes are fully reviewable and reversible, and the try-this guidance explicitly includes asking Copilot to rewrite a paragraph and then reviewing the tracked changes. Roadmap 557673 (Copilot can edit your document by default in Word) targeted general availability for March 2026 across desktop, Mac and web — treat Message Centre and your tenant’s build as the source of truth for when it landed for you.

That path is Copilot in the Word document, not a separately published agent that lives only in Copilot Chat. Agents are brilliant for Q&A and drafting about a file; they are a poorer fit when the requirement is “change this .docx and leave a review trail.” If your team built a proofreading agent and only got a table of suggestions, you’re not doing it wrong — you’re using the wrong surface for an in-document edit.

For the shared instructions, use organisational prompts. Learn’s Organizational prompts lets AI Admins (and delegated Search Editors where you’ve set that up) publish prompts that show up in Copilot Chat, Teams and Edge: pinned suggestions, Prompt Lab, and autosuggest as people type. Publish one approved proofreading prompt — style guide, tone, what never to invent, “edit in Word with reviewable changes” — instead of a SharePoint folder of competing markdown files. Analytics on active users and submissions tell you whether people actually use it.

Steady before scale here is the Adoption pane meeting GRC: one approved prompt, edits people can reverse, and no fantasy that an agent will silently become Word’s Track Changes engine.

Options that actually work:

1. In-Word Copilot + one organisational prompt. Publish a short house prompt (“Proofread this document for clarity and house style; keep meaning; leave every change reviewable”). Train people to open Copilot in Word, not only in Chat. Best Steady default.
2. Chat for critique, Word for apply. Use Copilot Chat or a narrow agent to list issues; apply fixes in Word with Copilot edit (or by hand) so the review trail stays in the file. Slightly slower; clearer for regulated sign-off.
3. Document Validation / Tuning templates where you have Frontier access. Learn’s Document Validation agent template can insert findings as Word comments against a rulebook — useful for compliance review, not a substitute for everyday proofreading. Early-access / Frontier; don’t promise it tenant-wide yet.
4. Hundreds of personal prompts and a Chat-only agent. Consistent only in the sense that everyone is inconsistently disappointed.

12 Panes action / comms: Tell Communications: The supported edit trail is Copilot in Word; the supported shared wording is an organisational prompt — not a free-for-all agent. Tell AI Admins: Publish one pinned prompt, measure submissions, retire the shadow copies. Tell reviewers: Accept or reject Copilot’s changes the same way you review a colleague’s markup; meaning still needs a human. Leadership: This is writing quality with a review step, not unsupervised publishing.

Benefits / risks: People get consistent starting instructions and edits they can inspect; organisational prompts reduce prompt sprawl; edit-by-default speeds drafting and raises the need for a review habit on contracts and board papers; Chat agents that only narrate changes will keep frustrating teams that expected Track Changes; confirm your channel and licence cover Copilot in Word before you brief the whole org.

I’d suggest a thirty-minute dry run with Comms this week: same page, once via the organisational prompt in Word Copilot, once via the Chat agent, and compare the review trail. When people see which one leaves markup they can accept or reject, the surface choice stops being a debate.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer