Compare Document Versions With ChatGPT: What Changed?
Compare two document versions with source IDs. Check changed deadlines, scope and deliverables, then separate confirmed revisions from actions to approve.
A revision summary should point back to both originals
A revised document may move a deadline, narrow a reporting period or require an extra attachment. A general summary can miss exactly the condition that changes your work. Give ChatGPT both versions and ask for a comparison you can check line by line.
This workflow produces a review draft. It does not decide which version is approved. Keep the original files and distinguish a textual change from your proposal for what to do next.
1. Prepare comparable excerpts
Label the old and new versions and give each relevant passage an ID. Include the same sections from both. Preserve words such as only, optional and required; their removal can matter more than a rewritten sentence.
Use material you are permitted to share. Remove private details and unrelated internal information. Account data controls do not replace permission to upload a work document.
- Record the comparison scope and each version date.
- Keep units, dates and time zones in the text.
- Mark approval status unknown unless you have confirmation.
2. Try a small, fictional revision
The following reporting instructions are a fictional example created for this guide. The versions contain five matching requirements, so you can verify the result without a long document. Neither label proves approval.
In your own document, a paragraph may move or split into two. Match its meaning before treating its old position as missing.
| Requirement | Old version | New version |
|---|---|---|
| Deadline | 10 October, 17:00, Asia/Seoul [O1] | 12 October, 12:00, Asia/Seoul [N1] |
| Reporting period | April [O2] | May [N2] |
| Deliverable | Excel and PDF [O3] | Excel only [N3] |
| Appendix | Optional [O4] | Required [N4] |
| Reviewer | Team lead [O5] | Team lead [N5] |
3. Open the comparison prompt
Open the shared prompt below, replace the bracketed fields and paste your numbered excerpts. Ask for short source passages on both sides of every change. Include an unchanged list so that a revised file does not make every requirement look new.
For a scanned file, check that the extracted text includes the numbers and tables correctly before comparison. Missing text is an input problem to resolve, not evidence that a condition was removed.
Open, edit and copy the full prompt
4. Separate a change from its practical effect
These are editorial example checks, not a recorded model test. Four requirements change; the reviewer remains the same. The comparison should preserve the new noon deadline and the explicit Excel-only wording.
“Move our internal review” is a proposed action. It requires your actual review process and approval, neither of which is supplied in this example.
| Change and evidence | Effect to review | Next check |
|---|---|---|
| Deadline [O1, N1] | Delivery timing changes | Confirm the revision is approved. |
| Period [O2, N2] | May records are needed | Verify access and the period in the original. |
| Format [O3, N3] | PDF is excluded by “only” | Check for another instruction requiring PDF. |
| Appendix [O4, N4] | An optional item becomes required | Confirm appendix contents; they are not specified. |
| Reviewer [O5, N5] | No stated reviewer change | Keep the team-lead requirement. |
5. Check the differences before acting
Read every cited passage yourself. An accurate quotation can still be matched to the wrong requirement. For dates, compare the day, time and time zone separately; for numbers, check the unit and whether the number is a limit or a target.
- Count each requirement once even if wording moves.
- Distinguish explicit removal from absence in a partial excerpt.
- Keep contradictions visible instead of silently choosing a version.
- Approve proposed actions separately from the comparison.
6. Make a concise review note
A review note could say: “The supplied revision changes the deadline, reporting month, file format and appendix requirement. The reviewer is unchanged. Please confirm that this revision is approved before we update the work plan.” Add the version labels and evidence IDs.
If only two sections were compared, say so. For a large document, work in matching sections and maintain a requirement index. You can then ask for a combined review list while retaining the source IDs for every row.
Related guides and source checks
Use the original documents as the authority for the requirements. OpenAI’s accuracy guidance supports checking important output; the comparison method and fictional example here are Praclane editorial workflows.
- Verify ChatGPT answers
- Clarify a work request
- OpenAI: accuracy and verification
- OpenAI: data controls
Photo: Nick Morrison / Unsplash.
