How to Insert a Table of Contents in Word for Video Scripts

Why Video Scripts Fall Apart Without a Table of Contents

A feature-length script is rarely read from top to bottom in one sitting. It is navigated: the editor jumps to the shot that needs a new sound effect, the voice actor needs only their lines on page 14, the client wants to see the opening hook again, and the animator needs to know which scene the new prompt belongs to. When the document has no map, every one of those trips becomes a manual scroll-and-search exercise, and someone eventually edits the wrong revision.

A table of contents (TOC) turns a script from a single long block of text into a navigable structure. In Microsoft Word, that structure is generated automatically from heading styles you apply to your script sections. You do not type the TOC by hand, and you do not maintain it by hand. You assign meaning to your headings once, insert the field, and then refresh it whenever the script changes.

That matters more than it used to. Scripts are no longer only read by humans. They are parsed by collaborators, by production tracking sheets, by subtitle tools, and increasingly by AI video pipelines that take a scene description and render a clip from it. A script organized with consistent headings and predictable naming is dramatically easier to hand off than a wall of styled paragraphs.

This guide walks through the mechanical steps in Word, then goes further: how to shape your heading hierarchy for video work specifically, how to keep the TOC accurate when scenes get reordered, how to troubleshoot the failures that trip people up, and how to extend the same structure into a full pre-production system.

Heading Styles Are the Engine Behind the TOC

Word's automatic table of contents only sees text that has a heading style applied to it. Bold text is not a heading. Larger font size is not a heading. Centered capitals are not a heading. They look like headings to you and completely invisible to Word.

This is the single most common reason a TOC comes out empty or half-finished. If you have manually formatted your script with bold lines and paragraph spacing, the References → Table of Contents command produces a blank or near-blank result, and people conclude the feature is broken. It is not broken; the document simply has no structure for it to read.

Choosing a Hierarchy That Matches Video Production

Standard academic advice — Heading 1 for chapters, Heading 2 for sections — needs translation for scripts. A hierarchy that works well for video:

• Heading 1 for major structural units: acts, sequences, or numbered blocks such as "Opening", "Segment A", "Interview Block", "CTA".
• Heading 2 for individual scenes or beats within that unit.
• Heading 3 for shot-level detail, camera notes, or interview questions inside a scene.
• Heading 4 sparingly, for alternate takes or branching variants that you want visible in the TOC but not dominant.

Keep the hierarchy about three levels deep in practice. A TOC that lists 180 Heading 3 entries is functionally the same as no TOC at all.

Scene Headings Should Carry Real Information

Because the TOC becomes the fastest way to jump around the document, the heading text itself is the navigation label. Write headings that identify location, time, and content in a compressed form:

1.2 — Rooftop, dawn — Mara confronts the courier
1.3 — Rooftop, dawn — Insert shots: hands, envelope, skyline

A heading like "Scene 4" is technically sufficient, but it forces the reader to jump in anyway to remember what Scene 4 contains. Numbered headings with a descriptive tail give you the TOC as a one-page story outline for free.

Where Numbering Should Live

You have two options: type the numbers into the heading text, or let Word's multilevel list numbering generate them. Typed numbers are simpler and survive export to PDF, plain text, or a spreadsheet without renumbering surprises. List-generated numbers are cleaner when you reorder scenes frequently, because Word renumbers automatically — but they can behave unpredictably when you paste content from another document.

If your script will be exported into another tool — a shot tracker, a spreadsheet, or an AI generation queue — typed numbers are usually the safer choice. They are visible as literal text everywhere.

Step by Step: Inserting the Table of Contents

With headings in place, the actual insertion takes under a minute.

1. Position the cursor. Place your insertion point where the TOC should appear — typically on its own page immediately after the title page. Insert a page break first so the TOC sits cleanly on a fresh page.
2. Open the References tab. On the ribbon, go to References → Table of Contents. Word offers two automatic styles and one manual option. Choose one of the automatic styles; the manual option requires you to build the list yourself and defeats the purpose.
3. Review the generated list. Word scans the document and lists every heading, indented by level, with page numbers. If the list looks wrong, the problem is almost always heading styles, not the TOC itself.
4. Style it for readability. Click into the TOC and use Table of Contents → Custom Table of Contents to control whether to show page numbers, whether numbers are right-aligned with dot leaders, and how many levels to include. For a script, three levels is a sensible ceiling.
5. Add a page break after it. Press Ctrl+Enter at the end of the TOC so the script body starts on a new page. This prevents the TOC from reflowing into the first scene when you add or remove entries.

If you want the TOC to include headings but the numbering column looks messy, check your tab stops rather than retyping entries. Right-aligned tab stops with dot leaders are what produce the clean ".... 42" look.

Naming the TOC Page

Label the page clearly, for example "Contents" or "Script Map". When multiple people on a production touch the same document, an obvious label reduces the chance that someone deletes the page as clutter. It happens more often than you would expect.

Keeping the TOC Accurate as the Script Changes

A generated TOC is a snapshot. When you add a scene, split a scene, or move a block, the entries and page numbers drift out of date until you refresh.

To update: click anywhere in the TOC, then press F9, or use the small Update Table button that appears above the field. Word asks whether to update page numbers only, or the entire table. Choose the entire table when headings have changed. Choose page numbers only when you have moved content without renaming headings and want a faster refresh on a long document.

You can also configure the TOC to update automatically before printing, which is useful when the document's main purpose is to be exported to PDF for review. It is not a substitute for a manual refresh while you work, because on-screen page references will still be stale.

Two habits keep this painless:

• Refresh after every structural change, not at the end. Updating takes two seconds when the change is fresh in your mind. Doing it after twenty edits means you cannot tell whether a strange entry is a real problem or leftover drift.
• Keep the TOC on its own page. If it shares a page with the script body, adding entries pushes content around and makes page references harder to trust.

Working With Track Changes and Comments

During review cycles, tracked changes can make heading text temporarily messy. When the TOC picks up a heading that is marked as inserted or deleted, the entry can appear oddly formatted. Accept or reject heading-level changes before finalizing, then refresh once more. Comments do not affect the TOC, so reviewers can leave notes freely.

Troubleshooting: When the TOC Refuses to Cooperate

Most TOC problems fall into a small number of categories.

The TOC is empty or missing scenes. Your headings are not styled as headings. Select the line, then apply Heading 1 or Heading 2 from the Styles gallery. If a line looks like a heading but has manual bold formatting, restyle it.

Some headings appear, others do not. Check the heading level. If your TOC is set to show three levels and a section uses Heading 4, it will be excluded by design. Either promote the section or raise the levels shown in the custom TOC settings.

Page numbers are wrong. The TOC has not been refreshed, or your document uses section breaks with restarted numbering. If page numbering restarts in a new section, decide deliberately whether the TOC should follow the restarted numbers and set that in the page number formatting options.

A heading appears in the TOC but should not. You have likely applied a heading style to a label that is not a real section — a title page, a table caption, or a divider. Either remove the heading style or wrap the document so that the TOC is scoped to a portion of it. Using a distinct style, such as a custom "Script Divider" style based on body text, solves this cleanly.

Formatting changed unexpectedly after updating. Custom TOC formatting can be overwritten when the field is regenerated with default settings. If you restyled TOC entries, either recreate them through the custom TOC dialog so Word remembers the intent, or accept minor resets and reapply your tweaks. The dialog route is more durable.

The TOC disappeared entirely. It may have been converted to plain text by someone who copied and pasted with formatting stripped. If the entries are now ordinary paragraphs, you can delete them and insert a fresh automatic TOC, provided your heading styles are intact.

Extending the Structure to AI-Assisted Production

Once a script is cleanly structured, it becomes machine-readable in a way that a manually formatted document never is. That has practical value when parts of the workflow involve AI tools — text-to-video generators, voice synthesis, image generation for storyboards, or automated captioning.

Consistent Headings Become Scene Identifiers

If every scene heading follows the same pattern — number, location, time of day, description — you can copy the TOC into a spreadsheet and instantly have a scene list with identifiers. Those identifiers travel well. They can label generated clips, name exported frames, and tag prompts so that a rendered asset is traceable back to the exact script section that produced it.

Inconsistent headings destroy this. "Scene 3", "The Kitchen", and "INT. KITCHEN — NIGHT" in the same document cannot be processed the same way. Pick a pattern and enforce it during review.

Notes Lines for Generation Parameters

A lightweight practice that pays off: under each scene heading, add a short parenthetical line describing generation intent — aspect ratio, duration target, visual style, whether the shot is live action or generated, and which asset library or model family you plan to use. Because it sits under the heading, it stays attached to the scene even when scenes are reordered.

This line is not part of the spoken script. Keep it in a visually distinct style, such as italic gray text or a dedicated "Production Note" style, so it never gets read aloud by accident.

Where the TOC Stops Being Useful

For a two-minute social clip, a TOC is overkill. For a 20-minute explainer with multiple segments, it starts earning its place. For a 60-page script with interviews, generated segments, and animation inserts, it is close to mandatory. Match the overhead to the length and complexity of the production, not to the prestige of having a formal document.

Companion Tables Worth Building Alongside the TOC

Word can hold more than a script. Several lightweight tables, each keyed to the same scene numbering, keep a production legible.

• Shot list table. One row per shot with scene number, shot type, movement, duration estimate, and status. Because it uses the same scene numbers as your headings, cross-referencing is trivial.
• Asset tracker. Columns for asset name, source (footage, generated, stock, licensed), location, and rights notes. This prevents the classic late-stage scramble when someone asks whether a music cue is cleared.
• Narration and voice log. Track which lines are recorded, which are pending, and which takes are approved. Useful when multiple voice talents are involved.
• Prompt and parameter log. If any part of the video is AI-generated, log the prompt, the settings, and the resulting file name per scene. Regeneration requests become routine instead of archaeology.

Each table should sit in its own section with its own heading, so it appears in the TOC. That way the document doubles as a navigable production hub rather than a pile of appendices.

Matching the Workflow to Your Team Size

Solo creator. Keep it simple: Heading 1 for segments, Heading 2 for scenes, a single TOC page, and one shot list table. Refresh before every export.

Small team with an editor or animator. Add a production notes line under each scene and keep a shared asset tracker. Agree on a naming convention for exported files that mirrors the scene numbers.

Larger production with clients. Freeze the script into a numbered revision (for example, a version label and a locked scene list) before distributing, and note in the document which revision the TOC reflects. Distribute PDFs with an embedded outline so reviewers can navigate without needing Word at all.

Hybrid AI and traditional pipelines. Treat the script as the source of truth and everything else as generated output. When a generated clip is rejected, the fix starts in the script section, not in the render settings.

Mistakes That Quietly Break Script Documents

• Manual TOCs. Typing dots and page numbers by hand guarantees drift within a day.
• Using bold instead of heading styles. The most common cause of an empty TOC.
• Mixing numbering systems. "Act 1", "Segment 1", and "01" in the same script make cross-referencing painful.
• Renaming scene headings mid-production. If the visual effects breakdown already references "Scene 7 — Parking Garage", renaming it breaks the link for everyone downstream.
• Letting the TOC span onto a script page. Layout shifts make page references unreliable during review.
• No revision marker. Two versions of the script with identical filenames and no version note is a recipe for edits landing on a stale document.
• Skipped heading levels. Jumping from Heading 1 to Heading 3 creates odd indentation in the TOC and confuses parsers reading the outline.

FAQ

Does the table of contents update automatically when I add a scene?
No. Word generates the field once. You refresh it manually, typically by clicking in the TOC and pressing F9, or by using the Update Table button. You can enable update-on-print, but on-screen entries stay stale until you refresh.

Why is my TOC blank?
Almost certainly because no heading styles are applied. Select each section title and apply Heading 1 or Heading 2 from the Styles gallery, then regenerate.

Can I have more than one TOC in a document?
Yes. This is useful when a script has a main body plus an appendix of interview transcripts or legal notes that you want listed separately. Scope each TOC using a switch that limits it to a bookmark or a heading range.

Should the title page appear in the TOC?
Usually not. Keep the title page styled as normal text or with a non-heading title style so it stays out of the list.

Does the TOC survive conversion to PDF?
The visible list survives. The clickable navigation bookmarks depend on your export settings; enabling the option to create bookmarks from headings gives reviewers a navigable outline.

How deep should the TOC go?
Three levels is a good default for scripts. Four levels is workable for documentary or animation work with heavy shot detail, but expect a long contents page.

What if scenes get reordered frequently?
Use Word's multilevel list numbering so numbers regenerate automatically, keep the TOC on its own page, and refresh after every reorder. If your production is highly dynamic, consider keeping the master shot order in a spreadsheet and using the script for content rather than sequencing.

Is a table of contents useful for AI video pipelines?
Yes — not for the AI itself, but for you. The heading structure gives you stable scene identifiers you can paste into a tracker, use as file-naming roots, and reference when reviewing generated output. It is a coordination tool more than a generation tool.

Bringing It Together

Inserting a table of contents in Word is a two-minute task. Maintaining useful structure over the life of a production is the real work, and it depends on three habits: apply real heading styles instead of manual formatting, use a consistent numbering and naming pattern that means something to the people and tools downstream, and refresh the field every time the document's shape changes.

Do that, and your script stops being a document you hunt through. It becomes a map of the production — one that a voice actor, an editor, a client reviewer, and a generation queue can all read from the same page.