Before exporting the final book, review the front and back matter as part of the current manuscript. Confirm that introductory promises, contents entries, acknowledgments, appendices, and resource instructions still match the accepted chapters. These sections often change less frequently than the main text, which makes them easy places for abandoned plans to survive.
Compare the introduction with the finished book
Read the introduction after the substantive chapters have reached their accepted state. Identify what it says readers will learn, create, or receive. Compare those statements with the material that remains in the book. An early introduction may promise a later chapter, a particular sequence, or a resource that was removed during revision. Update the promise rather than assuming readers will understand why it was never fulfilled.
Pay attention to instructions about how to use the book. If the manuscript now supports selective reference reading, an opening that insists every chapter must be completed in order may be misleading. If later exercises depend on earlier outputs, the opposite instruction can also cause trouble. Describe the actual reading path and prerequisites using the structure that will be exported.
Recheck contents and section labels
Verify that the contents entries reflect the accepted headings and order. Depending on the production workflow, some entries may update automatically while others were typed manually. Inspect the actual result rather than assuming that a refresh command covered everything. Appendices, introductory sections, and back-matter resources can be omitted or mislabeled even when the main chapter list is correct.
Use consistent names when the body refers to a supporting section. If a chapter directs readers to a resource checklist, the back matter should not call the same item an equipment appendix without making the relationship clear. Search for the earlier names as well as the current ones. A renamed section can leave references that are technically readable but difficult for a new reader to follow.
Review supporting claims and acknowledgments
Inspect author information and acknowledgments for statements that no longer describe the project accurately. A contributor may have reviewed an early draft rather than the final edition, or an introductory note may describe a production approach that changed. Use precise wording and confirm the intended credit with the relevant records. Do not allow a general expression of thanks to imply a specific endorsement or review that did not occur.
Keep factual and permission-related questions visible for the appropriate reviewer. This check does not determine every publication-rights issue, but it can identify claims or included material whose treatment remains unresolved. Compare names and credit wording across the manuscript and cover where they appear. Correct inconsistencies in the source files so the next export does not restore an outdated version.
Follow every resource instruction as a reader
Test the directions for accessing any supporting material using the wording that will appear in the book. Confirm the destination and whether it contains the promised resource. If the instructions depend on a link, code, or named page, check that the reader can distinguish the intended destination from a draft or obsolete location. A working address is not enough if the resource itself is missing.
Review the book’s dependence on that material. An optional reference page creates a different expectation from a required worksheet needed to complete a central exercise. Make that relationship clear and decide how the publication remains useful if an external resource changes. Remove unfinished-resource promises or complete the underlying work before treating the back matter as ready for release.
Inspect the supporting sections in the exported file
After updating the source, inspect the front and back matter in the intended output. Check the reading order, headings, navigation where applicable, and the placement of blank or separator pages. These sections can use different styles from the body, so they may reveal export problems that a sample chapter does not. Follow the current preparation guidance for the actual format you intend to publish.
Record the reviewed output version and any remaining issues with the release package. If a later body revision changes a promise, section name, or resource dependency, reopen the affected supporting section. Front and back matter are part of the book’s instructions and identity, not a static wrapper around the chapters. Keeping them synchronized helps readers understand what they have purchased and how to use it.
Frequently asked questions
Clear answers for this publishing decision.
Should the introduction be written last?
It can be drafted early, but review it against the accepted manuscript before export. The final check matters more than the drafting order because the book’s scope and structure may change during revision.
Is an automatically generated contents page enough?
Inspect the result. Automatic entries can still reflect incorrect heading styles, omit supporting sections, or preserve labels that no longer match the references in the text.
What if a back-matter resource will be finished after publication?
Complete it before release if the book promises it, remove or revise the promise, or reconsider the publication timing. An intention to add the resource later does not fulfill the current reader expectation.
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