Workflow guide
What a logline is (and what it is not)
A logline is a one- or two-sentence summary of a screenplay that names a protagonist, a goal, and the obstacle or stakes that make the goal hard: it is not a tagline, not a synopsis, and it does not tell the ending.
The four-piece formula
A working logline usually holds four pieces, not a clever slogan: who the protagonist is (with a trait that matters), what incident breaks the status quo, what they want, and what makes that want expensive. In Save the Cat!, Blake Snyder treats the logline as a one- or two-sentence description and asks for irony plus a mental picture; that is a clarity test, not a statute.
Original feature example: «When a mosaic restorer finds a cache of denunciations under the cathedral scaffolding, she must choose whether to save the artwork or the families still living in town, while the bishop who hired her wants the vault sealed before the papal visit.» Pieces: protagonist (restorer), incident (the archive), goal (get the truth off the site / decide what to save), obstacle (the bishop and the liturgical clock).
Original series example: «A family mediator in a border city learns that every couple she advises signs the same trap clause; to dismantle it she has to work with the lawyer who wrote it — her ex-husband — without letting the firm collapse before the court season.» The engine is not «a woman has work problems»: it is a conflict that can generate episodes without burning the secret in the pilot.
Logline, tagline, soggetto, synopsis
These labels get mixed in development emails. A logline is the premise contract; a tagline is poster marketing; the Italian soggetto is a short narrative of the story; a synopsis is for readers or commissioners and usually does not hide the outcome.
Syd Field, in Screenplay, talks about the idea and the dramatic premise more than the Hollywood «logline» as a pitch object. The question is similar (who wants what), but an Italian soggetto is not a translated logline.
| Form | What it does | How long | Does it tell the ending? |
|---|---|---|---|
| Logline | Names protagonist, goal and obstacle for the pitch and the bible | One or two sentences | No |
| Tagline | Marketing hook (poster, trailer, one-sheet) | A few words | No |
| Soggetto | Short narrative of the story, used in Italian development | Often a few pages, with no official page count | Usually yes, in summary |
| Synopsis | Summary for readers, commissioners or a dossier | Variable | Often yes |
Length and names
There is no correct word count. Industry practice is one or two sentences: past three, you are probably writing a mini-synopsis. Snyder uses that length as discipline, not as a WGA rule.
Proper names are optional. Use them when recognition helps («a tax-court judge in Bari»), not as a substitute for a trait. «Marco must save Lucia» is not a logline: it never says why it is hard. The title does not live inside the logline; Snyder keeps it beside it, as a separate test.
Film versus series
For a feature, the logline describes a closed arc: one protagonist, one pressure, stakes paid at the climax. It should not spoil the ending, but it should make clear that the story has one.
For a series, the logline also has to name the generative engine: what repeats each episode and what must not be burned in the pilot. If you delete the city name and the sentence still reads like a feature, you do not have a series logline yet — you have an episode premise.
Common mistakes
A list of themes («it is a film about identity, grief and capitalism») with no character who wants something. Theme and logline are not the same object.
A tagline wearing a logline's clothes: «Some secrets weigh as much as marble.» Fine on a poster, useless in a writers' room.
A compressed synopsis: three acts, names, and the ending. That reveals the story instead of stating the premise.
No engine: «a chef opens a restaurant.» Missing incident and obstacle. Without stakes, a copilot and a commissioner will ask the same question: why now?
How CineQuill uses it
In CineQuill the logline is a story-bible field, next to theme and premise — not a shop-window slogan. It keeps the promise visible while characters, beats and pages grow.
The Copilot does not invent the engine for you. It can stress-test whether the logline matches the draft: if the bible's protagonist is not the one acting in the scenes, or the declared obstacle never appears, the contradiction becomes a question, not an automatic rewrite.
Put it into practice
Apply this guide directly in your project
Open CineQuill and use this resource as an operational checklist: move from reading to a concrete decision about bible, characters, structure or scenes.
Frequently asked questions
What is a logline?
A one- or two-sentence summary that names a protagonist, a goal, and the obstacle or stakes that make the goal hard. It is not a tagline, not a synopsis, and it does not tell the ending.
How many words should a logline be?
There is no official count. Practice is one or two sentences. If you need three paragraphs, you are writing a soggetto or a synopsis, not a logline.
Do I have to use character names?
No. Names help only when recognition is useful. A trait, a job or a wound that shows who is acting matters more.
How is a logline different from a soggetto?
A logline is one or two sentences of premise. In Italian development, a soggetto is a short narrative of the story, often a few pages, and it usually includes the arc through the outcome. They are not synonyms.
Are feature and series loglines the same?
No. A feature logline describes a closed arc. A series logline must also name the engine that generates episodes, without burning in the pilot what keeps the season open.
Can AI write it?
It can propose variants and flag a missing piece. It should not invent the conflict: if the AI writes a logline the draft cannot support, you have a slogan, not a premise. In CineQuill the Copilot compares logline and pages; the author decides.
Related resources
More workflow guides to apply
How to use the story bible to keep the story centered
A practical guide to CineQuill's story bible: premise, theme, world, tone, rules, characters and narrative coherence before the screenplay.
Workflow guideHow to use templates without writing formulaic stories
A guide to CineQuill templates: narrative methods, character sheets, beats, scenes and how to adapt them without becoming formulaic.
Workflow guideCharacter sheets: from description to dramatic function
A guide to character sheets: desire, wound, mask, archetype, relationships and coherence across scenes and structure.
Workflow guideScenes: the bridge between structure and screenplay
A guide to scene work: objective, conflict, internal beats, narrative function and the move from structure to screenplay editor.