Slugline Discipline: Why Screenplay Format Consistency Actually Matters

Introduction: The Line That Looks Trivial

Ask a writer whether slugline formatting matters and most will shrug. It's the least "creative" line on the page — a boilerplate header before the actual writing starts. That attitude is exactly how a script ends up with a location typed three different ways across ninety pages, none of them wrong on their own, all of them wrong together.

INT. COFFEE SHOP, INT. COFFEE SHOP - DAY, and INT. THE COFFEE SHOP read as the same place to a human skimming the script. They are not the same string, and any process that treats a script as structured data — a scheduling spreadsheet, a location-tracking sheet, an AI breakdown tool, or a diligent second AD doing it by hand — has to actively decide these three lines mean one thing. Most of the time, nobody makes that decision on purpose. It just happens, or it doesn't, and the resulting mess gets inherited by whoever builds a shot list, a schedule, or a scene count next.

We covered the discipline of turning a messy script into a clean character and location list in our piece on character and location breakdown. This article is narrower and comes first, chronologically: it's about the sluglines themselves, before you've even tried to resolve anything into a canonical list. Get the format right, and the resolving pass in that piece gets dramatically easier. Get it wrong, and you're debugging string variants instead of building a breakdown.

A Slugline Is Three Fields, Not One Phrase

The habit that causes most of the damage is treating a slugline as a single descriptive phrase instead of three independent fields typed in a fixed order. Every standard slugline carries:

Notice what's missing from that list: style. A slugline has no room for a writer's voice, which is precisely what makes inconsistency in it so avoidable compared to inconsistency in dialogue or action lines. Nobody is being creative when they type INT. THE COFFEE SHOP - DAY instead of INT. COFFEE SHOP - DAY — they're just not thinking of the slugline as a field with a fixed value.

How the Same Location Ends Up With Three Sluglines

Drift rarely happens in one sitting. It accumulates across drafts, across the writer's own memory of how they typed it last time, and across the exact scenarios a slugline is supposed to handle cleanly:

  1   INT. COFFEE SHOP - DAY

  ...

 41   INT. THE COFFEE SHOP

  ...

 88   INT. COFFEE SHOP - LATER THAT DAY

Three sluglines, one physical set, and three different reasons it happened: the definite article "THE" got added on a later pass because it read more naturally in isolation; the time-of-day field got dropped entirely on page 41 because the writer assumed continuity was obvious from context; and page 88 introduced a new time-of-day phrase that isn't one of the handful of conventional values a parser or a scheduler expects.

The Three Most Common Drift Patterns:

What Inconsistent Sluglines Break Downstream

None of these three patterns are dramatic on their own. The damage is cumulative, and it lands on exactly the numbers a production depends on to plan:

This is the same failure mode we describe in the source line problem: a downstream number that looks authoritative — a scene count, a location count, a shoot-day estimate — but can't actually be traced back to a clean, consistent read of the script it came from. Slugline drift is one of the most common ways that trust gets broken before the shot list stage even begins.

A Simple Discipline for Keeping Sluglines Clean

None of this requires new software or a formatting course. It requires treating a slugline as a value you look up, not a phrase you retype from memory.

Keep a Running Location Key

The moment a location is introduced, write down its exact slugline text somewhere outside the script itself — a sidebar, a notes doc, anything. Every future scene at that location gets copy-pasted from the key, never retyped. This single habit eliminates the article problem and the renamed-location problem almost entirely, because the temptation to improvise a slightly different phrasing disappears when the correct one is one paste away.

Restrict Time-of-Day to a Fixed Vocabulary

Pick a short, closed list — DAY, NIGHT, CONTINUOUS, LATER — and don't invent variants. If a scene genuinely needs to convey "a few hours after the previous one," that's a note in the action line, not a new value in the slugline's third field. A field that only ever holds one of four values is trivial for a human or a tool to parse correctly. A field that holds free text defeats the purpose of it being a field at all.

Do a Slugline-Only Pass Before You Call a Draft Final

Read through the script once, ignoring everything except scene headings, and check each one against your location key. This pass takes minutes on a short script and catches drift that's easy to miss when you're reading for story, dialogue, or pacing at the same time — which is most of every other read-through you'll ever do.

Format Hygiene Isn't Pedantry

It's tempting to treat slugline consistency as a screenwriting-class rule with no real stakes — the kind of thing a script reader might dock you for, but nothing a production actually feels. That's backwards. A slugline is the one line in a script explicitly designed to be machine-readable: fixed fields, fixed order, all caps, on its own line. Treat it as loose prose and you throw away the one piece of your script that was built to be parsed cleanly.

Fix the sluglines, and every downstream count — scenes, locations, day/night splits — starts from the same clean read, whether the thing doing the reading is a spreadsheet, a first AD, or an AI pipeline building your shot list.