Find out what a policy change means for your team
A revised policy lands with a note saying “please review the changes”. Nobody has said which of your checklists, deadlines or approvals actually move.

What you'll make
a plain-English list of what changed between two policy versions, and a draft checklist your team can agree, with each action traced to the policy.
What you'll need
Claude (or Gemini or Copilot) in your work account, the old and new policy versions, a few sentences describing the affected work, and about fifteen minutes. This is for internal process changes. Statutory, employment or regulated duties need the policy owner and a qualified reviewer for the right jurisdiction.
Example result.
Change: Content Lead review now required before external help pages are published. (New rule 1)
Unchanged: price changes still need service-owner approval as well. (New rule 2)
Timing: effective 15 October. Existing pages need a first review by 15 November; new pages follow a 30-day cycle.
Action (draft): update the publishing checklist to add Content Lead review, keeping service-owner approval for prices. Owner: to confirm.
Open question: which calendar defines a "business day" for urgent-outage reviews?
1. Upload the right versions
Start a new chat in Claude. Select + › Add files or photos in the lower left of the chat box and attach both policies, or paste the text. Label which is old and which is new, with their approval and effective dates: they’re often different.
Add a few sentences about how your team works: the checklist you use, where approvals happen, how review dates are tracked. If a policy is a long PDF, Claude only reads charts and diagrams in PDFs of up to 100 pages, so check any important flowchart yourself.
To practise first, use the fictional publishing-policy pack: two policy versions and a short process description.
Why this works: the comparison is only as good as the versions you give it. A model comparing the new policy with an abandoned draft can produce a beautifully organised wrong answer.
What you should see: both files attached, labelled old and new, with dates and a short description of your work.
2. Ask what changed and what to do
Compare these old and new policies. Explain the important changes in plain English, including what stays the same, exceptions and when each rule takes effect. Then give me a short action checklist for the team, using the process description I gave you.
Point to the policy passage behind each action. Distinguish required outcomes from your suggested ways to meet them. Leave owners and dates unknown unless the documents state them, and don't imply anyone has accepted an action. Flag ambiguous wording for the policy owner.
Why this works: asking for what stays the same keeps continuing rules on the page, and separating requirements from suggestions stops a helpful idea becoming a suspiciously firm obligation.
What you should see: a plain-English summary of changes, a list of unchanged rules and exceptions, and a checklist where each item names its policy section.
3. Check one change all the way through
Pick the change that affects most work and follow it from policy to action.
In the practice pack, the new policy starts on 15 October 2026 and adds Content Lead review before external help pages are published. Price changes still need service-owner approval too. A useful action is “Update the publishing checklist to include Content Lead review, keeping service-owner approval for price changes.” Adding a CMS approval field could help, but the policy doesn’t require that technical solution.
Timing is where checklists go wrong. Pages already live before 15 October need their first review under the new policy by 15 November. Newly published pages follow a 30-day cycle. Changing every due date to “today plus 30 days” would lose the transition rule.
Why this works: one change traced end to end shows whether the checklist kept the conditions, or only the headline.
What you should see: one action with its policy section, the required outcome, any optional way of meeting it and the right start date for its clock.
4. Review three things before assigning work
- Dates. Compare approval, effective and transition dates with your working timetable. The example policy is approved on 1 October and starts on 15 October. You can prepare earlier, but it isn’t in force on 4 October.
- Exceptions and unchanged rules. The Support Lead may publish urgent outage instructions immediately, with Content Lead review recorded by the next business day. Internal-only drafts stay out of scope, and price approval still applies.
- Authority. Proposed owners and implementation ideas stay proposals until the right people agree. Ask the policy owner to settle unclear wording.
Why this works: these are the three places a tidy checklist most often misstates a policy.
What you should see: a checklist with dates marked as required or proposed, exceptions intact and questions listed for the policy owner.
Check the result
- Every action names the policy rule or section it comes from.
- Rules that continue unchanged still appear, alongside the new ones.
- Each date says which clock it uses: approval, effective, transition or ongoing.
- Suggestions (a CMS field, a log) are labelled as options, not requirements.
The usual failure: the draft treats the new policy as a clean replacement. A continuing rule disappears (“Content Lead review instead of service-owner approval”), or every deadline is reset to one cycle. Spot it by checking each old rule: is it kept, changed or removed, and does the new policy say so?
Check this checklist against both policy versions. For each rule in the old policy, say whether the new policy keeps, changes or removes it, with the section. Then list any checklist action that drops a continuing rule or uses the wrong start date for a deadline, and rewrite only those actions.
Worked example: one checklist, two flattened rules
Fictional example. From the practice pack:
Old policy, effective 1 June 2026:
1. Authors may publish external help pages without content review.
2. Pages changing published prices need service-owner approval.
3. External help pages are reviewed every 90 calendar days.
4. Internal-only drafts are out of scope.
New policy, approved 1 October 2026, effective 15 October 2026:
1. All external help pages need Content Lead review before publication.
2. Price changes also need service-owner approval.
3. Pages published from 15 October are reviewed every 30 calendar days.
4. Pages live before 15 October get their first review by 15 November 2026, then every 30 days.
5. Support Lead may publish urgent outage instructions immediately, recording Content Lead review by the next business day.
6. Internal-only drafts remain out of scope.
The first checklist said: “Price changes now need Content Lead review instead of service-owner approval. Reset all review dates to today plus 30 days.”
- The failure. Two rules flattened. New rule 2 keeps service-owner approval, so price pages need both reviews. New rule 4 gives existing pages a 15 November deadline, not a rolling 30 days from whenever someone ran the checklist.
- The repair. The repair prompt listed old rule 2 as “kept (new rule 2)” and old rule 3 as “changed, with a transition rule for existing pages”, then rewrote the two actions as in the example result.
- What stayed open. “Business day” isn’t defined anywhere. A neat date generated by AI doesn’t resolve missing policy wording, so it went to the policy owner as a question.
Try it
Approval, effective date and review deadline
Select a marker to see which clock it starts.
- 1 October
- 15 October
- 15 November
- New pages
- Urgent outage
The policy is approved; it is not yet the effective date.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: Build a change register before the checklist
For a bigger revision, ask for the comparison first and review it before any actions exist.
Using only these two policy versions, first confirm which is old and which is new, with approval dates, effective dates and scope. Do not assume the approval date is the effective date. Then build a change register: old rule and section; new rule and section; type (added, changed, removed or unchanged); scope; exceptions; timing; ambiguity for the policy owner. If paragraphs split or merge, compare their meaning, not only wording. Don't draft actions yet.
The version read-back is the important line. If it names the wrong document, stop there.
Optional training: Map each change to the work it touches
List the checklists, systems, pages and routines that might be affected, using the names you already use. Then map one change at a time:
new review rule → publishing checklist → Content Lead reviews external pages before publication → optional extra checklist step → checklist tried on a routine page and a price-change page.
The required outcome comes from the policy. The way of meeting it and the completion check are proposals for the owner. The policy requires review before publication; it doesn’t require a CMS field to record it, and a temporary log might do. Keeping that distinction stops an interpretation turning into an expensive technical requirement.
Optional training: Test the exceptions before you sign off
Before the checklist goes to the policy owner, test it against cases the main route might miss:
- A price page needs both reviews; the old approval isn’t lost.
- An internal draft doesn’t pick up a public-publishing gate it doesn’t need.
- An existing page and a new page get different first-review dates.
- An urgent outage page keeps its exception and its next-business-day review.
- Nobody is listed as having accepted an action without evidence.
Then have the policy owner approve the interpretation and the implementation owners confirm actions and timing. A drafted action isn’t an accepted assignment, and an assignment isn’t completed work.