You can write a completely coherent outline of a completely incoherent world. That sentence is the entire difference between these two practices, and it is worth sitting with, because it explains a failure that catches experienced writers who have done nothing wrong.
An outline is a commitment to sequence, written at summary altitude. A zero draft is a stress test, written at scene resolution and thrown away afterwards. They are complements, not alternatives — but they catch different classes of problem, and only one of them can catch the expensive kind.
The difference is altitude
An outline says: Eli confronts Maren about the signal. That line is compatible with almost any set of underlying facts. It stays true whether Maren has aged, whether Eli already knows what she is, whether the confrontation happens at the lighthouse or four miles inland, and whether it is the same night or eleven years later. The line survives all of it, which is exactly what makes outlines fast and exactly what makes them blind.
A scene cannot do that. To write the confrontation you have to decide where they are standing, what time it is, what she calls him, whether he has already worked out what she is, and how much of the eleven years is visible on her. Each of those decisions is a query against your established canon, and any one of them can come back with no answer or with the wrong one.
Summary is the register in which contradictions are invisible. Scene is the register in which they surface. That is not a claim about which one is more rigorous — it is a claim about resolution.
Order versus load
The cleanest way to hold the distinction:
- **An outline tests order.** Does this happen before that. Does the escalation build. Does the midpoint turn. Does the ending pay off what the opening set up. These are sequence questions, and an outline is the right instrument for all of them.
- **A zero draft tests load.** Can the world actually bear the weight of this scene. Are the facts it needs established, consistent with each other, and consistent with what was established four hundred pages earlier.
A story can pass the first test perfectly and fail the second one badly. That combination — structurally sound, internally contradictory — is one of the most common shapes of a troubled draft, and it is frustrating precisely because every structural note you get back says the architecture is fine.
How they fit together
The usual order is: outline, then zero draft the scene the outline is quietly nervous about, then revise the outline with what the draft found.
That middle step is where the value is, and picking the target is most of the skill. You are not looking for the most important scene or the hardest one to write. You are looking for the scene with the most collisions — where two characters with separate histories, a rule you invented early, a location you only ever sketched, and a specific date all have to be true simultaneously. Load concentrates at intersections.
If you cannot tell which scene that is, choose the one you have been putting off. Avoidance is diagnostic. Writers defer the scene where they already half-know the world does not add up, and they are usually right.
What an outline structurally cannot catch
It is worth being specific about the blind spot, because it is not a matter of writing a more detailed outline. Detail does not fix it — a more granular outline is still summary, just more of it.
- **Established-fact collisions.** Two things you decided months apart that cannot both be true. The outline references neither.
- **Unestablished dependencies.** Facts the scene needs that the world never decided. An outline can say "they argue about the signal" without ever needing to know how the signal works.
- **Knowledge-state errors.** Who knows what, when. The single most common continuity failure in produced work, and completely invisible at summary altitude, because summary does not track information as it moves between characters.
- **Physical and temporal impossibility.** Distances, durations, and whether someone could actually be where the next scene needs them.
Every one of these is cheap to find in a ninety-minute zero draft and expensive to find in a table read.
In a room, they do different jobs
A writers' room outlines constantly and well — the board is an outlining instrument, and breaking a season is outlining at scale. What a room does not have is a mechanism for catching the parallel canon it generates: eight writers leaving a break holding eight slightly different versions of the show, all confident, none written down in the same words.
A zero draft is cheap to run against that. Assign one writer a collision scene, timebox it to ninety minutes, and have them read back only the two lists — never the pages. The room resolves the items on the spot and they go into the bible. Run it after the season is broken and before scripts are assigned, which is the last point where a structural answer is still free.
The reason this works is the same reason it works alone: the outline was never going to surface those items, because the outline is not written at the resolution where they exist. If the underlying question of why these errors persist at all is the interesting one, that is the logic problem.
Frequently asked questions
- Does zero drafting replace outlining?
- No. They test different properties. An outline tests order and sequence at summary altitude; a zero draft tests whether the world can bear the load of a specific scene at full resolution. Most writers do both, in that order.
- Should I outline first or zero draft first?
- Outline first. Zero drafting needs enough established canon to contradict — before a record exists there is nothing to test against, and what you are doing is just writing. Once the outline exists, zero draft the scene it is quietly nervous about.
- Can a more detailed outline catch the same problems?
- No, and this is the counterintuitive part. Detail does not change the register — a more granular outline is still summary. Knowledge-state errors, unestablished dependencies, and established-fact collisions only become visible when a scene is forced to make specific decisions.
CanonBoard scans your whole world and tells you where it disagrees with itself.
Start free