PolyzPolyz
All articles

How to Write a Novel Synopsis That Doesn't Read Like a Tax Form

How to write a synopsis agents actually want to read: the full arc, the ending, the spoilers, what to cut, and a clear template. Stop writing plot summaries.

Polyz Team5 min read

Ask a room of novelists what they hate most about getting published and the synopsis wins by a landslide. People who happily wrote 90,000 words of fiction will stare at a blank page for a week rather than compress that book into two. And the ones who do force it out usually produce something that reads like a deposition: "Then Sarah goes to the house. Then she finds the letter. Then she calls her sister."

That dry, this-happened-then-this-happened recitation is exactly what makes a synopsis painful. Learning how to write a synopsis isn't about summarizing every plot point. It's about telling the story's spine in a way that proves you can structure a narrative. Here's how to do it without producing a tax form.

What a synopsis is actually for

The synopsis exists to do one thing for an agent or editor: show them that your book has a working structure, a real arc, and a satisfying ending, before they invest hours in the full manuscript. It is not a teaser. It is not back-cover copy. It is not designed to create suspense.

This is the single biggest misunderstanding. People write coy synopses that withhold the ending, thinking they're building intrigue. The agent reads that and assumes you don't have an ending, or that you don't understand what a synopsis is for. Both are bad.

Spoil everything. The twist, the death, the betrayal, who ends up with whom, the final image. The reader of a synopsis wants the spoilers, because they're evaluating whether your story holds together, and they can't do that if you hide the load-bearing turns.

Length, tense, and voice

A few mechanical rules first, because they trip people up.

  • Length: usually one to two pages, single-spaced, unless a specific agent asks for something else. Always check submission guidelines. Shorter is harder and usually better.
  • Tense: present tense. "Sarah discovers," not "Sarah discovered." It's the convention; just use it.
  • Person: third person, even if your novel is first person.
  • Character names: put a major character's name in CAPS the first time they appear. This is a common request and it makes the cast easy to track at a glance.

On voice: the synopsis should carry a faint flavor of your book's tone without trying to be a performance. A thriller synopsis can be taut. A comic novel's can have a dry wit. But don't sacrifice clarity for style here. The job is to be clear and structurally convincing, and a little voice on top is a bonus, not the goal.

What to include (and what to cut)

The hardest part is deciding what survives. A synopsis can't hold every scene, so it has to hold the causal spine, the chain of events where each one forces the next.

Include:

  • The protagonist, their goal, and what's at stake if they fail.
  • The inciting incident that kicks the story into motion.
  • The major turning points, especially the midpoint shift and the climax.
  • The character arc: who the protagonist is at the start, and how they've changed by the end.
  • The actual ending. All of it.

Cut:

  • Subplots that don't bear on the main arc. Mention only the ones that change the protagonist's path.
  • Minor characters. If someone can be cut without breaking the causal chain, cut them. Naming twelve people in two pages is how synopses become unreadable.
  • Backstory and worldbuilding, except the minimum the plot can't stand without.
  • Most dialogue and scene-level detail. You're summarizing the river, not describing each rock.

A good test: every sentence should either advance the plot or illuminate the protagonist's change. If a sentence does neither, it's furniture. Remove it.

The trap of the "and then" list

The reason most synopses read like a form is that they list events instead of connecting them. "And then" is the enemy. It signals chronology without causation, and causation is the entire point.

Watch the difference. Weak: "Sarah finds the letter. Then she confronts her sister. Then she leaves town." Stronger: "When Sarah finds the letter, she realizes her sister has been lying for years, and the confrontation that follows leaves her with no choice but to leave town for good."

The second version uses because and so and which forces. It shows events causing other events, which is exactly what proves you can plot. Go through your draft synopsis and hunt every "then." Most can be replaced with a word that shows why the next thing happens.

A clean template

Here's a structure that works for most novels. Adapt it; don't worship it.

  1. Opening paragraph: Introduce the protagonist in their normal world, what they want, and the inciting incident that disrupts it. End on the central dramatic question.
  2. Rising action (a few paragraphs): The protagonist pursues the goal. Hit the major obstacles and the midpoint turn. Show the stakes escalating. Keep it causal.
  3. The climax: The confrontation everything's been building toward. Don't soften it.
  4. The resolution: How it ends, what the protagonist learned or lost, the final state of things. One short paragraph.

If you've already done the structural work of seeing your book's shape, the synopsis is mostly transcription. If you haven't, the synopsis is brutally good at exposing it, which is its hidden value: a story you struggle to summarize cleanly often has a structural problem worth fixing in the manuscript itself.

This is one place an AI writing coach earns its keep, not by writing the synopsis for you (a generic AI summary will read exactly as flat as the "and then" version), but by reading your draft and asking the useful questions: "What's the central dramatic question? Where does the causal chain break? Which subplot can you cut?" You answer; it pressures the structure. That's the same coach-not-ghostwriter logic that makes the case for a Sudowrite alternative built to sharpen your judgment rather than replace it.

Write it last, then cut it in half

Practical order of operations: draft the synopsis once you know your story cold, dump everything onto the page in a messy first version, then cut it ruthlessly to length. The cutting is where it gets good, because compression forces you to find the true spine.

And if writing the synopsis reveals that your spine is wobbly, that's not a synopsis problem. Go back to the structural edit of the novel itself and fix it there. The synopsis just held up a mirror.

Nobody loves writing these. But a clean, spoiler-filled, causally-driven synopsis tells an agent you understand story, and that impression starts working for you before they've read a single line of your actual prose.


Polyz keeps your whole manuscript and its structure in one place, so when it's time to summarize, you can see the spine you're working from. Start a free trial.

Try Polyz free for 7 days

Every feature, all three Claude models, a generous monthly quota. Card required to start. Cancel before day 7 and you owe nothing.