When merging drafts, preserve the creation history of material that enters the accepted manuscript. Identify each source version, record which passages or assets were retained, and keep unresolved origins visible until checked. A new combined file does not make all of its contents share the same origin.
Identify the drafts before comparing their prose
Start by naming the exact versions being combined and describing how each was created. One draft may contain the author's original text with editorial assistance, while another may include generated alternatives. A generic label such as revised manuscript does not explain that difference. Preserve the source copies before editing so later questions can be traced to actual material.
The same principle applies when the drafts come from different contributors. Ask what content was created, what was edited, and which assets were added during each stage. Keep the account specific enough to identify the retained material. The purpose is not to reconstruct every keystroke; it is to maintain an understandable relationship between the accepted book and the work from which it was assembled.
Track accepted material at a useful level of detail
Use the smallest practical unit that keeps the merge understandable. For some chapters, the author can record that the whole chapter came from one source version. For a heavily combined section, paragraph or passage identifiers may be more useful. Do not label a mixed chapter solely by the origin of its opening paragraph or the identity of the person who performed the merge.
Imagine an author retaining an original explanation from Draft A and adding a generated example from Draft B. The combined section now contains both histories. Record the example's source beside the decision to retain it. This provides a clearer basis for later publication review than assigning one broad label to the entire file and discarding the evidence of how its parts were created.
Separate a new edit from a change in creation history
KDP distinguishes content generated by an AI tool from an author's own content edited or refined with AI assistance. Its guidance states that substantial editing does not remove generated status from content created by the tool. Apply the current guidance to the actual history rather than inferring origin from the polish of the final prose.
During a merge, an editor may shorten a generated passage, combine it with an original introduction, or replace some of its wording. Record those changes without treating the editing action as proof that the earlier generation no longer matters. If the project genuinely replaces material with a separately created passage, preserve evidence of that replacement rather than making a broad assumption from the amount of revision.
Include images, captions, and translations in the review
A manuscript merge can move more than body text. It may bring in a generated illustration, a translated passage, or a caption copied from an alternative draft. Track these elements explicitly so their histories do not disappear behind the chapter's general record. Check that each accepted asset corresponds to the version actually included in the final layout.
For example, Draft B may contain a revised caption for an illustration still taken from Draft A. The caption and image can have different source records. Keeping them linked in the production register helps the author review both accurately. A new filename or a change of placement does not explain where the content came from, so avoid relying on those details as substitutes for the creation record.
Resolve unknowns without guessing from style
When a passage's origin is uncertain, mark the question and investigate the available draft history, contributor notes, or saved outputs. Do not decide that text is human-written because it sounds distinctive or generated because it sounds generic. Style is not a reliable record of the actual process used to create a passage.
Keep unresolved material separate from completed origin review. The author can request clarification from the contributor or reconsider whether the passage should remain in the release. If replacing it, document the new work and remove the superseded material from the accepted manuscript. The record should show what is known and what remains uncertain, rather than hiding a gap behind a convenient label.
Reconcile the record with the final merged export
After the merge is accepted, compare the content-origin register with the assembled manuscript. Confirm that discarded alternatives are not counted as retained material and that accepted additions have not been omitted from the record. This final comparison matters because the merge plan may differ from the decisions made during close editing.
Save the accepted source versions, merge decisions, and final file together in the release record. Consult the current KDP questions and guidance when preparing the publication information. A well-maintained merge history makes that review more reliable and makes later revisions easier to understand. The author can explain how the book was assembled without assuming that one final document has only one kind of origin.
Frequently asked questions
Clear answers for this publishing decision.
Can I label the whole merged draft by the person who edited it?
That does not necessarily describe how its retained content was created. Keep the relevant origins of passages and assets, especially where the combined draft contains different histories.
Does heavy editing automatically turn generated text into assisted text?
No. KDP’s current guidance retains the generated distinction for content created by an AI tool even after substantial editing. Review the actual process and preserve supporting records.
What should I do with a passage whose origin is unknown?
Mark the uncertainty, inspect the available history, and seek clarification from its source. Do not infer origin from writing style or silently treat the gap as resolved.
How do I get from an idea and a brief to an editable manuscript I can finish?
Write the brief first, generate a structure you can edit, then draft and revise the manuscript in reviewable sections so one change never overwrites work you already approved.
Start a book project from a brief