How to Outline a Novel After You've Written It
A reverse outline isn't a summary of what you wrote. It's the first time you read your own book as a reader, and it changes everything about how you revise.
A reverse outline isn't a summary of what you wrote. It's the first time you read your own book.
You know your manuscript the way you know a conversation you had years ago. You were there for all of it. You know what happened, what mattered, what the other person meant even when they didn't say it directly. But if someone asked you to draw a map of it — to show them where the turning points were, where the mood shifted, where the whole thing went sideways — you'd find that the knowledge doesn't work that way. It lives in you, not in front of you.
That's the problem with revising a discovery draft. The manuscript isn't opaque to you. It's too transparent. You wrote every sentence with the full weight of everything that came before it. You can't unknow that. And revision requires exactly the kind of outside view that writing burned away.
The reverse outline is how you get it back.
What a reverse outline actually is
A reverse outline isn't a summary of your manuscript. It's a document you build by reading what you wrote as if someone else wrote it — scene by scene, chapter by chapter — and recording only what's actually on the page, not what you intended or remember being there.
That distinction matters more than it sounds. When discovery writers try to outline their own drafts from memory, they outline the story they meant to write. The reverse outline forces you to account for the story that exists. Those two things are rarely the same.
What you're looking for when you build it: what happens in this scene, whose point of view is it, what changes between the opening of the scene and the close of it, and what does this scene promise the reader: about what's coming, about who these characters are, about what the story is about. Write that down. Move to the next scene. Repeat.
By the time you're done, you have something you've never had before: a map of the book that actually exists, not the one you've been carrying in your head.
How to do it
The process is slow and a little uncomfortable, and that's not a bug. The discomfort is information.
-
Work from the manuscript, not your memory. Open the document. Read each scene as if for the first time. Resist the urge to edit as you go: you're not here to fix anything yet, you're here to see.
-
Write one to three sentences per scene. Not a summary of what you intended — a record of what's on the page. What happens. What changes. If nothing changes, write that down too. That's the one that matters.
-
Track whose scene it is. Note the POV character for each scene. You're looking for characters who disappear for long stretches, and for scenes where the POV shifts in ways you didn't notice while writing.
-
Mark the promises. Every scene makes implicit promises to the reader: about what will happen next, about what this character wants, about what kind of story this is. Write them down. You'll come back to this list when you're looking for what the middle of your book is or isn't delivering.
-
Don't stop when it gets hard. The scenes that are hardest to reduce to a sentence are the scenes where the least is happening. That difficulty is the reverse outline doing its job.
For a closer look at what to write for each scene — what to track, what patterns to look for, and what to do before you open the manuscript to revise — the scene-by-scene guide goes deeper on the mechanics.
What it reveals
Here's a thing that happens often enough to be worth naming. You're working through your reverse outline, scene by scene, and somewhere around chapter four you write something like: Mara tells Daniel about her brother's accident. He doesn't know the family yet. You note it. You keep going. Then thirty scenes later you write: Daniel confronts Mara about keeping secrets from him. And you stop, because you remember — he already knew. You told the reader he knew, back in chapter four, and then you wrote twenty chapters as if he didn't.
That's not a continuity error you would have caught in a normal reread. You knew Daniel knew, so you read past it every time. The reverse outline caught it because it strips your manuscript down to what's actually on the page and lines it up where you can see it.
The same process surfaces other things: the scene that sets up a confrontation that never arrives, the character whose interiority goes quiet in the exact middle of the book, the moment you thought was your midpoint sitting fifteen thousand words earlier than you expected. Not problems, exactly — possibilities. Things the story is doing that you couldn't see while you were inside it.
The part you can automate
Building a reverse outline manually takes most writers several days. It's slow partly because reading your own work critically is cognitively exhausting, and partly because the act of compression — reducing forty pages to three sentences — requires a kind of attention that's hard to sustain across a whole manuscript. By the time you get to the middle third, you're tired, and tired readers of their own work start to summarize what they meant again instead of what they wrote.
That drift is where the value of the reverse outline quietly leaks away. Which is why automating it isn't just about saving time — it's about getting a document you can actually trust.
discowriter generates a reverse outline automatically from your manuscript. The outline it produces is the same document you'd build manually — without the days it takes to get there and without the fatigue that skews what you find. It's a starting point, not a verdict. You'll have things to add, things to push back on. But you'll have the map.
If you've finished a draft and you're trying to figure out what you actually wrote, that's what it's for.