Choose the Correct Source File for a Book Revision

Choose a revision baseline by examining the content and history of candidate files, not only their names or modification dates. Identify which file contains the approved text and accepted corrections, then reconcile missing changes deliberately. Preserve the alternatives while you investigate. The selected source should explain how it relates to the published or last-approved edition and be capable of producing the next controlled revision.

Collect candidates without overwriting them

Gather the plausible source files, relevant exports, and editorial correction records into a review inventory. Keep their original names and locations recorded before making working copies. A document called final may predate a proof correction, while a later copy may contain an abandoned experiment. Do not resolve that ambiguity by deleting older-looking files or saving one candidate over another before the differences have been examined.

Record what each candidate is believed to represent and the evidence supporting that belief. An email attachment may be the version sent to an editor; a local file may include later accepted changes; a PDF may show what was actually approved for production. These artifacts can all be useful without any one of them being the complete editable baseline. The inventory should preserve those distinct roles rather than force an immediate winner.

Compare meaningful content checkpoints

Choose passages and features that distinguish the known revisions. These might include a corrected chapter ending, a renamed character, an updated table, or the final back-matter wording. Compare those checkpoints across candidates and record which versions contain them. This gives you stronger evidence than a timestamp alone, especially when files have been copied between devices or exported under reused names.

Expand the comparison when the checkpoints reveal disagreement. A file containing the newest ending may still lack earlier copyediting corrections elsewhere. Avoid selecting it as authoritative solely because it passes one memorable test. Use available document comparison tools within their limits and read important differences in context. The aim is to establish the actual state of the manuscript, including missing accepted edits and unapproved material that should not enter the revision baseline.

Reconcile accepted changes through an explicit decision record

Create a list of differences that require a decision. For each one, identify the competing wording, the relevant editorial note, and the author's accepted outcome. If the record is incomplete, mark the decision unresolved and review it rather than guessing that the newest text must be correct. Keep creative alternatives separate from mechanical corrections so the reconciliation does not accidentally settle story questions by file chronology.

Apply the approved decisions to a designated working baseline while preserving the original candidates. Record where each incorporated correction came from. This is especially important when one editor's returned file and the author's later draft contain different sets of changes. A careful merge is an editorial task, not merely an exercise in choosing the longest document or copying every visible difference into one increasingly inconsistent manuscript.

Test whether the source can reproduce the intended book

Inspect the chosen source's structure, linked assets, styles, notes, and other dependencies. A document can contain the right prose while lacking the images or formatting information needed for the next export. Identify which missing elements can be recovered and which need rebuilding. Compare the source with the relevant approved export to understand those gaps without assuming that every visual difference is an error in the text.

Create a test export if the workflow supports it and examine representative passages and unusual elements. Keep format-specific differences explicit. The goal is not necessarily to reproduce every accidental feature of an old file, but to establish a usable source that reflects the approved content and understood design decisions. Before a new submission, the revised package will still need current KDP checks rather than relying on the age or prior use of the recovered source.

Freeze the baseline before starting new revisions

Save the reconciled source as a clearly identified checkpoint with the decision record and required assets. State what it includes, how it relates to the previous edition or approval, and which issues remain for the new revision project. Only then begin the planned content changes. Mixing recovery and new creative work without a boundary makes it harder to tell whether a difference was restored from history or newly introduced.

Preserve the candidate inventory and superseded files in an archive outside the active delivery set. Future questions about an old correction can then be answered without reopening every file as a possible current master. The successful outcome is a defensible starting point for revision, not merely a file renamed final. That baseline makes later editing, export review, and publication handoff more reliable because everyone can identify what the new work began from.