Use AI to compare two email drafts and list substantive differences

Set up a comparison that keeps the drafts straight

Use two complete drafts, clearly marked as the earlier version and the revision. Include the subject line if it matters to the message. Avoid pasting unrelated correspondence unless context is genuinely needed; extra material can distract from the comparison or expose information unnecessarily.

Tell the assistant not to rewrite either draft. Ask it to distinguish substantive changes from cosmetic edits such as spelling, punctuation or reordered sentences. If your mail account offers AI assistance, availability may depend on the plan and provisioning state. Treat any output as a review aid, not as an authoritative record.

Use a prompt built around meaning

A useful prompt names the exact risks you want checked and asks the assistant to show evidence from both versions. Ask it to flag additions, removals and changes in certainty, not merely summarize the overall impression.

Compare the two email drafts below. Do not rewrite them.
List substantive differences under: obligations or promises; scope or exclusions; dates, deadlines or conditions; responsibility or ownership; and tone or level of certainty. For each difference, quote the relevant short phrase from the earlier draft and the revised draft, explain the practical change in plain language, and say whether it appears to strengthen, weaken or leave the commitment unchanged. Separate wording-only edits from meaning changes. If a difference is unclear, say what is ambiguous rather than guessing.

EARLIER DRAFT:
[paste earlier draft]

REVISED DRAFT:
[paste revised draft]

Read the output as a set of questions

The assistant should make differences easier to inspect, not settle what they mean for your situation. For each flagged item, ask: Did a firm promise become a possibility? Did a condition disappear? Was a task added, removed or shifted to someone else? Did the revision narrow what will be delivered, or imply that another party has agreed?

Pay particular attention to small words: “will,” “may,” “only,” “including,” “unless,” and “by.” A change from “We will review all three files” to “We may review the files” affects certainty; changing “all three” to “the relevant files” affects scope. A fluent comparison can still overlook a small but important edit.

EARLIER: “I will send the completed summary by [Friday].”
REVISED: “I expect to send a summary around [Friday], if the figures arrive.”
Possible change: the revised sentence makes the timing less certain and adds a condition. Confirm whether that qualification is intended.

Compare the revision with your intended meaning

Before accepting a change, write down the message you meant to convey in a plain sentence: for example, “I am committing to send the complete file on Friday, even if I need to note any unresolved figures.” Then compare that statement with the revised draft. If the draft no longer supports it, restore or clarify the missing commitment rather than relying on the AI’s label.

This check also catches changes the assistant may call neutral. A sentence can preserve the same basic topic while changing who is responsible, what counts as complete, or whether the recipient must do something first. Your intended meaning is the standard; the assistant’s explanation is only a prompt for inspection.

Verify the final email before sending

After editing, read the final version from top to bottom. Make sure each intended obligation, boundary and condition is present in clear language. Check that the revised draft has not accidentally retained contradictory wording from an earlier version. Confirm names, dates, recipients, attachments and any financial details against the original source rather than trusting an AI comparison.

A compact final check: Is every promise deliberate? Is the scope explicit? Are conditions and deadlines accurate? Does the tone fit the relationship without implying agreement or certainty you do not have? If an answer is uncertain, pause and resolve it before sending.

Know when a comparison is not enough

AI may miss a difference, misread context or confidently describe an ambiguous sentence. If the drafts concern a consequential commitment, ask the relevant person to confirm the intended wording. Do not treat a comparison as proof that the drafts are equivalent or that a recipient will interpret them as you do.

You can confirm the process worked by checking that every AI-flagged substantive change has a decision—keep, revise or restore—and that a separate manual read finds no unintended change to scope, obligation, timing or tone. The goal is not a clean AI report; it is a final draft whose meaning you have deliberately verified.