---
title: "Can I Review an Article Before It Is Published? A Founder Guide"
description: "Can you review an article before it's published? Usually not. What crypto reporters may allow (fact checks, quote checks), and what never to ask for."
author: "Shilika Jain"
date: "2026-10-28T02:18:50.255+00:00"
tags: ["media relations", "crypto journalists", "founder pr", "earned media"]
canonical: "https://www.shilikajain.com/blog/can-founders-review-article-before-publication"
---

# Can I Review an Article Before It Is Published? A Founder Guide

By [Shilika Jain](https://www.shilikajain.com/authors/shilika-jain) - 10/28/2026

Can you review an article before it's published? Usually not. What crypto reporters may allow (fact checks, quote checks), and what never to ask for.

---

# Can I Review an Article Before It Is Published? A Founder Guide

In earned media, generally no. Reporters don't send drafts to the people they write about, and asking for "approval" or a full preview is one of the fastest ways to damage a relationship. What you can often get is narrower: a reporter may check specific technical facts or figures with you, and some will read back a quote if accuracy is in doubt. Paid or sponsored content is a different product where review is normal, and your own op-eds go through editing that you may or may not see before publication.

## Why won't reporters let you see the article first?

Because the story belongs to the publication, not to you. Editorial independence is the whole point of earned media: readers trust a news article precisely because the subject didn't sign off on it. If sources could approve copy, every story would read like a press release.

It's the same principle I've been repeating for years.

> the journos are not on the project's payroll but rather media's payroll!
>
> [Shilika Jain on X, 20 Sep 2023](https://x.com/Shilika_jain/status/1704482702299394125)

There's a practical reason too. A reporter writing about your project is often also talking to critics, competitors, analysts and users. Sharing a draft with you would expose those other sources and invite pressure to soften or cut them. No serious newsroom will do that.

Crypto media earned a lot of its credibility by refusing to be friendly to the industry when it mattered.

> I'm literally impressed by how crypto medias aren't scared of standing against crypto industry heroes! kudos to the journalists working on investigative stories to bring out the truth
>
> [Shilika Jain on X, 18 Nov 2022](https://x.com/Shilika_jain/status/1593450701803245568)

You can't admire that independence when it's pointed at someone else and expect to switch it off for your own story.

## What reporters may allow: the ask, offer, never table

Not all pre-publication contact is off limits. The useful distinction is between helping a reporter be accurate and trying to control what they say. I sort every request founders want to make into three columns.

| Ask (reasonable to request) | Offer (proactively give) | Never (don't request) |
|---|---|---|
| "Could you check the technical figures with me before you file?" | Written fact sheet with numbers, dates and spellings | Seeing the full draft |
| "If you use the quote about X, can you read it back? It's easy to garble." | Links to on-chain data, docs or filings that verify your claims | Approval or sign-off |
| "When is it likely to run?" | Availability for follow-up questions on their deadline | Changing the angle, headline or tone |
| "Can you confirm which of my titles you'll use?" | A short glossary for complex terms | Removing other sources or critics |
| | Correct spellings of names, products and partners | Adding your marketing lines or links |
| | Logos, headshots and approved images | Holding publication until you're happy |

The left column is about accuracy. Many reporters will say yes to some of it, especially on technical stories where a wrong number embarrasses them as much as you. Some won't, because their outlet has a policy against it. Ask once, accept the answer.

The middle column is where you have the most control, and it's the column founders forget. If you hand a reporter clean, verifiable facts before the interview, you rarely need to see anything afterwards.

The right column ends relationships. Every item in it asks the reporter to compromise their job for your benefit.

## How do you ask for a fact check without sounding controlling?

Make it about accuracy, make it specific and make it optional. The best time to ask is at the end of the interview, not after the reporter has gone quiet.

The kind of follow-up email I'd send, adapted to each situation:

"Thanks for the time today. A couple of the figures we discussed are easy to mix up: the node count and the date of the mainnet upgrade. Both are in the attached fact sheet. If it's useful, I'm happy to check any technical details before you file. No pressure if that's not how you work."

Why this works:

- It names exactly what might go wrong, so it reads as help, not suspicion.
- It puts the facts in writing first, so a check is easy.
- It explicitly gives the reporter permission to say no.

What doesn't work: "Can we see the piece before it goes live, just to make sure everything's right?" Every reporter hears that as "we want approval."

## What should you do before the interview so you don't need a review?

Most of the anxiety behind review requests comes from founders who said something loosely and are worried it'll come out wrong. The fix sits before the call, not after it. This is the accuracy-first prep kit I put together for interviews:

1. **A one-page fact sheet.** Funding totals, user and usage numbers with dates, launch dates, partner names spelled correctly, founder titles. Every number your founder might mention.
2. **A pre-agreed list of what's public.** If a number isn't confirmed for release, the founder doesn't say it, on or off the record.
3. **Three key messages, rehearsed.** Short enough to quote cleanly. A founder who rambles produces quotes that need cleaning up.
4. **A glossary for anything complex.** Two lines each for the concepts the reporter is likely to get slightly wrong.
5. **Source links.** Dashboards, explorers, audits, documentation. Reporters prefer to verify things themselves.
6. **Attribution terms, decided in advance.** If anything is going to be on background, agree it before the call. My explainer on [off the record vs on background](/blog/off-the-record-on-background-crypto-founders) covers how.

A reporter who has all of that rarely gets a fact wrong, and you've given them nothing to resent. The broader version of this prep is in my [founder interview brief for tier-1 media](/blog/web3-founder-media-interview-brief-tier-1).

## How is sponsored content or an op-ed different?

The rules change when the content isn't independent reporting.

**Sponsored or paid placements.** These are advertising products sold by an outlet's commercial team and labelled as sponsored. Because you're paying, you typically see and approve the copy. One of my past campaigns, the Bullieverse funding round, mixed organic pitching with some sponsored placements; the CoinDesk piece in that campaign was sponsored content, not earned coverage. The two shouldn't be confused, by you or by your investors. My guide on [earned vs paid media in Web3](/playbook/earned-vs-paid-media-web3-2026) explains the trade-off.

**Op-eds and contributed articles.** Your name is on it, so you write it, and the outlet's editors edit it. Practice varies: some editors send back substantive changes for your agreement, others only make light edits and publish. You can reasonably ask to see significant edits that change your argument. You can't insist the editor runs your preferred headline.

**Q&A formats.** Some publications run interviews as edited question-and-answer pieces. Even then, the outlet controls the edit. Ask about their process at the start rather than assuming you'll see it.

| Format | Usually see it before it runs | What you can reasonably ask for |
|---|---|---|
| News story or feature | No | Fact or figure checks, quote read-back if accuracy is in doubt |
| Op-ed under your byline | Often, depending on the outlet | To see edits that change your argument |
| Q&A interview | Varies by outlet | Clarity on their editing process upfront |
| Sponsored content | Yes | Copy approval, within the outlet's labelling rules |

## What if the published article has a mistake?

Then you ask for a correction, after publication, through the right channel. That's the normal, accepted way to fix errors in independent journalism, and it's far better received than pre-publication pressure.

There's an important distinction between a factual error (a wrong number, a misspelled name, a misattributed quote) and framing you dislike (a critical angle, a sceptical headline, a competitor's quote). Outlets generally fix the first. The second is the reporter's editorial judgement. How to tell them apart, and how to ask, is covered in [how to ask a journalist for a correction](/blog/what-to-do-when-journalist-gets-story-wrong).

## When this doesn't apply

There are a few situations where the usual answer bends:

- **Highly technical or regulated topics.** Some reporters and outlets will run specific passages past a source to check technical accuracy, for example on security research or complex financial mechanics. That's their choice, not your right.
- **Different media cultures.** Expectations around review vary between countries and between trade and mainstream outlets. In some markets, reviewing an interview transcript is more common. Ask the local reporter or a local PR partner rather than assuming.
- **Brand-owned or partner content.** If an exchange, ecosystem foundation or partner is publishing about you on their own blog, you'll usually review it because it's co-marketing, not journalism.

The trade-off is simple. Earned coverage gives you credibility you can't buy, and the price is giving up control. If you need control, buy a sponsored placement or publish on your own channels, and accept that readers will weigh it accordingly.

Preparing founders so they don't need to see the draft is a core part of my [founder profiling work](/services/founder-profiling).

## FAQ

### Can I ask to record the interview myself?

Yes, and it's common for PR teams to do so, as long as you tell the reporter upfront. A recording also helps you check any later concern about a quote against what was actually said.

### What if a reporter offers to send me the draft?

It happens occasionally, usually for technical accuracy. Treat it as a courtesy: point out factual errors only, quickly, and don't try to change tone or angle. Overreaching once means you won't be offered it again.

### Can my PR person ask for approval on my behalf?

No. A request from a PR person is still a request from you, and reporters read it the same way. A good PR lead will steer you towards a fact sheet and a fact-check offer instead.

### Is it OK to ask when the article will be published?

Yes, as long as you ask once and accept "I'm not sure yet." Publication dates move with editors, news cycles and space, and the reporter often doesn't control them.

*Nervous about an upcoming interview and how your words will land? [Talk to me first](/contact) and we'll build the fact sheet and prep together so accuracy isn't left to chance.*

---

**Book a 30-min interview prep call with Shilika** - https://calendly.com/shilikajain/30min/

Canonical: https://www.shilikajain.com/blog/can-founders-review-article-before-publication