Tools and troubleshooting
Use Copilot in Word to Pressure-Test a Policy Memo Before Sharing
Summary
Cihan's view: Open a fictional policy memo in Word, use Copilot in Chat only to ask source-bound review questions, and check each finding against the document before changing or sharing it. Keep unsupported claims, unclear owners, missing process details, and ambiguous exceptions visible until the policy owner answers them.
A policy memo can be grammatically clean and still leave readers guessing about what changes, who decides, or what remains open. Copilot in Word can help you question the document before you edit it, provided you keep the first pass in Chat only.
This guide uses a fictional memo and an illustrative output. It does not report a personal test or a measured result.
The fictional input
Open a Word document named travel-approval-policy.docx with this text:
Travel approval update
Starting next quarter, all client travel should be approved in advance. Managers will review requests quickly, and the new process will reduce unnecessary travel. Employees should use the normal request form and contact Finance with questions.
The policy applies to client visits and conferences. Exceptions can be approved when needed.
The review questions are:
Review questions
- What exactly changes for an employee?
- Who approves an exception?
- Which claims need evidence before the memo is shared?
- What information is missing from the request process?
- Is there a sentence that could confuse a customer or employee?
The goal is a findings table, not an automatic rewrite. Microsoft documents Chat only as a way to ask about a Word document without making changes, and says that Copilot can show references from the document for answers.
Three steps
-
Open the document in Word and select the Copilot button. If available, choose Chat only before asking for the review. Copilot availability depends on your Microsoft 365 subscription, license, platform, and organization settings.
-
Paste the review questions and use the prompt below. Ask Copilot to separate text found in the document from questions the document cannot answer. Do not ask it to edit the memo during this pass.
-
Check the findings against the document. If a passage needs a change, select that passage and request a proposed revision separately. Review the preview or inserted text, then decide whether to keep, discard, or refine it.
Copy this prompt
Review this Word document in Chat only. Do not edit or replace any text.
Use only the document as evidence. Do not add a policy rule, owner, date, threshold, benefit, or exception process that the document does not state.
For each question below, return:
- Finding: one plain-English sentence
- Evidence: an exact short quote from the document, or "Not stated"
- Risk: low, medium, or high, with one reason
- Question for the policy owner: the smallest question needed to close the gap
Review questions:
1. What exactly changes for an employee?
2. Who approves an exception?
3. Which claims need evidence before the memo is shared?
4. What information is missing from the request process?
5. Is there a sentence that could confuse a customer or employee?
End with a section called "Do not share yet" containing only the findings that need an owner answer.
Illustrative output
1. What exactly changes for an employee?
Finding: The memo says advance approval is required for client travel and conferences, but it does not say what employees must submit or when.
Evidence: "all client travel should be approved in advance" and "use the normal request form"
Risk: medium, because the required process is not described.
Question for the policy owner: What fields and lead time must the request include?
2. Who approves an exception?
Finding: The memo allows exceptions but does not name the approver.
Evidence: "Exceptions can be approved when needed."
Risk: high, because employees may not know whose decision is valid.
Question for the policy owner: Which role approves an exception, and where should the approval be recorded?
3. Which claims need evidence before the memo is shared?
Finding: The claims about quick manager review and reduced unnecessary travel have no supporting evidence in the memo.
Evidence: "Managers will review requests quickly" and "the new process will reduce unnecessary travel."
Risk: medium, because the claims may create expectations the process cannot support.
Question for the policy owner: What approved source supports each claim, or should the wording be changed to a stated goal?
4. What information is missing from the request process?
Finding: The memo does not state the request form location, required fields, or Finance contact.
Evidence: "use the normal request form and contact Finance with questions."
Risk: medium, because the reader cannot act from the memo alone.
Question for the policy owner: Which form link and Finance contact should the final memo include?
5. Is there a sentence that could confuse a customer or employee?
Finding: "when needed" does not explain the condition for an exception.
Evidence: "Exceptions can be approved when needed."
Risk: medium, because different readers may apply different standards.
Question for the policy owner: What approved condition qualifies as an exception?
Do not share yet
- Name the exception approver and the recording method.
- Support or revise the quick-review and reduced-travel claims.
- Add the form location, required fields, and Finance contact.
- Define the exception condition.
The exact wording will vary. The checkable artifact is the findings list with quotes, risks, and owner questions. The policy owner still decides what the policy means.
Acceptance checks
Before sharing the memo, check that:
- Every finding has a quote that appears in the document or says
Not stated. - Every risk has a concrete reason tied to the memo.
- The owner questions ask for missing information instead of answering it.
- Any claim about speed, savings, compliance, or outcomes has an approved source or is rewritten as a goal.
- The final document names the process, approver, exception rule, and contact path clearly enough for the intended reader.
- You reviewed any proposed edit before it changed the document.
Troubleshooting
Copilot is missing. Check the license and organization settings. Microsoft says the feature may not be included or enabled for your account. Use Word’s ordinary review process as the fallback and keep the same question list.
Copilot edits the document. Start a new request in Chat only and say do not edit or replace any text. Keep the source file unchanged until the findings pass your review.
The answer includes outside knowledge. Ask for an exact quote or Not stated, then remove any answer that cannot be traced to the document. The document-review pass should not decide a policy from general knowledge.
You cannot find a citation. Microsoft notes that Copilot can provide references, but later document content may not always receive citations in automatic summaries. Treat a missing reference as a review stop and check the source passage manually.
Verdict
TRY this when a policy owner can answer the open questions. SKIP it as a sign-off system because a polished finding is still an assistant output. USE Chat only for the first pass, then make edits only after a human checks the source and approves the policy wording.
For one practical AI workflow each week, join The Weekly Verdict.
Sources
- Welcome to Copilot in Word documents Copilot’s comprehension features, Chat only, review before changes, and availability limits.
- Chat with Copilot about your Word document documents document questions and references from the source document.
- Create a summary of your document with Copilot in Word documents summary limitations and the need to check citations.