Before booking: 7 checks for the announcement
Planning day 1 should lock the news, evidence and audience. Start with the announcement, not the outlet list. Use this checklist before approving a route:
- News: State the completed change in one plain sentence.
- Audience: Name who needs this update and why now.
- Evidence: Attach a public source for each central claim.
- Status: Label work as live, testing, planned or complete.
- Spokesperson: Confirm the speaker, title and approved quote.
- Partners: Clear names and descriptions with the relevant party.
- Disclosure: Mark confidential details and claims needing review.
If one item is unresolved, hold the draft there. A missing source needs confirmation, not stronger copy. Ask the person or document owner to close the gap before distribution.
For launch communications, compare the announcement with the token launch marketing checklist. The release should support that plan. It should not replace it.
Which crypto announcement has a clear angle?
A strong angle gives the update a consequence readers can understand. It connects what changed with who can use, inspect or respond to it. Start with one sentence describing that connection.
Then test that sentence against 3 questions:
- What changed, in terms an outside reader can check?
- Who is affected, and what can they do now?
- Which source supports the main point?
A product announcement can name what is available and where to inspect it. An integration can explain each party’s role. It should also state the work’s current status. A governance update can point readers to its public record.
Keep supporting detail behind one main story. A release may mention a product, token, partnership and roadmap. That combination can leave editors unsure which update matters most. If the central news is still a plan, label it clearly. Don’t present an intention as completed work.
For 2 distinct updates, consider separate releases. Use separate drafts only when each has enough evidence and audience relevance.
5 parts editors can scan quickly
A 5-part format puts the announcement first and its proof within reach. Keep each part focused. Check that readers can understand what happened without project background.
| Part | What to put there | Check before sending |
|---|---|---|
| Headline | The change and the named parties | Does it state the news plainly? |
| Opening | Who did what and the relevant timing | Is the announcement clear immediately? |
| Body | Evidence, status and useful context | Can readers inspect the central claims? |
| Quote | An approved spokesperson’s perspective | Does it add information, not slogans? |
| Contact | Project description, source links and media contact | Are names and links current? |
Use short paragraphs and consistent names throughout. Explain technical terms when they first appear. Preserve important distinctions: a test environment is not a production release. An announced partnership is not proof of a finished integration.
Keep the project description separate from the news. Include only background that helps identify the organization. Check that contact details and source links work before sending.
A source beside every material claim
A source file makes fact-checking quicker and corrections easier. Build it alongside the release, not after the copy is finished.
Use a 3-column claim log: draft wording, supporting source and confirming person. Public pages, documents and transaction references can substantiate claims when they directly support the wording. Confirm each link works and its content is cleared for sharing.
Before approval, check these 5 details:
- Names and titles match approved project records.
- Quotes match the speaker’s final wording.
- Partner statements have the required approval.
- Product, audit and access claims match their evidence.
- Planned work is not described as completed.
For a separate profile or supply question, consult the CoinGecko listing guidance. A press release can explain an update. It does not replace a platform’s submission or verification process.
Remove any claim its source cannot support. Don’t patch an evidence gap with stronger adjectives. Ask the relevant owner to confirm the facts or leave them out.
Distribution routes: match the format to the job
The route determines how the announcement reaches outlets, not whether it deserves coverage. Clarify the actual work before booking distribution.
| Route | What it does | Proof to confirm |
|---|---|---|
| Broad release distribution | Sends approved copy through an agreed route | Outlet list, terms and publication evidence |
| Direct editorial pitch | Presents the angle to selected journalists | Target list and submission record |
| Owned channels | Shares the announcement with your audience | Post format and live link |
Ask whether a provider handles writing, editing, pitching, paid placements or a combination. Get the named outlets, route and proof of delivery in writing. Distinguish a submission from an accepted story and a live placement. Those are different checkpoints.
Compare crypto press release distribution services by the work they agree to do and how they document it. If the story needs analysis or a longer conversation, compare the fit with digital PR campaigns.
A regional pitch only makes sense when local relevance is real. Check language needs and spokesperson access before choosing that route.
Run-of-show: 5 moves from draft to record
5 clear handoffs keep approved copy and publication status visible. Assign an owner to each move so questions do not disappear between teams.
- Prepare: Confirm the announcement, sources, audience and spokesperson.
- Draft: Write one release around the strongest supported angle.
- Review: Resolve factual edits and lock the approved version.
- Distribute: Use the agreed route and log each submission.
- Record: Separate responses, accepted stories and live links.
For support, request a written quote before approving the route. After the route is confirmed, agree who approves copy and who receives the status log. While a placement is live, the report can track status and links.
A final record should distinguish what was submitted from what appeared publicly. Keep one approved copy as the source of truth. If wording changes during review, note which version went out.
For broader channel planning, see the PR and media hub.
What does a distribution booking actually confirm?
A booking confirms the work and terms written down for that route. An editorial outlet decides whether to accept a pitch, when to publish and how to edit it.
Paid placements follow the named outlet’s agreed terms. No distribution route can promise independent editorial acceptance or a specific editorial treatment.
Before approval, confirm these 4 points:
- Named outlets or channels, not just a broad label.
- Whether writing, editing or pitching is included.
- What counts as delivery: submission, acceptance or live link.
- How delays, changes and publication proof are handled.
A clean report separates submitted, accepted and live coverage. That record helps you see what happened without treating a receipt as editorial endorsement. It also gives your team usable links for its own channels and follow-up.
Send DigitalMedia1 the announcement, source links, target audience and any approval limits. We can check the angle against the evidence and map the route before you approve it.
How it works
- Name the updateWrite what changed and who it affects. Mark completed work separately from plans or testing.
- Collect the sourcesGather public references, approved assets and spokesperson details. Flag claims that still need confirmation.
- Draft one angleBuild the release around one supported announcement. Keep secondary details in a supporting role.
- Approve the copyAsk the relevant project owners to check facts, quotes, naming and disclosure boundaries.
- Choose and log the routeConfirm outlet terms before authorizing distribution. Track submissions, responses and live links separately.
Frequently asked questions
How do I know whether a crypto update merits a release?
1 clear update is a useful starting point: an outside reader should understand what changed and inspect its evidence. Name the affected audience and explain why the update matters now. If the main claim is unconfirmed or describes only a future intention, finish that review before drafting.
Which documents should support claims in a token announcement?
1 source for each material claim is the right baseline. Depending on the announcement, that may be a public project page, approved document, transaction reference or attributable spokesperson. Match the source to the exact wording, check that it can be shared and label the status accurately. Leave out details that cannot be substantiated.
Should we use broad distribution or pitch journalists directly?
2 routes serve different jobs. Broad distribution follows the agreed publishing route; direct pitching presents an angle to selected journalists. Ask the provider which outlets it will approach, what work it performs and what evidence it returns. Keep a submission record separate from an accepted story or live link.
How many versions should we prepare for regional outlets?
1 approved master copy is a sensible starting point. Prepare another version only when language, local relevance or outlet requirements call for meaningful changes. Keep the core facts aligned across versions, and have the relevant project owners approve regional edits. Confirm who checks translations before sending them.
How is the cost of crypto press release distribution calculated?
3 things shape cost: the surface, the window and the volume. You get a fixed written quote within 2 working days, before you pay. Ask the provider to name the route and explain what counts as delivery. Keep writing, editing and placement terms clear in that quote.
How long does drafting and distribution usually take?
3 inputs shape the schedule: source checks, quote approvals and partner clearance. The chosen route also affects timing. Set a target after the draft and evidence are ready, not before. Ask the outlet or provider to confirm its timing. Avoid announcing a publication date until confirmation is in hand.
Can a publication be required to run a submitted crypto release?
1 submission does not require an outlet to publish an editorial pitch. Editors control acceptance, timing and final treatment. A paid placement should name its outlet and agreed terms in writing. Include what happens if publication changes or becomes unavailable. Record submissions separately from live coverage.
What should the final distribution report show?
4 report fields make follow-up clearer: outlet or channel, current status, response and live URL where available. Separate submissions, responses, accepted stories and live placements. Keep screenshots or other agreed proof with the record. That prevents a submission receipt from being mistaken for publication.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…