Build a Story-Day Breakdown From a TV Pilot

A scene heading tells you the light. A story day tells you how much time the story has spent. A shoot day tells you who is called to set on Thursday. Three coordinates, routinely collapsed into one, usually by accident — a naked "DAY" in a heading becomes "the next day," a new location becomes "later that week," and a flashback quietly joins the present tense.

A story-day breakdown is the record that keeps them apart. It is a scene-by-scene account of how far into the story each scene sits, with the clue that put it there written down beside it, and a visible gap wherever the draft did not say.

The method is short. Work from one named draft. List its scenes in the order they appear on the page. Beside each one, record what it actually says about time: the heading, the dialogue, the transitions, the props, the actions. Then advance the story day only when a clue crosses a boundary. Everything else gets a provisional label and a question for the writer.

What follows is one version of that method, worked on an invented eight-scene fragment. It is not a real pilot, and nothing here settles the days of one.

Identify the pilot version and keep its scene order

Start by naming the thing you're reading. "Harbor Line, third draft, dated" is a workable start; "the pilot" is not. Two drafts of the same script can move a "CONTINUOUS," cut a line about the six o'clock boat, or flip a night scene into a morning one, and a breakdown that silently blends them can't be checked by anyone — including you, three weeks later.

Then build the table in screenplay order. Not chronological order, not shooting order, not the order you think the story happens. Screenplay order is the only order that lets a second reader find the row you're defending. If your row for scene six says "Day 1, night, supported by the clerk's line," another reader should be able to open the draft, read scene six, and agree or object.

Two habits worth forming at this stage:

Quote the evidence, don't summarize it. "Roughly evening" is not checkable. "Dockmaster: Six in the morning. First boat." is.

Don't treat a production scene number as a timestamp. The numbers that appear in a script supervisor's or first AD's breakdown are a production filing system; they get renumbered, split, and merged as the shoot takes shape. They tell you where a scene sits in the machinery. They say nothing about Tuesday.

For the fragment I'll be using — call it Harbor Line, an invented eight-scene pilot fragment — the draft is stable, the headings are as written, and the scene order is the order given. Everything below depends on that stability, which is exactly why the version gets named first.

Assign story days only when the clues support them

Pick an anchor. Choose whichever stretch of the draft gives you the firmest temporal footing, label it Day 1, and build outward. The number itself is arbitrary — you could call it Day Zero or Day 400 without changing anything — but it has to be identified and it has to stay put.

In Harbor Line, the anchor is scenes 1 through 3. They turn on a single named departure: the six o'clock boat. Scene 2's heading carries "(CONTINUOUS)," and the harbor clerk says the six o'clock boat is the last one today. Scene 3 shows that same boat pulling out. One departure, named once, seen once. Call it Day 1 and move on.

That gives the first three rows:

Notice what row 3 is doing. It is a night scene that belongs to the same story day as two day scenes, because the boat that left at six is the boat the earlier scenes named. This is the ordinary case, not the exotic one. A story day runs from the moment a character wakes (or from wherever you anchored) until the next sleep or the next stated jump, and most of them contain a night.

The reverse mistake is more common. A heading that reads DAY is a statement about light on set, not about which day. Nothing in "DAY" distinguishes the morning after the dock from a morning three weeks later. Only a clue does that: a stated interval in dialogue, a transition the draft writes out, or contextual action — a boat that left last night is now docked and unloading; a bandage has come off; a season has changed on the trees.

When the draft gives you less than that, say so in the label. "Day 1," "Day 1 (provisional)," and "unplaced" are all legitimate entries. "Day 2, probably" is the entry that gets copied into a bible and then treated as fact for the rest of the season.

One practitioner account of the job — Film Independent's script-supervisor workshop piece, in the version dated 13 September 2026 — describes the day-night breakdown as assigning scenes a day in story time, and lists clock questions among the continuity problems the role tracks. That is a statement about a working habit, not a rule, and it says nothing about any particular pilot. It is useful here as confirmation that the separation is normal practice, not as authority for any row in your table.

Preserve parallel action, flashbacks, and uncertain gaps

Four rows in Harbor Line need care, and each needs a different kind of care.

The parallel scene. Scene 5 sits at Station Point Adams. A Coast Guard operator lifts a microphone and says, into a dead channel, the same line we heard in scene 3: "Harbor One, Harbor One, Station Point Adams." No reply, again. That repeated line is the clue: it connects this scene to one we've already placed. So scene 5 is Day 1, night, running alongside scene 3.

The row after it is where breakdowns usually break. Scene 5 appears later on the page than scene 3, so a page-order reading pushes the story forward. But page order is delivery order, not chronology. A parallel scene's position on the page tells you when the audience learns something, not when it happened.

The flashback. Scene 4 is marked as a flashback in the draft — that's what "marked" means, and it matters. The reader doesn't have to guess and neither do you. But a marked flashback still needs a placement, and it still shouldn't get a number in the present-day count, because it doesn't sit in that count. It gets a relation instead: "before Day 1, interval unspecified." If the draft later anchors it — a year on a wall calendar, a character's age that conflicts with the present — you can tighten the note. Until then, "before Day 1" is as far as the evidence goes, and it's an honest distance.

The return. Scene 6 comes back to the dock that same night. The clues: the clerk from scene 2 is locking the harbor office after the last departure, and she says, "Nothing else tonight, miss." The paper cup Mara set on the bench in scene 3 is still there, dented. The line is doing the real work; the cup corroborates it. Worth saying out loud, because it's the difference between evidence and atmosphere: a cup left on a bench does not establish how many nights have passed, since someone could leave a cup there for a week. Its presence supports the reading; it doesn't settle it.

The gap. Scene 6 ends with a stated plan. The dockmaster says the first boat goes at six in the morning; Mara says she'll be on it. That is a stated next morning in the only sense a draft can state one — as an intention, spoken aloud.

Scene 7 is INT. MARA'S FLAT — MORNING. The case is no longer on the table. Nothing else in the scene ties it to the dock, to the six o'clock boat, or to any interval. It could be the morning after scene 6. It could be a morning a week later when Mara has finally come home. The draft does not say, and the heading's "MORNING" narrows the light while leaving the day wide open.

Scene 8 continues scene 7 mid-action — the phone rings while someone is still talking, the same two people in the same room. So scenes 7 and 8 share one placement, not two. Giving scene 8 its own date because it got its own heading is how a one-evening story becomes eight days.

Here is the completed table:

Now the same fragment read by the wrong method, stated once and applied to every row without exception: each new scene heading is a new story day, and CONTINUOUS is not read as a clue, so the two scenes that carry it are split off anyway.

A story that covers one evening and one unplaceable morning is billed as eight days. Nothing in that table is a lie about the draft. Every row just treats a heading as a fact about time when the heading only ever described light.

Return useful contradictions to the writer and the bible

The breakdown earns its keep when you set it against the claims people are already making. A bible line reading "the pilot covers a single weekend" is not contradicted by the fragment above — but it isn't supported by it either, and that difference needs to survive the trip to the writer.

Sort your findings into three piles before you send anything.

Contradictions. The source says one thing and the scene shows another. If the bible promised "the following morning" and a scene's own dialogue puts two days between them, that's a contradiction, and it comes with two passages attached — the claim and the scene.

Uncertainties. The source is silent. Scene 7 is this pile. It is not a contradiction; it is an absence, and an absence is not the same complaint.

Decisions. Only the writer can settle whether the eleven-month gap is real, whether the flashback is a memory or a lie, whether the flat scene is the payoff morning or a week later. Your job is to arrive at that decision with the question sharpened, not to guess and then defend the guess.

That means your queries should read like this: "Scenes 7 and 8, pp. 41–44, are headed MORNING with no interval. Scene 6, p. 38, has the dockmaster promise the six o'clock boat. Are 7 and 8 the morning after scene 6, or a later morning? If later, how much later should the bible say?" A writer can answer that in one line. A query reading "the timeline doesn't work" gets ignored, correctly.

Then leave the bible alone until the answer comes back. Updating it on your own reading turns your provisional label into a production fact, and the next person to build on it will have no way to see where it came from.

Two distinctions to carry all the way to the end of the document. Story days are not dates: "Day 1" is a position, not a Tuesday, and if the pilot never names a weekday you shouldn't either. And story days are not shoot days: the stripboard's day boundaries follow locations, cast, and page counts, and a single story evening may be shot across nine days in three counties. If you need the second thing, that's a different document with a different author.

What the finished record looks like

The end product is a table, a version name, and a short list of questions — nothing more ambitious than that.

The record above is checkable. Every firm assignment leads back to a named clue in a named draft: the six o'clock boat for scenes 1–3, the repeated radio line for scene 5, the clerk locking up for scene 6. The flashback carries a relation instead of a number. Scenes 7 and 8 carry the same open placement, visible in the main table rather than buried in a footnote, because a reader who skims the story-day column should see the uncertainty without being told to look for it.

The questions that go to the writer:

• Scenes 7–8: is this the morning after scene 6, or a later one? If later, what should the bible say about the gap?
• Scene 4 (the marked flashback): is there an anchor for the year or the season, or is "before Day 1" the intended level of precision?
• Scene 6: is the six o'clock boat meant to be paid off on screen, or is the plan deliberately left hanging?
• Bible wording: "the pilot covers a single weekend" isn't supported by the draft as written — one evening plus an unplaced morning is what the scenes show. Which phrasing should the bible carry?

Four questions, each answerable in a sentence, each attached to a passage someone else can read. That's the difference between a breakdown and an argument: when the writer comes back, you'll know exactly which rows to change, and everyone reading the record afterward will be able to see why they changed.

Frequently asked questions

What is a story-day breakdown meant to separate?

A scene heading tells you the light, a story day tells you how much time the story has spent, and a shoot day tells you who is called to set. The breakdown is a scene-by-scene record of how far into the story each scene sits, with the clue that put it there written beside it and a visible gap wherever the draft did not say.

What is the basic working method, and what order should the rows follow?

Work from one named draft and list its scenes in screenplay order—not chronological, shooting, or assumed story order. Beside each scene, record what it actually says about time; quote evidence instead of summarizing. Advance the story day only when a clue crosses a boundary. Do not treat a production scene number as a timestamp.

How should a night scene, a CONTINUOUS heading, or a parallel scene be handled?

A night scene can belong to the same story day as earlier day scenes when a clue connects them—for example, the six o'clock boat named in scenes 1–3. CONTINUOUS can show the same placement, so it should not be split off just because a new heading appears. A parallel scene's page position tells you when the audience learns something, not when it happened; a repeated line can connect it to an already placed scene.

How are marked flashbacks and uncertain mornings recorded?

A marked flashback still needs placement but should not get a number in the present-day count; it gets a relation such as 'before Day 1, interval unspecified' unless the draft later anchors it. A headed MORNING scene with no interval clue can be 'unplaced' or provisional; it should not be guessed into a numbered day. The uncertainty should be visible in the main table, not buried.

What should go back to the writer and the bible?

Sort findings into contradictions, uncertainties, and decisions. Contradictions attach the source claim and the scene; uncertainties name an absence, not a contradiction; decisions are left to the writer. Queries should cite scenes and pages and ask an answerable question. Do not update the bible from your own reading until the answer comes back. Story days are not dates or shoot days.

Further reading

• Build a Searchable Script Concordance for a Series Bible — To confirm where a quoted line appears and what surrounds it, this builds a checkable list from scene fragments and traces each hit back to the source.
• Edit a Series Bible for the Collaborator Who Has to Build From It — Before you change any bible line the breakdown contradicts, this explains how to mark claims as governing, illustrative or open and leave the conflict visible for its owner.