How to edit AI generated content: compare the draft with the final version

For AI content workflow, the first decision is whether one small example can be reviewed by a person. How to edit AI generated content becomes a harder question when the first draft has been overwritten. Preserve the original in a document with version history, save the final text separately, and compare matching passages. Use a free document account if its available history supports this task. Mark factual corrections, tone changes, and deletions in a before-and-after table, with a reason for each substantive edit.

Preserve: Save identifiable original and final versions.
Compare: Match passages and label what changed.
Explain: Record the evidence or editorial reason behind each change.

This playbook provides a comparison procedure and a copyable artifact. It does not report a completed product test or a measured editing result.

What the evidence supports

The supplied facts establish the preparation date. They do not contain document snapshots, an editing trial, or verified feature availability for a particular free account.

Evidence item	Date or status	Conditions and scope
Preparation date	2026-09-05	Date supplied for this article’s generation
Reviewed date	No independent source-review date supplied	Current document features have not been verified
Tested date	No test date supplied	No hands-on comparison is claimed
Required conditions	To be checked before use	Access to the original draft, final text, and readable version history
Example evidence	Illustrative only	The comparison below demonstrates annotation, not observed results

That boundary matters. A proposed method is not a test receipt. Your saved passages, change labels, and supporting sources become the receipts when you apply it.

The free route is conditional: check whether your existing document account exposes the history you need without an upgrade. If it does not, retain separate draft and final documents and compare them manually.

Preserve the draft before editing starts

Paste the first AI draft into your document and let it save before changing the wording. Where version naming is available, give that saved state a clear label such as Original draft. Otherwise, keep a separate copy with that label.

Check that the preserved text opens correctly. A label alone does not establish that the whole draft was captured.

Edit the working document, then preserve the accepted text as Final reviewed version. Avoid treating the most recent automatic save as the final version unless someone has actually accepted it.

Version history is useful for finding earlier wording. It is not, by itself, an explanation of editorial judgment. A highlighted replacement might fix an error, soften an unsupported claim, or merely change punctuation.

If several people or automated processes touched the document, describe the result as changes between versions unless you have reliable evidence of who made each change. An account name beside a revision does not necessarily establish human authorship.

Version history preserves wording; the comparison table records why it changed.

Build the before-and-after comparison

Open the original and final versions in separate views if your document supports that arrangement. Otherwise, put their text in separate documents. Work through matching sections and copy short, exact passages into the table.

Use the sentence or paragraph containing the meaningful change as your comparison unit. Tiny fragments can hide context; whole sections can bury the edit.

The following example is invented. It concerns a fictional convenience-store offers guide. The wording and supporting materials are placeholders, not verified product claims.

Location	Before: illustrative draft	After: illustrative final	Edit label	Reason or evidence to record
Availability	“Every branch accepts this offer.”	“Check whether your branch accepts this offer.”	Factual claim correction	Record the dated offer terms that establish branch restrictions; without them, mark availability unresolved
Opening	“Unlock incredible savings with this powerful guide.”	“Check the offer conditions before shopping.”	Tone change	Replace promotional language with a concrete reader action
Closing	“Remember to check the offer conditions.”	Deleted	Deletion	The instruction already appears in the opening; record that retained location
Redemption	“Show the offer when paying.”	“Check the redemption instructions before paying.”	Factual qualification	Record whether the original instruction lacked support and whether the final wording still needs verification

Comparison caption: Original and final passages shown beside edit labels and the evidence or editorial reason needed to justify each change.

Keep the labels specific:

• Factual correction: Changes a claim because supporting evidence contradicts it.
• Tone change: Changes delivery while preserving the underlying meaning.
• Deletion: Removes text; the reason might be repetition, irrelevance, or an unsupported claim.
• Factual qualification: Narrows a claim or makes uncertainty explicit.

A deletion can also remove a factual error. Give it both labels when necessary. Do not classify it as harmless shortening if it changes what the reader understands.

For a new passage, write Absent from original in the before column. For moved text, record the destination so it is not mistaken for a deletion.

Make the comparison reproducible

Copy this checklist into the review document. Replace bracketed fields with your own record.

Document: [non-identifying title]
Original version: [label and document timestamp]
Final version: [label and document timestamp]
Review date: [actual date]
Comparison scope: [whole document or named sections]

[ ] Original and final text are preserved and readable.
[ ] Each row contains exact wording from the saved versions.
[ ] Matching passages have been checked in context.
[ ] Factual corrections include a supporting source and source date.
[ ] Tone changes preserve the intended meaning.
[ ] Deletions include a reason.
[ ] Added or moved passages are identified.
[ ] Mixed changes carry the relevant labels.
[ ] Unresolved claims remain marked.
[ ] Shared evidence excludes private or identifying details.

Decision: [ready / revise / hold]
Unresolved items: [claim, missing evidence, required action]

Read each completed row against the saved versions. Then read the final document continuously. A passage can look reasonable in isolation while contradicting a statement elsewhere.

To answer “how much did a person change?”, start with the scope and substance of the edits. Distinguish corrections affecting accuracy from changes affecting voice. Do not turn a visual impression into a percentage of human contribution.

A small factual correction can matter more than a rewritten paragraph.

Keep model news separate from editing evidence

A changed draft does not establish that a model changed. Different source material, instructions, or editorial choices could also explain different wording.

If a recent model change is relevant, require a dated official announcement, release note, or documentation update. Record the publication or update date, the exact claim supported, and any stated availability conditions.

A retrieval date is not a release date. A search excerpt or community discussion is not a substitute for the original source.

No usable dated official model-change evidence is supplied here, so this playbook makes no claim about a recent release. Keep that question separate from the document comparison unless verified evidence connects them.

Know what can fail, then decide

These are possible failure modes, not reported test results.

History may not preserve the untouched draft if editing began before a distinct version was saved. Imported text may arrive without its earlier history. A document may expose broad snapshots without enough detail to identify every intermediate change.

When that happens, narrow the claim. You may still compare preserved endpoints, but you cannot reconstruct missing revisions reliably.

The comparison also cannot prove that the final text is correct. That requires checking claims against evidence. Nor can a revision record reliably divide authorship into human and AI shares when attribution is incomplete.

Final decision: Use a free document’s available version history to recover and preserve the endpoints, then use the annotated table to explain substantive edits. If the original is missing, label the comparison incomplete. If a factual correction lacks support, keep it unresolved.

Related build logs

• The First AI Agent Use Case Should Produce a Reviewable Draft
• Your First Content Repurposing Approval Workflow: When to Stop