Operations
A buyer-owned announcement workflow: evidence, approval, release lanes and close-out
A step-by-step workflow for moving one England announcement through evidence, rights, approval, release lanes, exceptions, corrections and close-out.
This workflow moves one authorised announcement for an England-operating buyer from source evidence to close-out. It does not treat the buyer's newsroom, manual outreach, technical transmission, paid placement, monitoring or independent editorial publication as interchangeable. Each state has its own owner and proof.
This model was built without inspecting any supplier account, real contact list or launch record, and it covers buyer-owned controls rather than campaign results.
What to take away
- Each state in the announcement workflow has its own owner and proof, so newsroom, outreach, transmission, placement and monitoring are not interchangeable.
- Material claims without evidence or quotations without authority must go to rework, not the release queue.
- Unresolved ownership questions on territory, duration, editing or attribution put the affected asset on hold.
- Late edits return to affected approvers, and copy should not be patched inside a supplier account without a new approved version.
- Supplier acceptance is not indexing, indexing is not readership, and monitoring is not endorsement or outcome.
- Name functions and stop authority before any file moves, so approval cannot be granted silently.
1. Open the source record
The factual owner creates a claim register for names, dates, quotations and objective statements. Attach the source, retrieval date, geography, scope, quotation authority and expiry. The editor creates a source-copy ID and checksum. If a material claim lacks evidence or an attributed quotation lacks authority, move the item to rework rather than the release queue.
The rights owner records authorship, employment, assignment or licence for every asset. The IPO's copyright ownership guidance explains why commissioned work and payment do not settle every ownership question. Unresolved territory, duration, editing or attribution puts the affected asset on hold.
Create one immutable working package before configuring any route. It holds the exact source copy, version identifier, checksum, factual evidence, quotation authority, rights records, intended geography, audience note, approved timing and correction owner. Keep original evidence separate from any text a supplier exports.
2. Complete specialist decisions
Route objective commercial claims and any controlled placement to the advertising and sector reviewers. CAP's misleading advertising rules address evidence and presentation within their remit. A separate recognition check applies to paid or controlled material. The decision record names the reviewer, rule or guidance considered, conclusion limits and recheck date.
For each contact record, the privacy and PECR reviewer captures provenance, role, purpose, subscriber type where relevant, transparency route, objection and suppression state. The ICO's business-to-business marketing page is UK guidance currently marked under review following the Data (Use and Access) Act. A public address does not bypass the factual assessment.
3. Freeze the approved version
The editor incorporates authorised corrections, then issues a new checksum. Record included assets, intended recipients or endpoints, newsroom destination, paid-placement label, planned time and timezone. Late edits return to affected approvers. Nobody should patch copy inside a supplier account without creating and approving another version.
The accessibility owner checks the exact output and any required alternative formats. GOV.UK's accessible communication formats guidance recommends early planning and final approved text for suppliers, although its direct context is government communication.
4. Configure and test safely
The security owner gives named people the minimum necessary access and records configuration, logs, recovery and revocation. Use a synthetic record confined to a test system or a specifically authorised fixture directed only to non-editorial test endpoints. Do not send dummy news to journalists.
State expected fields, transformation, status, error and clean-up before observing the test. NCSC's SaaS security guidance provides questions for access, logging, recovery and offboarding. A pass covers only the inspected configuration and date.
5. Release by lane
The buyer publishes its newsroom page and retains the rendered record. The outreach operator uses only the approved contact set. The supplier returns its defined submission or acceptance status. A paid publisher provides evidence of the controlled placement and label. Monitoring uses the prewritten population, query and time window.
Independent editorial publication stays outside every controlled lane and is logged separately. A deadline or senior preference cannot override a failed release gate.
| Lane | Owner | Evidence |
|---|---|---|
| Newsroom | Buyer | Rendered page and retention copy |
| Outreach | Outreach operator | Send log |
| Transmission | Supplier | Acceptance status |
| Paid placement | Paid publisher | Placement proof and label |
| Monitoring | Monitoring owner | Results and window |
| Independent coverage | No buyer control | Separate log |
Write functions rather than job titles. One person may hold several, but the record must show which authority they exercised and where independent review was required. The person who prepares an item must not silently grant factual, legal, rights, data or payment approval. Where roles are combined, name who can challenge the decision and who can stop release.
The buyer owns the purpose, budget, contract and final go or hold decision. Spend varies by volume. Newsroom costs are mostly staff time and hosting. Outreach cost depends on list size, tooling and review time. Technical transmission is usually a per-release or subscription fee plus overage. Paid placement is often the largest line, set by outlet, position and duration.
For example, a West Midlands manufacturer could publish the approved text on its own newsroom page, send named trade contacts from an approved list, and buy a labelled placement with one regional business outlet. Each lane keeps its own evidence.
Duration depends on the item. These are the drivers, not published benchmarks.
| State | What sets the clock |
|---|---|
| Source record | Claims, assets and rights queries |
| Specialist decisions | Reviewer availability and sector input |
| Approved version | Corrections and affected approvers |
| Safe test | Access provisioning and test window |
| Release by lane | Endpoint response and placement lead time |
| Close-out | Objections, invoices and retention decisions |
6. Resolve, close and exit
Failures go to a named queue with the affected version, lane, evidence, owner and restart authority. A factual correction stops unreleased lanes, preserves history and generates a newly approved source. Suspected incidents follow the buyer's response plan; NCSC incident-management guidance supports defining decisions and recovery before an event.
At close, reconcile statuses, corrections, objections and financial records. Export required evidence, apply approved retention, revoke access and document deletion or residual retention. The final owner records unresolved items and the condition that would reopen them.
Close-out checks
- Create a claim register with source, retrieval date, geography, scope and expiry.
- Record authorship, employment, assignment or licence for every asset.
- Capture provenance, role, purpose, transparency route, objection and suppression state for each contact.
- Issue a new checksum after incorporating authorised corrections.
- Give named people minimum necessary access and record configuration, logs, recovery and revocation.
- Reconcile statuses, corrections, objections and financial records at close.
Common questions
What happens if a material claim lacks evidence or a quotation lacks authority?
The item moves to rework rather than the release queue. The factual owner creates a claim register for names, dates, quotations and objective statements, attaching source, retrieval date, geography, scope, quotation authority and expiry. The editor creates a source-copy ID and checksum.
How should a test be run without sending dummy news to journalists?
Use a synthetic record confined to a test system or a specifically authorised fixture directed only to non-editorial test endpoints. State expected fields, transformation, status, error and clean-up before observing the test. A pass covers only the inspected configuration and date.
