Press Statement Format Sample

Writing press statements that don't look like they came from a template factory

I've been drafting org communications for about seven years now, mostly in crisis mode where every hour you spend on wording is an hour the news cycle moves without you. The format itself is deceptively simple. You've got the org header, dateline, the body copy, boilerplate, and contact block. That's it on paper. In practice the thing that kills you is the middle section where you have to state facts without admitting liability, promise action without committing to a timeline, and make something sound important without using five paragraphs to say what could be said in two. I learned this the hard way during a supply chain disruption back in 2019. We had to issue a press statement about a product recall, and I'd written what I thought was a clean draft. Two hours into legal review they flagged a single sentence where I'd used the word \"defect\" instead of \"deviation from specification\". One word changed our entire exposure profile. The workaround I use now is to run the full draft past legal before you polish the tone, not after. It sounds backwards because lawyers are boring, but getting their note on word choice early saves you from rewriting the whole thing later when you already think it's done.

Press Statement Format Sample

Here's the structure I actually use, not the one from whatever PR textbook you found online. The header takes one line with the organization name, sometimes a logo line if you're sending it to wire services. Then the dateline: city, state/country, and the full date in spelled-out form, not numeric. I've seen people write \"New York, NY – 03/15/2024\" and then get called on it because different markets read that date differently. Write it out. Full stop. The body follows a strict inverted pyramid. Lead paragraph states what happened, when, and the immediate impact. Second paragraph gives context or background. Third paragraph covers what you're doing about it. That's three paragraphs maximum for most routine statements. If you're exceeding that you're probably hiding something or you don't know what you're trying to say yet, and neither does the reader. Boilerplate comes last. This is the standard \"About [Organization]\" paragraph that every outlet will either use or adapt. Write it once, keep it current, and don't try to be clever here. It should read like a dictionary entry, not a sales pitch. Contact block goes below that with a media liaison name, email, and phone. Some orgs include a second contact for technical questions. I recommend it if your statements regularly draw follow-up from trade press who need engineering-level detail.

The thing nobody warns you about is the embargo handling. If you're giving early access to a reporter, you need a separate line at the top that says \"EMBARGOED UNTIL [DATE/TIME]\" in caps. I've worked with juniors who forgot this and then spent three panicked hours on the phone trying to get a story pulled before publish. It happens more than you'd think, especially when you're juggling multiple outlets with different embargo times. Keep a shared tracker. Google Sheets works fine. Put the time in the outlet's local timezone, not yours, and double-check it before sending. Here's a quick reference for the full format layout: [Organization Letterhead or Name]
FOR IMMEDIATE RELEASE

[CITY, State/Country] — [Full Date]

[Headline: one line, active voice, no more than 20 words]

[Lead paragraph: who, what, when, where, why — aim for 40-60 words]

[Supporting paragraph(s): context, quotes, details]

[Action paragraph: what's being done, next steps]

###

[Boilerplate: About the organization]

Media Contact:
[Name]
[Title]
[Email]
[Phone]

The \"###\" separator is industry standard. Wire services recognize it immediately as the end-of-body marker. Skip it at your peril if you're distributing through AP or similar channels. They'll auto-format around it or flag it as an error, which delays your statement by however long their manual review queue is on any given day. Quote placement matters more than people realize. Put the most quotable line in the first or second paragraph. Reporters grab the first sentence they can lift. If your best quote is buried in paragraph four you've essentially handed them someone else's language to lead with. I once had a CEO's actual highlight moment — something sharp and genuine — stuck in a middle paragraph while the editor took the stock \"we're committed to transparency\" line from the lead instead. Frustrating doesn't cover it. Length varies by situation but the sweet spot for routine announcements is 300 to 500 words. Crisis statements skew shorter, usually 200 to 350, because longer equals more places for misinterpretation. Investigations or complex product launches might run 600 to 800 if you actually need the space, but anything over 900 words is a blog post, not a press statement. Use the blog for detail. The statement gets the headline version.

Tone is where most drafts fail quietly. Active voice, present tense for what's happening now, past tense for what already occurred. Avoid adverbs unless they're doing real work. \"Strongly believes\" tells the reader nothing. \"Believes\" with a specific reason attached tells them everything. Same with hedging language. \"We are working to address the issue\" is weaker than \"We are remediating the issue by [specific action]\". Specificity reads as confidence even when the news is bad. One counter-intuitive tip: never send a press statement without first running it through a readability checker. Tools like Hemingway Editor or even the built-in one in Word will flag sentences over 25 words and passive constructions. I know that sounds basic but I've reviewed statements where the average sentence length was 38 words and the passive voice count was high enough to make the whole thing sound evasive, even when the content was direct. Plain language isn't dumbing it down. It's removing the friction between your message and the person reading it at 7 AM before their first meeting. The file naming convention is another mundane thing that causes real problems. Use \"orgname_statement_dateline.pdf\" or the equivalent in your system. Not \"final_v2_revised ACTUAL.pdf\". Not \"Statement FINAL.docx\". I've been the person who had to dig through a shared drive to find which version legal actually approved, and it took 45 minutes because nobody followed a naming standard. Five seconds to set a rule now prevents that later.

When to hold back is worth mentioning too. Not everything needs a press statement. Internal policy changes, minor vendor switches, routine hiring — these don't warrant the format and they sure as hell don't warrant the attention. A press statement signals importance. Using it for trivial matters trains the press to ignore you when something actually matters. I've seen orgs burn their credibility on this by issuing half a dozen boilerplate announcements in a single quarter about things that didn't deserve the overhead. The press that pattern. If you're looking for a downloadable template, most professional PR associations offer one. The Public Relations Society of America has a solid sample format you can adapt. Government communications offices often publish their own style guides that double as templates — the White House press briefing format is publicly available and surprisingly useful even for private sector use if you strip the partisan formatting. Your local bureau of tourism or economic development might also have a press release kit you can borrow from. These are free and already vetted by people who do this for a living. The biggest mistake I see is treating the format as decoration rather than function. Every line has a purpose. The dateline isn't aesthetic. The marker isn't tradition. The boilerplate exists so outlets don't have to write their own background section. The contact block exists so you control who responds instead of leaving it to chance. When you understand why each piece is there you stop seeing the format as a constraint and start seeing it as a delivery system.

One final thing that nobody puts in the template: always keep a versioned archive. I use a simple folder structure with dates, and I save every issued statement plus the working drafts that led to it. Six months later when someone asks why you said X on date Y and your memory is vague, having the exact document in hand is worth more than any reformulation you could produce on the fly. I've had board members ask me to explain statements I wrote three years prior, and my archive has always had the answer within 30 seconds.