# Preparation before delivery storyboard

Previous setup: Agree objectives, scope, responsibilities and what readiness means.

| Unit | Audience arrives with | Headline / point | Substance + status | Closing beat | Audience leaves with | Connection to next | Layout/use and alternatives | Missing input / format limit |
|---|---|---|---|---|---|---|---|---|
| 1 | The reader assumes delivery begins immediately or that all preparatory work is implicitly included. | Prepare before the trial starts. | The preparation boundary remains visible, while the three lanes distinguish a prerequisite, the main service and continuous coordination. Fictional, not proof. | Agree readiness and preparation costs before delivery begins. | The reader can distinguish readiness work, delivery phases and the conditions for moving between them. | Approve the readiness check before setting a delivery start. | S77 / preparation-before-delivery; alternative S89 | HTML only; real evidence required. |

Suggested next headline: Approve the readiness check before setting a delivery start.

Copy says: Preparation is real work with its own scope, timing and agreement; it must not disappear inside the delivery promise.

Image adds: Phase-aligned bars make a readiness-only lane, delivery-only lane and continuous support visibly different; each bar also names its phase range.

Together: The reader can distinguish readiness work, delivery phases and the conditions for moving between them.

Medium: editable HTML diagram and typography; no generated artwork needed. Canvas: 16:9 desktop; free-height responsive document on phone. Reading order follows the relationship and ends with the implication. Qualifications stay visible; no client assets.

Selected treatment: S77 phase grid and spanning workstreams, with an explicit readiness boundary and text phase labels on every bar.

Alternative: S89 Chronology. Allows more explanation of each milestone, but loses the overlap between continuous support and delivery. Use when event sequence is the main question.

Count: Three ordinal phases in these examples; repeatable workstreams have explicit start and end phases. See reuse.json for actually checked instances.