How to find changes between two drafts for a change request

You have two versions of a document and a change request that says what should be different. The hard part is often not finding any difference, but deciding whether each change is requested, accidental, or still needs clarification.

Use Text Compare to check the drafts side by side and focus your review on changed text. Then match the differences against the request before you approve the revision or send it back.

Compare the two drafts

1. Open Text Compare. Keep the original draft and the revised draft open so you can confirm which is which.
2. Copy the complete text of the original into the first text area and the complete revised text into the second. Label them in your notes as “original” and “revised” so you do not reverse the comparison.
3. Review the comparison from the beginning. Look for text added, removed, or changed, and read a little before and after each marked difference.
4. Keep the change request nearby. For every difference, note whether it matches a requested change, is a necessary related edit, or is unexplained.
5. Check the final draft in its original document after reviewing the comparison. Confirm that headings, lists, and other formatting still look right before sending it on.

For a long draft, review one section at a time rather than trying to interpret every change as a single block. If the document has important formatting, copy plain text for the comparison, then use the original file to verify the layout.

What the differences mean

Text appears only in the revised draft

This is an addition. Check whether it supplies the requested information, such as a new deadline or an updated requirement. Confirm that the added wording does not introduce a promise, date, or condition that the request did not authorize.

Text appears only in the original draft

This is a deletion. It may be an intentional removal, but check that it does not remove a required warning, qualification, or piece of context. If the change request did not call for it, ask why it was removed before approving the draft.

Wording is different in both drafts

A replacement can look like a deletion followed by an addition. Read the whole sentence to see whether the meaning changed, not just the word choice. For example, changing “may” to “must” changes an option into a requirement.

A small change appears in many places

Repeated differences may come from a global edit, such as changing a product name or date. Check that every instance should change and that the revised text does not contain a mixture of old and new wording.

The comparison shows many changes you did not expect

First confirm that you compared the right files and included the full text in each side. If those are correct, the revised draft may contain other edits, formatting-related text changes, or a different version history. Do not treat a large number of differences as proof that the requested change was completed correctly.

How to resolve unclear changes

1. Check the source versions. Confirm the original is the version the request refers to and the revised draft is the one under review. Similar filenames can hide older or interim copies.
2. Compare the full document. Make sure you did not copy only the visible paragraph or miss text below the cursor. For a large document, work through it section by section and keep the section names with your notes.
3. Separate wording edits from formatting. A heading restyle or list change may create a difference without changing the intended meaning. Check the document itself before reporting that as a content change.
4. Match each difference to the request. Mark it as requested, related, or unexplained. If one edit affects another section, record the connection rather than assuming it was included in the request.
5. Ask about consequential edits. If a change affects a deadline, price, obligation, approval, or safety instruction and the request is not clear, pause and ask the requester. Do not guess based on what seems likely.
6. Save a review record. Keep the two version names, the date, and a short note about unresolved changes. Follow your organization’s rules for storing drafts, especially when they include confidential or personal information.

If you are comparing Markdown files, the same review approach applies: verify that both copies are the intended versions and read changed lines in context. See how to compare two Markdown document drafts for a format-specific workflow.

Make the comparison useful for approval

A text comparison shows what differs, but it cannot tell you whether a change is authorized, accurate, or legally appropriate. Treat it as a review aid, then check the request and the surrounding document. When you report a result, identify the section and describe the actual change, for example, “The revised draft adds a new response deadline in the support section.”

If you need to share the comparison, remove any sensitive material that the recipient does not need and use your approved document-sharing process. Keep the original draft unchanged so you can revisit the baseline if the request is revised.