Back to Basics: Press Release “Musts” To Check For Before You Submit
Before you submit a press release, check the news, the source, facts and quotes, contacts, links, assets, and timing so small errors don’t undo good work.
Read article
A useful press release answers the reader’s first questions quickly and gives them enough reliable detail to go further. Its job is to explain a development, not to make the reader work through a sales pitch. This guide walks you through the process from fact sheet to final read.
Write the facts before the headline
List what happened, who is involved, when it takes effect, where it applies, and why it matters. Confirm those details with the people responsible for them. This fact sheet becomes your reference when several reviewers suggest changes, and it helps you notice when a draft has drifted away from what is actually true.
Add a line for anything that is not yet confirmed. Pricing, availability dates, and partner names often change late in the process. Marking them clearly prevents an uncertain detail from slipping into the final version as if it were settled.
Keep the fact sheet short enough to read in a minute. When a reviewer proposes a new sentence, you can check it against the list instead of debating it from memory. If a proposed claim is not on the sheet, ask who can confirm it and what the source is before it goes into the draft.
Put the development in the opening
The first paragraph should make sense on its own. Name the organization, state the news, and give the most important context. Avoid opening with a broad observation such as “In today’s fast-moving world.” It delays the information the reader came for.
A simple structure is: organization + action + specific development + audience benefit. For example, a manufacturer might announce a new repair center, its opening date, and the region it will serve. That single paragraph can be quoted by a reporter, shown in a search result, or summarized by an AI assistant without losing its meaning.
Build the body around likely questions
Move from the most important details to the supporting context. Explain availability, scope, evidence, and any relevant limitations. Use short paragraphs and descriptive subheadings when they improve scanning. Keep background material separate from the announcement itself.
Imagine the questions a reporter would ask on a call. How much does it cost? Who can use it? What happens to existing customers? What is not included? Answering those questions in the release saves time for everyone and reduces the chance of someone filling the gap with a guess.
Be honest about limitations. If a service is available only in certain regions, or a feature arrives later for some customers, say so plainly. Readers and journalists notice when a release avoids an obvious question, and a clear statement of scope makes the rest of the announcement more believable.
Make the quote add something
A quotation should explain a decision, offer perspective, or describe a consequence. It should sound like a person who understands the subject. A quote that merely repeats the opening paragraph occupies space without helping the reader. Obtain approval from the person being quoted.
Read the quote aloud. If it sounds like something nobody would say in conversation, simplify it. A sentence about why the team chose a particular approach, or what customers asked for, is usually more useful than a statement of pride or excitement.
A partner or customer quote can add an outside view, but only if it says something specific about the change. Make sure the person has approved the exact wording and understands where the release will appear, including your website and social channels.
Make it accessible and easy to reuse
Write link text that describes the destination rather than “click here.” Give every image a caption and a meaningful text alternative, and add captions to any video. Avoid putting key information only inside an image or a PDF, where some readers and tools cannot reach it.
Many people will meet your release through a LinkedIn share, a post on X, or a search snippet. Clear facts, plain language, and consistent names help each of those versions stay accurate.
Use the same product names, spellings, and figures throughout. When an AI answer engine or a search tool draws on your release, small inconsistencies can turn into confusing summaries. A short, factual description of the organization near the end also gives those tools a reliable sentence to quote.
Finish with the practical details
- A short, factual company description without unsupported superlatives.
- A media contact who is available after publication, with a direct email.
- Descriptive links to relevant documents or product information.
- Captions, credits, alt text, and permissions for supplied images and video.
- A final check of names, dates, numbers, time zones, and URLs.
- Confirmation that every reviewer has approved the final wording.
Read it without the branding
Imagine that the company name belongs to an organization you do not know. Is the announcement still understandable? Is the benefit clear? Reading from that distance makes jargon and unsupported enthusiasm easier to spot before publication.
If possible, ask someone outside the project to read it and tell you what happened in one sentence. If their summary matches your fact sheet, the release is doing its job. If it does not, revise the opening before you change anything else.
