After combining manuscript files, compare the complete export with a written sequence of sections and page boundaries. Check every join for missing, repeated, reversed, or misplaced pages, then review pagination and navigation in the final assembled artifact.
Define the intended sequence before the merge
A book assembled from separate chapter exports needs a clear order that does not depend on how files happen to sort in a folder. Front matter, main chapters, appendices, and end matter may use different naming conventions. Write the intended sequence using recognizable section titles and the specific versions that belong in the release.
Include any deliberate blank or separator pages in that sequence. Otherwise, a reviewer may remove a planned page or assume that an accidental gap serves a purpose. The sequence should describe the reading experience the author intends, while the file list identifies the material used to build it. Keep those two records connected but distinct.
Check the start and end of each source section
Before assembly, inspect the first and last content page of every source file. Confirm that the chapter begins at the intended heading and ends after its complete final paragraph, table, or exercise. A filename cannot reveal that an export accidentally omitted the last page or retained a previous chapter's ending.
Record a short boundary cue for each section, such as its opening heading and final topic. These cues make the merged file easier to inspect without rereading every word during the ordering check. They do not replace the substantive edit; they establish that the approved components are present in the intended order.
Inspect every join in the assembled file
Move through the merged manuscript one boundary at a time. Compare the final page of the preceding section with the first page of the next. Look for repeated title pages, missing continuation pages, and duplicated paragraphs that appear when two exports contain overlapping material. Confirm that a section has not been inserted twice under different filenames.
A page-count total is useful but insufficient. One missing page and one duplicate page can cancel each other numerically. Use the boundary cues and section sequence to verify identity as well as quantity. Where the manuscript contains long tables or multi-page illustrations, inspect the join closely enough to confirm that the content remains complete.
Review pagination after the sequence is correct
Once the content order is established, check the numbering scheme in the assembled artifact. Distinguish the file's page position from the page number printed on the page. Front matter and deliberate blank pages can make those values differ, and a reviewer needs to know which reference a correction uses.
Consult KDP's current paperback submission guidance for pagination and file preparation. Its requirements include attention to missing pages and sequential numbering, but a mechanically plausible sequence still needs editorial review. Confirm that chapter references, contents entries, and any index entries point to the intended content after assembly and any subsequent layout changes.
Check sections that look similar
Repeated exercise pages, recurring chapter openers, and standardized appendices are especially easy to confuse. Compare their identifying details rather than relying on appearance. A worksheet for week four can look almost identical to the worksheet for week five while asking for a different activity or using a different example.
Use the manuscript's own labels to distinguish these sections. If those labels are absent or ambiguous, improve the source before the final export where practical. An internal file-order checklist can prevent an assembly error, but readers also benefit from knowing which section they are using once the book is printed or opened digitally.
Reassemble from approved sources after a correction
When a source chapter changes, update the assembly record and rebuild using the approved components. Avoid an undocumented patch that leaves one corrected page among several older versions without a clear explanation of its origin. If a page-level replacement is part of the workflow, record exactly what changed and inspect both adjoining boundaries again.
Save the checked assembled file with its version and sequence record. The upload handoff should identify that artifact, not merely the folder containing its components. Complete the platform preview review using the same file so the final check confirms the actual book being submitted, including its first page, last page, and every section between them.
Frequently asked questions
Clear answers for this publishing decision.
Can matching the expected page count prove the merge is correct?
No. Missing and duplicate pages can produce the same total. Check the identity and order of sections, especially their beginnings, endings, and joins.
Should deliberate blank pages be listed in the assembly plan?
Yes. Record their purpose and position so reviewers can distinguish them from accidental gaps. Verify their effect on the final reading order and pagination.
What needs checking after replacing one page?
Confirm that the replacement belongs to the intended revision and inspect the pages immediately before and after it. Recheck any numbering or references affected by the change.
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