What is Synopsis?
A submission synopsis is an evaluator-facing summary of the book’s complete narrative arc or, where appropriate, full argument progression. For fiction it normally reveals the major causal turns, character decisions, climax, and actual ending; it is a separate Manuscript Submission deliverable from the selective Query Letter pitch.
What good synopsis looks like
A strong synopsis follows the recipient’s requested length and format, preserves the complete central causal arc including the ending, names only consequential characters/subplots, stays clear rather than salesy, and can stand beside a query without merely repeating the query pitch.
- Opening state: identify the protagonist or central narrative subject, relevant situation, primary desire/pressure, and destabilizing event.
- Causal spine: summarize only the major turns that change what the central character knows, wants, risks, or can do.
- Character logic: include motivations and reactions where they explain why one event produces the next decision.
- Selective support: keep secondary characters and subplots only when removing them would make the main arc or ending hard to understand.
- Climax and resolution: reveal the decisive confrontation/choice, its consequence, the ending, and the important changed state.
- Submission fit: compress to the recipient’s stated word/page limit and formatting rules after the complete arc is accurate.
A practical structure to follow
Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.
- Opening state: identify the protagonist or central narrative subject, relevant situation, primary desire/pressure, and destabilizing event.
- Causal spine: summarize only the major turns that change what the central character knows, wants, risks, or can do.
- Character logic: include motivations and reactions where they explain why one event produces the next decision.
- Selective support: keep secondary characters and subplots only when removing them would make the main arc or ending hard to understand.
- Climax and resolution: reveal the decisive confrontation/choice, its consequence, the ending, and the important changed state.
- Submission fit: compress to the recipient’s stated word/page limit and formatting rules after the complete arc is accurate.
Choose the right approach
Use the task, reader, and relationship among ideas to choose a structure instead of forcing every situation into one formula.
| Approach | Use it when | Why / what to watch |
|---|---|---|
| You need to know whether/how a recipient requests a synopsis | Use Manuscript Submission. | The umbrella page controls package requirements and channel. |
| You need the complete evaluator-facing story summary | Use Synopsis. | Reveal major causal turns, climax and ending. |
| You need a selective pitch that preserves curiosity | Use Query Letter. | Do not turn the query into a full spoiler summary. |
| You need to hit one/two pages or another stated limit | Use Synopsis Length. | Compression is a separate constraint once the artifact is required. |
| You need reader-facing promotional copy | Use Book Description. | Sales copy should preserve curiosity rather than disclose the full evaluator arc. |
| You need nonfiction market/competition/chapter/sample acquisition material | Use Book Proposal. | A proposal is broader than a synopsis. |
Diagnose a weak draft quickly
Use the symptom first: identify what feels wrong, inspect the underlying writing decision, then make the smallest revision that fixes the real problem.
| Draft problem | What to inspect | Revision move |
|---|---|---|
| Requirement | Did the recipient actually request a synopsis and specify a length? | Follow the current submission instructions. |
| Completeness | Does the evaluator see the central setup, escalating causality, climax and actual ending? | Do not hide resolution for suspense. |
| Causality | Do major events connect through decisions/consequences rather than chapter-list chronology? | Compress around causal turns. |
| Cast/subplots | Does every named secondary element materially affect the central arc? | Cut names/details that consume scarce summary space without changing evaluation. |
| Tone | Is the prose clear and controlled rather than teaser-heavy sales copy? | Prefer evaluator clarity over promotional mystery. |
| Boundary | Does the synopsis merely repeat the query pitch? | Expand to the complete arc and ending. |
See the difference: before and after
A direct contrast makes the writing decision easier to see. The goal is not to copy the stronger sentence, but to understand which underlying choice changed.
The synopsis introduces the protagonist and mystery, lists a few complications, then stops before the climax to avoid spoilers.
The synopsis compresses the central causal chain, explains the protagonist’s decisive turns, states the climax, and reveals the actual ending within the recipient’s requested length.
Why this is stronger: A submission synopsis helps an evaluator inspect the complete architecture; it is not reader-facing teaser copy.
Revision rule: Reveal the whole central arc and ending, then compress secondary detail—not the resolution.
How synopsis changes by situation
The core principle can stay the same while the best execution changes with audience, format, evidence, genre, stakes, or length. Use these variations to adapt the technique rather than copying one pattern everywhere.
| Context | What changes | Practical adjustment |
|---|---|---|
| One-page synopsis | Prioritize protagonist/central subject, major turns, climax and ending. | Minimize secondary names. |
| Two-page synopsis | Allow one consequential subplot or additional turn where it changes the climax/resolution. | Do not fill space with scene-by-scene detail. |
| Form text box | Respect character/word limits and plain-text transfer. | Keep causal clarity when formatting disappears. |
| Series fiction | Give the queried book a complete arc first. | Separate future-book positioning from the current story summary. |
| Memoir/narrative nonfiction | Preserve the actual narrative progression and resolution rather than converting it into generic topic description. | Adapt the causal unit to the work. |
What to learn next
These links follow the writing decision rather than alphabetical similarity. Use them as a short path from the current concept to the next structural, evidence, revision, or publishing decision.
How to write synopsis step by step
- 1Read the actual submission instructions and record the requested length, file/form format, and whether the recipient uses “synopsis” in a special way.
- 2Write the full central arc in plain language before trying to make it elegant or short.
- 3Identify the inciting change, major commitments/reversals, crisis, climax, resolution, and final state.
- 4Connect events through motivation and consequence so the document does not become an “and then” event list.
- 5Add only the secondary characters, subplots, world rules, or backstory required to make those causal turns intelligible.
- 6Reveal twists and the ending; do not preserve suspense as if the synopsis were back-cover or retailer copy.
- 7Compress repetition, scene choreography, dialogue and decorative description before removing a causal step the ending depends on.
- 8Audit names, sequence, tense, motivations and ending against the manuscript before submission.
17 Synopsis examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
Mystery: Archivist Mara Vale receives a box of evidence from a 1989 disappearance that was never meant to reach her department. When she discovers the missing girl’s identity was changed in the original record, Mara traces the alteration to a retired clerk who was protecting a witness, not a killer. The real culprit is the witness’s father, now a prominent donor. Mara releases the corrected archive publicly, sacrificing her promotion but reopening the case.
Romance: After a flood closes both restaurants, rivals Lena and Gabriel are assigned the same temporary kitchen. Their attempts to divide the space fail as shared suppliers and staff force cooperation. Lena learns Gabriel quietly covered wages for her employees during the closure; Gabriel learns her expansion plan would preserve his family’s market stall. They abandon the rivalry, merge the temporary venture into a permanent partnership, and begin a relationship after choosing terms that protect both businesses.
Fantasy: Mapmaker Ilyra discovers that imperial borders become real barriers when she inks them on a sacred atlas. Ordered to divide a rebellious valley, she obeys and traps thousands without access to water. With help from a smuggler, she learns the atlas can also erase borders at the cost of the mapmaker’s memories. Ilyra destroys the empire’s boundary network, loses her memory of the rebellion, and leaves the final map blank for local communities to redraw.
Thriller: Compliance analyst Dev notices the same misspelling in paperwork for four unrelated companies. The trail leads to payments routed through a supplier owned by his manager’s brother. When Dev’s access is revoked, he copies the audit trail to an external regulator, only to discover his manager had been gathering the same evidence. Together they expose the executive sponsor who created the scheme; Dev keeps his job but leaves the department after testifying.
Coming-of-age: Scholarship student Ana begins writing classmates’ essays for money to cover exam fees. Her business grows until her closest friend submits one of Ana’s pieces to a national contest. When the essay wins, Ana must either stay silent or expose both of them. She confesses before the award ceremony, loses the scholarship competition, and later earns a smaller grant with an essay about the consequences of her choice.
Science fiction: The crew of the colony ship Horizon believes navigation failures are caused by aging hardware. Engineer Sol finds corrections hidden inside the errors and realizes they were sent by a future version of the ship after a failed landing. The messages guide Horizon away from the planned planet toward an uncharted moon. Sol follows the final correction, preventing the original disaster, but doing so erases the future timeline that sent the warnings.
Synopsis templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
[PROTAGONIST] is [situation] when [inciting incident]. To [goal], [he/she/they] must [main action], but [opposition]. After [major turning point], [decision] leads to [consequence]. In the climax, [final action]. The story ends when [resolution].
Beginning: [protagonist + status quo + disruption]. Escalation: [first major attempt and consequence]. Midpoint: [reversal or commitment]. Crisis: [greatest loss/choice]. Climax: [decisive action]. Resolution: [ending and changed state].
[Character] wants [goal] because [motivation]. [Inciting event] makes that goal urgent. [Obstacle] forces [decision], which causes [turning point]. After [setback], [character] chooses [climactic action], resulting in [ending].
Common mistakes to avoid
- Writing a teaser, blurb, or query-style hook that withholds the ending.
- Listing events chronologically without explaining character motivation, causality, or consequence.
- Naming so many secondary characters that the central arc becomes hard to follow.
- Spending most of the available space on setup and compressing climax/resolution into one vague sentence.
- Trying to preserve every scene, joke, clue, worldbuilding detail, or subplot instead of protecting the causal spine.
- Following a generic one-page rule when the actual recipient requests a different length or format.
Final revision checklist
- Does the opening make the purpose clear quickly?
- Is every important claim, detail, or example doing a distinct job?
- Could a reader misunderstand any pronoun, transition, time reference, or instruction?
- Is the tone appropriate for the relationship and situation?
- Can you remove repetition without removing necessary context?
- If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?
Questions about Synopsis
What is Synopsis?
A submission synopsis is an evaluator-facing summary of the book’s complete narrative arc or, where appropriate, full argument progression. For fiction it normally reveals the major causal turns, character decisions, climax, and actual ending; it is a separate Manuscript Submission deliverable from the selective Query Letter pitch.
What makes Synopsis effective?
A strong synopsis follows the recipient’s requested length and format, preserves the complete central causal arc including the ending, names only consequential characters/subplots, stays clear rather than salesy, and can stand beside a query without merely repeating the query pitch.
How do I write Synopsis?
Start with the purpose and reader, then work through the structure in order. Draft for meaning first, check the examples for pattern, and do a final revision for clarity, accuracy, tone, and unnecessary repetition.
What should I avoid when writing Synopsis?
Writing a teaser, blurb, or query-style hook that withholds the ending. Listing events chronologically without explaining character motivation, causality, or consequence. Naming so many secondary characters that the central arc becomes hard to follow.
Does Synopsis change for different audiences, formats, or constraints?
Yes. The underlying principle stays recognizable, but length, evidence, reader knowledge, genre, stakes, and publication context can change how strongly it should be stated and how much explanation or structure the reader needs. Use the context section to adjust the technique instead of treating one example as a universal formula.
How do I know which version of Synopsis fits my situation?
Start with the job the writing must perform, then compare audience, length, evidence, genre, and stakes. The worked-scenario section shows how the same broad technique changes under different constraints, and the guided path links the next concept to check when the problem actually belongs to a neighboring writing decision.
What should I practice first if I am learning Synopsis?
Start with the beginner example and make the core writing job unmistakable. Move to the intermediate example only after you can explain which additional constraint it introduces. The advanced example then shows how the same principle changes when evidence, audience, genre, stakes, or publication context becomes harder. Use the skill ladder for the next neighboring concept instead of trying to master every related topic at once.
What should I do when the usual Synopsis advice does not fit my situation?
Identify the constraint that changed first: audience knowledge, evidence quality, length, genre, stakes, workflow, or publication context. Keep the core job of Synopsis intact, then adapt the surface pattern. The constraint-comparison examples on this page show what can change without losing the underlying writing decision.