Use a Change Table to Review an AI Rewrite
A clean rewritten document can hide changes you did not request. For a substantial edit, ask for a short change table beside the proposed copy. Review meaning, facts and commitments before spending time on sentence rhythm.
Set up a practical example
Create columns for Original passage, Proposed passage and Reason. For a fictional service notice, protect dates, URLs and the distinction between a confirmed event and a possible event. A revision from “may be delayed” to “will be delayed” is not merely a style improvement.
Focus the table on material changes rather than every comma. Ask the assistant to flag removed qualifications, added examples and altered instructions. Its table may omit a change, so compare the final copy with the original as well.
Verify before proceeding
When you reject a change, state the rule it violated. “Preserve uncertainty where the source is uncertain” is more reusable than asking for a vaguely softer tone. Apply the rule to the whole document and check other similar passages.
Before publication, remove the internal review table and inspect the actual final version. Retain the source and approved revision together. A change table reduces review friction, but it does not replace a proper comparison when accuracy or commitments matter.
Comments