Loading BoundHive

Prepare a First Paperback’s Pre-Export Input Sheet

Before exporting a first paperback, collect the inputs that define the intended file in one reviewable sheet. Identify the accepted manuscript, relevant production choices, included assets, and current official requirements. Resolve missing or contradictory values before running the export. The sheet does not approve the resulting file; it establishes what the export is supposed to produce so later checks have a clear basis.

Identify the accepted manuscript and its content boundaries

Record the manuscript version selected for production and distinguish it from research notes, alternate chapters, and review copies. Confirm that front matter, main text, and back matter intended for the edition are included. A source folder can contain everything the project needs while the actual export document omits an accepted section. The input sheet should identify the assembled source, not merely the location of miscellaneous files.

List unresolved content decisions that could affect production. A planned appendix, missing illustration, or pending chapter replacement can change the package later. Decide whether each belongs in the current release or a future revision. Do not fill uncertain fields with convenient guesses to make the sheet look complete. The purpose is to expose decisions needed before export, while preserving the work already accepted.

Record the intended production configuration

Write down the relevant paperback choices and verify them against current KDP guidance for the actual book. Keep author preferences separate from confirmed available options. An early layout sample may use provisional dimensions or presentation choices that were never approved for final production. Identify those assumptions before they become settings in an export template.

Give every value enough context to be interpreted correctly. A number without a unit or a page-count estimate without a manuscript version can cause avoidable confusion. Where the final value depends on layout, mark that dependency explicitly rather than treating the estimate as a finished specification. The sheet should support a controlled transition from manuscript to reviewed file, including decisions that must be finalized after pagination.

Symbolic publishing workflow for record the intended production configuration
Record the intended production configuration

Connect images and special elements to accepted sources

List the illustrations, tables, and other elements that require particular attention during export. Identify their accepted versions and intended locations. Distinguish final assets from placeholders and rejected variants. A file with a familiar name can be an earlier draft, so use reliable identifiers and inspect its relationship to the manuscript where necessary.

Record the checks relevant to each special element without claiming that a source-file property alone proves reader usability. An image can have ample source detail while its labels become too small at the intended placement. A table can be present yet difficult to follow. These become explicit output-review questions, informed by the inputs and the role each element plays in the book.

Attach current requirement evidence to changing assumptions

Keep official source references and review dates for the platform-dependent choices being used. Note the relevant format and scope of the guidance. A source about one kind of output should not silently support a different production decision. If the information is incomplete or unclear for the project, identify the exact question requiring clarification rather than substituting an undocumented rule from an old checklist.

Keep content-origin and supporting review records available alongside the production sheet where relevant. They answer different questions from geometry or file preparation, but they remain part of a responsible publication workflow. The sheet can point to those records without pretending to summarize every editorial and rights decision in a single status. Clear references preserve scope and make later review more efficient.

Symbolic review checklist for attach current requirement evidence to changing assumptions
Attach current requirement evidence to changing assumptions

Use the sheet to inspect the first export

Generate the candidate file from the identified inputs and record its version. Compare the result with the sheet: confirm content completeness, accepted assets, intended configuration, and the special elements requiring visual review. Inspect the actual output under the applicable current requirements. The first export is evidence to examine, not a finished product merely because the process completed successfully.

If a correction changes an input, update the sheet and record the reason before exporting again. Preserve the relationship between source, configuration, and result. This gives the author a reproducible production baseline for a first paperback and reduces confusion during later corrections. Final approval still requires review of the actual file and its coordinated cover and metadata package, but the input sheet makes that review concrete.

Frequently asked questions

Clear answers for this publishing decision.

Does a complete input sheet approve the exported paperback?

No. It defines the intended result and its evidence. Inspect the actual export for completeness, readability, and applicable requirements before approving the file.

How should provisional values be recorded?

Label them as estimates or unresolved dependencies and identify what will establish the final value. Do not silently treat a layout sample assumption as an accepted production choice.

What should change after an export correction?

Update any affected source or configuration entries, preserve the reason, and connect the new export to those inputs so the result remains reproducible and reviewable.

Get all of our updates directly to your inbox.
Sign up for our newsletter.

We could not save your subscription.