Why this matters
A new version of a policy, a contract or a price list arrives, and everyone asks the same thing: what changed? Reading two long documents side by side takes an hour, and small changes, like a number of days, are the easiest to miss.
Claude can line up two versions in a table, topic by topic, in a minute. It can also file something in the wrong list, so the table is something you check, not something you forward.
In this module you compare last year’s and this year’s remote work policy, catch one mistake in Claude’s answer, push back in plain words, and get a short note to staff built only from the facts.
What you’ll build
A comparison table of a made-up company’s 2025 and 2026 remote work policies (topic, 2025, 2026, what changed), with lists of what was added and removed underneath.
You spot that the removed list mixes changes with real removals, ask Claude to fix it, and get a five-sentence note to staff that uses only the facts in the table.
What you need
- Nothing to start the practiceClaude is a practice copy, and both policy versions are ready to paste.
- A Claude account, to do it for realclaude.ai. The free plan handles two short documents like these. Use your company account if you have one.
- Both versions of the documentThe old and the new text. For contracts or anything private, use a copy with names and private details taken out, and follow your employer’s rules on AI tools.
Concepts
3 ideas you’ll use in the practice.
Label each version and fence it in
Paste both versions with a clear label on each ("2025 POLICY", "2026 POLICY"), so Claude never mixes them up.
Add one rule: use only the text I pasted. That stops Claude from filling gaps with what policies like this usually say.
Ask for a table, then check it row by row
A table with topic, old, new and what changed is easy to check. Read each row against the two versions, especially numbers, days and dates.
Read the added and removed lists closely. A rule that changed is not a rule that was removed, and staff will read it very differently.
Push back in plain words
When something is wrong, say exactly what and why ("the office days rule changed, it was not removed; fix the removed list"). You do not need special wording.
Then ask for the note to staff from the corrected table only, so the mistake cannot sneak back in.
Practice
Do every step yourself in a practice copy of the real tool. It checks your work, and “Do it for me” finishes any step you get stuck on.
Do it for real
Now repeat it in your own account. Tick each step as you go.
Quick check
3 questions to check you’ve got it.
1. Why put a label on each version?
- It is required to paste
- So Claude never mixes up the old and the new text
- It makes the answer shorter
Show the answer
So Claude never mixes up the old and the new text. Clear labels keep the two versions apart, so each row compares the right text.
2. Claude lists a changed rule under removed. What do you do?
- Forward the table anyway
- Say plainly what is wrong and ask Claude to fix the list
- Start a new chat
Show the answer
Say plainly what is wrong and ask Claude to fix the list. A plain-words correction in the same chat fixes it, and the rest of the work stays.
3. Where should the note to staff get its facts?
- From Claude’s general knowledge
- Only from the corrected table
- From last year’s note
Show the answer
Only from the corrected table. Building the note from the checked table keeps it accurate.