Before you send a release, do you know which mistake a last read would catch? It is rarely the headline. More often it is a wrongly typed job title, a quote nobody approved, or an "announcement" with no benefit to any reader. This article is for anyone building a press release publishing checklist: a way to test newsworthiness, headline, accuracy, quote approval, contact details, embargo, link and follow-up in one table before sending. Akua Adforce does not distribute press releases. The checklist is for readers who do their own sending. The release, people, companies and dates used here are hypothetical, and nothing in the article promises publication or any result.
Why Use a Press Release Publishing Checklist Before Sending
A sent release cannot be recalled, only corrected
Once a release reaches a recipient it is out of your hands. A wrong date or a missing contact line can only be fixed with a second email, and the second email dents trust in the first. The job of a checklist is to catch the need for a correction before sending. For the difference between a release and a promotional article, see what is a press release versus a guest post; this article assumes you already know it.
Who the checklist serves
It serves two people: the one sending and the editor reading. An editor usually filters a release in seconds. If newsworthiness, accuracy and contact details are in place at first glance, the release is read; if not, it is closed. If you also plan a reader-facing article alongside the release, the guide to PR articles and bylined thought leadership gives a frame for that piece.
Think of the checklist as a gate where each item closes with a yes or a no. A "maybe" means the item is not finished. In a hypothetical case, a software firm wants to announce a new regional office. Under newsworthiness, writing "industry staff" as the audience is not enough; the answer must say what the opening changes for them. Without that, the release is not ready to leave. A gate like this costs less effort than rewriting the same release five times.
The Newsworthiness Test: Why Now, for Whom?
The timing question
The first measure of news is time. If the release does not explain why today, an editor can set it aside. An anniversary, a product launch, a legal change or an event date supplies the timing. Your organisation merely doing something new is not news; novelty becomes news when it touches something the reader needs.
The reader question
The second measure is audience. An editor reads a release through the eyes of the publication's readers. A release may matter to your industry and still mean little to them. In a hypothetical case, a local producer announces a certification. For a trade outlet the certification is a benchmark; for a general outlet it is a passing note. The same event carries different weight in different places, so factor that into who you send it to.
A three-question quick test
Run the test like this:
- What happened? Say it in one sentence with no adjectives.
- Who does it matter to? Name what changes for them, not just a group.
- Why now? Point to a date, a development or a calendar reason.
If all three can be written, the release can become a story. If one cannot, that gap is the weak link and should be solved before sending. Write the three answers on the record line too, so the same reasoning comes out whenever an editor asks.
Headline, Summary and Opening Paragraph
The news itself in the headline
A release headline states the news; promoting the brand is not its job. "Company X is thrilled to announce" carries no information. "Workshop Y opens its second branch" says what happened. For principles that carry over, see writing a sponsored post headline, then strip out the adjectives.
The opening paragraph as an inverted pyramid
The first paragraph answers who, what, where and when, and leaves detail for later paragraphs. Editors may stop reading after it, so the most important fact goes first. For the structure of news writing, how to write a news-style sponsored article is a useful companion; a release follows a similar pyramid.
The summary line and length
The summary sits under the headline and opens the news one step further in a short sentence. Keep it to two lines and avoid repeating the headline. A release that fits on a single page is a sound limit; longer text makes the editor's job harder. Move long detail into supporting material and mention it in one closing sentence.
Accuracy: Names, Titles, Dates and Figures
The four fields to verify
A release is exposed to errors in four fields: names, titles, dates and figures. For each, someone other than the author should check the source and say "correct". In a hypothetical case, the release says 1 November and the event is on 8 November. That error can only be repaired by a second message after the editor has read the first.
The source and date of each figure
Every figure in a release needs a known source and date: if it is your own data, which period does it cover; if it is external, who published it? Leave out any figure you cannot source. For ways to present sources to readers, citing sources in articles: an attribution guide offers a framework.
Putting the check in a table makes it easier. Next to every figure, date and name, open a "source" and a "checked by" column. A hypothetical release with seven verifiable facts gets seven rows. A blank row means the fact is either removed or verified. This simple routine also stops late "let us add one more thing" edits from entering without a check.
Quotes and Approval
The quoted person must approve
If a release quotes someone, show the wording to that person and get written approval. Approval should not rest on a memory that they once said something similar. In a hypothetical case, a general manager made a remark in a meeting; the release polishes it slightly and attributes it to her. If she objects later, correcting it is harder. Keep the approval message with the release record.
Authority to speak for the organisation
The person quoted should be able to speak for the organisation. Using a quote from an intern or someone who has recently left creates trouble. Their title must also be valid on the date the release goes out, and that title belongs in the accuracy table.
What a quote is for
A good quote adds a view to the facts rather than repeating them. "We are very happy to open our new office" is not information. "With the new office we can answer local support requests on the same day" explains an intention. For every quote, ask whether the release loses anything if the sentence is cut. If not, the quote is not needed.
To make approval easy, send the quote to the person as its own line, not buried in the draft, and ask three things: are the words right, is the title right, may it run as written? Keep the reply. If they ask for a change, send the new version back for approval. In a hypothetical case the manager prefers "we are shortening service times" to "we are happy", which makes the quote more concrete. Approval must always cover the final version, not an earlier draft.
Contact Details and Supporting Materials
What the contact line needs
The contact line at the end shows the editor whom to ask. A name, title, email and phone number are enough. The person must really be reachable; naming someone on holiday makes an editor give up. On personal data, list only the person assigned to this task and only with their agreement. A general organisation address is a safer choice than a personal number.
Preparing supporting material
Images, logos and documents speed the editor along. You must hold the right to use each image; if third parties appear in a photo, their permission needs a separate check. That is a check question only, since legal detail is outside this article. Keep file names clear, gather files behind one link rather than embedding them in the email, and open the link yourself before you send.
- Is the usage right and resolution of each image written in the file name or note?
- Does each image have a short, accurate caption line?
- Will the linked files stay reachable after sending?
The third point matters because an editor may open the release the next day. A temporary link then looks broken, and the release loses its pull.
Embargo and Timing
When an embargo note is needed
An embargo is a note asking that news not be published before a stated date and time. It is needed when a release is shared ahead of a launch or statement. Give the date, time and time zone. Because an embargo is a request, you cannot assume every editor accepts it; for anyone who does not, the only safe path is not to send early.
Choosing the day and hour
Timing follows the calendar of the news itself. An event release goes before the event, a results release when the results are public. We have no measured data on which weekday works better, so choose day and hour from your own recipients' past behaviour. No timing choice should be presented as affecting whether a release is published.
The most common embargo error is writing the date but leaving out the hour and time zone. In a hypothetical case, a note reading "Embargo: 12 November" does not tell the editor whether that means morning or evening. A correct note reads "Embargo: 12 November 2026, 09:00 (local time)". If the news has already appeared on another channel, such as social media or your own site, the note means nothing, so match your own channels' calendar to the release schedule before sending.
The Link and Anchor Decision
Is a link needed at all?
Not every release needs a link. Add one when it takes the reader to a detail page, a document or a source. A link to a home page is noise for an editor. In a hypothetical release, a single link to a page with the new office address and opening hours is enough. Do not add a link on the assumption that releases help rankings.
Care with anchor text
The anchor should be natural, such as the page name or brand name. Google's spam policies list keyword-focused anchors in content distributed across other sites, press releases included, as link spam examples, so stuffing a commercial keyword into the anchor is both risky and unnecessary. To go deeper, safe link building under Google link spam policies explains the boundaries.
Open the target page the day before sending. A redirect, a maintenance page or deleted content lowers the release's credibility. There is also a rel question. If a release goes free to a publisher, the choice of how to mark the link is the editor's. If a paid placement is involved, the Google page on outbound links points to the sponsored value. You do not set that in the release, but if you run a paid article alongside, do not hide the sponsorship, and check that the right value was applied.
Follow-Up After Sending
Keeping the record from the start
The after-sending record is simple: who got which version on which date, and what came back. Without it, "nobody replied" is an impression, not a fact. To measure follow-up more systematically, the tracking logic in sponsored post reporting with UTM, GA4 and Search Console can be adapted by tagging the release link.
Meeting the reply
If an editor asks a question, answer the same day, which is why the named contact must be reachable on sending day. In a hypothetical case, an editor asks for the source of a figure. If the accuracy table is ready, the answer takes a minute. If it is not, the editor will not wait.
- Record the version sent and the date.
- Answer incoming questions the same day.
- If the release appears, save the published text, because it may change later.
Add one more column to the record: what will I change next time? A line such as "fewer adjectives in the headline" or "get quote approval two days earlier" is enough. As entries build up, you see whether the same mistake repeats. That improves your process more than any single release, and the knowledge survives a change of team. It also answers a manager's question about which release went to whom, and what came back, in a single look.
What to Do When No Reply Comes
Reading the silence
No reply usually means no, but do not record it as a firm refusal. Possible reasons are stale timing, the wrong recipient or a headline that did not catch attention. Run the release through the checklist again and look for the weak item. Resending without fixing that item achieves nothing.
One short follow-up
If you follow up, write one short message: add new information or a current development and refer to the first release. Resending the same text or calling repeatedly pushes the recipient away. If there is still no answer after one follow-up, close the matter and record the lesson for the next release. No sending ensures publication, and silence does not block future releases either.
When no reply comes, an article written for readers beside the release is another option. On Akua Adforce you could choose the content writing product for that, but that is new content production rather than release distribution, and the decision to publish still belongs to the other party.
Example Template: Pre-Send Checklist Table (Hypothetical)
The table that follows is entirely hypothetical; the release topic, names and dates are invented. Close every row with a yes or a no before sending.
| Checklist item | Hypothetical entry | Decision |
|---|---|---|
| Newsworthiness | Hypothetical: a local workshop opens a second branch; weekly service hours start for the neighbourhood | Yes, date confirmed |
| Headline and summary | Event in the headline, audience in the summary; no adjectives | Yes |
| Accuracy | Names, titles, dates and figures matched to sources | Yes, checked by a second person |
| Quote approval | Hypothetical: the manager's written approval received | Yes |
| Contact | General address and a named person, reachable on sending day | Yes |
| Embargo | Opening date, hour and time zone written in the note | Yes |
| Link and anchor | One descriptive link, brand-name anchor, target page loads | Yes |
| Follow-up plan | Send record and one follow-up message ready | Yes |
If any row says no, the release waits. Fill in the table afresh for each release; copying old answers defeats the purpose of the check.
Frequently Asked Questions
What should be the first item on a press release publishing checklist?
The newsworthiness question: why is this news now, and for whom? If you cannot answer it in one sentence, the other items will not rescue the release. Settle what happened, who it affects and why today matters first. The headline, quote and contact details are all built around that answer.
How do you test newsworthiness before sending?
Read the first two sentences as an editor would and ask three things: what happened, who does it matter to, and why now? If any answer is vague, the release is an announcement draft. Also check whether you could rewrite the same fact for the publication's own readers. If you cannot, the audience fit is weak too.
When is an embargo note added?
An embargo asks that the information not be published before a stated date and time. Add the note when you share a release ahead of a launch, event or statement and the content must stay private until then. State the exact date, time and time zone. It is a request, so never assume every editor will honour it.
Should the release include a link?
Include a link when it sends the reader somewhere useful, such as a detail page, a document or product information. One descriptive link is enough for most releases. Choose natural wording such as the brand or page name rather than a keyword-packed anchor, and do not assume a link in a release helps rankings.
Should a release be resent if there is no reply?
Not straight away. First ask why the release went out and why no reply came: was the topic stale, was the recipient wrong, was the headline weak? If you do resend, add something new or a current angle in one short follow-up. Repeated messages push the recipient further away.
Does sending a release guarantee publication?
No. Sending only means the information has arrived. The decision to publish belongs to the editor, and no release can promise publication, timing or visibility. That is why the checklist focuses on giving the editor complete, verifiable information instead of chasing an outcome.
Conclusion and Next Step
The checklist asks one thing: does this release deserve an editor's time? If newsworthiness, accuracy and approval are all yes, send it; if not, hold it and close the missing item. You run release distribution yourself or with a third party, and Akua does not offer it. If you also want a source-backed piece that speaks to readers directly, look at the content writing page and start an order there; once the order reaches the seller, decisions about the content and publication are the seller's editorial responsibility.
Post a comment
Please log in to leave a comment. Login