PLAYBOOKAll posts

How to Respond to a Journalist Request for Comment

A reporter is writing something critical and wants your side by 5pm. How founders respond: the deadline clock, statement options and what no comment costs.

Shilika Jain at the Marina Bay railing with the Singapore financial district skyline behind her
On this page12
  1. What is a request for comment, and why are you getting one?
  2. What should you do in the first hour?
  3. Which response option should you choose?
  4. How do you write the statement itself?
  5. What does "no comment" actually cost you?
  6. What should you never do when a critical story is coming?
  7. When does this approach not apply?
  8. FAQ
  9. Can I ask the reporter for more time?
  10. Should I ask to see the questions in writing?
  11. Can I respond after the story has been published?
  12. Should the founder or a spokesperson respond?

When a journalist asks for comment on a critical story, reply quickly to confirm you've received it and will respond before their deadline, then use the time to establish the facts, decide what you can say on the record, and send a short, factual statement that addresses their specific questions. Don't ignore it and don't stall past the deadline. The story will usually run either way, and silence means it runs without your side.

Most founders get one of these eventually. The ones who handle it well treat it as a deadline problem first and a messaging problem second.

What is a request for comment, and why are you getting one?

A request for comment is a reporter giving you the chance to respond before they publish something about you. In a critical story, it's usually a sign the piece is well advanced. They've spoken to other sources, they have documents or on-chain data, and they're checking your side, partly because fairness requires it and partly because their editor expects it.

It typically arrives as an email with a list of specific questions and a deadline, often the same day or the next. Sometimes it's a DM or a message to a team member who isn't in comms.

Read it as information. The questions tell you what the reporter already believes and what they still need to confirm. That's useful, even if it's uncomfortable.

What should you do in the first hour?

Move fast, and keep the circle small. This is the deadline clock I run with clients from the moment the request lands.

  1. Within 30 minutes: acknowledge. A two-line reply to the reporter: you've received it, you'll respond by their deadline, and who their single point of contact is. No comment on substance yet.
  2. Within the first hour: get the right people in one place. The founder, whoever holds the facts (engineering, finance, legal), and whoever will speak. Three to five people, not the whole company.
  3. Within the first hour: freeze outside contact. Tell your team not to reply to the reporter, post about the topic or speak to other media until there's a plan.
  4. Next two to three hours: establish the facts. Go question by question. For each one, write down what you know, what you can prove, and what you don't yet know.
  5. Before the deadline: send the response. Leave enough margin that the reporter can actually use it.

Step one matters more than founders think. A quick acknowledgement tells the reporter you're engaging, which often makes them more willing to wait for a fuller answer.

Which response option should you choose?

You have more choices than "full statement" or "no comment." This table is how I weigh them, and I call it the response ladder, from most to least exposure.

OptionWhen it fitsMain benefitMain cost
On-record interview with the founderYou're confident in the facts and the founder is well preparedYour voice and reasoning appear in fullUnscripted answers can create new headlines
Written on-record statement answering each questionMost critical storiesPrecise, controlled, quotableCan read as corporate if it's vague
Short on-record statement plus factual materialFacts are complex, like on-chain flows or contract termsReporter gets evidence to checkTakes longer to prepare well
Background guidance, not for attributionYou need to correct a misunderstanding but can't be quotedCan prevent a factual errorMust agree terms first and it won't show as your response
Declined to comment, with a reasonActive legal process or regulator involvementAvoids legal riskReads as evasive unless the reason is clear
No response at allAlmost neverNone that lastsStory runs as "did not respond," often seen as guilt

Most of the time, the second or third row is right. If you're considering background guidance, read my explainer on off the record vs on background before you say a word, because terms must be agreed in advance.

How do you write the statement itself?

Answer the questions they asked. That sounds obvious, but the most common failure I see is a statement that talks about the company's mission and ignores the specific claim.

A workable structure:

  • Lead with the direct answer to the most serious question. If something went wrong, say so plainly.
  • Give the facts you can verify. Numbers, dates, transaction hashes, audit reports. Link to them.
  • Correct what's wrong, calmly. "The withdrawal was paused for 14 hours, not three days, as shown here."
  • Say what you're doing about it, if there's an issue to address.
  • Keep it under 200 words so it's likely to be quoted rather than paraphrased.
  • Avoid words that sound like spin, such as "FUD," "misinformation" or "the community knows the truth," unless you can show it.

Transparency is your strongest tool here, and crypto has learned that the hard way.

• Transparency is the key to successful web3 business • Medias have emerged as the strongest source of truth this season Shilika Jain on X, 18 Nov 2022

I wrote that in the weeks after FTX collapsed, when reporters were doing work that many in the industry hadn't. Founders who assume the journalist is the enemy tend to write defensive statements. Founders who assume the journalist is trying to get it right write better ones.

If you need starting language for the acknowledgement or an interim line, my holding statement templates are a good base.

What does "no comment" actually cost you?

More than founders expect. "Declined to comment" or "did not respond to a request for comment" sits in the story permanently, and readers tend to fill the gap with the worst interpretation. It also means the critical claims run without any counterpoint, so the reporter's other sources define you.

There are legitimate reasons not to comment: active litigation, a regulator's instruction, or information you're legally barred from sharing. If that's your situation, say so: "We can't comment on an ongoing legal matter, but we can confirm that user funds are not affected." A reason plus whatever fact you can share is far better than silence.

Size and reputation don't exempt you. I've watched large teams handle this badly.

delayed responses, lack of collaboration, missing deadlines, being too picky w journos lol Shilika Jain on X, 10 Nov 2025

Missing a request-for-comment deadline is the most expensive version of that. The reporter doesn't wait, and the piece runs on schedule.

What should you never do when a critical story is coming?

A short list, because each of these has made a story worse:

  • Don't try to get the story killed by going to the editor, the outlet's owners or advertisers. It rarely works and often becomes part of the story.
  • Don't pre-empt the story publicly in a way that attacks the reporter. Publishing your own facts is fine. Discrediting the journalist before they publish invites a follow-up.
  • Don't ask to approve the article. You can offer to confirm facts. Copy approval is a separate question, covered in whether founders can review an article before publication.
  • Don't let ten people respond. One spokesperson, one channel, one statement.
  • Don't fight it out on X during the reporting window. Founders are, as I once put it, natural fighters.
founders are naturally born FUD-fighters. Shilika Jain on X, 27 Feb 2023

That instinct helps in a bear market. It hurts when a reporter is still writing and every reply-guy argument becomes source material.

When does this approach not apply?

The sequence above assumes a normal critical story: a reporter with questions, a deadline and a fair process. A few situations need something different:

  • An active exploit or security incident. You're in incident response, and public safety messaging comes before any individual reporter. My crypto crisis communications playbook covers that order.
  • A rug-pull or fraud allegation. These move faster and need on-chain evidence at the centre of your response, which I've laid out in the rug-pull allegation playbook.
  • Bad-faith outlets. A site that publishes paid hit pieces isn't running a fair process. Responding can legitimise it. Get advice before you engage.
  • Regulatory matters. Legal counsel leads, and comms supports.

If you'd rather have someone run the deadline clock with you next time, it's part of how I support teams on Web3 PR campaigns, including the uncomfortable weeks.

FAQ

Can I ask the reporter for more time?

Yes, once, with a reason and a specific new time. "We're confirming the transaction data with our auditors and can respond by 10am tomorrow" is a fair request. The reporter may say no if their editor has set the publication time, so prepare to send something by the original deadline anyway.

Should I ask to see the questions in writing?

Yes. If the request came by phone or DM, ask the reporter to send the questions by email. It gives you a clear record of what was asked and helps you answer each point precisely.

Can I respond after the story has been published?

You can, and outlets sometimes add a late response as an update. But it rarely gets the same attention as the original piece. Treat the deadline as real.

Should the founder or a spokesperson respond?

For serious allegations, the response should carry the founder's name or a named senior executive. An anonymous "company spokesperson" line reads as distance. The comms lead's role is to prepare the founder and manage the reporter.

If a request for comment just landed and the clock is running, book a 30-minute call and we'll work through the response together.

Shilika Jain in a pink dress by the Singapore River with the old bridge behind her

Work with Shilika

Book a 30-min intro call.

I come prepped with a teardown of your current press footprint.

Keep reading

Similar playbooks

01

Crisis Comms Long-Tails for Web3 Founders: Scenarios Nobody Plans For

Most Web3 crisis plans cover hacks and regulatory letters but miss the slow-burn secondary scenarios that quietly destroy reputation. The full long-tail map.

Read playbook
02

Rug Pull Allegations: The 72-Hour Crisis Communications Playbook for Web3

Accused of a rug pull? The first 72 hours decide survival. The holding statement, on-chain proof bundle and channel sequencing you need, with templates.

Read playbook
03

Holding Statement Templates for Web3 Crises

Five holding statement templates for Web3 founders: exploit, hot wallet compromise, oracle failure, depeg and rug pull allegation, with channel variants.

Read playbook
All playbooks