The situation
Your organization has revised its travel policy, but a general announcement will not tell managers which routines to change. You have the previous policy, the approved replacement, and a list of directly affected teams and existing processes. Build an impact table that identifies changed obligations, unchanged rules people may confuse, effective dates, and open implementation questions. The policy owner should resolve ambiguous wording before the team sends instructions to staff.
Build a small, reviewable version
Mark the source boundaries
Label the old and new documents with version dates. Ask the assistant to extract changed passages, preserving section identifiers and exact wording. Keep moved text separate from altered requirements, and record missing sections before considering what any change means operationally.
Check: Every change links to a passage in each available version.
Map changes to routines
Provide the current process list and affected teams. For each confirmed change, request an impact row containing the current routine, required adjustment, proposed owner, effective date, and supporting passage. Mark any connection inferred from process context for a human to review.
Check: Inferred impacts are visibly distinct from explicit policy requirements.
Resolve implementation questions
Review rows with the policy owner and process leads. Turn uncertain interpretations into specific questions with the disputed wording attached. Record each answer and its approver, then update the table without silently rewriting the source or treating an unanswered question as settled.
Check: Each published interpretation has an identified approving owner.
Draft the team announcement
Use the approved impact table to draft a brief announcement explaining who acts, what changes, and when. Include a route for exceptions or questions only when the policy supplies one. Compare every actionable sentence with its approved row before sharing the message.
Check: Every action and date matches an approved impact row.
Your acceptance checklist
- Every changed requirement retains its section reference and version date.
- Each affected routine has a proposed owner and implementation action.
- Unresolved wording stays in the questions list with a decision owner.
- The announcement includes only approved actions, dates, and contact routes.
Where the process can go wrong
- Treating a relocated paragraph as a new requirement creates unnecessary work.
- Converting an example into a mandatory rule changes the policy's meaning.
- Assuming an effective date hides a decision the owner must make.
Choose the workflow deliberately
Choose Claude, ChatGPT, or Gemini according to your approved document workflow and the materials you can provide. Compare their handling of one difficult exception before committing. A clear source table matters more than a polished announcement when the revised wording still needs an owner's interpretation.
A working brief to copy
Compare [OLD POLICY, DATE] with [APPROVED NEW POLICY, DATE] for [TEAMS AND CURRENT ROUTINES]. First extract changed passages with section identifiers. Then create an impact table with source wording, operational implication, action, owner, and effective date. Label inferred implications and unanswered questions explicitly. Preserve exceptions and qualifying language. Do not invent approval routes or dates. Finish with a draft announcement based only on confirmed rows, plus questions for [POLICY OWNER] that block a reliable instruction.
Tool context and original sources
This is an editorial task plan using the products’ published positioning, rather than a record of controlled product testing. The steps describe a trial for you to run. Confirm current access and terms, and review each tool’s limitations.
- Claude official website ↗ — Develop a document, reason through a problem and iterate in conversation. Profile and source-check notes →
- ChatGPT official website ↗ — Draft, explore and work through ideas in a conversational workspace. Profile and source-check notes →
- Gemini official website ↗ — Explore ideas and get assistance across text and multimodal tasks. Profile and source-check notes →