Quick answer: Ask the AI assistant for two outputs: a change log grounded in the old and new text, and a separate list of possible follow-up actions. A changed date is a fact visible in the documents; updating a registration page is an action to consider. Keep those roles distinct so a suggestion does not appear to be an approved decision.
This guide uses two fictional versions of a short event notice. Version A says registration closes on October 6 and participants should bring a personal notebook. Version B says registration closes on October 8 and participants should bring a personal notebook and a pen. These dates and items are demonstration data, not information about a real event.
Identify the exact versions being compared
Label the files A and B, then record their filenames, version labels, and any available update dates. State whether you supplied full documents or excerpts. If a PDF was converted to text, keep the rendered pages nearby: table cells, headers, and reading order may need visual comparison. A reliable change log starts with a clear boundary around its inputs.
Make the observed changes a source-backed table
| Item | Version A | Version B | Location |
|---|---|---|---|
| Registration deadline | October 6 | October 8 | Registration sentence |
| What to bring | Personal notebook | Personal notebook and pen | Preparation sentence |
Copy the relevant wording closely enough to identify the change, then open both versions and compare it. For a long document, add section titles or paragraph numbers. Record additions, removals, and revised wording separately. Do not fill in a reason for the revision unless an authorized source provides it.
Put potential work in a different list
The deadline changed in the example; that observation can lead to a proposed check of the registration form and public schedule. The supplies changed; that can lead to a proposed check of the confirmation email. Neither proposal proves that the other surfaces have already changed. Mark the owner and due date as “to decide” unless the source material assigns them.
| Observed change | Possible next check | Decision still needed |
|---|---|---|
| October 6 → October 8 | Compare registration form and public schedule | Owner and timing |
| Pen added | Compare confirmation email | Whether an update is required |
This second table is a planning aid. Keep it out of the “confirmed changes” section when sharing the comparison with someone who has not reviewed the follow-up work.
Give the assistant a precise comparison request
Compare Version A and Version B below. Create a table of changed dates, quantities, audiences, and required items. For each row, include the old wording, new wording, and source section from both versions. Identify additions and removals. State whether the inputs are full documents or excerpts. Then create a separate list of possible follow-up checks. Use an owner or deadline only if the supplied material states it. Leave change reasons and other documents for human review unless they are provided.
Verify before using the result
Check numbers and dates first, then read each added or removed sentence in context. Inspect the actual PDF pages if extraction changed the line order or a table layout. If the assistant compared only excerpts, label the result “based on supplied excerpts.” Finally, decide which possible actions to assign and record those decisions outside the source-backed change log.
Try it: Create two three-sentence practice notices and change one date and one item. Ask for the two tables, then trace every change back to both versions. The diagram below shows the boundary between observed text and proposed work.
Read the Korean edition of this article.
댓글