Keep running headers and page labels tied to the right section

Map section roles before changing visible text

Microsoft’s Link to previous guidance, checked 7 November 2026, describes separate links for corresponding header and footer types. Its page-numbering guidance uses section breaks and permits a section’s numbering format and start to be set. These are scoped Word capabilities, not a claim that a page break creates a new section or that every publishing tool uses the same model.

Outline the document’s semantic parts: opening material, main argument, appendices and any independently titled insert. Decide what running title and page-label sequence each part should present. Keep the audience-facing decision separate from the existing file structure; a copied template may have inherited boundaries that no longer match the content. Identify who approves the document’s navigation conventions before changing them.

Create a section-by-type inheritance map

Give each actual section a stable worksheet label and record where it begins in the current file. For every relevant first-page, odd-page and even-page header or footer, record the intended content, whether it is independent or inherited, and the predecessor it depends on. Keep header and footer rows distinct. A single checkbox labeled section fixed is not enough to explain which running elements will follow an earlier edit.

Add the page-label sequence beside the map without confusing it with the physical position in the exported file. A contents page can refer to a visible label that differs from the viewer’s file-page count. Note the intended restart or continuation and any deliberately absent label. Do not type a sequence of numbers manually to imitate the desired appearance; that hides the structure the reviewer needs to accept.

Use insertion and title changes as structural tests

In a recoverable synthetic copy, specify a short insertion near the end of one section and a changed running title in another. Ask the operator to supply the resulting preview. Compare which running elements change, which remain independent and how the opening page of the next section is treated. A correctly isolated appendix should not acquire the main chapter’s title merely because an upstream edit added a page.

Inspect both ordinary and special page types after the change. A clean middle page says little about the first page, and a single facing pair may miss the next boundary. If an unexpected title appears, identify the exact row and predecessor in the map rather than replacing the visible text repeatedly. Keep the test insertion distinct from a proposed editorial change so nobody accidentally approves new substantive content through a formatting fixture.

Verify the export against the section contract

Request the final exported document and compare the section openings, transitions and visible page labels with the accepted map. Check any contents references that use those labels. Export acceptance is a separate observation from the editable file’s apparent correctness. Preserve the file identity and relevant page references so a later correction can be traced to the actual distributed version.

Retain the section map with the template handoff. When a new part is inserted or copied from another document, review its incoming dependencies before treating it as an independent chapter. Keep this workflow separate from print imposition, binding creep and tagged-PDF reading order. It does not change a live document, authorize its distribution or declare the full publication accessible; it establishes how running matter should follow document structure.

Make the reasoning concrete.

A fictional research report adds an appendix copied from an earlier edition. Its first page looks correct, but after a paragraph is inserted upstream, the appendix’s ordinary pages display the preceding chapter title.

The editor requests a corrected structure and a supplied insertion fixture, then checks the final export. No real publication is edited or sent.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Parts

   Which semantic sections require different running matter?

2. Types

   What should each relevant first, odd and even header or footer contain?

3. Dependency

   Which row intentionally inherits from which predecessor?

4. Labels

   Where should visible numbering continue, restart or be absent?

5. Export

   Which final-file boundaries prove the accepted structure survived?

Watch for the wrong conclusion.

• Confusing a page break with a section boundary.
• Fixing one visible page without identifying its inherited element.
• Treating file-page position and printed page label as interchangeable.

Sources & scope

Workflows, fixtures, worksheets and examples are original editorial analysis. Sources support the narrow attributed statements, not measured business results. Platform guidance is scoped to the documented implementation and date checked. Synthetic offline planning only; no external account, file publication, permissions or production configuration is changed.

• Link to previous →Primary platform documentation or published technical standard · Supports: Supports corresponding header/footer inheritance; the section map and insertion fixture are original.
• Customize page numbers and their formats in different Word document sections →Primary platform documentation · Supports: Supports section-specific numbering format and start, using section breaks.