PLOT LAB / OUTLINE COMPRESSION
How do I shorten an outline without losing causal links?
Shorten an outline by combining actions that serve the same turn, while keeping the event that enables the next decision. For each proposed cut, ask what the following beat needs the character to know, possess or be allowed to do. If the removed beat supplied that condition, carry it into a surviving beat before deleting it. Fewer headings do not have to mean a missing cause.
Mark the bridge before cutting the journey
This exercise addresses revising the outline itself, rather than drafting prose from it or fixing a repetitive middle. The original fictional delivery case below is a planning comparison. It is not a courier policy, a real customer incident or an observed output from a plot generator.
Seed seller Elin promises gardener Ro a delivery for a community planting event. The parcel label still names Ro's former workshop. Elin notices the mismatch before dispatch, contacts Ro, receives confirmation that Ro can collect at the garden gate, and asks the courier to use that agreed destination. Ro collects the parcel there. The destination is not a guess: Ro's confirmation is the bridge between discovering the bad label and choosing the replacement.
The longer outline separates those actions into different beats: Elin checks the order, notices the old address, sends a message, receives the garden-gate confirmation, changes the dispatch note, and gets news of collection. This does not establish a preferred number of beats for every story. It gives this particular comparison enough visible joints to show what a cut removes.
A shorter version that still earns the destination
Combine the order check and discovery: while preparing dispatch, Elin sees the former workshop on the label. Combine the message and reply: Elin contacts Ro, who confirms collection at the garden gate. Combine the changed instruction and its result: Elin dispatches to the agreed gate, where Ro collects. The compressed route preserves discovery, confirmation and execution, although each surviving beat now covers more than one small action.
What disappeared is separation, not permission. Elin still learns the usable destination before giving the instruction. Ro still has a reason to be waiting at that gate. The sequence can later become several scenes, a brief exchange or a summary passage; this exercise does not decide the prose length merely by shortening the outline.
The attractive cut that breaks the route
A broken compression reads: Elin spots the outdated address, changes the parcel to the garden gate, and Ro collects it. If the draft has not established that Elin knows the gate is acceptable, the middle action arrives without support. Perhaps it is a sensible guess, but the outline must then treat it as a guess and allow its risk. Do not silently inherit certainty from the reply you deleted.
There are two honest repairs. Restore Ro's confirmation inside the discovery beat, or change the story so Elin knowingly sends to an unconfirmed location. In the second route, Ro's collection needs another explanation: how Ro learns of the delivery, finds the gate or is already there. That route may be interesting, but it creates a new planning task instead of achieving a free cut.
When the reply becomes a real obstacle
Now vary one condition: Ro cannot answer until after dispatch closes. The message and confirmation cannot simply be merged as an effortless exchange. Elin must wait and miss dispatch, seek another agreed contact, or choose an uncertain destination. The delay is doing causal work because it forces a decision. Cutting it would remove the very problem the revised version is about.
For the original quick-reply version, a long account of Elin checking the same label twice can be folded into preparation if it changes nothing else. For the delayed-reply version, time spent waiting may change what options remain. Decide from the function of the event in this version, not from a blanket rule that messages, travel or waiting should always be removed.
Leave a cut note another draft can follow
Combine: preparation and discovery of the outdated label. Carry forward: Ro confirms the garden gate before redirection. Combine: dispatch instruction and eventual collection. Do not silently grant: knowledge of an acceptable new destination. If confirmation is removed: mark the destination as a guess. Reopen the cut when: a late reply creates the central choice.
Use that note when revising a plot generator outline into a shorter form. The outline-to-scene guide covers expanding an accepted beat into immediate action. The middle-repetition guide checks whether events change the story state. Here the question is which enabling condition must survive a compression.
Questions about compressing an outline
Can I change the structure instead?
You can reorganize headings, but inspect the events they contain afterward. A framework label does not supply missing knowledge or consent. Compare the revised event sequence rather than assuming a smaller framework automatically preserves the logic.
Does every cause need its own beat?
No. Elin's contact and Ro's answer can share a beat in the quick-reply version. They must still appear in its event description. A compact sentence can retain the bridge without creating another heading.
What if I deliberately want uncertainty?
Let Elin make the uncertain choice openly. The outline can say she guesses the garden gate and later discovers whether it worked. What fails is presenting that guess as confirmed while removing the only event that once confirmed it.
Source and scope
The Reedsy plot tool offers length and story-structure choices. Those controls are a general planning context, not evidence that a compressed outline preserves its causes. Elin, Ro, the seed parcel and the quick-reply and delayed-reply comparisons are original editorial fiction. This page does not claim that the method is absent from every competing page or that a shorter outline guarantees better prose.