How to Know If Your Pacing Is Off (Without Hiring an Editor)

You know that feeling. You're rereading chapter fourteen for the ninth time and something is... off. The story isn't broken. The scenes make sense. The characters are doing things. But the whole section feels like walking through wet concrete.

Your gut says pacing. Your gut is probably right. But "fix the pacing" is about as useful as "write better." Where, specifically? And what KIND of pacing problem?

Every writer who's revised a novel has been in this exact spot. Most just... move things around until it feels less bad. Which is a strategy, technically. The way throwing darts blindfolded is a strategy.

So let's talk about what pacing actually IS in fiction, how to diagnose specific problems yourself, and when you might want a second set of eyes (even if those eyes aren't attached to a $4,000 editor).

What pacing really means and it's not just speed

Most writers think pacing means "how fast the story moves." That's part of it. But only part.

The best craft frameworks address this directly. Pacing is about TURNS. Every scene should contain at least one value shift. Something changes between the beginning of the scene and the end. A character enters hopeful and leaves angry. A relationship starts warm and ends fractured. Information arrives that changes the stakes.

When scenes turn, pacing moves. When they don't, it stalls.

Progressive complication is the related principle. Turns should escalate. Each scene should build pressure beyond what came before. The story accelerates as tensions compound and stakes increase. When you've got a stretch of chapters where the complications plateau (or worse, where scenes end at roughly the same emotional register they started), the reader registers it as drag. They might not know WHY it feels slow. But they'll tell your beta reader "the middle lost me."

And the beta reader will pass that along, helpfully, without any additional context. Because that's the gig.

The scene-sequel rhythm matters for pacing

The scene-sequel model is probably the most practical pacing framework available. The short version: your fiction alternates between SCENES (goal, conflict, disaster) and SEQUELS (reaction, dilemma, decision).

Scenes are where things happen. Tension, confrontation, plot movement. Sequels are where your character processes what just happened, weighs their options, and decides what to do next.

The pacing issue? Most writers who struggle with a dragging middle are writing too many sequels. Or writing sequels that run way too long. The character reflects... and reflects... and reflects some more. Internal monologue stretches across three pages. The reader already understood the emotional stakes on page one of that reflection. The next two pages are just the writer making sure.

The fix isn't to cut all the sequels (you'd lose emotional depth). The fix is to check the RATIO. How much scene vs. sequel do you have in the problem section? If you've got four consecutive chapters where nothing external happens and the POV character is just thinking and feeling... yeah. That's your pacing problem.

On the flip side, all scene and no sequel reads as exhausting. Relentless action without processing time makes readers feel unanchored. They need a breath. They just don't need a nap.

Five signs your pacing is off

OK, so how do you actually diagnose this in your own manuscript? Here's what to look for.

1. Scenes that don't turn. Read through a suspect chapter and ask: what changed? If the answer is "nothing, really" or "the character learned something they (and the reader) already knew," the scene isn't earning its page count. The value shift test is brutal but honest.

2. Sequel bloat. Flag every passage of extended internal monologue or reflection. Are they earning the space? Or are you over-explaining emotions the reader already grasped from the scene itself? Two paragraphs of sequel after a tense confrontation might be perfect. Two pages might be a problem.

3. Repetitive emotional beats. Your character feels worried in chapter ten. And chapter eleven. And chapter twelve. Same worry, same internal churn, no new information. The pacing isn't technically slow here... but it FEELS slow because the emotional register isn't progressing.

4. Missing escalation. Read your chapter endings in sequence. Do the stakes go up? Does each complication push harder than the last? If you can rearrange four consecutive chapter endings without anything feeling out of order, your progressive complication has stalled.

5. Scene openings that re-establish instead of launching. If every scene starts with a paragraph of orienting description before anything happens (where we are, what time it is, what the weather's doing), that's cumulative drag. One or two of those is fine. Ten in a row is a pacing tax the reader pays every chapter.

The problem with self-diagnosis

Here's the honest part. Everything above is real. These checks work. But there's a catch, and it's a big one.

You can't feel pacing accurately in your own manuscript after your fifth read-through.

You just can't. You know what's coming. You know the big reveal in chapter twenty. You know the slow build is worth it. So when you reread the slow build, it doesn't FEEL slow to you... because your brain is already anticipating the payoff. You've lost the ability to experience the text the way a first-time reader will.

This is why writers have always relied on outside readers. An alpha reader who can evaluate craft, or a developmental editor who charges accordingly. Somebody who encounters your chapter fourteen cold and can tell you, objectively, whether those scenes turn.

The traditional options are: pay $3,000 to $5,000 for a developmental editor (and wait weeks or months for the report), or hand it to beta readers and hope someone can articulate what "the middle felt slow" actually means.

Neither option is bad. But there's a gap between them that most writers just... live with.

What a pacing analysis actually looks like

Pacing analysis is the systematic evaluation of scene structure, sequel length, value shifts, and progressive complication across a manuscript to identify where narrative momentum stalls or accelerates unnaturally. Effective pacing analysis checks each scene for a measurable turn, maps the scene-to-sequel ratio by chapter, and tracks whether stakes escalate across story movement.

When someone (or something) does a proper pacing analysis, you should get specifics. Not "the middle is slow." You should see WHICH scenes lack turns. Which chapters are sequel-heavy. Where the progressive complication flatlines. What the scene-to-sequel ratio looks like across the full manuscript.

That level of detail is what you'd get from a really good developmental editor. It's also what an alpha reader with craft training would flag.

And it's what FirstReader was built to do. The tool runs a rules-based analysis across your entire manuscript, checking each scene against established craft principles covering scene turns, progressive complication, scene-sequel rhythm, and show vs. tell. Every finding traces to a named principle. You get a craft report, not a vague opinion.

I built FirstReader because I needed it. An alpha reader that could evaluate pacing systematically, cite why, and do it in under an hour instead of six weeks... that's the tool I wanted.

What this won't replace

A tool can map your pacing structure. It can identify scenes that don't turn, sequels that overstay, and escalation gaps. What it can't do is tell you HOW to fix it. That's still you. The craft decisions, the creative instincts, the understanding of what YOUR story needs at that moment in the narrative... that's writer work.

A developmental editor gives you both the diagnosis AND suggestions for treatment. FirstReader (and any alpha reader, human or otherwise) gives you the diagnosis. The treatment plan is yours to write.

For a lot of writers, the diagnosis is the part they're missing. They can fix it once they can SEE it.

Try it on a chapter

If you're sitting on a manuscript right now and the middle feels soft... try running a single chapter through FirstReader's free chapter analysis. See what it flags. See if the pacing findings match your gut.

If they do, you've got a starting point. If they don't, well... that's diagnostic information too.

Final words

Pacing problems are real, they're common, and they're almost impossible to see in your own work after a few drafts. The craft frameworks exist and have been refined over decades. The diagnostic checklist above will help. But the honest truth is that pacing is a manuscript-level problem, and manuscript-level problems need manuscript-level analysis.

Whether that comes from a developmental editor, an alpha reader, or a rules-based analysis tool... get a second perspective before your beta readers do. They'll tell you it's slow. They won't tell you why.

If you found this useful, leave a comment and let me know. If you didn't... well, I'd like to hear that too.

If you haven't already, feel free to subscribe so you don't miss anything!