How to summarize changes between supplied policy texts
A policy-change summary helps readers see what changed and what may require action. Comparing actual versions keeps the summary tied to the wording rather than assumptions about the policy's intent.
Start with the right material.
- What you provide
- two owner-supplied internal-policy versions shown together as text.
- The intended result
- List textual changes and practical questions; provide no legal interpretation.
How the workflow works.
Align corresponding sections and identify added, removed or revised provisions. Preserve effective dates and conditions, and separate a direct textual change from an interpretation of its consequences.
What to check in the result.
Review material changes with the responsible policy owner. The summary is a reading aid, not a substitute for the authoritative policy or a qualified interpretation where that is required.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.