Two project documents can give different answers to the same question. A planning brief says a community workshop starts at nine. An approved venue schedule says ten. If you ask an AI assistant for a combined summary, it may return a tidy paragraph that quietly picks one time or drops the disagreement. Ask it to prepare a list of differences first. Then check the originals and ask the person responsible for the schedule which time you can publish.
Define the decision before you compare
Write down what you need to settle. In the workshop example, the immediate decision is what time to print on the flyer. A second decision is when volunteers should arrive. Those questions could have different answers. A tool asked to find every inconsistency may spend its effort on minor wording changes and bury the handful of details that actually change what somebody does.
Give the documents short labels such as A and B. Alongside each label, note the date, version, author or owner, and whether the file is a draft or approved. Record what you know and leave unknown status blank. A file’s modification date can reflect a formatting edit. An effective date or approval record tells you more about when a change applies. When using an approved AI tool, share only the sections needed for the comparison. See our guide to redacting a document before sharing it with AI if the material includes names or details the task does not require.
Ask for evidence on both sides
Request one row per issue, with these fields: issue, what A says, where A says it, what B says, where B says it, and a question for the owner. Give the model categories to use: direct conflict, different scope, missing information, and possible version change. If page numbers are unavailable, have it use headings or paragraph labels that you can locate yourself.
Compare only these excerpts to help me decide what public start time belongs on the workshop flyer. For each difference, list the two claims separately and give each one a heading or paragraph label. Mark information absent from either excerpt as “not found in excerpt.” Flag anything that might refer to staff arrival or a different session. End with the questions I should ask the schedule owner. Leave the final time undecided.
Read the proposed evidence before relying on the rows. A reference can point to the right page while the claim misses an exception in the next sentence. NIST’s Generative AI Profile identifies confabulation as a risk and recommends verifying sources and citations in generated outputs during assessment and monitoring. At the document level, the practical equivalent is opening both originals and checking each material row in context.
Separate real disagreements from differences in scope
Suppose A says “Doors open at 9:00” and B says “Workshop begins at 10:00.” Both statements may be accurate. A useful row would ask whether the flyer should advertise doors opening, the start of the session, or both. Now suppose A says “Public workshop starts at 9:00” and B says “Public workshop starts at 10:00,” with both referring to the same event and time zone. That row needs an owner’s decision.
Look for quiet differences that can change the outcome: a draft versus an approved copy, a time zone that appears only in a header, a capacity limit that applies to one room, or a date written in two regional formats. Treat a blank cell as unknown until you check the surrounding text or the missing attachment. An empty field on a comparison worksheet says something about the material you inspected. It cannot tell you whether another document contains the answer.
Record the ruling and update the places people use
Send the schedule owner one focused question with the two passages attached. Ask them to identify the applicable version and confirm whether both times belong on the flyer. Once they reply, record the confirmed wording, source, person responsible, and date. If the ruling affects a decision with downstream consequences, use a decision log so a colleague can see why the wording changed later.
Then check the places that repeat the information. For the workshop, that could be the event page, flyer, and volunteer email. Assign each update to someone and leave unresolved items visible. If the venue confirms the start time but has yet to confirm when doors open, write “start time confirmed, doors opening pending” in the handoff. Only release wording the owner has approved.
For a recurring workflow, save one reviewed comparison as a reference example. Include a genuine conflict, a difference in scope, and an omission. When you reuse the prompt, check whether it still captures all three and whether the source references remain easy to find. A short, traceable list of disagreements gives the next person something they can verify and act on.
