Why Your Logline Isn't Working and What It's Telling You

You've written the logline. You've revised it, reordered the clauses, swapped the adjective in front of the protagonist's description. It still isn't landing, and you can tell — but you can't tell why.

Here's what most logline advice won't say: the problem is almost never the sentence. When a logline resists improvement despite multiple revisions, it's usually because the sentence is faithfully representing a screenplay that hasn't fully resolved its own foundational questions. The logline isn't broken. It's accurate. And that's the problem.

Logline failures aren't random. They fall into a small set of recognizable patterns, and each one points to a specific weakness in the screenplay itself. Once you can name the pattern, you can stop reworking the sentence and start addressing the actual issue.

You're Describing a Situation, Not a Conflict

This is the failure pattern writers are least likely to catch on their own. The logline describes a world, a setup, a character in a circumstance — but never names what that character is actually fighting against or fighting for. It reads like a premise summary rather than a story engine.

A logline built around a situation tells the reader what the movie is about in the loosest possible sense, where a logline built around a conflict tells the reader what drives the movie forward. The difference matters because readers, agents, and producers aren't evaluating whether your concept sounds interesting in the abstract. They're evaluating whether it sounds like it generates two hours of sustained dramatic pressure. A situation doesn't do that. A conflict does.

If your logline keeps drifting toward description — "a wrongly convicted surgeon adjusts to life on the run" — the screenplay probably hasn't yet defined its central dramatic engine. The character exists in a circumstance, but the story hasn't committed to what forces that character into motion, what resists them, and what happens if they fail. The fix isn't a better verb in the logline. The fix is defining the conflict in the script so clearly that the logline can't avoid stating it.

Your Stakes Are Declared, Not Dramatized

This pattern shows up when the logline includes a clause about what's at risk — "with everything on the line," "before it's too late," "or lose everything" — but the stakes feel abstract rather than visceral. The writer knows the story needs stakes and has dutifully included them, but the logline reads like it's asserting importance rather than demonstrating it.

Stakes work in a logline when they're specific enough to create weight without explanation. "Before the marshals close in" is a deadline with built-in tension. "Before it's too late" is a placeholder. "Or Kimble dies on death row for a murder he didn't commit" lands because the reader can feel the cost without being told it matters. "Or he'll lose everything" collapses because the reader has to take the writer's word for it. The difference isn't craft sophistication — it's whether the screenplay itself has defined what failure actually looks like in concrete, dramatizable terms.

When stakes feel vague in the logline, it's usually because they're vague in the script. The writer may know, in a general sense, that the protagonist needs to succeed. But they haven't built the specific mechanism of consequence — what is lost, who is affected, what becomes irreversible — with enough clarity for the logline to compress it into a phrase that lands. Revising the logline won't solve this. Defining the cost of failure in the screenplay will, and the logline will sharpen on its own once that work is done.

Your Protagonist Could Be Anyone

Why is this person the only person who could be at the center of this conflict? If your logline can't answer that question through the protagonist's description alone, the screenplay may not have answered it either.

A logline where the protagonist is "a young woman," "an ambitious newcomer," or "a desperate man" without any detail that connects them to the story's specific pressure is signaling a character-definition problem. This doesn't mean every logline needs a backstory-loaded character description. It means the protagonist's defining trait should create friction with the conflict itself. "A surgeon on the run who uses his medical expertise to hunt the man who killed his wife" tells you something about the character's relationship to the story's pressure. "A desperate man on the run who must find the real killer before it's too late" is basically doing the same thing, but tells you nothing substantive. The logline can only be as specific as the screenplay's understanding of why this character, in this situation, creates a story that wouldn't exist with someone else at the center.

If you're cycling through generic descriptors and none of them feel right, the issue is upstream. The screenplay needs a protagonist whose identity is load-bearing — whose specific qualities create, complicate, or intensify the central conflict. Once that's in place, the logline descriptor stops being a cosmetic choice and starts being an obvious one.

Your Concept Has No Irony

"A doctor sworn to save lives is convicted of murder." Before you know anything else about this story — the plot, the structure, the stakes — you can already feel the pressure built into the premise. That's irony in a logline, and it has nothing to do with humor. It's the collision between who the character is and what they're forced to do, and it creates an immediate sense that the concept contains a movie.

When a logline lacks that collision, it often reads flat even if every other element is technically present. The conflict is clear, the stakes are specific, the protagonist is defined — but the concept doesn't generate any pull. There's no tension baked into the premise itself. This usually means the screenplay's concept is functional but not yet compelling. The story works logically, but it doesn't contain the kind of inherent friction that makes someone want to read the script rather than just acknowledge that the premise makes sense.

This is one of the harder problems to fix because it often requires rethinking the character-concept relationship rather than adjusting plot mechanics. But it's also the pattern that, once resolved, tends to fix the logline almost instantly. A concept with real irony practically writes its own logline.

What the Logline Is Telling You

The instinct to keep revising the logline is understandable, but it becomes counterproductive once you've passed the point of diminishing returns. If you've written a strong logline using sound craft principles and it's still not working after several revisions, the sentence is no longer the problem. The screenplay is telling you something through the logline, and the most productive move is to listen.

That ability — to read your own material the way the industry will, to identify what's working structurally and what isn't before external readers confirm it — is the same skill that drives effective self-analysis at the screenplay level. A writer who can diagnose their own logline failures is already practicing the kind of structural self-awareness that separates scripts that are ready for professional evaluation from scripts that aren't. And once the logline does work — once it clearly expresses a conflict-driven concept with specific stakes, a defined protagonist, and genuine irony — the next question becomes whether it's built to travel professionally: to function as a transmissible hook in the rooms, inboxes, and conversations where projects actually get traction.

Forme evaluates screenplays the way professional readers do — structurally, diagnostically, and without encouragement for its own sake. If your logline diagnosis points to a screenplay problem, Forme's coverage can help you see exactly where and how the script itself needs to change before the logline — or anything else — will improve.