Happy Monday, Reader,

Last week I told you there are two kinds of plot stacked on top of each other in every story. Scene level plot, the engine, problem, solution, problem. And big picture plot, the thing all those problems and solutions are supposed to be building toward. I told you most manuscripts I read are missing the second layer even when the first one is technically running.

This week I want to show you exactly what that looks like, because it’s sneakier than it sounds. A manuscript with a broken engine is easy to spot. Nothing moves, nothing escalates, you can feel it stalling by chapter three. A manuscript with a broken big picture plot is harder to catch, because chapter by chapter, everything seems to be working.

I beta read a contemporary romance last year that’s stayed with me for exactly this reason.

The engine that ran perfectly

Two people meet. He’s still in a relationship with someone else when it happens. Not on the way out, not drifting, still in it. She and he start orbiting each other anyway, work, tea, class, coffee, work, the pub, wine, work again. For roughly two thirds of the manuscript, that’s the shape of it. A rotation of ordinary scenes, over and over, while he stays with someone who isn’t her.

Here’s the part that made this one hard to diagnose at first. Every single one of those scenes worked on its own terms. Problem, she wants to know if he feels what she feels. Solution, a conversation at the pub that almost gets there. Problem, he pulls back because of the relationship he’s still in. Solution, they fall into an easier rhythm at work instead, safer ground. Problem, that safer ground starts feeling like something anyway. Solution, coffee, more time together, more almost. The chain never actually broke. Each scene hooked, each one moved into the next one, nothing stalled.

If you’d handed me any three of those scenes in isolation and asked whether the engine was running, I’d have said yes without hesitation. That’s what makes this example worth sitting with. The failure isn’t visible at the scene level at all. You have to step back to see it.

What the engine was actually running toward

In a romance, the big picture plot is the couple. Not the events around them, the couple themselves, whether they’re actually moving closer to being together in a way the reader can track and believe in. That’s the thing every scene level engine in a romance needs to be serving, underneath whatever surface conflict is driving each individual scene.

And that’s where this manuscript stalled, even while nothing else did. He was in a relationship for two thirds of the book. Not almost out. In it. Which means for two thirds of the book, the actual big picture plot, the couple, could not move. It could orbit. It could almost. It could ache in that specific way unrequited feelings ache when both people know something is there and neither can act on it. But it couldn’t progress, because progression would have required him to actually leave, and he didn’t.

So every time the relationship was supposed to end, something happened to keep it from ending. Not once. Repeatedly. And I want to be careful here, because this isn’t a note about that choice being wrong on its face. Slow burns work. Longing works. A couple who can’t be together yet is the entire premise of half the romance novels either of us has ever loved. The problem wasn’t that they weren’t together. The problem was that the big picture plot, the actual falling in love between these two specific people, had nowhere to go during all that time, because the thing standing in the way wasn’t circumstance. It was a relationship that kept getting rescued from ending right when it needed to end.

By the time he finally realizes he’s in love with her, it takes something external, an accident, to force the resolution the couple itself couldn’t produce on its own. And then the book ends with them traveling together, which is a lovely image, but it arrives having skipped the part where two thirds of the manuscript’s worth of scenes were supposed to have been building.

Why this is so easy to miss as the writer

I think this happens for a reason that has nothing to do with skill. When you’re deep in a scene, checking whether it works, whether it hooks, whether something happens and something else results from it, you’re checking the right thing. The scene level engine is real craft, and getting it to run at all is genuinely hard. It’s reasonable to feel like the manuscript is working, because in a very real sense, it is.

What’s much harder to see from inside the draft is whether all that working machinery is actually accumulating into anything. A writer can produce forty competent, hooky, well paced scenes and still not notice that none of them were allowed to change the one relationship the whole book is supposed to be about. The scenes felt like progress because each one, taken alone, was progress. Just not progress toward the thing the reader came for.

This is part of why beta and alpha readers exist, honestly. Not to tell you your scenes don’t work, they might work beautifully one at a time, but to read at the distance a writer inside their own draft can’t hold. From that distance, “he’s still in a relationship for two thirds of the book” reads very differently than it does scene by scene. It reads as a big picture plot that’s been stalled the entire time, dressed up in scenes that are individually doing their job.

What I’d have told this writer

Not to cut the longing, and not to cut the orbiting. Those can be the whole appeal of a slow burn done well. What I’d have pushed on is the thing actually blocking the couple. If he’s still in another relationship, that relationship needs to be visibly ending, not paused, not rescued back to life every time it gets close to over, actually eroding in a way the reader can track alongside everything else that’s happening. The big picture plot needs its own problem, solution, problem chain too, even if it moves slower and quieter than the scene level ones sitting on top of it. Right now, only one layer had a chain. The other one just waited for an accident to solve it from outside the story.

This week’s exercise

Take the manuscript you’re working on and name your big picture plot in one sentence, the actual thing the whole book needs to be building toward, not the events, the underlying shift. Now go through your last five scenes and ask, for each one, whether it moved that specific thing forward, or whether it just kept the reader entertained while standing still. Be honest. A hooky scene and a scene that advances your big picture plot are not always the same scene, and the gap between them is exactly what we’re talking about this month.

Next week, we get into how big picture plot actually gets built and planted, so it doesn’t have to arrive by accident.

Maria Acosta Ramirez Alpha & Beta Reader, MAR Literary Services Florida, USA gravatar.com/unabashedd4deba3b56 ​

​