# Bounded scope storyboard

Previous setup: Establish the desired programme and its necessary delivery activities.

| 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 may infer that the whole ambition is covered by the quoted core programme. | Make the boundary of the offer visible. | Each row makes the boundary observable; additional services remain choices instead of being smuggled into the core offer. Fictional, not proof. | Resolve essential gaps before agreeing the core scope. | The reader can identify included work, separately quoted additions and unresolved needs before agreement. | Resolve required additions and acceptance criteria before agreement. | S40 / bounded-scope; alternative S57 | HTML only; real evidence required. |

Suggested next headline: Resolve required additions and acceptance criteria before agreement.

Copy says: A price or programme description is usable only when its units, period and exclusions are explicit.

Image adds: Aligned descriptive columns separate included work from separately quoted work; mobile rows retain both column labels.

Together: The reader can identify included work, separately quoted additions and unresolved needs before agreement.

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: S40 reference-table family with wide descriptive columns and labelled stacked rows instead of narrow tick/count columns.

Alternative: S57 Comparison columns. Useful for choosing among complete packages; misleading if it turns inclusions and exclusions within one offer into competing offers.

Count: Repeatable bounded deliverables; quantities are example content, never universal scope requirements. See reuse.json for actually checked instances.