This workflow helps you review wording and requirements across versions. It does not replace a document editor's exact comparison feature when you need a complete record of every textual edit.
OpenAI's file guidance, checked October 24, 2026, describes attaching files for comparison. Features depend on account and workspace settings. Use documents you are permitted to provide, and keep the originals unchanged during the review.
Label the versions before asking what changed
Name the files clearly, such as Volunteer-guide-v2.pdf and Volunteer-guide-v3.pdf. Also read the titles and dates inside them. A filename alone does not prove which document is newer or approved.
Ask ChatGPT to identify the attached files and their internal version labels before comparison. If one file cannot be read, supply an accessible version through your approved process. Do not accept a whole-document comparison based on a few pages that happened to extract successfully.
For documents whose section numbering changed, compare by topic as well as heading. Section 4 in the newer guide might correspond to Section 3 in the older one. A numbered-section mismatch is a reason to check the mapping, not automatically a removed requirement.
Ask for differences with paired evidence
Compare the two attached documents.
Older version: [FILE NAME AND INTERNAL DATE/VERSION].
Newer version: [FILE NAME AND INTERNAL DATE/VERSION].
Review purpose: [WHAT CHANGES I NEED TO UNDERSTAND].
First identify the files you can read and any missing sections.
Match sections by subject, accounting for moved or renamed headings.
Return a table with:
topic | older wording and location | newer wording and location |
change type | practical effect | question for human review.
Separate additions, removals, changed requirements, and wording-only
changes. Distinguish a moved passage from a deleted passage.
Do not infer approval, legal effect, or the author's intention.
If a difference cannot be checked, mark it unverified.
Do not edit either original. End with a list of sections compared
and any sections not compared.
Locations can be page numbers and headings. If page labels differ from the viewer's page count, state which numbering you used. Check each important reference in the original file before circulating the comparison.
Test a change that hides in a familiar sentence
These fictional excerpts illustrate a version change; they are not uploaded documents or observed ChatGPT output:
| Version | Section | Wording |
|---|---|---|
| v2 | Equipment returns | Return kits within three working days. |
| v3 | Equipment returns | Return kits within three calendar days. |
| v2 | Arrival | Collect the key at the front desk. |
| v3 | Building access | Collect the key at the front desk. |
The return period changed even though the number stayed three. The arrival instruction moved under a different heading but retained its wording. A comparison that labels both rows “minor wording changes” misses the different practical effects.
The checked note should say that v3 changes the return period from working days to calendar days, while the key-collection instruction appears unchanged under Building access. If the organization has a separate definition of either term, read that definition before calculating an actual due date.
Investigate omissions as well as reported changes
Search the originals for distinctive phrases in a supposedly deleted section. It may have moved into an appendix or table. Conversely, a short summary may overlook an exception that disappeared from the newer version.
For a consequential difference, ask ChatGPT to show the surrounding paragraph from each document. Inspect the full passages yourself. “Same meaning” is a conclusion you should assess, especially when the words include dates, exclusions, obligations, or approval conditions.
If you need exact character-level differences, run the files through the comparison feature in your document editor, then use ChatGPT to help explain selected differences. A clean summary should accompany the detailed comparison rather than standing in for it.
Keep the comparison separate from the approved document
Use the review table to resolve questions with the document owner. Then confirm which version readers should use and retain the older one according to your team's record process. The comparison does not approve the newer version or update other copies.
For summarizing a single source, the file-upload guide covers that separate task. With two versions, leave reviewers with the paired passages and the questions still needing a decision. In the example, the key question is whether the change to calendar days was intended.