A press release can survive several opinions more easily than several competing drafts. When reviewers work from different files, approvals become ambiguous: someone approves yesterday’s number, another changes a partner description, and the publisher cannot tell which version is cleared. A reliable process makes every approval specific to a version, a responsibility, and a publication scope.
Use the checklist below as a sequence of gates. A gate closes only when its required evidence and approvals are recorded. Adjust the participants and timing to the announcement’s risk; do not treat a routine product update like a regulated financial disclosure.
Gate 1: Assign authority before drafting
Owner: release coordinator. Name people, not just departments. One person may hold multiple roles on a small team, but the responsibilities must remain distinguishable.
- Coordinator: maintains the master draft, assigns checks, resolves routing problems, and records decisions.
- Fact checker: verifies statements against evidence and flags gaps; does not approve unsupported wording because it sounds plausible.
- Scoped reviewer: checks an assigned area, such as product accuracy, partner permissions, or confidentiality. Reviewing one section does not approve the whole release.
- Final approver: authorizes the complete, identified version after required checks close.
- Publisher: distributes only the authorized package and verifies that the published material matches it.
Record a named substitute for each critical role, including who may delegate authority. An out-of-office message does not transfer approval rights.
Gate 2: Establish the brief and source of truth
Owner: coordinator; gate closer: final approver. Create one controlled workspace containing the draft, evidence ledger, assets, comments, and approval record. Share links rather than circulating editable attachments.
- Define the intended audience, announcement purpose, distribution channels, jurisdictions, and publication date, time, and time zone.
- Identify the essential facts: who is announcing what, where it applies, when it happens, and why it matters to that audience.
- Confirm a monitored media contact and accurate contact details.
- Separate public material from restricted supporting documents. Give reviewers access only to what their assignments require.
- Assign a version identifier and keep the release status visible: draft, review, approved, frozen, published, or corrected.
For context on whether the announcement warrants a release, consult this explanation of press releases and when to send them. Purdue OWL’s press release guidance is a useful reference for essential information, audience, dates, and contact details.
Gate 3: Build the fact and evidence ledger
Owner: fact checker. Give each material assertion a ledger entry. A link alone is insufficient if the linked page changes or does not support the precise wording.
- Claim identification: claim ID, exact draft wording, section, and responsible subject-matter owner.
- Evidence: source title, author or issuing organization, location, relevant passage or calculation, document version, and access date.
- Timing: source publication date, measurement period, effective date, and any expiry or recheck deadline.
- Metrics: numerator, denominator, units, population, sample exclusions, baseline, comparison period, rounding, and calculation method.
- Disposition: supported, needs qualification, unsupported, or removed; checker name, check date, and approved wording.
Check names, titles, locations, availability dates, prices, currencies, and geographic limits. Distinguish observed results from forecasts. Comparative, environmental, health, performance, and market-leading claims need evidence matching their breadth. Route specialist questions to appropriately qualified reviewers where necessary, with jurisdiction identified. This checklist is an operational aid, not legal advice.
Do not invent missing details, copy another organization’s prose, or turn a narrowly measured result into an unrestricted promise. If evidence is unavailable, remove or qualify the claim rather than marking it checked.
Gate 4: Run scoped checks in parallel
Owner: coordinator; gate closers: assigned reviewers. Once the factual draft is stable enough, send simultaneous assignments. Specify the sections, questions, version, and response deadline for each reviewer.
- Quotes: verify wording, attribution, title, and context. Obtain the speaker’s or authorized representative’s approval of the exact quotation; later wording changes require renewed approval.
- Partners: confirm the precise partner name, relationship description, announcement permission, and any contractual review requirement. Obtain separate authorization for logo use where required.
- Images: document copyright ownership or license, permitted channels and territories, required credit, modification limits, and relevant subject or property permissions.
- Confidentiality: check customer details, personal information, financial information, unreleased plans, screenshots, metadata, and linked files. Confirm that public links expose no restricted material.
- Specialist issues: route securities, privacy, intellectual property, regulated-product, employment, or other sensitive issues to suitable specialists when relevant.
Require reviewers to distinguish mandatory corrections from preferences. Their response should say approved within scope, approved subject to specified edits, or blocked with a reason. Conditional approval remains open until someone verifies the conditions.
Gate 5: Resolve conflicts and missing responses
Owner: coordinator; escalation owner: final approver. Set explicit deadlines and a buffer for corrections. For example, a team might request reviews by Tuesday noon for a Thursday release. Those deadlines are illustrative, not universal; contractual obligations, specialist availability, and announcement risk determine the actual schedule.
- Silence never counts as approval. Log missing responses and escalate at the agreed cutoff.
- Activate the recorded substitute when an assigned reviewer is absent. Record the substitution and authority.
- Classify disagreements as evidence, permission, risk, or editorial preference. Record the decision, decision-maker, and rationale.
- If a required check remains unresolved, delay publication or remove the affected material through the same approval process.
Illustrative disagreement: a metric versus a preference
Suppose a draft describes delivery as 30% faster. The evidence ledger shows that a controlled test measured 30% less processing time for one defined workload, excluding setup. A product reviewer wants to retain the broader phrase for readability; the fact checker objects because delivery was not measured.
The coordinator resolves the factual issue using the test record: narrow the statement to processing time and disclose the relevant conditions, or remove it. The final approver can choose between accurate editorial alternatives, but cannot settle an evidence gap by preference. Record the revised wording and obtain approval from the affected reviewers. This is a hypothetical example, not a reported company result.
Gate 6: Approve and freeze the complete package
Owner: final approver; custodian: coordinator. Review the assembled release, headline, attachments, captions, links, and channel-specific adaptations. Close every required ledger item and permission before authorizing the identified version.
- Record explicit final approval, timestamp, publication scope, and any restrictions.
- Freeze the approved package in a read-only snapshot. Maintain a change log showing editor, timestamp, old wording, new wording, and reason.
- Reopen affected approvals for substantive changes, even after freeze. Changed figures, claims, quotes, dates, partners, or permissions require renewed checks and final authorization.
- Record purely mechanical changes too; do not classify a meaning-changing edit as a typo correction.
For an embargo, record who agreed to it, the covered material, release time and time zone, and any conditions. Sending material labeled embargoed does not itself establish agreement. Company signoff governs the company’s release, not an independent journalist’s reporting, framing, or publication decisions.
Gate 7: Publish, verify, and correct transparently
Owner: publisher. Check the scheduled time, recipients, access settings, attachments, and live links against the approved package. Record publication locations and timestamps, then compare the live copy with the frozen version.
If a factual error appears, alert the coordinator immediately. Verify the correction, reopen relevant approvals, replace affected copies, and notify distribution partners or recipients as appropriate. Preserve the earlier version and record what changed, when, and why. Use a visible correction note for factual changes; do not silently rewrite facts. Purely typographical fixes may follow a separately documented policy.
Reuters’ standards and values provide reference points on accuracy, corrections, avoiding fabrication and plagiarism, and fair comment. Those editorial principles inform careful communication; Reuters does not endorse this workflow.
Reusable approval record template
Copy this record into the controlled workspace for each release. Link supporting records rather than relying on memory or scattered messages.
- Identity: release title; record ID; master link; version; status; jurisdiction; audience; channels; scheduled publication time and zone.
- People: coordinator; fact checker; scoped reviewers and assignments; final approver; publisher; authorized substitutes.
- Evidence: ledger link; unresolved claim IDs; required qualifications; source recheck dates.
- Permissions: exact-quote approvals; partner name and logo permissions; image rights; confidentiality clearance; specialist decisions.
- Review tracking: reviewer; scope; version reviewed; deadline; response; conditions; completion timestamp; substitution or escalation.
- Decisions: disagreement; evidence considered; resolution; decision owner; rationale; affected approvals reopened.
- Authorization: final approved version; explicit approval statement; approver; timestamp; restrictions; frozen-package link.
- Publication and corrections: embargo agreements; publisher; live URLs; publication verification; change log; correction notices and recipients.
The release is ready only when the record proves it—not when the comment thread becomes quiet.
