How to Edit Any Section of a Word Document with Claude in 30 Seconds Using the Highlight Workflow
Claude for Word's highlight-to-edit feature scopes your next prompt to any selected text. Here's how to use it for contracts, reports, and writing reviews.
You Can Edit One Paragraph Without Touching the Rest — Here’s How
Most people using Claude in Microsoft Word are doing it the slow way. They paste in a prompt, Claude rewrites the whole document, and then they spend five minutes undoing the parts they didn’t want changed. There’s a better approach, and it takes about 30 seconds once you know it: the highlight-to-edit workflow, where you select any section of text and your next prompt applies only to that selection. Everything else stays exactly as it was.
This is one of those features that sounds obvious once you hear it, but isn’t obvious at all from the interface. Claude for Word doesn’t announce it. There’s no button labeled “edit selection.” You just highlight, then prompt — and Claude scopes its response to what you selected.
This post walks through exactly how to use it, what it’s good for, and where it breaks down.
What this actually lets you do
Imagine you’re reviewing a contract. You don’t want to rewrite the whole thing — you want to flag the clauses that could hurt you. You highlight the contract body, type “highlight areas where I may be getting screwed over,” and Claude marks up only those sections.
Or you’ve written a report and one paragraph feels weak. You highlight just that paragraph, type “make this more assertive,” and Claude rewrites that paragraph. The rest of the document is untouched.
Plans first. Then code.
Remy writes the spec, manages the build, and ships the app.
Or you’re editing someone else’s writing. You highlight a section that buries the lead, type “rewrite this so the main point comes first,” and Claude restructures just that block.
The highlight-to-edit workflow is the difference between a scalpel and a sledgehammer. Without it, every prompt risks touching the whole document. With it, you control exactly what’s in scope.
What you need before starting
A Claude Pro or Max plan. Claude for Word runs on Anthropic’s API, and the free tier won’t work. If you try to use it without a paid plan, you’ll hit an authentication error. Get the plan sorted first.
The Claude add-in installed in Word. Open Word, go to Add-ins, search “Claude,” and click Add. It appears in the top-right sidebar. If the sidebar loads blank or glitched, click one of the dropdown menus in the Claude panel — there’s a refresh option that fixes it most of the time.
The right model selected. For general editing work, use Sonnet 4.6. It handles writing tasks well and uses less of your monthly usage than Opus. If you’re doing math-heavy documents, Opus 4.6 is the better choice. One thing to watch: Opus 4.7 is expensive on usage and isn’t better than Opus 4.6 for non-math tasks — the presenter in the source video specifically calls this out as a mistake people make. Your usage is shared across your whole Claude account, so burning through it on Opus 4.7 for a cover letter is wasteful. If you want a deeper breakdown of how these models compare on real document tasks, the GPT-5.4 vs Claude Opus 4.6 comparison is worth reading before you commit to a model for heavy editing work.
A document with text in it. This sounds obvious, but the highlight workflow only works on existing text. You need something to select.
How to use the highlight-to-edit workflow
Step 1: Open your document and the Claude sidebar
Open Word, open your document, and click the Claude add-in in the sidebar. You should see the chat interface on the right side of your screen.
Now you have: a document with text, and Claude open and ready.
Step 2: Highlight the section you want to edit
Click and drag to select the text you want Claude to work on. This can be a single sentence, a paragraph, a section, or the entire document body — whatever scope makes sense for your task.
The key behavior: once you have text highlighted, your next prompt will apply only to that selection. Claude reads the highlight as a scope constraint.
Now you have: a highlighted section and Claude waiting for your instruction.
Step 3: Type your prompt in the Claude sidebar
With the text still highlighted, type your prompt in the Claude chat box. Be specific. “Expand this section” is fine. “Rewrite this paragraph to sound more confident and direct, without adding new claims” is better.
Some prompts that work well with highlighted sections:
- “Expand this section” — Claude adds detail to just the selected text
- “Rewrite this for a non-technical audience”
- “Highlight areas in this contract where I may be getting screwed over” — this uses Claude’s literal highlight function to mark up the selected text visually
- “Highlight parts of my writing that make me sound weak”
- “Split this into three shorter paragraphs”
- “Add a subheading to this section”
Built like a system. Not vibe-coded.
Remy manages the project — every layer architected, not stitched together at the last second.
The highlight-and-mark-up use case is worth pausing on. You’re not asking Claude to rewrite anything — you’re asking it to identify specific characteristics in your selected text and mark them visually. This is genuinely useful for contract review, script analysis, or editing someone else’s work before you decide what to change.
Now you have: a prompt scoped to your selection, ready to send.
Step 4: Review the output and decide what to keep
Claude will apply the change to your highlighted section. Read it. If it’s right, move on. If it’s wrong, hit Ctrl+Z (or Cmd+Z on Mac) to undo — don’t re-prompt Claude asking it to undo, because that wastes usage and often makes things worse. Just undo directly in Word.
This is the presenter’s explicit recommendation from the source video, and it’s good advice. Claude is generative, which means it can make mistakes. Undo is free. Re-prompting costs usage.
Now you have: an edited section, and the rest of your document exactly as it was.
Step 5: Repeat for other sections
Highlight the next section you want to change. Type a new prompt. Review. Undo if needed. This is the full workflow.
One thing that makes this faster: you don’t have to re-explain context each time. Claude has the whole document in its context window, so when you highlight a new section and prompt it, it understands how that section relates to the rest.
Adding live data to your document
While you’re in this workflow, there’s one more feature worth knowing about. Click the + button in the Claude sidebar and toggle on “search for the web.” Now you can prompt Claude to pull in current information without leaving Word.
For example: “Add a paragraph based on the most recent data about [topic].” Claude will run a search, pull the results, and draft the paragraph inline.
When you do this, Claude will ask for a permission: “allow once” or “dangerously always allow.” For most document work, “allow once” is the right choice. Claude can make mistakes when browsing, and you want to review each web-sourced addition before it becomes part of your document.
This is a convenience feature, not a replacement for real research. But for a quick data point or a recent statistic, it saves the tab-switching.
Where this breaks down
Complex templates with heavy formatting. If you’re working in a Word template that has multiple columns, bordered boxes, image placeholders, or intricate layout blocks, Claude will sometimes corrupt the formatting when it edits. This isn’t a prompt problem — it’s a current limitation of how Claude interacts with complex DOCX structure. The workaround is Ctrl+Z, not re-prompting. If you need to fill out a template like this, consider pasting the content into a plain document first, editing there, then moving it back.
Highlight scope doesn’t persist. If you highlight text, then click somewhere else before prompting, you lose the selection. The highlight-to-edit behavior only works if the text is still selected when you send the prompt. This is easy to accidentally break.
Day one: idea. Day one: app.
Not a sprint plan. Not a quarterly OKR. A finished product by end of day.
Vague prompts on highlighted sections. “Make this better” doesn’t give Claude enough to work with. The more specific your instruction, the more useful the output. “Rewrite this paragraph so the main claim is in the first sentence and the supporting evidence follows” will outperform “improve this” every time.
Usage limits. Because your Claude usage is shared across your whole account (Word, the web app, API calls — all of it), heavy editing sessions in Word can eat into your monthly allocation. This is why the model choice matters: Sonnet 4.6 for general editing, Opus 4.6 only when you need it. If you’re building more complex AI workflows that need to run independently of your personal usage, MindStudio handles this differently — it’s an enterprise AI platform with 200+ models, 1,000+ integrations, and a visual builder for orchestrating agents and workflows, so your document automation doesn’t compete with your personal Claude quota.
What to try next
Once you’re comfortable with the highlight workflow, the natural next step is combining it with Claude’s cross-file capability. Enable “Work across files” in the Claude settings (More Options > Settings), and Claude can pull data from an open Excel spreadsheet directly into your Word document. The Word agent and Excel agent communicate silently — you don’t have to copy-paste anything. The demo in the source video shows this clearly: regional sales data in Excel, a shareholder letter in Word, signed “Andrew Black,” generated in one prompt.
If you want to go further with document analysis — not just editing, but extracting structured information from PDFs or images — the + button in the Claude sidebar also lets you upload files directly. PDFs, Word docs, and images all work. Claude will ingest the content and you can prompt against it.
For teams building more systematic document workflows — where the same editing logic needs to run on dozens of documents, or where you want to chain document processing with other tools — the highlight workflow is a good starting point for understanding what’s possible. If you’re thinking about how AI agents can be composed into larger workflows, the five Claude Code workflow patterns post covers the underlying patterns that apply whether you’re in Word or writing code. And if you’re interested in how to structure prompts so they produce consistent, reusable results across many documents, Claude Code for content marketing walks through a skill-based system that applies the same scoping logic at scale.
One more thing worth knowing: the highlight-to-edit workflow is a good mental model for AI editing in general — scope your context, be specific about the transformation, review before accepting. That principle applies whether you’re in Word, in a code editor, or building something more custom. Tools like Remy take a similar spec-driven approach to full-stack app development: you write annotated markdown describing what you want, and the application — TypeScript backend, database, auth, deployment — gets compiled from that spec. The source of truth is the description, not the generated output. Same idea, different domain.
The highlight workflow is one of those things that’s obvious in retrospect and invisible until someone shows you. Now you know it.
Claude for Word requires a Claude Pro or Max plan. Install via Add-ins > search “Claude” in Microsoft Word. Recommended model for general editing: Sonnet 4.6.
