Is Your Announcement Newsworthy? A 5-Question Test

Is your announcement newsworthy? The honest answer comes from five questions, asked before you write a word: is it new, why does it matter now, who cares beyond your own team, what proof supports it, and what is the story a stranger could retell? If you can answer all five clearly and specifically, you have a press release. If you cannot, you have something else — a plan, an update, or a hope — and publishing it as news will not make it newsworthy.

This guide works through the five-question test one question at a time, shows how to score your answers honestly, and explains what to do when the answer is no. It is a pre-writing decision test, not a diagnosis of a release that has already been sent. Use it to decide whether to write, wait, bundle, or pitch, and to strengthen a borderline announcement before it reaches a reader.

Key takeaways

• Ask five questions before you write: is it new, why now, who cares, what is the proof, and what is the story?
• A yes to all five means you have a release; a yes to three or four means the story needs strengthening first.
• If the answer is no, do not force a release — wait for a stronger moment, bundle smaller news into one real change, or pitch privately instead.
• The test is for the reader, not for you: judge newsworthiness by what changes for someone outside your team.
• A borderline announcement can often be saved with a date, a fact, a customer, or a clearer reason why now.

Question 1: Is it actually new?

New means something has changed that was not true yesterday. A launch, a result, a decision, an opening, a finding, or a new service all count, because each one creates a fact that did not exist before. A new slogan, a redesigned website, a restated mission, or a routine internal change does not count, however much work went into it, because nothing in the world is different for a reader. The test is not effort; it is change. Ask what a reader would learn from your announcement that they could not have learned last week, and write the answer in one sentence.

Be specific about the change, and be honest about its scale. A small change can be newsworthy if it matters to a defined audience: a local shop extending its hours, a service adding a feature its customers requested, or a charity opening a new session for a waiting list are all real changes. A large claim with no specific change behind it — a transformation, a revolution, a new era — is not newsworthy, because it cannot be checked. Specificity is what turns a claim into news: name what changed, for whom, and from when.

If you cannot name the change, stop and find it. Look for the decision that was taken, the date something starts, the result that was measured, or the offer that is now available. If none of those exists yet, the announcement is premature. Note what would make it new, set a date to revisit it, and use the waiting time to gather the proof and the detail that will make the eventual release strong. A release written too early cannot be unwritten, but a release written at the right moment, with a real change to report, will always be stronger.

Question 2: Why does it matter now?

Why now is the test of timing. A newsworthy announcement has a reason to be published this week, not at any convenient moment in the future. That reason might be a launch date, a deadline, a seasonal moment, a response to a public development, or a result that has just become available. Without a timing reason, a release reads as an announcement in search of a date, and a journalist has no reason to prioritise it over the stories that do have one.

State the timing reason plainly in the opening of the release, so the reader understands the urgency without being told to feel urgent. A launch on a stated date, a service available from a stated day, or a finding published this week all give the reader a clear why now. Avoid manufactured urgency: claiming a deadline that does not exist, or tying a routine update to a major news event it has nothing to do with, will be recognised quickly and will damage trust. The timing reason should be real, checkable, and relevant to the audience.

If there is no why now, create one honestly or wait for one. A genuine milestone, a customer result, a seasonal opening, or a completed project all provide timing. A vague intention to announce soon does not. Ask what would be lost if the announcement waited a month: if the answer is nothing, the timing is not yet right. If waiting would mean missing a launch, a deadline, or a moment when readers need the information, the timing reason is real, and it should be stated clearly at the start.

Question 3: Who cares, beyond your own team?

Who cares is the test of audience. A newsworthy announcement matters to people outside the organisation that issued it, and the release should be able to name them. Those people might be customers, a local community, a specialist profession, or a wider public, but they must be identifiable, and the benefit to them must be stated in their terms. An announcement that matters only to the team that made it — a promotion, an internal award, a new office layout — is internal news, and it belongs in a staff update or a company blog, not in a press release.

Name the audience early, and describe the change from their point of view. Instead of saying your business has launched a new system, say what customers can now do, how long it will take, or what it will cost. Instead of announcing a partnership, say what the combined offer gives to the people who will use it. This shift in perspective is the single most reliable way to turn an internal update into a reader-facing story, because it forces the writer to prove that someone beyond the office will notice a difference.

If the audience is narrow, that is not a weakness, provided the release is honest about it. A story for a specialist audience, written in that audience's language and sent to the journalists who serve them, can be highly newsworthy within its field. A story that pretends to be for everyone, when it is really for a small group, will satisfy no one. Define the audience, write for them, and judge the announcement by whether they would care, not by whether the whole world would.

Who is this for?

• Named customers or users who gain something, save time, save money, or get access to something new.
• A local community affected by an opening, a closure, a service change, or an event.
• A specialist audience that follows this topic and would act on the information.
• A wider public with a reason to care, stated in their terms, not yours.
• Only your own team, investors, or suppliers: a sign the announcement is internal news.

Question 4: What is the proof?

Proof is the test of credibility. A newsworthy announcement can be checked: it offers a fact, a figure with context, a date, a document, a named person, or an experience a reader can verify. A claim without proof — a market-leading product, a record result, an exceptional response — asks the reader to trust the sender's judgement, and most readers, quite rightly, will not. Proof does not need to be elaborate, but it does need to be present, and it needs to be specific enough to be checked.

Gather the proof before you write, not after. If you claim a result, know how it was measured, over what period, and compared with what. If you cite a survey, know who carried it out, when, and among whom. If you announce a partnership, know what each side contributes and when the joint offer starts. If you quote a customer, have their permission and their exact words. A release written around proof will be shorter, clearer, and more persuasive than one written around adjectives, because the facts do the work the adjectives were trying to do.

Be honest about the limits of your proof. A result from a small pilot, a survey of a limited group, or an early figure should be described as such, with the scope stated plainly. Modest, accurate proof builds trust; inflated proof destroys it when it is checked, and it will be checked by the journalists and readers whose trust matters most. If the proof is not yet strong enough, use the time before publication to strengthen it: collect the figure, confirm the date, or secure the quote. A release with proof will always outperform a release with promises.

Question 5: What is the story?

What is the story is the test of retellability. A newsworthy announcement can be retold by a stranger in a sentence or two, without notes, and still make sense. That sentence should contain a person or group, a change, and a reason to care: a local bakery now delivers to a new neighbourhood, a small manufacturer has cut delivery times in half, a charity has opened a service for families on its waiting list. If the announcement cannot be retold that simply, it is not yet a story; it is a collection of details in search of one.

Find the story by listening for the human element. Who is affected, what did they need, and what changed for them? A story with a person in it — a customer, a patient, a resident, a student — will be remembered and repeated far more readily than a story about a system, a strategy, or a brand. That does not mean inventing a person or exaggerating an experience; it means choosing the real detail that shows the change in human terms, and letting the background support it rather than lead it.

Test the story by telling it aloud to someone outside the business. If they can repeat it back, and if they ask a follow-up question that shows interest, the story works. If they look puzzled, ask what happened, or repeat your own jargon back to you, the story needs another pass. Rewrite until the retelling is easy, because the ease of retelling is what determines whether a journalist, a reader, or a search summary will carry the story onward. A story that cannot be retold cannot be picked up, however well it is distributed.

How do you score your answers honestly?

Score each question separately, and be strict. A clear answer is specific, checkable, and stated in the reader's terms: a named change, a real date, a defined audience, a verifiable fact, and a retellable story. A vague answer — a general improvement, an approximate audience, a claim with no source, a story that needs three paragraphs to explain — counts as weak, however much you wish it were strong. The purpose of the test is to protect the next release from the weaknesses of the last one, and that only works if the scoring is honest.

Write the five answers down, in plain sentences, before you draft the release. That written record is your brief: it tells you what to lead with, what proof to include, and what to leave out. If one answer is weak, the brief tells you exactly what to fix, whether that is a date, a fact, a customer, or a clearer story. Do not start writing the release in the hope that the weak answer will resolve itself during drafting; it rarely does, and the resulting release will carry the same weakness in a longer form.

Share the five answers with a colleague who was not involved in the announcement, and ask them to mark any answer they do not understand or do not believe. An outside reader is the best proxy for a journalist, because both meet the announcement without prior context or loyalty to it. If the outside reader passes all five answers, the release has a strong foundation. If they flag one, fix that one before you write. The time spent on the test is repaid many times over in the strength of the release that follows.

Scoring the test

• Five clear, specific answers: write the release now, leading with the story and the timing.
• Four clear answers, one weak: strengthen the weak answer first, then write.
• Three clear answers: the announcement is borderline — bundle, wait, or pitch, as below.
• Two or fewer clear answers: do not issue a release; the story is not ready.
• Any answer that relies on hype, adjectives, or a promise with no proof: treat it as a no, and fix the fact, not the wording.

What should you do when the answer is no?

When the answer is no, you have three good options, and forcing a release is not one of them. The first is to wait. Many announcements become newsworthy with time: a product moves from plan to launch, a pilot produces a result, a partnership gains a joint offer, or a seasonal moment arrives. Waiting is not inaction; it is using the interval to gather proof, confirm dates, and prepare a release that will be ready when the news is real. Set a date to revisit the announcement, note what would make it pass the test, and work towards that milestone.

The second option is to bundle. Several small updates, none of which passes the test alone, can combine into one meaningful change: a set of service improvements that together transform an offer, a series of hires that together open a new capability, or a collection of local changes that together affect a community. Bundling works only when the combined story is genuinely one story, with a single headline and a single reason why now. Do not bundle unrelated news to manufacture importance; a reader will see through it, and the release will be judged as a list rather than a story.

The third option is to pitch instead of releasing. A story that is too small, too specialist, or too early for a press release may still interest one journalist, if it is pitched privately with a clear angle and an offer of access, data, or an interview. Pitching respects the journalist's judgement, it keeps the relationship warm, and it avoids publishing a weak release that trains readers to ignore your next one. Choose the option that fits the material, and remember that a no from this test is information, not failure: it tells you what the story needs, and it protects your reputation for the announcement that will pass.

How can you strengthen a borderline announcement?

A borderline announcement — three or four clear answers — can often be strengthened with one concrete addition. A date turns a plan into news. A fact turns a claim into proof. A named customer turns an abstraction into a story. A clear audience turns a general update into a relevant one. Identify the weakest answer from the test, and add the missing element, rather than rewriting the whole announcement in stronger language. Stronger language without a stronger fact is hype, and it will not survive the test when a reader applies it.

Work through the weak answer systematically. If the timing is weak, find the launch date, the deadline, or the seasonal reason, and state it. If the proof is weak, collect the figure, the document, or the quote, and check it. If the audience is weak, name the people affected and describe the change in their terms. If the story is weak, find the person or the moment that makes it retellable, and lead with that. Each fix is small, each is concrete, and each moves the announcement closer to passing the test without inventing anything.

Finally, cut what does not help. A borderline announcement is often weakened by extra material added to make it look bigger: background history, unrelated achievements, or praise from partners. Removing that material clarifies the story and makes the real news easier to see. A shorter, sharper announcement with a clear story, a real date, and a checkable fact will always outperform a longer one padded to look important. Strengthen the weak answer, cut the padding, and re-run the test. If it passes, write the release. If it still does not, choose wait, bundle, or pitch, and keep the material for the moment when it is ready.

Ready to test your next announcement?

The five-question test is a habit, not a hurdle. Ask it before every announcement, score it honestly, and let the answers decide whether to write, wait, bundle, or pitch. Over time, the test will change how announcements are planned: teams will gather proof earlier, set real dates, and look for the customer story before the release is drafted. That shift is the real value of the test, because it makes the news stronger before a word is written.

When your announcement passes all five questions, PressFudge can help you share it with news sites and the audiences who will care about it. You can see the current plans and prices at pressfudge.com/pricing, from Basic at $149 to Enterprise at $2,749, with professional writing available as a $99 add-on on every order. Test the story first, then publish it with confidence.