Press release distribution supplier selection framework

For press release distribution, a buyer should choose a supplier for one defined announcement job, not a promise of reach.

The guide's working case is an England-operating organisation. It must publish an authorised item on its own newsroom, send it to a documented subset of media contacts, and, if needed, buy technical transmission to specified endpoints. Paid placement and monitoring are separate purchases. Independent editorial publication is not a supplier deliverable.

Research closed on 6 September 2026. No commercial platform was accessed, configured or tested, and no provider has been shortlisted. The guide therefore explains what evidence would be needed to admit an exact legal entity and service edition to evaluation. It does not recommend a tool, quote a price or find that any supplier is lawful, secure, accessible or suitable.

What to take away

Choose a supplier for one defined announcement job, not for a promise of reach.
Keep route categories separate and never create an aggregate score across different functions.
Match the legal entity across the order form, terms, privacy material, data agreement and invoice.
Record the exact service edition and evidence cut-off, and mark unknown where the supplier defines nothing.
Treat accessibility and security as gates, not as features to weigh against price.

Write the job before opening a product page

The job record needs an authorised announcement, intended audience, permitted recipients, buyer-owned source copy and an observable endpoint. Define success at the event the chosen route controls.

For a newsroom, that may be the approved page and its correction log. Direct outreach may mean transmission to the authorised address list. A wire may mean the precise status the contract defines.

Keep these later events outside the acceptance decision unless separately evidenced:

Write the job first

another system accepting or republishing the item;
a search service indexing a page;
a journalist reading or using the material;
an editor independently publishing a story;
a member of the public seeing or understanding it;
traffic, reputation, enquiries or revenue following the announcement.

A supplier receipt proves only its own named technical state. Before comparison, ask for the status vocabulary, its definition, timestamp source, failure code and correction behaviour.

Keep route categories separate

One product search often mixes services that do different work. Treat them as separate rows.

Route categories and evidence limits

Route

Buyer-owned baseline: Versioned page
Direct outreach: Send records
Technical transmission: Supplier status
Paid placement: Order record
Monitoring: Dated results
Editorial publication: Publisher's item

Controllable output

Buyer-owned baseline: No discovery proof
Direct outreach: No attention proof
Technical transmission: No syndication proof
Paid placement: Not earned editorial
Monitoring: Absence not proof
Editorial publication: Buyer not in control

Evidence boundary

Buyer-owned baseline
Direct outreach
Technical transmission
Paid placement
Monitoring
Editorial publication

Buyer need

Buyer-owned manual baseline: Publish and correct an approved newsroom page
Direct outreach: Send an authorised message to documented contacts
Technical transmission: Deliver a record under defined endpoint rules
Paid placement: Buy controlled space or content treatment
Monitoring: Observe a stated source universe and query
Independent editorial publication: Publisher chooses whether and how to report

Controllable output

Buyer-owned manual baseline: Versioned page and change log
Direct outreach: Send and failure records
Technical transmission: Supplier status and endpoint evidence
Paid placement: Order, placement and disclosure record
Monitoring: Dated results and exclusions
Independent editorial publication: The publisher's item

Evidence boundary

Buyer-owned manual baseline: No proof of discovery or readership
Direct outreach: No proof of attention or future marketing permission
Technical transmission: No automatic proof of syndication or indexing
Paid placement: Must not be represented as independent editorial coverage
Monitoring: Absence is not proof that nothing was published
Independent editorial publication: Not controlled by the buyer or distribution supplier

Do not create an aggregate score across these categories. First decide which function the announcement requires, then compare candidates within that function.

Verify the contracting identity

A website's service name may differ from the entity that invoices, processes data or supplies support, so record: legal name, company number where relevant, registered office and previous names. Record contracting address, group relationship, authorised signatory.

GOV.UK's Companies House information service explains which register details can be checked. Those records do not prove trading activity, solvency, service quality or fitness for this job.

Match the entity across the order form, terms, privacy material, data agreement and invoice. If different group companies perform different roles, document each one. A legal or procurement owner should stop evaluation when the identity chain cannot be reconciled.

Fix the exact service and evidence date

Capture the edition, service tier, add-ons, territory and evidence cut-off. Save the dated first-party pages or documents supporting each material claim. A general homepage is not evidence that a particular UK contract includes a feature. Record unknown when the supplier does not define an endpoint, correction facility, export format or retention behaviour.

The dossier should distinguish:

supplier description of a capability;
contractual commitment for the selected service;
configured behaviour observed in an authorised test;
independent or regulatory evidence where it exists;
buyer inference, which should not be written as fact.

Product badges, testimonials and case studies remain supplier evidence. They cannot establish the buyer's own result.

Keep price and outcome claims out of the feature grid

Price evidence needs exact currency, VAT statement, unit, billing period, term, volume, included endpoints, add-ons, renewal and exit charges. Leave every field blank if the current UK offer does not state it. A price per release, per contact, per seat and per month cannot be compared without converting them to the same defined buyer quantity and period.

HMRC's VAT rates guidance says treatment depends on the goods or services and applicable conditions. A named tax reviewer must decide the actual supply; a supplier display or this guide cannot do so.

Do not convert possible publication, syndication or traffic into monetary value. A buying decision can compare cash cost and internal work against a manual baseline without inventing a return.

Trace contacts and supplier data roles

For media-contact data, request provenance, collection date, purpose, accuracy process and subscriber classification. Request privacy-information route, objection workflow and suppression handling.

The ICO's business-to-business marketing guidance says public personal data does not equal automatic agreement to direct marketing. It separates UK GDPR duties from PECR treatment by channel and subscriber type.

The B2B page carries a DUAA review notice, so buyers should recheck its status before any contact import.

Map who determines purposes and means for the buyer's copy, account data, media list, tracking, monitoring and supplier analytics. The ICO's controller and processor contract guidance explains the required relationship records and is also marked for DUAA review. Contract labels should be tested against actual conduct.

If support, hosting or subprocessors involve a separate organisation outside the UK, use the ICO's current international transfer guide to map whether a restricted transfer occurs and what evidence is needed. The guide was updated in January 2026. A UK server location alone does not answer every entity and access question.

Review claims, paid control and rights

The supplier should preserve the approved copy and approval history. It does not become the factual authority. For marketing communications within remit, CAP Code Section 3 covers substantiation and misleading presentation. The buyer's advertising and sector reviewers remain responsible for deciding whether the claim file supports the final placement.

Paid or controlled material needs its own identification evidence. CAP Code Section 2 addresses recognition and advertorials within its scope. The contract should not describe purchased space as earned editorial coverage.

Create a rights ledger for copy, images, video, charts, logos, quotations and monitoring outputs. IPO copyright ownership guidance notes that commissioned work usually remains with its creator unless the parties agree otherwise. Record licence or assignment, media, territory, term, alterations, credits, archive use and exit.

Treat accessibility and security as gates

The service dossier should state which formats it accepts, changes or strips, and how the buyer can inspect the result. Government accessible communication formats guidance, updated in June 2026, gives practical public-sector advice on planning formats and suppliers. It is not evidence that an unnamed platform or document meets a private buyer's duties.

Ask for access roles, strong authentication options, logs, administrative recovery, support access, incident notification, backups and deletion evidence. NCSC SaaS guidance covers secure configuration and recovery. Its supplier assurance questions extend the enquiry to governance, incidents, offshoring, testing and contract exit. Neither page certifies a supplier.

Security, accessibility, privacy, rights and claims are non-compensating gates. A convenient workflow cannot offset a failure in one of them.

Run one controlled test

Use an authorised announcement fixture that is safe for the selected endpoints, or a synthetic non-news record confined to a test environment. Never send dummy news to real journalists. The test plan names the service edition, configuration, operator, input, expected state, timestamp, permitted destinations, observation method and clean-up.

Check whether the system preserves approved text, blocks an unauthorised destination, records a rejection, exports evidence and supports a correction request. Also check whether it retains accessibility features and allows access to be revoked. Do not claim a test that was not run.

A pass establishes only observed behaviour for that configuration and date, not future uptime, legal compliance, readership or commercial effect.

The manual baseline should run through the same acceptance fields where possible. This reveals whether buying a service solves a real control gap or simply moves work to another interface.

Contract for correction, change and exit

Define service scope, status terms, evidence, support route, charging unit, subprocessors, security responsibilities, data return, deletion, rights, changes, suspension, correction and termination. NCSC supply-chain guidance recommends identifying what must be protected and what suppliers can access. Apply those questions to the actual service rather than claiming generic assurance.

Rollback should identify the authorised source, affected endpoints, person who can halt further sending, correction request, evidence to preserve and person allowed to restart. Exit needs a usable export, suppression continuity, account revocation, final invoice reconciliation, surviving rights and deletion evidence. An independent publisher remains free to decide how to handle a correction request.

Decision record

The buyer can admit a candidate only when the entity, exact service, UK availability, contract, price basis, data roles, provenance, claim controls, rights, accessibility, security, support, correction, export and exit evidence are complete. Buyer weights and thresholds stay blank until the actual job owners approve them.

No named supplier currently clears that dossier in this research. The verdict is HOLD. Before procurement or publication, named UK legal, advertising, sector, privacy and PECR, IP, accessibility, security, procurement, finance, commercial and editorial reviewers must examine the live service, contract, configuration and announcement. Recheck every first-party record on the decision date.

Before you act

Write the job record before opening any product page.
Decide which function the announcement requires before comparing candidates.
Reconcile the contracting identity across every document in the chain.
Capture the edition, service tier, territory and evidence cut-off.
Leave price fields blank when the UK offer does not state them.
Map controller and processor roles against actual conduct.

Common questions

What should a buyer define before comparing announcement suppliers?

The job record needs an authorised announcement, intended audience, permitted recipients, buyer-owned source copy and an observable endpoint. Success should be defined at the event the chosen route controls, such as the approved newsroom page and its correction log, transmission to an authorised address list, or the precise status the contract defines.

Why should route categories not be combined into one score?

One product search often mixes services that do different work, such as direct outreach, technical transmission, paid placement and monitoring. The guide says to treat them as separate rows, decide which function the announcement requires first, then compare candidates within that function only.

What evidence is needed for media-contact data?

Request provenance, collection date, purpose, accuracy process, subscriber classification, privacy-information route, objection workflow and suppression handling. The ICO guidance says public personal data does not amount to automatic agreement to direct marketing, and the B2B page carries a DUAA review notice, so recheck its status before any contact import.