Create a layered table of contents and reading route

Author: AILesson8 min setupTested with:ChatGPTReviewed: 2026-08-28

Quick answer

Map a long document by structure, purpose, dependencies, evidence, and reader-specific routes without pretending unread sections were reviewed. Provide: Document with locators, Readers and reading goals, Outline and route rules. Expected result: A verified hierarchical outline with quick, decision, study, and reference reading paths.

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Document with locatorsReaders and reading goalsOutline and route rules

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Create a layered table of contents and reader-specific route through the supplied long document.

Document, version, headings, locators, figures/tables, appendices, and missing ranges:
[document]

Reader roles, decisions/learning goals, time, prior knowledge, required evidence, and mandatory sections:
[readers]

Depth, locator, summary, prerequisites, visual material, caveats, and incomplete-document rules:
[rules]

Reconstruct the document's actual hierarchy before creating a conceptual map; do not invent headings or contents for unavailable pages. For each section record locator, purpose, key question, evidence or operation, dependency, outputs, and who needs it. Distinguish navigational heading from analyst-created label. Mark repeated, superseded, contradictory, reference-only, and missing sections. Build routes by reader goal and time budget, preserving prerequisites, definitions, limitations, safety/legal conditions, and tables or appendices required to interpret conclusions. Do not replace reading of decisive evidence with a summary. Return: document coverage statement; three-level table of contents; one-line section annotations; concept/dependency map; quick orientation route; decision route; deep-study route; lookup route; skip/defer rationale; checkpoints; and unresolved navigation or missing-content issues.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Document with locators: Operations Continuity Manual v3.2, 96 pages. Available markers: pp.1–3 cover/version/change log; pp.4–9 Part I Scope and definitions (1.1 purpose, 1.2 covered services, 1.3 severity levels); pp.10–18 Part II Roles (incident lead, service owner, communications, supplier liaison); pp.19–37 Part III Activation (detection, severity assessment, activation, first-hour checklist); pp.38–55 Part IV Response playbooks (data-center loss, SaaS outage, supplier failure); pp.56–67 Part V Communications and notification templates; pp.68–75 Part VI Recovery and closure; pp.76–84 Part VII Exercises and maintenance; pp.85–92 appendices A contact matrix, B service priorities, C RTO/RPO glossary, D evidence log template. Pages 93–96 are referenced as Appendix E legal notifications but are missing from the supplied copy. On p.21, severity table refers to v3.1 definitions, while change log says v3.2 revised severity. Figures: activation flow p.24; first-hour table pp.30–31; RTO table pp.88–89.
Readers and reading goals: Incident lead needs a 10-minute orientation before on-call shift and must know activation/first-hour routes. Service owner has 25 minutes to assess a live SaaS outage and needs scope, severity, roles, playbook, communications, recovery, and RTO evidence. New continuity analyst studies the whole manual over three sessions. Staff sometimes need to locate templates or contacts quickly. No one may skip missing legal-notification warning.
Outline and route rules: Three outline levels using page ranges. One-line annotations. Analyst labels prefixed ‘Concept map’. Mandatory prerequisites: scope/severity before activation; role authority before action; RTO definitions before interpreting table. Never summarize missing Appendix E. Flag p.21 version conflict. Legal and safety instructions must be read in original. Routes state estimated minutes and checkpoints.

Example output

Coverage: pp.1–92 are described from the supplied copy; pp.93–96 Appendix E are unavailable and cannot be summarized. A version conflict exists between the p.21 v3.1 reference and v3.2 change log; resolve before relying on severity activation.

Layered contents: Front matter pp.1–3—version authority. I Scope/definitions pp.4–9: 1.1 purpose; 1.2 covered services; 1.3 severity levels—mandatory activation vocabulary. II Roles pp.10–18: authority and handoffs. III Activation pp.19–37: detection; severity; activation; p.24 flow; pp.30–31 first-hour checklist. IV Playbooks pp.38–55: select by event, including SaaS pp.46–49 if locator confirmed from original. V Communications pp.56–67: channels/templates, with legal caveat. VI Recovery pp.68–75: criteria, evidence, closure. VII Exercises pp.76–84. Appendices pp.85–92: contacts, priorities, RTO/RPO, evidence log. Appendix E pp.93–96—missing, mandatory warning.

Incident lead 10-minute route: p.1–3 version check (1 min) → 1.2/1.3 pp.5–9 (2 min) → authority pp.10–14 (2 min) → activation flow p.24 and first-hour table pp.30–31 (4 min) → missing Appendix E warning (1 min). Checkpoint: confirm current severity authority and contacts; do not execute from summary. Service owner 25-minute live route: same prerequisites, SaaS playbook original, communications conditions, recovery criteria, Appendix C definitions then RTO table, and Appendix E warning. Stop if severity conflict affects activation or legal notification is needed.

Deep study: session 1 Parts I–III plus conflict log; session 2 playbooks/communications with scenario tracing; session 3 recovery, exercises, and appendices with an evidence-log practice. Lookup: contacts A, service priority B, RTO/RPO C before table, evidence template D, communications templates Part V. Legal/safety wording always requires the original; missing E must be obtained from the document owner.

Why this works

1
Separating actual headings from conceptual labels keeps navigation faithful while improving understanding.
2
Dependency-aware routes prevent a time-limited reader from skipping definitions or conditions needed to interpret conclusions.

Check the result

Does every outline entry map to an available locator, with invented analyst labels clearly marked?
Do routes preserve prerequisites, limitations, safety/legal conditions, and decisive evidence?
Are unavailable, repeated, superseded, and contradictory sections visible?

Use it with confidence

Frequently asked questions

Practical answers about when to use this recipe, what to provide, and where human review still matters

What should I prepare before using “Create a layered table of contents and reading route”?

For “Create a layered table of contents and reading route,” prepare Document with locators, Readers and reading goals, and Outline and route rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Create a layered table of contents and reading route” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A verified hierarchical outline with quick, decision, study, and reference reading paths—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Create a layered table of contents and reading route”?

The published test record for “Create a layered table of contents and reading route” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

More ways to explore