Include project archiving as a defined production task with its own scope and estimated effort. Preserve the files and records needed to revise the book later, verify that the package can be opened, and identify any ongoing storage or access costs. Keep this work separate from printing cost and avoid assuming that a folder of final PDFs constitutes a reusable project archive.
Define the future task the archive must support
Decide what a future editor should be able to do with the retained project. Correcting a typo, rebuilding an illustrated layout, and creating another format require different source files and records. The budget should reflect the intended capability rather than an undefined instruction to save everything.
Write a short acceptance description. For example, a future editor should be able to locate the accepted manuscript, identify the cover specifications, and trace an illustration to its source and usage record. This gives the archiving work a finish condition that can be checked before the production team disperses.
Inventory more than the release exports
List the editable manuscript, layout sources, images, fonts or font references, accepted exports, source notes, and relevant decision records. Identify which items are held by collaborators and which already exist in the project workspace. Gathering missing dependencies can take time even when the published files are complete.
Separate essential revision material from disposable trials and duplicates. Keeping every intermediate file without explanation can make the archive harder to use. Preserve important alternatives where their history matters, but label them so a later editor does not mistake a rejected cover or obsolete manuscript for the accepted version.
Estimate preparation and verification work
Include time to organize the files, write a concise inventory, resolve unclear names, and check that important links or dependencies remain usable. This is different from simply copying a folder. The effort depends on how consistently the project was maintained during production.
Test a representative reopening task before treating the archive as complete. Open the editable manuscript and a layout file in the intended environment, and confirm that the expected assets can be found. Record any software dependency or unresolved issue rather than assuming a successful file transfer proves future editability.
Separate one-time work from continuing access
Record the one-time cost or time allowance for preparing the archive. List ongoing storage, software access, or maintenance separately where the project actually requires them. Use the terms of the selected services rather than assuming that a current account or license will remain available indefinitely.
Do not automatically assign every continuing tool subscription to this one book. Explain the allocation when an account supports several projects. Equally, do not hide a necessary recurring expense merely because it occurs after publication; the planning record should make the continuing obligation visible.
Keep the break-even question consistent
State which production expenses the project's break-even estimate is intended to recover. If archive preparation is part of that scope, include it once and distinguish paid work from any separately tracked value of the author's time. Avoid adding the same collaborator invoice under both editorial handoff and archive preparation.
Keep per-copy production economics separate from the archive total. Use the actual intended edition and current KDP calculation when estimating the contribution from a print sale. The archive expense belongs to the project plan, while printing costs and applicable royalty terms determine the contribution assumed for each relevant sale.
Close the task with a usable inventory
Save an inventory that identifies the accepted files, the location of supporting records, and the date the reopening check was performed. Note who maintains access and which later changes should create a new archive version. This prevents the archive from becoming obsolete as soon as a corrected edition is prepared.
Compare the actual archiving effort with the estimate and retain the lesson for future books. If unclear source records caused most of the work, improve their maintenance during the next project. A modest planned closeout task can be more useful than an apparently complete archive that a future editor must spend hours reconstructing.
Frequently asked questions
Clear answers for this publishing decision.
Is saving the final PDF enough?
It may preserve the release artifact, but it usually does not preserve every capability needed for later editing. Define the intended future work and retain the sources required for it.
Should I keep every draft?
Keep the history needed to understand important decisions and recover useful work. Organize or exclude routine duplicates so they do not obscure the accepted edition.
Does archiving change the printing cost of each copy?
Archive preparation is a project expense. Keep it separate from the edition's per-copy printing calculation and explain how it enters your chosen cost-recovery plan.
When should I verify the archive?
Verify it before production access or collaborator availability changes, and update the record when later revisions alter the accepted files or dependencies.
What does this book cost to print and produce, and what should the list price be?
Printing cost follows from the trim, ink, and page count, the list price sets the royalty after that cost, and the production budget should be estimated before generation starts, so compare these numbers before you commit to a format or a plan.
See what a book project costs in credits