These documents describe the same show at different levels of detail. A useful way to choose between them is to ask what the reader needs to understand next. The labels vary between companies, so always follow the recipient’s specific request.
The logline: the central promise.
A logline is a compact introduction, usually one or two sentences. It connects the central character or situation with a goal, obstacle, or compelling tension. It should give the reader a foothold in the story without relying on a long explanation of its mythology.
Avoid using a theme as a substitute for a premise. ‘A story about belonging’ names a subject; it does not yet describe a show. Tell us whose belonging is at stake, what changes their circumstances, and what they might do as a result. The emotional meaning can emerge through that specific situation.
The synopsis: the story in motion.
A synopsis expands the idea into a readable overview. For a series pitch, it can introduce the world, central relationships, and the movement of the first season. Show how one pressure leads to another, rather than offering only a sequence of disconnected events.
Clarify whether you are writing a pilot synopsis, season synopsis, or general series overview. They answer different questions. A pilot synopsis describes that episode; a series overview explains what the show becomes. Where a recipient asks for an ending, include it. A development reader may need to evaluate the resolution rather than experience a surprise.
The pitch deck: a guided presentation.
A pitch deck combines concise writing and visual material to communicate the project’s identity. It may include a logline, a brief synopsis, characters, world, tone, and creator information. Its sequence should make the idea easier to absorb, with each page earning its place.
A deck does not need to contain everything you know. A page overloaded with lore often hides the decision or relationship that would make someone care. Put the essential creative promise in the foreground and save deeper material for a follow-up conversation.
The series bible: a deeper reference.
A development bible explores the show in more depth: character arcs, world rules, themes, episode ideas, and longer-term possibilities. During production, a series bible may also serve as a working reference that records established facts and creative decisions. These uses overlap, but they are not identical.
There is no universal length or mandatory template. An elaborate fantasy world and an observational documentary have different needs. Organize the document around the questions collaborators must answer, and keep its assumptions consistent with the script or other materials you are sharing.
Prepare the next useful document.
If you are at the concept stage, start with a clear logline and a short overview. Use them to find gaps: a protagonist without a meaningful choice, a premise without an episode engine, or a world without a perspective. Expanding a weak premise into a longer document rarely solves those problems by itself.
For an initial pitch to Stable Studios, a title, short hook, and contact details are enough to begin. A longer overview, development stage, and finished bible are optional. If you have further materials, upload a script, deck, or bible privately, or provide a view-only link and identify what the reader will find there.