Book Back Matter Template 1
Research-heavy order: Notes → Bibliography/References → Appendices → Index → Acknowledgments/Author note as house style requires.
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Effective back matter gives every post-body element a distinct reader, documentation, scholarly, legal, navigational, or engagement job; preserves the completed ending of the body; orders required/useful material before optional promotion where appropriate; and verifies every cross-reference against the final edition.
Research-heavy order: Notes → Bibliography/References → Appendices → Index → Acknowledgments/Author note as house style requires.
Reader-engagement order: Acknowledgments → Discussion questions → Reading guide → About the author → Related books.
Appendix test: Include [material] in an appendix only if readers may need it but placing it in [chapter] would interrupt the main flow.
Back-matter audit: Element | Reader purpose | Required? | Cross-references checked? | Final order.
Source-record and update audit for Book Back Matter: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Source-ledger and revision-history audit for Book Back Matter: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].
Back-matter architecture: element [x] | primary reader [x] | job [documentation/reference/context/engagement/promotion] | required? [yes/no] | final position [x].
Priority audit: required/legal [x] → evidence/reference [x] → context/contribution [x] → reader engagement [x] → optional promotion [x].
Cross-reference QA: source note [x] | body marker [x] | appendix/page/link target [x] | final-file check [pass/fail] | correction [x].
Element removal test: section [x] | distinct job [x] | duplicated by [x] | harm if removed [x] | verdict [keep/merge/cut].
Reader-aid branch: need is [discussion / guided reading / reference / reusable tool] → choose [questions / reading guide / glossary-index / appendix-resource].
Context branch: reader needs to know [x] after the body → Author Note if disclosure/context; Acknowledgments if contribution/gratitude; notes/bibliography if evidence trail.
Edition check: material tied to current edition [x] | date/version [x] | likely to change? [x] | maintenance owner/location [x].