Happy Wednesday, Reader,

Before I get into today’s newsletter, I want to be honest with you about something. Last week I told you we’d spend this issue looking at how readers feel the gap between scene level and big picture plot before they can name it, and I’ve changed my mind about that. I realized halfway through drafting it that it actually needs its own arc rather than a single issue tucked inside this one. It deserves more room than I was giving it, and squeezing it in here was going to shortchange both the topic and you.

So instead I want to go back to something I opened a door on last week and then walked straight past. I told you the word plot gets used to mean at least three different things depending on who’s talking, and that most of the confusion writers run into starts right there, and then I defined plot against theme, moved on, and never even mentioned the third word doing damage in that same sentence. Premise.

I actually think this ends up being the more useful issue for where we are in the arc, because it’s a confusion I watch trip up writers constantly, not just in queries and back cover copy, but quietly in their own heads while they’re drafting. If you’ve ever sat down to explain your book to someone and reached for the wrong word, or felt certain you had a great idea only to discover ninety thousand words later that you somehow didn’t have a story, this is probably why.

What premise actually is

Premise is the what if. A mercenary is sent to kill a mortician and falls for him instead, or a woman inherits a bookstore from an aunt she never met, that sentence you’d give a stranger at a party who asks what your book is about, the line on the back cover that makes someone pick it up off the shelf in the first place.

It’s genuinely useful too. A strong premise creates curiosity and promises a reader a kind of story before they’ve read a single scene of it, which is exactly why writers reach for it so naturally when they’re asked to describe their own work. But a premise on its own can’t fill three hundred pages, because a premise is a situation, and a situation, left alone, doesn’t move.

I think back to a manuscript I beta read, near future AI science fiction, the writer told me when I asked what it was about, and once I got into the ninety one thousand words behind that description, with eighty thousand of them arriving before an actual plot inserted itself, I understood exactly why he’d reached for a category instead of a plot when I’d asked him directly. There wasn’t one yet, not in any sense I could point to. There was a fully imagined world and a premise full of potential sitting inside it, and he could talk about that world for an hour without ever once telling me what actually happened in it.

That’s the tell I want you to listen for in your own answer when someone asks what your book is about. If what comes out is a situation, a world, a dynamic between two people, you’ve described your premise, and that’s not a failure so much as a sign that the plot still needs to be named as its own separate thing, because right now it’s hiding inside the setup instead of standing apart from it.

What plot actually is

We’ve already built this vocabulary over the last three weeks, so I won’t rebuild it from scratch here. Plot is the chain, problem, solution, problem, running at the scene level, and it’s the transformation that chain is quietly building toward underneath. The mercenary and mortician’s premise is the sentence above. Their plot is everything we spent those three weeks tracing, the investigation that unravels into a trafficking ring, the mercenary losing the story he’d built his entire identity on, the mortician claiming a truth about himself he wouldn’t have had permission for on page one. None of that lives inside the premise sentence, even though all of it grew directly out of it.

I think this is where a lot of writers get stuck without ever quite realizing it. A premise implies a plot roughly the way a seed implies a tree, and it’s easy to mistake that implication for the thing itself, to sit with a gorgeous premise for months, falling more in love with the situation, without ever forcing it to actually move. The fortress book I told you about on the first email of the August arc is the extreme version of this. Eight people trapped together with a vague sense that something was coming is a premise too, and an intriguing one at that, but nothing in those eighteen chapters ever converted it into a real chain of problems and solutions. The book just sat inside its own situation instead of moving through it.

What theme actually is

Theme gets flattened into plot even more often than premise does, and I think that’s because theme is genuinely easier to hold onto. It’s a single idea underneath everything that happens, rather than a record of the things that happen, the question your story is actually arguing about, the thing that would still be true even if you changed every surface detail of the plot and kept the same bones underneath it.

Go back to the mercenary and the mortician one more time. Their premise is the setup, their plot is the investigation and the transformations we’ve already traced, and their theme is something closer to this: love a person all the way or none of you gets to be safe, and safety built on hiding parts of yourself was never actually safety to begin with. You can’t point to a chapter and say, there’s the theme, the way you can point to a chapter and say, there’s where he investigates the funeral home, because theme lives underneath every scene at once or it doesn’t really live in the book at all.

It’s much easier to tell someone your book is about found family than it is to actually trace what happens, in order, because of what, which I think is exactly why theme so often gets handed over in place of plot when a writer is asked to describe their own work. But when a writer describes their book primarily by its theme, what I usually find underneath is a manuscript where the idea gets stated more than it gets earned, characters saying things like family isn’t about blood out loud, because the theme got treated as the thing to communicate directly instead of the thing the plot was supposed to prove through what actually happens to these specific people.

Why the confusion actually costs you something

Here’s what I think is really at stake in keeping these three words straight. If you believe you have a plot when you actually only have a premise, you’ll sit inside the setup for eighty thousand words, waiting for something to happen that you’ve never forced into motion yourself, the way that AI manuscript did. If you believe you have a plot when you actually only have a theme, you’ll write scenes that state your idea rather than dramatize it, and readers will feel lectured instead of moved without always being able to say why. And if you can’t tell your premise from your plot from your theme in your own head, query letters get harder to write, back cover copy gets harder to write, and revision gets hardest of all, because you can no longer tell which layer of the book is actually broken when something in it isn’t working.

This week’s exercise

Take the manuscript you’re working on and write three separate sentences describing it, one for premise, the setup, the what if, one for plot, the actual chain of events and the transformation underneath it, and one for theme, the argument your story is making, stated as a claim rather than a topic. If two of those three sentences end up looking nearly identical, sit with that for a minute. It usually means one of those layers hasn’t actually been built yet and has just been standing in for the layer that has.

Next week we bring this whole month together and actually test your own manuscript against all of it, premise, both layers of plot, and now theme too, and I want to do that as something closer to a way of finally seeing your own book at the distance it takes to know what’s really there, not as a checklist you run through and forget.

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

​