How the advisory team should use Copilot in Word — from a blank page to a client-ready proposal grounded in your org's real files. Four distinct Word AI tools, six use-case workflows, and the vibe-writing pattern that reframes document creation as a dialogue.
Before the tools, the shift in mental model. Word used to be a blank canvas you filled with keystrokes. Now it's a conversation — you describe what you want, Copilot drafts into the document using Word's native styles, you steer. The advisory team that internalises this stops writing from scratch.
In September 2025 Microsoft launched vibe working, its umbrella term for the new human-AI collaboration pattern in Office. In Excel that pattern shows up as Edit with Copilot. In Word it shows up as the same capability, same reasoning models, applied to the problem of writing rather than modelling — which Microsoft calls vibe writing.
"Writing feels more like a dialogue than a task. You focus on intent; Copilot brings it to life with Word's native styles and polished formatting." — Microsoft, on Agent Mode in Word
The mechanical change: Copilot now edits into the document directly. Ask for a draft, ask for a rewrite, ask for a new section, ask it to update a table from numbers in last week's email — and it makes the change in place, using Heading 1 / Heading 2 / Body / Quote / List styles that already exist in the template. No more "here's a suggested paragraph, copy and paste it." Copilot is the drafter; you are the editor.
From blank page to scaffolded draft. Old pattern: stare at an empty document, write the first sentence, then the second, building up 3,000 words one keystroke at a time. New pattern: describe the document you want in two paragraphs of prompt, get a structured first draft in forty seconds, spend your time refining rather than producing.
From retyping to referencing. Old pattern: if you wanted Copilot to use information from another file, you'd copy it into the prompt. New pattern: type / and the filename, and Copilot pulls content from up to 20 Word docs, PowerPoint decks, PDFs, emails, or meeting transcripts in your OneDrive or SharePoint. The sources ground the draft — your prose is yours, but the facts are from your real files.
From writing to editing. Old pattern: your time was spent producing text. New pattern: Copilot produces text, your time is spent making it right — tightening the argument, correcting the tone, adding the Arup-specific nuance, catching where the AI has flattened a subtlety. It's a higher-leverage use of a senior consultant's hour.
The payoff is biggest for advisory work because everything the team produces is a document grounded in other documents — a proposal built from past proposals, a report built from research briefs, a policy doc built from regulations plus precedent. That's exactly the shape of task vibe writing is designed for.
Just like Excel, "Copilot in Word" is a family of tools, not a single feature. Each has a different job, a different starting point, and a different ceiling. Knowing which one you're in matters.
Tools → Edit with Copilot. Uses Work IQ — Microsoft's intelligence layer that grounds responses on your SharePoint, OneDrive, emails, meetings and chats. Reference other files with / followed by the filename — up to 20 items per prompt. Writes using Word's built-in styles, so document structure stays consistent. Shows its reasoning. Respects Track Changes when it's already enabled. March 2026 adds citations — sources are displayed inline whenever Copilot uses Work IQ or web content.m365.cloud.microsoft/chat, switch to the Word Agent. Describe the document you need, reference source files with /, and the agent produces a complete Word file — structured, formatted, with your org's styles where possible — and drops it into your OneDrive. Good when you want to stay in chat (mobile, another app), or when you're building several documents in sequence and don't want to bounce between apps. Copilot Chat users without a full M365 Copilot licence get basic access; licensed users get priority access plus Work IQ grounding on your work content.The single most important discipline in this chapter. The way Copilot reads, edits, and structures your document depends on Word's built-in Styles. A document with proper styles is a document Copilot can work with. A document styled as "all Normal, manually bolded" is a document Copilot struggles with — and will usually produce inconsistent output on.
Word Styles (Heading 1, Heading 2, Heading 3, Body, Quote, List Bullet, List Number, etc.) are not cosmetic. They are the document's structural metadata — the thing that tells Word "this is a section heading, this is body text, this is a subheading under a section." Copilot reads that structure and uses it. If every paragraph in your document is styled as "Normal," Copilot has to guess where the sections are, where the headings are, and where the hierarchy breaks. It guesses wrong often enough to matter.
1. Start from an Arup-branded template — ideally one with the Styles already configured to Arup brand: headings in the right fonts, body text in Inter or equivalent, tables styled, margins set. If the team doesn't have one, build one once and reuse it for every client document. The time saved across a year is enormous.
2. Apply Styles, don't fake them. If you want something to be a heading, use Heading 1 or 2 — don't make it bold and bigger and call it done. Copilot sees the style tag, not the visual effect. A visually-styled "heading" that's actually Body text reads to Copilot as body text.
3. Use the Navigation pane. View → Navigation shows your document as its heading structure. If the nav pane is empty or wrong, your styles are broken. Fix them before inviting Copilot in. The nav pane is also the fastest way to move sections around.
4. Think about referenceable context. Before starting a vibe-writing session, list the files, emails, and meetings you want Copilot to draw on. Save the relevant files to OneDrive or SharePoint (Copilot can only reference what's accessible to your account). Have the filenames ready — you'll type / followed by each one during the session.
None of this is new advice — good Word Style hygiene has been the mark of a competent consultant for twenty years. What's new is that Copilot punishes bad style hygiene more visibly than humans do. A document that wasn't styled properly used to just look slightly off. Now it also produces worse AI drafts.
The master workflow for Word. You have reference material — past proposals, a client brief, research notes, a previous report — and you need a new document grounded in them. The /filename reference pattern plus Edit with Copilot is the entire play.
The second most common Word task. You have a draft — your own, a colleague's, an inherited document — and it needs to be tighter, clearer, more appropriate to its audience. Copilot's strongest ground.
The highest-frequency use of Copilot in Word across advisory teams. Every consultant has a stack of PDFs, old reports, research documents to read for every new engagement. Copilot's Summarise is the fastest single time-saver in the product — and with multi-file reference, it extends from "summarise one doc" to "read the stack and tell me what matters."
The use case that historically was "don't use Copilot for this." March 2026 changed that. Word-level precision Track Changes, contextual comments, auditable edits, visible progress on multi-step operations — Copilot now has the safety scaffolding that governance and compliance work require. Still requires care.
Sometimes the fastest path to a Word document isn't through Word. The Word Agent in Copilot Chat builds a complete document from conversation — no Word app open, no formatting fiddle, no template hunt. For certain scenarios it's genuinely the right tool.
The tightest workflow in the whole Microsoft AI stack, and one almost no advisory teams are using yet. A client meeting just ended. An email thread just resolved. Both contain the material for a deliverable. Copilot bridges the gap in five minutes.
/meeting reference plus a well-structured prompt gets you 90% of the way in five. This single workflow change is probably worth more hours per consultant per year than any other pattern in this report — and it's the one that's almost never on people's radar. Highlight it in training.Six use cases, four tools, one table.
| Your scenario | Use this | Surface | Time |
|---|---|---|---|
| Draft a proposal or report from multiple source files | Edit with Copilot + /filename | Word app | ~30 min |
| Rewrite a section for a specific audience | Rewrite with Copilot (selection) | Word app | ~5 min |
| Consistent voice / jargon / heading pass on a long doc | Edit with Copilot (sequential prompts) | Word app | ~15 min |
| Summarise a single long document | Summarise with Copilot | Word app | ~3 min |
| Synthesise across 3-5 documents | Edit with Copilot + /filename refs | Word app | ~15 min |
| Contract / policy review with Track Changes | Edit with Copilot + TC on | Word (Windows) | ~20 min |
| Produce a document without opening Word | Word Agent | Copilot Chat | ~15 min |
| Meeting transcript → outputs document | Edit with Copilot + /meeting | Word app | ~10 min |
| Email thread → decision brief | Edit with Copilot + /email | Word app | ~5 min |
Patterns from training advisory teams on Word Copilot. Almost every bad Word Copilot experience traces back to one of these.
/ reference syntax religiously. A draft grounded in /Client_Brief.docx and /Past_Proposal.docx is qualitatively better than one that isn't./filename instead. The / reference is better, cheaper on context, and produces citable outputs./ so the draft is built on your org's actual material, not the model's generic training. Draft — let Edit with Copilot produce structured first drafts using Word's native styles. Sharpen — use Rewrite-with-Copilot and document-wide passes to refine voice, tone, length, and heading style. Almost every advisory writing task fits this three-move pattern. The consultants who internalise it stop writing from scratch and start writing as editors.