At 5 p.m., someone sends you a thirty-page proposal and asks, "Can you tell me if we should approve this?" Reading every line isn't the first job. You need to find the requested decision, the evidence, and the gaps. Copilot in Word can help you get oriented, but this work differs from drafting. Here, you're trying to understand and reshape material that already exists.
The risk is that a fluent summary can sound conclusive when the document isn't. Copilot might say a pilot "succeeded" when the text only states a target, or claim that a checklist "caused" an improvement that was never measured. Before repeating the answer, check it against the source.
Four ways to read a document you didn't write
Copilot gives you four distinct ways to work with an open document. Pick the one that matches the job instead of defaulting to the first button you see:
Summary is useful for a first pass, but any material claim still needs its source passage. Document chat suits a focused question such as "What decision is being requested?" Audio Overview lets you listen to the main ideas, then check what you heard in the text. Coaching, available in Word for the web, comments on the writing itself. Review its suggestions too, since a clearer sentence can still add a claim the document doesn't support.
Explicit, inferred, or absent: the habit that keeps you safe
Before you repeat anything Copilot tells you about a document, label it with one of three tags:
- Explicit: the document states it directly.
- Inferred: a reasonable read, but the document doesn't say it outright.
- Absent: the document gives no support for it at all.
Handle one claim at a time and split compound sentences before classifying them. Suppose a proposal sets a target of reducing onboarding from ten days to seven. It also reports that pilot teams used a checklist and saw fewer handoffs. "the checklist got onboarding down to seven days" combines two unsupported claims. The statement "onboarding reached seven days" is absent because no result was reported. "the checklist caused it" is absent too because the document never establishes causation. At most, "fewer handoffs might help onboarding in a future pilot" is a careful inference.
Keep targets separate from achievements, and reported associations separate from causes. Otherwise, Copilot's confident wording can become a false claim in your own report.
Editing the whole document: plan first, then execute
Rewriting one selected paragraph has a clear boundary. A whole-document edit can shorten the introduction, turn three paragraphs into a list, and change transitions across several sections at once. Word's Edit with Copilot experience, generally available since April 2026, can make those changes. Your instructions determine how much control you keep.
Use Plan → Execute → Review in separate prompts. If one prompt says "show me a plan and then make the changes", editing may begin before you inspect the proposal. Ask for the plan first. Read it, then use a second prompt to authorize only the changes you accept.
A bounded request defines five things: Outcome, Scope, Operations, Constraints, and Success criteria. "Make this better" defines none of them. State which sections may change, which must remain untouched, and which facts, dates, decisions, and qualifications must survive exactly.
Read the edit for what it did to the meaning
After executing an approved plan, review three levels. Scope: only the permitted sections changed. Content: dates, numbers, names, and decisions remain intact. Meaning: an observation hasn't become an instruction, and a possibility hasn't become a commitment.
Meaning is easy to miss. The source might say, "Two security questions remain open. No owner, action, or deadline is assigned." Shortening that to "Resolve the two open security questions" keeps the nouns and number but assigns an unsupported action. A faithful version is: "Two security questions remain open. No owner, required action, or deadline is specified." Fix that one item or restore it from the original. There's no need to reopen the whole document.
The same loop, every time
Summaries, questions, and edits all end with the same check. Break the output into individual claims, find the passage behind each one, and flag anything the document doesn't directly support. The format may change, but the source remains the standard.
Copilot's fluency can make a weak claim look settled. Correct or remove a summary line you can't trace. Reverse an edit that changes the statement's role. Keep a target written as a target. Before forwarding a summary, make sure every claim points to a passage you can open.
- document chat
- Asking Copilot focused questions about the document currently open in Word, such as what decision it requests or what evidence it provides.
- explicit, inferred, absent
- Three labels for a claim: directly stated by the source, a reasonable but unstated interpretation, or entirely unsupported.
- bounded editing request
- An edit instruction that names its outcome, scope, permitted operations, constraints, and success criteria so the change is inspectable.
- semantic drift
- When an edit preserves the words but changes a statement's meaning, such as an observation becoming a directive, or a target becoming a result.
