Elevator Pitch Template 1
[Project] helps [specific audience] achieve [outcome] by [distinct method], especially when [problem/context].
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong elevator pitch is easy to understand on first hearing, concrete enough to remember, short enough to deliver naturally, and focused on the listener’s likely question rather than trying to include every feature or plot detail.
[Project] helps [specific audience] achieve [outcome] by [distinct method], especially when [problem/context].
It is a [category] about [subject] for [audience], with a focus on [distinct angle].
Story pitch: When [inciting event], [protagonist] must [goal] before [stakes], but [central obstacle].
Problem → value: [Audience] struggles with [problem]. We provide [solution] that [distinct benefit].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].