Press Release Headline Template 1
[Organization] [launches/opens/announces/adds] [specific development] for [audience/location].
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 press release headline tells an editor what happened and why it may matter in one scan. It uses concrete nouns and verbs, avoids unsupported superlatives, and leaves secondary details for the subheadline and opening paragraph.
[Organization] [launches/opens/announces/adds] [specific development] for [audience/location].
[Organization] [reports/finds] [specific measured result] after [study/pilot/program].
[Organization] names [person] [role] to [relevant mandate, if material].
[Place/organization] expands [service/program] to [location/audience] beginning [date, if newsworthy].
Skill progression worksheet for Press Release Headline: beginner version → [ ]; intermediate constraint → [ ]; advanced constraint → [ ]; what changed in the writing decision → [ ]; next skill to study → [ ].
Constraint decision sheet for Press Release Headline: normal case → [ ]; harder constraint → [ ]; what must stay true → [ ]; what can change → [ ]; evidence/reader/genre check → [ ]; specialist skill to study next → [ ].
Misconception correction audit for Press Release Headline: shortcut or assumption → [ ]; why it fails here → [ ]; corrective move → [ ]; principle that must remain true → [ ]; goal-based next skill → [ ].
Failure-mode and reader-intent audit for Press Release Headline: visible symptom → [ ]; likely underlying problem → [ ]; reader need → [ ]; competing technique considered → [ ]; correction → [ ]; evidence/genre/format constraint → [ ]; final verification → [ ].
Boundary-and-tool-choice audit for Press Release Headline: reader objection → [ ]; actual writing job → [ ]; evidence/genre/format boundary → [ ]; tempting alternative → [ ]; why it is the wrong tool here → [ ]; correct adjustment → [ ]; final verification → [ ].
Evidence/support and mastery ladder for Press Release Headline: minimum acceptable → [ ]; strong → [ ]; expert → [ ]; audience/genre constraint → [ ]; evidence or story support → [ ]; boundary that would require a different technique → [ ].
Certainty and expert-exception audit for Press Release Headline: statement or choice → [ ]; evidence/canon/authority supporting it → [ ]; confidence level → [ ]; uncertainty that must be named → [ ]; expert exception → [ ]; nearest alternative technique → [ ]; why the final choice fits better → [ ].
Purpose-and-verification decision audit for Press Release Headline: real writing job → [ ]; plausible choice A → [ ]; plausible choice B → [ ]; downstream consequence of each → [ ]; facts/evidence/canon to verify → [ ]; reader or genre boundary → [ ]; final purpose-fit reason → [ ].
Publication-readiness audit for Press Release Headline: claim/advice/example → [ ]; strongest available source tier → [ ]; important disagreement or uncertainty → [ ]; what would change the conclusion → [ ]; publish now / qualify / revise / hold → [ ]; final verifier or source of truth → [ ].
Provenance and classification audit for Press Release Headline: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].
Source-record and update audit for Press Release Headline: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Source-ledger and revision-history audit for Press Release Headline: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
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 → [ ].