Tools and providers
Part of Press release distribution supplier selection framework
Press release distribution tool implementation: seven dry-run tests
Press release distribution tool implementation: seven dry-run tests for source, access, fixture, accessibility, statuses, correction and exit.
Press release distribution tool implementation starts with a dry run you can undo. Run the service through the seven tests below before a real announcement or media list enters it, so that every step can be reversed. There is no universal timetable. Owners set dates only after the exact UK service, contract and England announcement job are known.
What to take away
- Store the authorised text and approvals outside the supplier account, with a version identifier and checksum.
- Give named people the least access they need, and test revocation while only safe material is loaded.
- Use an approved or unmistakably synthetic fixture, never dummy material sent to journalists.
- Keep submission, acceptance, delivery, syndication, indexing and publication as separate endpoint statuses.
- Go-live stays on hold until named legal, privacy, IP, accessibility, security, procurement, commercial and editorial reviewers approve.
The dry run in seven tests
Each of the seven tests has a material, a pass condition and a record, and applies to whichever distribution tool the buyer has already selected. A pass means only that this configuration behaved as recorded on the test date. It says nothing about reach or readership.
| Test | Material | Pass means |
|---|---|---|
| Controlled source | Authorised text, claims evidence, assets, rights record, approvals | Held outside the supplier account with a version identifier and checksum |
| Access | Safe material only | Named roles work, revocation works, account recovery works |
| Fixture | Approved announcement or synthetic non-news record | Supplier output matches the controlled source |
| Accessibility | Actual rendered output | Supported formats documented, buyer-defined needs checked |
| Endpoint statuses | Each status the service returns | Event, system, timestamp, evidence owner and failure code recorded |
| Correction drill | A deliberately wrong version | Closure evidence captured |
| Exit | Records and test accounts | Records exported, accounts revoked, deletion evidence requested |
Fail any test and the service stays out of live use. Any change to edition, entity, terms, subprocessor, endpoint or approved content reopens the relevant test.
Source and access
Store the authorised text, claims evidence, assets, rights record and approval outside the supplier account. Name who can approve a change and who can halt transmission. The tool may carry the file, but it does not become the factual authority.
IPO copyright ownership guidance explains why commissioned copy or imagery needs an express ownership or licence decision. Record media, territory, term, alteration, attribution and post-exit use before upload.
Create named roles for administration, content preparation, approval, sending, observation and recovery. Protect administrator credentials and record support access. The NCSC says its lightweight approach to cloud security works best for SaaS services and focuses on measures that mitigate the most common cyber attacks. It is a configuration reference, not product certification.
Fixture and accessibility
Use either an approved announcement expressly authorised for the test route or a synthetic record that is unmistakably non-news and confined to a test environment. A workable synthetic fixture carries a headline that makes no news claim, one short paragraph of body text, a placeholder contact, a test marker in the first line, an image with alternative text and a link to a test landing page. Do not send dummy material to journalists. List the input fields, expected transformations, permitted destination, expected state, observer, evidence and clean-up.
Compare the supplier output with the controlled source. Check headline, text, links, images, character handling, dates and any structured fields.
Document which formats the destination supports and what the service changes. Test reading order, alternative text, link purpose, keyboard use or other buyer-defined needs on the actual rendered output where possible. Government accessible communication guidance is practical public-sector advice. It cannot supply a verdict for an untested commercial route.
Read the endpoint statuses
Submission, supplier acceptance, endpoint delivery, syndication, indexing and editorial publication must remain different statuses. For each one, record the event, system, timestamp, evidence owner and failure code.
Do not expand a technical success into reach or readership. If a supplier's "published" could mean hosted, syndicated or accepted, ask which, and write the answer into the record before the next test.
The correction drill and the media list
Run a safe correction exercise: identify the wrong version, stop further sending, preserve logs, authorise corrected text, make a route-specific request and capture closure evidence. The buyer can amend its newsroom and invoke contracted controls. It cannot silently alter an independent publisher's item.
Before importing a real media list, map source, purpose, recipient category, privacy information, PECR assessment, objections and suppression. The ICO's business-to-business marketing guidance says you can send B2B direct marketing emails or texts to any corporate body without their consent under PECR.
That sentence covers corporate bodies only, so the recipient category has to be recorded for every contact. The guidance carries a review notice after the Data (Use and Access) Act.
Prove rollback and exit
Export the source, destination evidence, failures, corrections, access history and suppression material in usable formats. Revoke test accounts, remove fixtures under the agreed schedule and request deletion evidence.
Record what survives termination, including licences, invoices, incident records and necessary suppression information. The contract issues to settle should say who holds each.
Use NCSC supplier assurance questions to check incident and exit evidence. Stop if the buyer cannot recover its account, export authoritative records, prevent a resend or identify supplier access.
Go-live remains on hold until named reviewers approve the configured service and the actual announcement. Choosing the supplier is a separate job: see the supplier selection framework. The same announcement job record should carry through to go-live.
Common questions
What must be in place before a real announcement or media list enters the service?
Implementation must be reversible first. Owners set dates only after the exact UK service, contract and England announcement job are known, and go-live remains on hold until named reviewers approve the configured service and actual announcement.
What should the test fixture contain?
Use an approved announcement expressly authorised for the test route, or a synthetic record that is unmistakably non-news and confined to a test environment. Dummy material must not be sent to journalists.
How should a correction be handled after a wrong version goes out?
Run a safe correction exercise: identify the wrong version, stop further sending, preserve logs, authorise corrected text, make a route-specific request and capture closure evidence. The buyer can amend its newsroom and invoke contracted controls, but cannot silently alter an independent publisher's item.
