Logline

Four elements, in roughly this order:

1. The protagonist, described by role or situation — not name. "A widowed sheriff" rather than "John." The role tells readers something about the person and the world they inhabit. A name tells them nothing. The description should communicate something: social position, a quality that will be tested, the tension the character will face. "A recovering addict turned public defender" is a more loaded description than "a lawyer." Both are technically correct; one does more work.

2. The inciting incident. What disrupts the protagonist’s existing life and makes the story necessary. This is the trigger, the event that could not be ignored. The inciting incident in the logline identifies what kind of story this is and sets the engine running. "When her daughter disappears" tells us we’re in a thriller or crime narrative; "when a dying patient leaves her his entire estate" signals something stranger.

3. The central goal. What the protagonist must now do. This is external and active — something that can succeed or fail visibly. "Must expose the conspiracy," "must survive the winter," "must win back her family." The central goal distinguishes the story’s plot engine from its thematic content. The external goal creates structure; the internal need creates meaning. The logline usually captures the external goal.

4. The stakes. What’s lost if they fail. Stakes create urgency; without them, readers have no reason to care about the outcome. Stakes in a logline are almost always stated in terms of life, relationship, identity, or professional ruin — the things that matter enough to justify a whole novel.

The Jaws logline is a clean illustration: When a killer shark unleashes chaos on a beach community, a local sheriff, a marine biologist, and an old seafarer must hunt the beast down before it kills again. Inciting incident first, protagonists described by role, goal explicit, stakes embedded in "before it kills again." Everything you need to understand the story’s engine is in that sentence.

Compare No Country for Old Men: When a welder stumbles onto the aftermath of a drug deal gone wrong and takes the money, he becomes the target of a relentless killer while an aging sheriff tries to stop the bloodshed. Three moving parts, each role-described, the central conflict stated, the stakes implied by the presence of a "relentless killer." The logline compresses a genuinely complex novel into a single coherent line.

It isn’t a tagline. "In space, no one can hear you scream" is marketing copy — evocative, non-specific, tells you nothing about who does what or why. A logline is structural, not atmospheric. Taglines sell the experience; loglines describe the mechanism.

It isn’t a theme statement. "A story about grief and family" is not a logline. It describes what the story is about in the literary sense — but it has no conflict, no protagonist with a goal, no stakes. You cannot evaluate from a theme statement whether a story exists. "A story about grief and family" describes thousands of novels, and whether any of those novels work structurally is not a question the theme statement can answer.

It isn’t a premise outline, though the two overlap. A premise outline allows two or three sentences and can develop character more fully. The logline has one sentence and must earn that compression: every word doing work, nothing present that doesn’t need to be. The premise outline is what you use when you need room for nuance; the logline is what you use when you need to know whether the story is there.

Here’s the real value: the logline test is brutal and fast. If the story doesn’t have a protagonist, a conflict, a goal, and stakes — all present at once, all working together — the logline won’t hold together. The sentence will feel vague, or it won’t fit in one sentence at all, or it will fit but sound uninteresting.

Any of those outcomes is useful information. A logline that sounds boring means the story might be boring — not certainly, because execution can transform a thin-sounding premise into extraordinary work, but the risk is real and worth examining. A logline that can’t be written in a single sentence means the story’s core conflict may not be clear enough yet; the writer may be confusing complexity with the story’s main engine. A logline that requires more than four clauses often means the writer hasn’t identified which part of the story is the main story.

This is where the logline does something that no other planning tool does quite as efficiently: it distinguishes between richness and lack of clarity. Some stories have multiple competing conflicts, an ensemble of equally important characters, and a thematic argument that resists reduction. Those stories are rich. But even a rich story has a main throughline — a primary protagonist facing a primary conflict with primary stakes — and the logline tests whether that throughline is clear. If the writer can’t find it, the reader won’t either.

The logline doesn’t fix these problems. But it surfaces them before the writer is 80,000 words in.

Start with the shape: When [inciting incident], a [protagonist description] must [goal] before/or/unless [stakes].

This template is a scaffold, not a formula. The best loglines don’t sound like they were written from a template — they sound like they describe something specific and worth experiencing. The template gets you to first draft; revision makes it read naturally.

Active verbs. Specific situations. No vague adjectives ("a small-town woman," "an unlikely hero"). If the description could apply to a thousand stories, it’s doing no work. The word "unlikely" tells us nothing about why this particular person is compelling. "A bureaucrat who hasn’t left his apartment in three years" tells us something.

Write multiple versions. The first logline is almost always too vague. Push toward specificity in each revision: what’s the most interesting thing about this protagonist, and can it go in the description? What’s the most interesting constraint on the goal? What’s the most painful version of the stakes?

The internal stakes — what the protagonist stands to lose psychologically, not just physically — can be harder to fit in a single sentence, and they often don’t make it into the logline at all. That’s acceptable. The logline operates at the external conflict level. The internal arc is what makes the story worth caring about; the logline is the door in. If the external conflict is strong enough, readers will follow it in and find the internal one.

One final test: does the logline sound like a story you’d read? Not just structurally coherent, but actually interesting? This is a subjective judgment and it’s not the logline’s primary job — but if the sentence produces no interest even in you, the person most invested in the material, something is probably wrong. Either the premise needs work, or the logline hasn’t found the right way into it yet.

The logline isn’t only useful at the planning stage. Writers who draft without planning sometimes write their logline after completing the draft — not to summarize what they wrote but to understand what they have. If the logline of the finished draft is significantly different from what the writer thought the story was about while writing it, the draft has discovered something important. The gap between the intended and the actual logline is a structural diagnosis.

Writers deep in revision often lose sight of the story’s core conflict among all the scenes and characters and subplots. Returning to the logline — or writing a new one for the draft as it currently stands — can restore perspective. Strip away everything except the main engine and ask: is it still running?

The logline is a compression tool. What it compresses is the story’s reason for existing.