Establish the versions before interpreting a change
Record the policy name, original version, proposed version, and sections being compared. Check whether each file is approved, a draft, or a working copy. A newer file date does not prove that its contents took effect.
Compare like-for-like text, then review the source documents for tables, formatting, signatures, or other material that text extraction may miss. Clarion’s Document Compare matches whole paragraphs in order. It identifies added and removed paragraphs; it does not decide why wording changed or what a policy legally requires.
Separate three questions
First: what exact text changed? Record the old and new wording and section references. Second: what questions does the change raise? Record the questions without presenting assumptions as answers. Third: who can confirm approval, effective date, and implementation? Leave those fields pending until that person responds.
Check related forms, instructions, training material, and references. A policy can be updated while a form still tells people to follow the old process. Record each dependent item and a confirmed owner for updating it. Use the appropriate policy, HR, legal, or subject-matter review when the content requires it; this checklist does not determine compliance.
Worked example: a shorter submission window
Fictional wording in section 3 changes from ‘submit receipts within 10 business days’ to ‘submit receipts within 5 business days.’ The revised file is marked draft and provides no effective date. The text change is clear; its approval and transition rules are not.
The review record should ask: ‘Who approves this draft? When would it take effect? How are expenses already incurred handled? Who can approve an exception? Does the expense form still show 10 business days?’ It should not announce the shorter deadline as a current rule simply because the comparison found it.
After approval is confirmed, record the approved version, implementation date, affected instructions, communication owner, and any unresolved issue. Keep the old and revised files with the review record so the decision can be checked later.
Before you share it
- Verify both versions, scope, and approval status.
- Check extracted text and non-text content against the originals.
- Preserve exact wording and source positions.
- Confirm approval, effective date, and any transition rules.
- Check related forms, guidance, and communication plans.
- Record unanswered questions and the person responsible for resolving them.