Mastering Pacing

A development executive once gave me notes that still bother me, not because they were harsh, but because they were precise: "The problem is I know exactly what's coming three pages before it arrives." She wasn't complaining about the plot being predictable. She was diagnosing pacing. The script was moving at a single steady tempo, like a song stuck on one note, and the flatness of it made the story feel smaller than it was.

Pacing is the rhythm of a screenplay — how fast it moves, when it accelerates, when it breathes. And it's one of the most misunderstood craft elements because bad pacing is usually diagnosed as something else: "the second act drags," "the ending feels rushed," "the opening is slow." Those complaints are almost always pacing problems in disguise. Here's how I've learned to hear them, diagnose them, and fix them.

Pacing is variation, not speed

The biggest misconception about pacing is that good pacing means going fast. It doesn't. A script that moves at one constant speed — even a fast one — becomes monotonous. The art is in the contrast: a quick, pressurized sequence followed by a quiet breath, a slow build that suddenly snaps. The peaks land because of the valleys around them.

I spent two years writing scripts that were consistently fast and consistently unengaging. The notes I kept getting were all about "energy" — the scripts needed more energy, more momentum. I kept solving this by cutting more, moving faster, getting to the action sooner. The scripts got worse. What they needed wasn't speed; they needed variation. They needed to earn the fast moments by slowing down beforehand.

Think of pacing as managing the audience's energy. After an intense sequence, they need room to breathe and process. Before a climax, tension needs somewhere to build from. The rhythm of your story is the rhythm of those contrasts — and sustaining it across 90 to 120 pages is a structural project, not a prose project.

How screenplay pacing actually breaks down

When I look at a script with a pacing problem, I first identify which kind it has. They're different diseases requiring different treatment:

Dragging pacing happens when scenes don't move the story forward, when dialogue runs twice as long as it needs to, or when the script keeps arriving at the same emotional beat repeatedly without escalating. The audience starts checking out not because they're confused but because nothing new is at stake.

Rushed pacing is the opposite: important emotional beats that need space get crammed into a scene or skipped entirely. A character makes a major decision in one quick exchange that should have taken three scenes to earn. The story arrives at its destination before the audience understands what it means. This is where the complaint "the ending felt unearned" almost always comes from.

Both are fixable, but you have to know which one you have before you touch a scene. Cutting to fix dragging when you actually have rushing makes a script that moves fast and feels hollow. Slowing down to fix rushing when you actually have dragging produces a script with beautiful emotional depth and a 170-page count.

Scene length controls everything

The most direct lever available to a screenwriter controlling pacing is scene length. A run of short scenes — half a page, one page — accelerates the feel of the story regardless of what those scenes contain. A three-page scene slows the clock down and asks the audience to settle in. Varying scene length deliberately is how you create rhythmic contrast on the page.

I didn't understand this viscerally until I went through a draft and mapped my scene lengths in a spreadsheet. I had a 22-page second act run where every single scene was between one and two pages. Every scene. Same tempo, over and over. No wonder it felt monotonous — it was metronomically regular. Identifying three scenes that could grow to three or four pages, and cutting two others to a quarter-page, broke the monotony without changing a single story beat.

The other thing scene length reveals: your act structure. If all your long scenes are clustered in the first act and your third act is almost entirely short scenes, you've accidentally written a script that starts slowly and ends in a blur. The long scenes — the ones that earn patience from the audience — should live near the moments that need to land hardest.

Mapping your scene lengths in outline form — even roughly — reveals pacing patterns you can't see reading the script linearly.

The five-page rule for diagnosing a slow second act

When the second act feels like it's dragging, there's a test I run before cutting anything. I take the act and identify every scene where nothing changes — scenes where the character ends in the same emotional or situational place they started. Then I ask: what would be lost if this scene didn't exist?

If the honest answer is "not much," the scene is doing maintenance work — keeping characters in the same holding pattern — and that's where pacing dies. The fix isn't always cutting. Sometimes it's merging two maintenance scenes into one, or finding the decision or revelation that should be in one of them to give it a turn.

I wrote about the mechanics of this in detail in the piece on why your scenes don't flow, but the principle is simple: dragging pacing is almost always caused by scenes without turns stacking up. A scene that ends differently from how it began takes the story somewhere, and a story that keeps going somewhere doesn't drag.

Where rushing comes from and how to fix it

Rushed pacing almost always comes from one source: the writer knows where the story is going, so they unconsciously write toward the destination faster than the audience can follow. You've lived with these characters for months. You know the relationship. The scene where they finally forgive each other feels obvious to you, so you write it in half a page, and readers feel cheated.

The fix isn't adding dialogue. It's identifying the emotional steps the audience needs to take before they arrive at the beat, and making sure those steps are actually in the script. For that reconciliation scene to land, the audience needs to have felt the weight of what's being forgiven. That weight has to exist in earlier scenes, specifically and viscerally. If it doesn't, the fix is upstream — going back to the scenes before the emotional climax and doing the setup work, not stretching the climax scene itself.

This is why I always do a pacing pass after a structural pass, never before. Pacing problems are almost always structural problems that look like timing problems. The scene isn't too short; the preparation for the scene is missing.

The rewrite tools I actually use for pacing

After completing a draft, I do a dedicated pacing pass that's separate from everything else. Here's the actual workflow:

First, I open a new document and write one line per scene: what the scene is, how long it is, and whether something changed by the end. This gives me a map of the whole script in about two pages. Pacing problems that were invisible in the full draft become obvious on the map: the long plateau in the middle, the place where five scenes in a row have the same emotional temperature, the third act that arrives too quickly.

Second, I look at scene transitions. How a scene ends and how the next one begins creates the reading rhythm. A scene that ends on a quiet beat and a scene that opens on a quiet beat creates a valley that's too long. Varying the temperature of scene transitions — ending a tense scene by cutting to a calm one, or ending ambiguously and cutting to urgency — is how you shape the reading experience moment to moment.

Third, I check the rewrite pass I did on individual scenes. Sometimes a scene-level polish — trimming the front and back, tightening the dialogue — is enough to fix a pacing problem without touching the structure at all. The most common quick fix: cutting the first quarter-page of every scene in the slow stretch. Just removing the throat-clearing at the top of scenes frequently restores momentum to an act that felt stuck.

Pacing lives in the edit — both the story edit on the page and the cut from scene to scene. The rhythm is built in revision, not first draft.

Why the "slow burn" excuse doesn't hold up

Writers with slow scripts often defend them as slow burns. Sometimes that's accurate — genuinely slow-burn storytelling is a legitimate tonal choice and audiences who sign up for it know what they're getting. But slow-burn is a specific register that requires being intentional about the slowness: building dread or anticipation deliberately, using quietness as pressure rather than absence.

The difference between slow-burn pacing and simply dragging pacing is whether the slow stretches are doing work. In a genuine slow burn, the quiet scenes are accumulating texture, establishing stakes, building unease. In a dragging script, the quiet scenes are just… quiet. Nothing is accumulating. Nothing is building. The audience isn't patient — they're waiting.

The test I use: read the slow section and ask whether the tension is increasing or holding steady. In a slow burn, tension increases even as action decreases. In a dragging script, both are static. That distinction is everything.

Pacing as an audience contract

The audience makes a deal with a script in the first ten pages. They read the opening speed, emotional temperature, and scene length as signals about what kind of experience they're in for. If your first act moves fast and light and your second act suddenly becomes slow and interior, you've broken the contract — even if both parts are well-written individually.

This is why I pay particular attention to tonal and rhythmic consistency in the overwriting pass. It's not just about removing excess; it's about making sure the texture of the writing matches the pace the story needs. Overwritten action lines slow the read even when the scene itself is short. Streamlined, white-space-heavy pages read faster than dense ones, physically. The visual rhythm of the page is part of the pacing.

Good pacing is invisible when it works. The audience simply feels the story moving the way it should — never aware of being managed, never aware of the scene lengths or the transition temperatures or the deliberate breathing room before the climax. That invisibility is the goal. It gets built scene by scene, beat by beat, in the rewrite — which means it never gets built in the first draft, and that's fine. First drafts are supposed to have pacing problems. Rewrites are for solving them.

← All articles