Add a Working Index to a Long Series Bible

A collaborator opens the bible with a noun in mind. Where does it describe the ferry station? What was the rule about how much story time a season covers? Is the person everyone calls Bird the same as Deirdre Vance?

The contents page can't answer any of those. It lists parts in the order you wrote them, which is genuinely useful — it tells a reader what the document contains and roughly where to begin. But it organizes the bible the way the writer built it. Readers arrive with a term, not a chapter number.

A contents page follows the document's order. An index follows the reader's term across that order.

That difference is the whole job, and it's why a working index is more than a list of words. Three moves produce one: choose a small set of terms people will actually look up, attach the references to the passages themselves instead of typing page numbers you'll have to maintain, and regenerate after layout changes before checking that the references still land.

About the example below. The show and its bible are invented for this piece, and I've fixed the page numbers so the arithmetic is followable. No InDesign document was built for this article and no index was generated from it. What I say about InDesign comes from Adobe's documentation on creating index entries, checked September 18, 2026 — not from a build I ran or a file I exported. Confirm your own version's route before you write instructions for anyone else.

The bible, and what it's hiding

Harrow Sound is a series about an island and the ferry that connects it to the mainland. The bible runs twenty-four pages in three parts.

• World, pages 1–8. Premise on 1–3. The ferry station — terminal layout, timetable, the staff, what the crossing looks like in each season — on 4–6. Weather, the island's economy and the mainland on 7–8.
• Characters, pages 9–14. Deirdre Vance, whom everyone on the island calls Bird, on 9–11. Two other principals on 12–13. Relationship notes on 14.
• Episode mechanics, pages 15–24. The twelve-week rule — each season covers twelve weeks of island time — on 15–16. How the crossing functions as a scene-turn device on 17. Episode breakdowns on 18–21. Season arcs and the finale rule on 22–24.

Two details in that summary shape everything that follows. First, most of the ferry material on pages 5 and 6 never says ferry station. It says the terminal, the dock, the waiting room. Second, there's a character called Bird and a four-line character entry for Deirdre Vance, and they're the same person.

Choose the question before the keyword

The quickest way to build a bad index is to start at page one and write down every proper noun you meet.

Do it the other way. Ask what someone will arrive looking for. On Harrow Sound the list is short:

• The place the show keeps returning to.
• The character whose name people get wrong, depending on whether they've read the scripts or the bible.
• The rule that governs how a season is paced.
• The event on page 5 that involves the boat but isn't the boat.
• The mainland port, which is called one thing in the World section and another in the breakdowns.

Then judge, for each term, whether the document has something substantial to say.

That judgment is what keeps an index usable. Deirdre Vance is named once on page 20, in a single line of episode breakdown noting which weeks she's off-island. That line doesn't answer anything a reader is likely to be asking. Indexing it wouldn't make the index more complete; it would put a number in front of the three-page discussion that actually helps. Page 20 stays out.

This is the line between a finding aid and a concordance. A concordance lists every occurrence. An index decides which occurrences deserve a reader's trip.

Here's the index that comes out of the questions above:

Bird. See Deirdre Vance. Carrow. 7–8. Crossing, the. 5, 22–23. See also Ferry station. Deirdre Vance. 9–11. Ferry station. 4–6, 17. See also Crossing, the. timetable. 5. staff. 6. Twelve-week rule. 15–16.

Six heads, three cross-references, two subentries. That's a real index for a twenty-four-page document, not a truncated one.

Pending, not indexed. Carrow Point — the mainland port as the episode breakdowns name it — may be the same place as Carrow in the World section. Until the style sheet rules on that, Carrow carries the entry, because that's the World section's name for it, and the variant waits in the terminology log instead of taking a See. See below.

A word about the subentries. At this scale they're optional — a reader who lands on the start of a three-page run will find the timetable a page later without much effort. Subentries start earning their place when a run is long enough that landing at its opening costs the reader a search, or when two clearly separable questions live inside one discussion. Include them when they save someone work, not because an index is supposed to have them.

References live in the passage, not in your head

The instinct to type 4–6 next to Ferry station is the one that makes an index expensive. Those numbers are true only until someone edits the World section, and then you're hunting through twenty-four pages to find out which references drifted.

Adobe's documentation on creating index entries describes a distinction worth taking seriously: entries can be topics placed as references in the text, and those references can carry page ranges or cross-references. The practical upshot is that you put a marker where the material actually is, and the reference picks up its own page number when the document is generated. You're not maintaining numbers. You're maintaining a set of claims about where passages are, and the numbers are a symptom of those claims.

That wording — "claims about where passages are" — is what separates a range from a list of pages. On Harrow Sound, pages 4, 5 and 6 are one continuous discussion of the terminal: where it is, what's in it, who works there. A single range, 4–6, tells the reader "this is one passage, three pages long." Three separate references — 4, 5, 6 — say something false. They say this is a place the show keeps touching down in, three separate times. Use a range when the discussion genuinely runs on. Use separate references when the mentions are genuinely separate, like the terminal on 4–6 and its structural use on 17.

Subentries are a third shape. timetable. 5. and staff. 6. don't repeat the parent range; they split it into the two questions someone might actually have.

Now the part automation gets wrong. Adobe's documentation describes an Add All operation that matches case-sensitive whole words. It does not interpret synonyms, and it does not identify meaningful discussions. Run it on ferry station in Edition 1 and you get pages 4 and 17 — because page 4 uses that phrase, page 17 uses that phrase, and pages 5 and 6 call the same building the terminal and the dock.

Four and seventeen look like a complete answer. The gap at 5–6 is invisible unless you already know it's there. That's the case for placing references by hand at the passage you mean and treating Add All as a way to catch occurrences you might have missed, not as a way to find the ones that matter. It also cuts the other way: if a heading reads Ferry Station with both words capitalized, a case-sensitive whole-word search for ferry station won't return it.

Two places text matching fails outright, worth knowing before you trust a sweep: diagrams and tables, which search tools largely can't read, and passages that discuss a thing without naming it. The relationship notes on page 14 are a diagram. No amount of matching will index them.

Aliases route; See also connects

Bird is what the characters say. Deirdre Vance is what the bible says. A reader who comes back from a script read will type Bird, so the index has to receive that word. It should receive it as a See reference, and nothing else:

Bird. See Deirdre Vance.

The tempting alternative is to list Bird with its own page numbers — 12, 20, 23, whichever ones match. Two problems. You'd be maintaining two lists that always say the same thing, and you'd be sending the reader to a scattered set of pages instead of the one sustained entry. A See means "there is nothing here; the material is under that other term." Use it when the alternate name has no independent content.

See also means the opposite: both terms have material of their own, and the reader should know about both. On Harrow Sound, Ferry station and the Crossing look mergeable and aren't. One is a building and a timetable. The other is an annual memorial event that the finale is built around. Merging them would bury the event's rules inside the location entry, where nobody looking for the finale's structure would find them. Two heads, each with a See also pointing at the other.

This is where the style sheet does work the index can't. If your project sets preferred terminology — which name goes in running text, which one is dialogue-only, which spelling of a place is current — check the index against it rather than deciding terminology yourself. And when the style sheet hasn't decided, don't settle it by indexing.

That's the situation with Carrow. The World section calls the mainland port Carrow. The episode breakdowns call it Carrow Point. If those are one place with two spellings, a See from the unused form is exactly right, and the style sheet should catch up within the week. If they might be two different places — and if the story has any reason to want them ambiguous — then a See is an editorial ruling made by a finding aid, which is not the finding aid's job. Index the form your style sheet currently prefers, log the open question where terminology gets logged, and leave the cross-reference out until someone decides. That's why the note under the index above sits where it does, outside the index.

One more caution that costs nothing to state: don't merge two things that share a name just to tidy the list. If the story intends an ambiguity, the index flattening it is a bug in the index, not a service to the reader.

Regenerate, then follow the references yourself

Here's the maintenance test. You've added a new three-page subsection to the end of the World section, ahead of the mainland material — say, the mainland's own history, which the show now needs. Pages 1–6 keep their numbers. The new material takes 7–9. Everything that used to sit on page 7 or later moves three pages down.

Regenerate the index and compare.

Notice what did and didn't move. Ferry station lost its 4–6 range to nothing — those pages stayed put — while its page 17 reference slid to 20. Its subentries, timetable and staff, held at 5 and 6 because they were inside the untouched stretch. The Crossing kept its page 5 mention and shifted its finale range by three. The alias entry never moved at all, because it never had a page number to lose. That's the reward for routing instead of duplicating. And Carrow Point isn't in either column, because it never entered the index; there's nothing to maintain there until the terminology decision lands, and nothing to unmaintain if it doesn't.

The range 15–16 became 18–19: both pages moved together, so the twelve-week rule is still one continuous two-page passage. The failure mode you're watching for is the one where a range splits. If those three new pages had landed inside the terminal description instead — inserted at what was page 5 — the old 4–6 would come back as 4, 8–9. The passage is still one discussion, but it now spans a break, and the index has to say so. No amount of hand-editing old numbers gets you there; the document has to be read again.

So the check after regeneration is short and specific. Open the exported reading file — the PDF someone will actually receive, not the Index panel where you built the entries — and follow three references by hand. Follow the alias, and see whether it lands on Deirdre Vance. Follow a range, and see whether it covers the whole discussion rather than clipping it. Follow one reference whose passage moved, and see whether it points at the passage or at the gap where the passage used to be. Check that the terms in the generated index match the terms on the style sheet, and that anything unresolved is still flagged as unresolved in the terminology log rather than having slipped into the index as a ruling.

What you're checking is not that the software worked. It's that the claims you made about where things are still describe the document in front of you.

Two limits worth carrying. An index is not a search engine — it won't find a scene someone half-remembers by its mood or its dialogue. It isn't a canon authority: a term appearing in the index doesn't make it approved story language, and a term missing from the index doesn't make it absent from the series. And it will never be a map of every meaningful mention in the bible. It's a selective set of doors, and the selection is the editorial work.

That's the version that survives the pagination change, and it's worth building precisely because it's small. A twenty-four-page bible doesn't need two hundred entries. It needs six or seven that a collaborator can trust, placed where the material lives, regenerated after the reflow and checked by someone who opened the export and followed them.

Frequently asked questions

How does a working index differ from a contents page?

A contents page follows the document's order and tells a reader what the bible contains and roughly where to begin. An index follows the reader's term across that order, so someone who arrives with a noun can find the passages about it.

What three moves produce a working index?

Choose a small set of terms people will actually look up, attach references to the passages themselves instead of typing page numbers, and regenerate after layout changes before checking that the references still land. A twenty-four-page bible may need only six or seven trustworthy entries.

Why do ranges, separate references, and subentries say different things?

A range such as Ferry station 4-6 says one continuous discussion runs for three pages. Separate references say the mentions are genuinely separate, as with the terminal on 4-6 and its structural use on 17. Subentries split a parent range into the questions a reader may actually have, such as timetable on 5 and staff on 6.

Why can't an Add All sweep replace placing references by hand?

Adobe documents Add All as matching case-sensitive whole words; it does not interpret synonyms or identify meaningful discussions. A sweep for ferry station returns pages 4 and 17 but misses the terminal and dock material on 5-6, and it may also miss a capitalized heading. Diagrams, tables, and passages that discuss a thing without naming it fail matching outright.

When should an index use See, See also, or leave a term out?

Use See for an alternate name that has no independent content, such as Bird pointing to Deirdre Vance. Use See also when both terms have material of their own, such as Ferry station and the Crossing. If terminology is unresolved, as with Carrow and Carrow Point, index the form the style sheet currently prefers and log the open question instead of letting a cross-reference decide it.

Further reading

• Keep Source Notes Attached While a Research Bible Reflows — Read this when references keep drifting: it applies the same reasoning to source notes, using references that travel with their text and checking the exported reading edition.