Install Claude in Word and review one useful edit
You've been copying a paragraph out of Word into a browser, pasting the answer back and losing the formatting on the way. Claude can now edit it where it lives, as tracked changes you can check one by one.
What you'll make
one paragraph in a Word document, edited by the Claude add-in as tracked changes, with every revision checked against a count before you accept it.
What you'll need
a Claude Pro, Max, Team or Enterprise account, permission to use the add-in at work, and Word on the web, Microsoft 365 Word for Windows (version 2205 or later) or Word for Mac (16.61 or later). It doesn’t run on Word 2016 or 2019 perpetual or volume licences, or on Word for iPad or Android. Save any .doc file as .docx first. About 20 minutes.
Example result.
Asked for: at most 3 changes. Claude's list: 3. Review pane: 4.
Revision 4 (not on the list): deleted "Blue badge spaces are unchanged."
Accepted: 3 · Rejected: 11. Install the add-in, or ask for it to be deployed
For yourself: open the Claude for Microsoft 365 listing, select Get it now, then open Word. Activate it from Home › Add-ins on Windows or Tools › Add-ins on Mac, and sign in with your Claude account.
If you’re the Microsoft 365 administrator: in the Admin Center, go to Settings › Org Settings › User owned apps and services and turn on Let users access the Office Store. Then go to Settings › Integrated apps › Add-ins, search for “Claude for Microsoft 365” and assign it to users or groups. Two known snags:
- If your admin roles are activated through Entra Privileged Identity Management, the Integrated apps page doesn’t recognise them and deployment fails. Deploy from an account with the role permanently active.
- If the Office Store is turned off, admin-deployed add-ins may not appear. Use Integrated apps › Upload custom apps with Anthropic’s manifest file instead.
If your organisation routes AI through Amazon Bedrock, Google Vertex AI, Azure AI Foundry or an LLM gateway, the admin can deploy it without individual Claude accounts. Before using work documents, check with the data owner: Anthropic says Word activity doesn’t inherit custom retention settings or appear in Enterprise audit logs.
Why this works: the documented route avoids loosening organisational controls just to get one add-in working.
What you should see: a Claude panel in Word, signed in to your work account.
2. Select one paragraph and ask for a small, counted edit
Use a copy of a short document you wrote, or the fictional notice in the worked example. Start with a plain notice, not a contract or a file from an unknown sender. Turn on the add-in’s tracked changes mode, select the paragraph and send:
Edit the selected paragraph only, using tracked changes. Make it clearer for [reader] and combine repeated wording.
Make at most [number] changes and no others. Keep every figure, date, name, condition and exception unchanged. Do not add facts, promises or decisions. Leave headings, numbering and the rest of the document alone.
After editing, list each revision you made, in order.[reader] is who the paragraph is for. [number] is a small limit, such as 3.
Why this works: a count gives you something to compare with Word’s review pane. If the list has three items and the pane has four, you’ve learned something.
What you should see: a numbered list of revisions in the Claude panel, and the same revisions marked in the document.
3. Compare the count, then check every revision
Open Word’s review pane and count the revisions. If the count doesn’t match Claude’s list, find out why before accepting anything. Then check each one:
- Is it inside the selected paragraph?
- Do figures, units and dates still match?
- Has “planned” become “will”, or “may” become “must”?
- Was a condition or exception removed to make the text shorter?
Accept the useful revisions and reject the others individually. If the document already had someone else’s tracked changes, don’t accept those by accident.
Why this works: Claude’s summary describes what it meant to do. The review pane shows what it did.
What you should see: every revision either accepted or rejected, and the clean paragraph reading correctly.
Check the result
- The review-pane count matched Claude’s list, or you found and dealt with the difference.
- Every number, date and exception from the original is still there.
- Nothing outside the selection changed.
- You read the clean paragraph as the recipient would, then saved the copy under a clear name.
The usual failure: an unlisted revision. The tidy summary lists the changes you asked for, while the review pane has one more, usually a deleted condition that made the paragraph shorter. Spot it by comparing the counts. Reject it in Word, which is a perfectly good correction, then ask for another attempt if you need one:
I rejected a revision because it removed [condition or fact]. Try again on the selected paragraph with at most [number] changes. Keep [condition or fact] exactly as written. Make no changes elsewhere, and list each revision.[condition or fact] is what the edit removed. If the same check keeps failing, finish that sentence yourself.
Worked example: a car park notice
Fictional example. A facilities coordinator wants a staff notice tightened:
From 2 February, the staff car park will have 40 spaces instead of 55 while
resurfacing takes place. The car park will have fewer spaces during this time.
Spaces are first come, first served. Blue badge spaces are unchanged.
Resurfacing is planned to take three weeks, weather permitting.She asked for at most three changes. Claude listed three: remove the repeated second sentence, shorten “while resurfacing takes place”, and join the last two sentences.
- The failure. The review pane showed four revisions. The fourth, missing from the list, deleted “Blue badge spaces are unchanged.” The shorter paragraph read well, and quietly dropped the one sentence some drivers needed most.
- The repair. She rejected revision 4 in Word and accepted the other three, leaving: “From 2 February, the staff car park will have 40 spaces instead of 55 during resurfacing. Spaces are first come, first served. Blue badge spaces are unchanged. Resurfacing is planned to take three weeks, weather permitting.”
- What stayed. “Planned” and “weather permitting” survived. A version saying “will take three weeks” would have been shorter, and a promise nobody made.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: ask for a change plan first
For a longer section, review the approach before allowing any edits:
Read [section] and suggest at most three wording improvements. For each, name the passage and explain the benefit. Don't edit the document, add facts or act on comments yet.[section] is the heading or passage. Choose the changes you want and apply them in a smaller, counted pass.
Optional training: try a contract clause, carefully
Once the method feels routine, try it on a clause in a practice copy. Asking Claude to turn “use reasonable endeavours to notify” into a firmer obligation will produce something like “shall notify… no later than [X] working days”. That’s a change of meaning, not wording. The tracked revision makes it visible. Whether it’s acceptable is a decision for whoever owns the contract.
Optional training: treat unexpected instructions as a warning
Anthropic warns that documents from outside sources, such as downloaded templates, counterparty files or emailed attachments, can hide instructions in text, comments, tracked changes, headers or footers. When Claude proposes a risky operation it asks you to confirm. Stop if it asks for an unrelated search, disclosure or destructive change, and use trusted documents while you learn.
Sources
- Claude docs: Use Claude for Word covers plans, supported versions, admin deployment, known issues and data handling.
- Microsoft Marketplace: Claude for Microsoft 365 is the install listing.
- Microsoft Support: Track changes in Word covers viewing, accepting and rejecting revisions.
- Microsoft Learn: Manage deployment of add-ins covers Admin Center deployment.