Knowing that a screenplay is a blueprint is one thing. Actually building one — getting the mechanics right, line by line — is another. This is where a lot of new writers stall out: not because they don't understand why format matters, but because nobody ever walked them through exactly how each element is supposed to work.
So let's get specific. Not the big picture this time — the actual mechanics.
Anatomy of a slugline
A slugline (or scene heading) is the all-caps line that opens every new scene. It follows a strict three-part structure, always in the same order:
INT. or EXT. — Interior or exterior. This tells production whether the scene is shot on a soundstage or built set (interior) or on location outdoors (exterior). It's the single most load-bearing abbreviation in the entire script, because it's often the first sort criterion production uses when grouping scenes for shooting.
Location — Specific enough to be useful, general enough to be reusable. "KITCHEN" is fine if there's only one. "SARAH'S KITCHEN" is better if there might be more than one kitchen in the script. Vague locations create real headaches during location scouting and scene grouping.
Time of day — Almost always DAY or NIGHT. Not "7:42 AM" or "late afternoon." This isn't about being literal — it's shorthand for lighting setup, which is one of the most expensive and time-consuming parts of any shoot. DAY and NIGHT are the two conditions a lighting department actually plans around.
Put together: INT. SARAH'S KITCHEN - DAY. That's it. That's the whole formula, and it doesn't change no matter how big or small the production is.
One habit worth building early: every time you introduce a genuinely new location or a meaningful jump in time, it gets its own slugline. This is one of the first things a first AD uses to build a shooting schedule, so a sloppy or inconsistent slugline habit doesn't just look unpolished — it makes the script measurably harder to break down.
Writing tight, visual action lines
Action lines describe everything that isn't dialogue: what we see, what we hear, what happens. The single governing principle is simple to state and hard to practice: if a camera can't capture it, it doesn't belong in an action line. That being said, sometimes rules are also meant to be broken.
That rules out interior monologue ("she wonders if she made the right choice"), backstory dumps ("he's never told anyone about the accident that changed everything"), and any kind of authorial commentary. All of that might be true of the character, but none of it is visible on screen — so on the page, it's dead weight. Again, sometimes rules are meant to broken.
A few habits separate tight action writing from bloated action writing:
- Short paragraphs. Long blocks of unbroken text are hard to read at pace and hard to skim during a table read or breakdown. Three or four lines is usually a natural ceiling.
- Present tense, active voice. "Sarah grabs the keys and bolts for the door" reads faster and plays faster than "The keys are grabbed by Sarah as she begins to bolt toward the door."
- Specific, chosen verbs. "Storms out" tells you more than "walks out quickly," in fewer words.
- White space is a tool, not a failure. A page that looks sparse often plays fast on screen. That's the goal, not a problem to fix.
New character introductions get a small formatting convention of their own: the character's name in ALL CAPS the first time they appear in an action line, along with a brief, purposeful description — usually age and one or two telling details. Not a whole paragraph. Just enough for a casting director to start forming a picture.
Dialogue block formatting and character cues
Dialogue has its own indented, centered column, distinct from action, so a reader can visually separate "what's said" from "what's happening" at a glance — this matters enormously during a table read, when actors are scanning the page for their own lines in real time.
The character cue (the character's name, in all caps, centered above their line) carries a few conventions of its own:
- (CONT'D) appears when the same character speaks again immediately after an action line interrupts their own dialogue, signaling to the reader that it's a continuation of the same speech, not a new thought.
- (V.O.) marks voice-over — a character heard but not physically present in the scene, like narration.
- (O.S.) marks off-screen — a character's presence outside the visible frame, like someone's voice on a phone call, answering machine or news report.
- (O.C.) marks off-camera — a similar but subtle difference where a character is present and speaking in the scene but not visible in the frame, like shouting from another room.
These aren't interchangeable, and using the wrong one is a small but noticeable tell that a writer hasn't spent much time around a working script.
Parentheticals: when to use them (rarely) and why
A parenthetical is the short, italicized-in-spirit direction that sits beneath a character cue and above their line — things like (beat), (sarcastic), (to Marcus). They exist to clarify something the dialogue alone can't convey, usually who a line is directed at, or a tonal turn that would otherwise be genuinely ambiguous on the page.
The operative word is rarely. Overusing parentheticals is one of the fastest ways to read as an inexperienced writer, for a simple reason: it utlimately signals a lack of trust in the actor to find the right delivery, and in your own dialogue to carry its own tone. If a line needs "(angrily)" to land as angry, the more useful fix is usually to rewrite the line itself so the anger is already built into the words.
A good gut check: if you can delete the parenthetical and the scene still reads clearly, just delete it.
Common formatting mistakes that flag a script as amateur
A handful of patterns show up again and again in early drafts, and experienced readers clock them almost instantly:
Inconsistent character names. A character introduced as "DETECTIVE MARA REYES" who becomes "MARA," then "REYES," then "DETECTIVE REYES" across different scenes creates confusion for a reader who is trying to track a cast, not solve a puzzle. Pick one name per character and stay with it. This is especially important for script breakdowns and tools like WorkstationOS to be able to accurately categorize speaking roles and cast lists.
Sluglines that don't earn their place. Creating a brand-new slugline for a two-line beat that's really still part of the same scene fragments the read and inflates page count in a way that throws off the page-to-minute estimate.
Directing the camera. Terms like "we see," "camera pans to," or "close on" are directing instructions, not writing. In a spec script, that's not the writer's job, and it reads as someone who hasn't yet learned where the line sits between story and direction. Some writers are also directors, and some key shots are important to impress upon the reader — however, use these notes sparingly if you are not intended to be an auteur.
Dialogue that over-explains. Characters who say exactly what they're feeling, or explain information the audience already has, are a common early-draft habit. Real dialogue almost always does more by saying less. You might hear the term "on-the-nose", and it's the mark of an amateur writer who hasn't had enough time to hone their craft.
Ignoring the page-to-minute rule. A script padded with excessive white space, or crammed with dense single-spaced blocks to hit a target page count, distorts the runtime estimate everyone downstream is relying on — and it's usually obvious to an experienced reader within the first few pages. You don't need to include "CUT TO:" after every scene, because we can assume that will happen.
Mechanics in service of the read
None of this is about rigid rule-following for its own sake. Every convention here — sluglines, action, dialogue blocks, parentheticals — exists to make a script easier to read, easier to break down, and easier to shoot. Get the mechanics right, and they stop being something a reader notices at all. That's the actual goal: format that disappears, so the story is the only thing left on the page.