Why Your Scenes Don't Flow

The note that finally broke me on my third draft was two words: "doesn't flow." My screenplay's scenes don't flow — I'd heard it twice before, from two different readers. Both times I nodded and went back and polished individual scenes. Made the dialogue crisper. Tightened the action lines. Sent it back. Got the same note. The scenes were fine in isolation. The script read like someone had shuffled a deck of loosely related cards and called it a story.

It took me an embarrassingly long time to understand what was actually wrong. Flow isn't about the quality of individual scenes. It's about the connective tissue between them — the invisible logic that makes one moment lead inevitably to the next. When that logic is missing, the script advances in stops and starts instead of building momentum.

Here's what I learned about fixing it.

The "and then" test: where your scene flow is breaking down

The clearest diagnostic for scene flow I've found comes from Trey Parker and Matt Stone, who described it in terms of scene transitions. If you summarize your story and every scene connects with "and then," you have a list, not a story. "He confronts his father, and then he goes to work, and then he meets a stranger, and then he decides to leave." Nothing causes anything. The story is just a sequence of events that happen to a person.

The fix is to replace "and then" with "therefore" or "but." "He confronts his father, therefore he can't face going to work, but when he tries to leave town he meets someone who changes everything." Now each scene is generating the next one. Causality is flow.

Go through your outline — or write one out from your existing draft — and try to connect each scene to the next using "therefore" or "but." Every place you can only manage "and then," you've found a gap. That gap is where flow dies. Some gaps you can fix by adjusting what a scene does at its end; some you fix by cutting the scene entirely; some reveal that you need a scene you haven't written yet.

What happens at the end of each scene matters as much as what happens in it

Scenes that flow well tend to end before resolution — on a question, a new piece of information, a decision that hasn't played out yet, a complication that just arrived. They don't wrap up tidily and hand the baton to the next scene. They end with a slight lean forward, with something unresolved that the next scene will have to answer.

Read the last paragraph of each scene in your script. Does it close a door or open one? Does it give the audience a reason to keep reading, or does it release all tension before the page turns? If your scenes consistently end on resolution — the argument is over, the deal is done, the character has processed everything — you've trained the reader to stop caring between pages. Each ending should make the next scene feel necessary.

Scene endings are where flow is won or lost. End before resolution, not after it.

Enter late, leave early — and mean it

You've probably heard this advice before. Enter scenes late, leave them early. Cut the arrivals and departures. Trust the audience to fill in the gaps. It's good advice, but it's easy to understand intellectually and hard to actually do, because the instinct to show everything — the character arriving, settling in, beginning the conversation, finishing the conversation, standing up, leaving — is almost irresistible.

Here's how I force myself to do it: after writing a scene, I delete the first paragraph. Then I read the scene again. Does it still make sense? Almost always yes. Then I delete the last paragraph. Same question. Usually the answer is still yes. The scene that remains is almost always tighter and better connected to what surrounds it.

The material in those deleted paragraphs was setup and cleanup — the scaffolding the writer needed to find the scene, not the scene itself. Readers don't need the scaffolding. Leaving it in is one of the most common reasons scenes feel sluggish and disconnected from each other.

Emotional continuity is as important as plot continuity

Even when the plot logic of your scene transitions is sound, flow can break if the emotional logic doesn't hold. A character who ends one scene in genuine grief and opens the next in high spirits — with no visible cause for the shift — creates a seam the audience feels even if they can't name it. Something is off, and they know it, even if they can't point to it in the script.

Tracking emotional continuity across scenes is different from tracking plot. You're not asking "what caused this event?" You're asking "what is this character carrying from the last scene into this one, and is it showing?" Sometimes the carry is explicit — they're still shaken, still angry, still distracted. Sometimes it's a single line of subtext in their first exchange. Sometimes it's just the physical behavior the actor would bring to the scene if they understood the previous one.

When I'm doing a flow pass on a draft, I go character by character and track their emotional state at the end of each scene, then check whether the opening of the next scene they appear in accounts for it. Where there's a mismatch, I figure out whether the gap is intentional — does something happen offscreen between scenes? — or whether I've just lost the thread.

Reading your script aloud, scene by scene, is the fastest way to feel where emotional continuity breaks down.

The structural causes of broken flow

Sometimes flow problems aren't caused by how individual scenes are written — they're caused by what those scenes are doing in the larger structure. A sequence of scenes that are all doing the same dramatic work will feel like a treadmill no matter how well each individual scene is executed. If you have five consecutive scenes where your protagonist is losing ground, or five scenes where a relationship deteriorates, the sameness creates drag even if each scene is competently written.

Flow requires rhythm — variation in scene length, tone, intensity, and function. A heavy dramatic scene followed by a brief, lighter transition followed by an action-driven scene reads completely differently than three heavy dramatic scenes in a row. Think of it like music: you need dynamic range, not just sustained volume.

Look at your script's structure on the macro level. Map out the emotional register of each scene — tense, light, confrontational, quiet, revelatory, comedic — and see what the pattern looks like. If you see long runs of the same register, that's often the hidden cause of flow problems that can't be fixed at the scene level.

Running the "therefore/but" pass on a finished draft

When I'm doing a flow pass on a complete draft, I work in Scrivener with the script in the binder and a notecard for each scene. On each card I write the scene summary in one sentence. Then I go through the cards and literally write the connective word between each one: "therefore," "but," or — if I have to — "and then."

Anywhere I write "and then," I flag it. Then I go into the script and figure out how to create causality where none currently exists. Sometimes that means adjusting what a character learns or decides at the end of a scene. Sometimes it means adding a single line of dialogue that makes the consequence explicit. Sometimes it means cutting a scene entirely because it was never connected to anything — it was just happening.

The pass takes a day or two on a feature draft. It's one of the most useful things I do in the revision process, because flow is the thing that makes all the other work matter. A script full of strong individual scenes that don't connect is still an unpleasant read. Connect those scenes with genuine causality and the whole thing changes register — it starts reading like a movie, not like a collection of moments someone decided to put in sequence.

That's the difference between a script that generates "the scenes don't flow" notes and one that generates "I couldn't stop reading." The scenes might be identical. The tissue between them is not.

← All articles