Before releasing a book, reconcile title and subtitle variants against one approved identity record. Compare the actual manuscript, cover export, metadata fields, and related descriptive copy. Resolve differences deliberately instead of choosing whichever version appears most recently in a folder. A late subtitle edit can leave several individually polished files describing different versions of the book.
Establish the approved wording and its reason
Collect the candidate title and subtitle forms and identify the decision that approved the intended version. Record the exact wording, author identity, and edition context. If no clear approval exists, resolve the choice using the manuscript and the book's intended audience before correcting files. A filename timestamp cannot establish that a wording change was reviewed or that it still represents the finished content.
For a practical guide to family interviews, a subtitle may have shifted from a broad promise about preserving a complete family history to a narrower promise about preparing meaningful conversations. That is more than a punctuation change. Explain which promise the manuscript supports and preserve the decision. The approved identity record should contain enough context to prevent an older, more expansive claim from returning during a later design revision.
Find variants in the actual release materials
Inspect the title page, cover source, final cover export, metadata draft, description, and other relevant public copy. Search for distinctive words from earlier variants as well as the final wording. A superseded subtitle may survive in a back-cover paragraph even after it has been removed from the front. Record each occurrence with its file or field location so the correction can be checked directly.
Keep historical files distinguishable from candidates for release. An old version in an archive is not the same problem as an old export in the final upload folder. Preserve history where useful while ensuring the package intended for submission is unambiguous. The inventory should show which files require correction and which merely document an earlier decision that no longer applies.
Distinguish visual presentation from wording changes
Review differences carefully before applying a global replacement. Line breaks and visual hierarchy can vary between a cover and a metadata form without changing the underlying words. A changed noun, omitted qualifier, or added audience label can alter the meaning. Classify those cases rather than treating every visible difference as either harmless design or a mandatory literal layout match.
Consult current KDP metadata guidance for the applicable identity fields and their relationship to the cover. Keep platform requirements separate from project style preferences, while satisfying both where they apply. If a designer proposes a shorter display version, evaluate it deliberately under the current guidance and the reader's understanding. Do not allow a visual convenience to become an unreviewed second title that conflicts with the submitted book details.
Recheck the claims surrounding the approved identity
Read the description and category rationale after the title and subtitle are settled. They should reinforce the same subject, audience, and level. A narrower subtitle does not fix a description that still promises advanced instruction removed from the manuscript. Identify those dependent claims and revise them against the actual book rather than mechanically inserting the final title everywhere.
Check any series context or edition wording relevant to the project. Preserve accurate relationships without allowing one book's identity to drift into another's metadata. If the change affects an already published edition, verify the current editing options before applying it. The editorial review determines the accurate desired wording; the publishing workflow determines how the change can be carried out for the actual record.
Approve the exact package selected for release
After corrections, open the final exports and inspect the identified locations again. Confirm that the upload candidates use the reviewed wording and that the metadata record belongs to the same package. Do not infer success solely from a corrected design source or a completed search-and-replace operation. The actual files and fields are the evidence that the reconciliation worked.
Save the identity record, changed-location list, and accepted version identifiers together. When later revisions propose a new subtitle, the author can see which files and claims depend on it. This reduces the chance of repeating the same mismatch and makes future changes easier to review. A consistent release package gives readers a clear description of the book while preserving an accountable history of how its public identity was chosen.
Frequently asked questions
Clear answers for this publishing decision.
Should I select the subtitle from the newest file automatically?
No. Find the approved decision and compare the wording with the completed manuscript. A recent file can still contain an unreviewed or unsupported variation.
Are different line breaks always a title mismatch?
Not necessarily. Distinguish visual arrangement from changes in actual wording or meaning, and review the applicable current metadata guidance for the intended edition.
What proves that the variants have been reconciled?
Inspect the actual final exports and submission fields against the approved identity record, then preserve the accepted file identifiers and corrected locations.
What should the title, subtitle, description, and keywords look like before I upload?
Check the mechanical limits first, then make sure title, subtitle, categories, and description describe the same book for the same reader; a keyword is useful when it matches how that reader searches, not because it is popular.
Draft the listing fields in a book project