Loading BoundHive

After reordering or renaming chapters, inspect running headers in the final print export, especially around section boundaries. Confirm that each header identifies the intended content and follows the book’s design consistently. Do not assume that a corrected chapter heading automatically updates every repeated header or imported section.

Establish the intended header pattern

Write down what the book’s running headers are meant to display. They may show the book title, author name, chapter title, or another deliberate navigation cue. Record any pages where headers are intentionally absent, such as particular opening pages. A clear pattern lets the reviewer distinguish a designed exception from a stale or missing element.

Keep the pattern tied to the actual manuscript and publication format. A header useful in a printed reference may have no equivalent role in another edition. Review the intended reader task rather than copying a template mechanically. If the design uses different content on left and right pages, specify that relationship explicitly so a single-page preview does not conceal an alternating error.

Identify which changes could leave stale text

Review the structural edits since the previous checked export: renamed chapters, moved sections, imported material, or changes to the book title and author text. These are likely places for running headers to retain an older value. Search the editable source where useful, but inspect the actual output as well. Some repeated elements may be controlled separately from the chapter text.

For example, a chapter moved from the middle to the beginning may display the correct heading while retaining the previous chapter’s name in its running header. The contents page can also be correct, making the error easy to miss during a general review. Treat the header as an independent navigation element that needs reconciliation with the page’s actual contents.

Symbolic publishing workflow for identify which changes could leave stale text
Identify which changes could leave stale text

Inspect boundaries and representative interior pages

Check the first pages after section breaks and several pages within each affected chapter. Include both page sides if the design alternates content. Confirm that intentionally suppressed headers appear only where intended and resume correctly afterward. A header can look right on the first inspected page while a separate setting creates a different result on the facing page.

Review front matter, appendices, and imported sections separately. They may follow another pattern or carry settings from an earlier document. Decide which differences are intentional and record them. Do not force every page into the same treatment simply to make the check easier; the goal is a consistent implementation of the book’s chosen design, including its justified exceptions.

Correct the source rather than individual output pages

Identify the setting, field, or source text responsible for an incorrect header using the editing application’s supported workflow. Consult its documentation when behavior is unclear. Avoid manually patching a few exported pages while leaving the source unchanged, because the next export can restore the error. Preserve the previous file until the correction has been verified.

After changing a shared header setting, inspect other sections that may inherit it. A repair intended for one chapter can alter neighboring chapters or change the left-right pattern. Keep the change scope visible and compare the resulting export with the intended pattern. The correction should be reproducible from the editable source, not dependent on an undocumented sequence of local adjustments.

Symbolic review checklist for correct the source rather than individual output pages
Correct the source rather than individual output pages

Review readability and the final navigation experience

Check that the running text remains legible, fits the available space, and does not crowd other page elements. Long chapter names may need a deliberate shortened form, but the result should still identify the content clearly. Review the relevant current formatting and margin guidance for the edition alongside the visual inspection. A technically placed header can still be confusing if its wording is ambiguous.

Save the checked export and header pattern with the publication checklist. Reopen affected checks after a final structural or naming change. Ask whether a reader opening the book at an arbitrary page receives the intended orientation cue. That practical test completes the purpose of running headers: they should help readers navigate the actual manuscript, not preserve a history of its earlier chapter order.

Frequently asked questions

Clear answers for this publishing decision.

Does updating the contents page also update running headers?

Do not assume so. The elements may use different source structures or settings. Inspect both in the final export and test the actual behavior of the editing workflow, especially after moving or renaming chapters.

Can I shorten a long chapter title in the header?

Use a deliberate, recognizable form that remains consistent with the book’s design and applicable requirements. Record the choice so later edits do not treat it as an accidental mismatch. Check that the shortened wording still helps the reader identify the chapter.

Should headers appear on every page?

Follow the intended design and relevant publication guidance. Some pages may deliberately omit them. The review should establish that omissions and resumptions are intentional and consistent rather than impose an unexplained universal pattern.

Format and interior

Which trim size, page count, margins, and bleed setting work together for my paperback?

Check the complete combination first: a trim size, ink and paper type, and page count must be a supported KDP set, and the page count then fixes the minimum inside margin and whether the interior needs a bleed page size.

Set the format in a book project

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

We could not save your subscription.