What Counts as a Verifiable Business Announcement?

By Kevin Mahoney

A verifiable business announcement has three parts. There is a specific event your organization can name and date. Every material fact in it maps to a record someone else could check. And an authorized person approved the exact wording before release. If any one of those is missing, you have a draft, not an announcement.

That definition is stricter than most businesses expect, and it should be. Newswire content rules and Google's search policies both reward the same basics: news that is real, clearly attributed to the company it names, and free of manipulation. This guide explains each test, shows what counts as a source record, and gives you a fact-documentation worksheet you can fill out before anyone drafts a word.

The Three-Part Test

1. A real, timely event (not a claim about how good you are)

An announcement reports something that happened or is scheduled to happen. “We launched a scheduling feature on October 6” is an event. “We are the most trusted scheduling platform” is a claim. Only the first can be the news.

ACCESS Newswire's published content guidelines list common news angles its editors accept. These include product launches, new hires or personnel changes, upcoming industry events, whitepaper or research releases, awards, store openings, and partnerships or deals between companies. The same guidelines say a release should not be used for advertising or to post a general-interest article, and that the news must be clearly stated in the headline.

My practical test: if you remove every adjective from the headline, is there still something new left? If not, there is no announcement yet.

2. A checkable record behind every material fact

“Verifiable” means a reader, editor, or reporter could confirm the fact without taking your word for it. ACCESS's guidelines state that information in a release must be legally and factually accurate. They also say editors may refuse a release containing pertinent information they cannot verify independently.

For objective statements that function as marketing claims, the Federal Trade Commission's Policy Statement Regarding Advertising Substantiation sets out the agency's position. Advertisers and ad agencies must have a reasonable basis for claims before disseminating them, and this covers implied claims as well as express ones. When a statement expressly references its support, such as “tests prove” or “studies show,” the FTC expects at least that level of substantiation.

That last point catches many announcements. Writing “research shows” in a release is itself a claim that the research exists and says what you say it says.

3. Authorized approval of the exact copy

A true fact can still be unpublishable if the wrong person released it. Approval has layers:

• Company approval. Someone with authority signs off on the final wording, not an earlier outline.
• Named-party approval. Partners, quoted spokespeople, and anyone whose name appears should confirm their role and wording.
• Publisher-required authorization. ACCESS's guidelines note that written authorization from a company executive may be required in certain cases. Examples include network marketing companies, affiliated third parties, releases using a stock ticker symbol, and major corporate announcements such as mergers, acquisitions, and venture or equity capital investment. Partnership, deal, and acquisition releases may also require additional verification forms. Celebrity mentions require verification that the celebrity is aware of and approves the content.

What Counts as a Source Record?

Not all evidence is equal. The ranking below is my working framework for deciding how much weight a record can carry. It is practical judgment, not a publisher rule, and a publisher can always ask for more.

Strong: public and independently checkable

• A live product, pricing, or location page that matches the announcement on the day of release.
• An announcement or listing published by the other party, such as an award organizer's winners page or a partner's own post.
• Government or registry records, such as a business filing, license lookup, or trademark record.
• Published research you commissioned or produced, available at a stable URL.

Acceptable: private but producible on request

• A signed agreement, purchase order, or letter of intent that supports a partnership or contract claim.
• Internal reports or system exports that support a milestone number, dated and saved.
• Written quote approval from the named spokesperson.

Private records are fine as long as you can hand them to an editor who asks. If you wouldn't be comfortable sending the document, don't publish the fact it supports.

Weak: not enough on its own

• A screenshot of a social comment or unsourced review.
• “Industry sources say” or “experts agree” with no named source.
• A verbal promise from a partner who has not approved the wording.
• A number someone remembers but cannot point to.

When a fact only has weak support, you have three honest options: find a stronger record, narrow the wording until the record you have supports it, or cut the fact.

Why Verifiability Matters for Search, Too

Press releases are often bought for search reasons, so it is worth being precise about what Google's spam policies actually say. They list keyword stuffing as a spam practice. Their link spam examples specifically include links with optimized anchor text in articles, guest posts, or press releases distributed on other sites, along with paid advertorials whose links pass ranking credit. Google also states that paid links are not a violation when they include a “nofollow” or “sponsored” rel attribute.

The same page lists wire service and press release service sites among its examples of what is not inconsistent with its site reputation policy. In other words, a distributed release is not the problem. Manipulative tactics inside it are.

My takeaway for planning: an announcement's search value comes from being a clear, attributable, factual record of something that happened, pointing readers to a relevant destination. It does not come from packing the release with keywords or anchor text. ACCESS reaches a similar place from the editorial side: its guidelines say it won't accept releases deemed purposefully over-optimized for SEO. No release, however well documented, guarantees pickup, indexing, rankings, or traffic.

The Fact-Documentation Worksheet

Fill this out before drafting. It forces the verification work to happen first, when it is cheap to change the angle, instead of after a rejection. Copy it into a document and complete one worksheet per announcement.

Part A: The event

1. What happened or will happen, in one plain sentence with no adjectives?
2. Exact date of the event (or scheduled date):
3. Legal name of the organization making the announcement, as it will appear in the headline or first paragraph:
4. Why is this news now rather than six months ago or six months from now?
5. Which type of news is it? (Launch, hire, partnership, event, research, award, opening, expansion, milestone, other.)

Part B: The fact ledger

List every material fact the release will state: every number, date, name, title, location, comparison, and “first,” “only,” or “largest” statement. For each one, record:

• Exact wording as it will appear in the release.
• Source record that supports it (document name or URL).
• Record type: public, private-but-producible, or weak.
• Who can confirm it (name and role).
• Date last checked. Live pages change, so recheck on release day.
• Status: supported as written, narrowed to fit the record, or removed.

A fact marked “weak” with no stronger record should end the worksheet as “narrowed” or “removed,” never “supported.”

Part C: Claim check

1. Does any sentence imply a level of support (“proven,” “clinically,” “studies show,” “recommended by”)? If yes, is that exact level of support in the ledger?
2. Does any sentence compare you to a named or implied competitor? If yes, where is the comparison data? ACCESS's guidelines also state that negative statements directed at another company, especially by name, will be refused.
3. Is the subject in a higher-scrutiny category, such as supplements, health, finance, crypto, or litigation? If yes, read the publisher's current category rules before drafting and plan for longer review.
4. Does any line read as a sales pitch rather than a report? Mark it for rewrite or removal.

Part D: Approvals

• Company approver (name, title, date approved, version approved):
• Each quoted person (name, confirmed wording, date):
• Each named partner or third party (name, role confirmed, written approval on file: yes or no):
• Publisher-specific authorization needed? (Executive authorization, verification forms, celebrity confirmation.)
• Media contact with a valid email address:
• Destination URL checked and working, and does the page match the announcement?

Part E: Decision

• Go: every material fact is supported or narrowed, and every approval is on file.
• Hold: the event is real, but a record or approval is missing. Name the missing item and who owns it.
• Different format: there is no event beyond a sales message. Use your own site, email, advertising, or a clearly labeled paid format instead of a news release.

Worked Example: Tightening a Partnership Announcement

Here is a hypothetical to show the worksheet in action. It is illustrative, not a client case.

A software company wants to announce a “strategic partnership with a leading payment provider that will transform checkout for thousands of merchants.”

• The event: the two companies signed an integration agreement, and the integration goes live on a specific date. That is real news.
• “Strategic partnership”: the agreement is a standard integration listing, and the partner has not approved the word “strategic.” Narrowed to “integration.”
• “Leading payment provider”: the ledger has no ranking data. Removed. The partner is named instead, with its approval.
• “Thousands of merchants”: this is a forecast, not a record. Removed, or replaced with the verified number of current customers who can enable the integration on launch day.
• “Transform checkout”: an outcome claim with no support. Replaced with a factual description of what the integration does.
• Approvals: partner sign-off on its name and the wording, plus any partnership verification form the publisher requires.

The result is less exciting on first read and far more likely to survive editorial review, because every sentence now points to something real.

What Remains Uncertain

• Publisher rules change. Guidelines are updated, and each newswire applies its own rules. What one route accepts doesn't guarantee another, so recheck the current rules for the route you intend to use.
• Editors make the final call. ACCESS's guidelines state that its editors have the final say on what is appropriate for distribution. A complete worksheet lowers risk. It does not guarantee acceptance.
• Legal questions need a lawyer. This guide summarizes the FTC's stated substantiation position. It is not legal advice. Health, financial, securities, and litigation announcements warrant qualified review.
• Distribution is not coverage. A paid release is published on the distribution route you purchase. Earned coverage happens only when an independent journalist or outlet decides to report on your news, and that decision is theirs. Neither guarantees pickup, rankings, backlinks, traffic, leads, or sales.

Your Next Practical Decision

Run the worksheet on the announcement you are considering. If it lands on “Go,” you have something worth publishing through whatever channel you choose. If it lands on “Hold,” the fix is usually one missing document or one approval, which is faster to get now than after a rejection. If it lands on “Different format,” you have avoided presenting a sales message as news.

If a release has already been declined, start with the rejection-repair checklist instead. If you want an outside route check, the MBK eligibility review looks at the announcement, category, and publisher fit before any payment. The service terms spell out what the customer, MBK, and the publisher each control, including who approves the final copy.