How to use Claude for Word on real documents
The Claude for Word add-in is not a chat window that hands you paragraphs to paste. It reads the document you have open — text, comments, tracked changes, footnotes, tables and bookmarks — and edits it in place. That difference is the whole reason it is worth learning, and it is also why the habits that work in a chat window do not transfer cleanly.
This is what actually works, checked against Anthropic's published documentation in September 2026.
What it is, and what it is not
It works on the document currently open in front of it. It answers questions about that document with clickable citations that navigate to the section they came from, and it recognises the structure of a real document — multi-level numbering, defined terms, cross-references, standard contract shapes — rather than treating it as a wall of prose.
What it does not do is reach beyond that file. It reads the open document. It cannot open, close, create or switch files for you.
Getting it installed
Install it from the Claude for Microsoft 365 listing on Microsoft AppSource, then open Word, activate the add-in and sign in with your Claude account. It is generally available on Pro, Max, Team and Enterprise plans.
It runs on Word for the web, on Windows with a Microsoft 365 subscription (Version 2205, build 15202.10000 or later), and on Mac from version 16.61. It does not run on the 2016 or 2019 perpetual and volume licences, on iPad, or on Android. If your file is a legacy .doc, save it as .docx first.
Select first, then say what changes
The single most useful habit: select the passage, then describe the change. Claude edits the selection and leaves everything around it alone, preserving surrounding styles, numbering and formatting. New text inherits the paragraph style, font and numbering of the content around it, so a clause you rewrite still looks like the rest of the document.
Describing which paragraph you mean in words is slower and less reliable than selecting it. This is the reverse of the habit most people bring from chat, where more description is usually better.
Turn on tracked changes before you let it edit
In tracked changes mode, edits arrive as revisions — the original as a deletion, the new text as an insertion — reviewable in Word's own review pane, and revertible with Ctrl+Z or Cmd+Z.
Turn it on before the first edit, not after the third. It converts "I think it changed something in section 4" into a list you can walk. On anything that will be read by someone outside your team, this is the difference between an edit you can defend and one you have to re-read the whole document to find.
Let it work through the comments
This is the feature people miss, and it is the one that saves the most time on a marked-up draft.
Claude reads the comment threads in the document, understands which text each one is anchored to, and works through them one at a time: it edits the anchored passage and replies to the thread explaining what it did. On a contract that has come back with fourteen comments from three people, that is an afternoon compressed into a review pass.
The reply matters as much as the edit. A thread that says what changed and why is a thread the next reader does not have to reconstruct.
Reading a counterparty's redlines
When a marked-up version comes back, Claude can read and summarise the tracked changes rather than making you scroll through them. Ask for the summary grouped the way you will act on it:
Summarise the tracked changes in this document, grouped by severity. Flag the ones worth pushing back on and say why.
That last clause is the useful half. A list of what changed is a diff; a list of what is worth arguing about is the start of a response.
Filling a template
Point it at your own template and it drafts inside the document's heading and paragraph styles. Tables populate in place, without reflowing the layout or changing column widths — which is the failure mode that makes most generated documents obviously generated.
The order of operations matters here in the same way it does in PowerPoint: open the template first, then ask. Asking for brand compliance after the fact is the slow route to the same place.
Persistent instructions worth setting
Settings has an Instructions field that applies to every conversation in Word. It is separate from the ones you set in Excel or PowerPoint. Good candidates are the conventions you would otherwise repeat: house tone, citation style, structural preferences, recurring context about the kind of document you work on.
One worth setting on day one, whatever else you add: tell it never to invent a figure, and to write a visible placeholder when a number is not in the source. It converts the most dangerous failure mode into something you can search for.
Working across Excel, PowerPoint and Word
The Excel, PowerPoint, Word and Outlook add-ins can share one conversation, so a memo in Word can draw on a model open in Excel. The setting is called "Let Claude work across files" and it lives in each add-in's settings. It is on by default for Pro and Max, and off by default for Team and Enterprise — so on a business plan somebody has to turn it on, and the toggle is per device.
Two limits are worth knowing before you rely on it: Claude can only read and write files that are currently open, and it cannot create, open, close or switch files itself.
What to check before you send it
Anthropic's own guidance is explicit that the add-in is not recommended for final client deliverables or counterparty sends without human review, for litigation filings or audit-critical documents without verification, or as a replacement for legal and financial judgement. Treat what follows as the minimum.
Every tracked change, before you accept it. Accepting in bulk is how a clause nobody read ends up in a signed document.
Every number and every defined term. Against the source, not against another paragraph.
Anything that states a position. Verify it matches your standard positions rather than a reasonable-sounding version of them.
Documents from outside. Anthropic warns that files from external sources — downloaded templates, counterparty drafts, anything emailed in — can carry hidden instructions designed to manipulate the add-in, and that these can hide in the text, the comments, the tracked changes, or the headers and footers. When Claude asks you to confirm an operation, read the confirmation rather than clicking through it. That is exactly the moment the warning is for.
Where to go from here
Most of what separates a useful answer from a disappointing one is not specific to Word — it is the habits that make any request land: saying who the output is for, giving it the raw material instead of letting it invent, asking for the format you actually want, and iterating instead of restarting. Claude Chat — The Beginner's Handbook covers those in 42 pages, along with the document skills that produce Word, Excel, PowerPoint and PDF files from a plain conversation.