Media Relations

A Journalist Said Yes, Then Nothing Ran: How to Tell What Went Wrong

Start by assuming the least dramatic explanation, because it is almost always the right one: the story was never as committed as it sounded, or it was written and lost its slot. Reporters rarely promise coverage, editors kill pieces routinely, and a stronger story in the same beat can push yours off the schedule on the morning it was due to run. Almost nothing about this is about you, and the diagnosis is mostly a matter of rereading what was actually said and checking what was actually asked for.

That matters because the fix differs by cause, and the default response — a chasing email a few days later — helps in only one of them and damages the relationship in two.

Reread the yes and work out what kind it was

Go back to the actual thread and read the reporter's words rather than your memory of them. Interest and commitment look identical when you are hoping.

  • "Send me more" or "this is interesting" is curiosity. Nothing was promised, and no follow-up is owed to you.
  • "I'll take a look" or "might be one for next week" is a maybe with no slot attached.
  • "I'm writing this up" or a request for a specific quote, image or figure is a real commitment to file — though filing is not publishing.
  • A freelancer saying yes means they intend to pitch it to an outlet. That is genuine enthusiasm and a real step forward, but the commissioning decision belongs to an editor who has not seen it yet, and a large share of freelance pitches are never commissioned.
  • An interview is not a promise. Reporters interview far more people than they quote, and a conversation that felt like a great fit may have been background for a piece that took a different shape.

If your yes belongs in the first two categories, you do not have a broken story — you have a pitch that has not landed yet, and the honest next step is a better angle rather than a chase. Our pitching guide covers what turns interest into a commitment.

Was the piece written and held, or never written at all?

These look the same from your inbox and need opposite responses. A few cheap checks separate them.

Did they ask you for something specific? A request for a headshot, a product image, a founder title, a customer willing to speak, or a number they could verify means someone was writing. Nobody chases assets for a story they have abandoned.

Did anything you sent arrive late, or not at all? This is the most common self-inflicted cause and the easiest to miss. A fact-check question that sat in an approvals queue for four days, an image that came back too small to print, a customer who went quiet when asked to be named — any one of them can stall a piece past its window. Check your own sent folder before you conclude anything about theirs.

Has their byline appeared since? If they have published several pieces on the beat, they are working and your story was deprioritised. If nothing has run under their name, they may be on leave, on another assignment, or gone from the outlet entirely — mastheads change more often than media lists do.

Did something similar run there? Search the outlet for your topic. A desk that has just covered the same ground rarely runs a second version, and an editor may have killed yours for exactly that reason.

What happened in that beat that week? A major story in your sector absorbs the section's space and attention. Your news did not get worse; the competition for the page got harder.

The reasons a committed story stops

Assuming there really was a commitment, these are the usual causes, and each has a different response.

The editor spiked it. The reporter wanted it, the desk did not — the angle was too close to something recent, too promotional in the retelling, or too narrow for that section. Nothing you send now revives it. What helps is understanding the objection for next time, which you can only get by asking neutrally.

It got bumped and never rescheduled. A filed piece that misses its slot sits in a queue behind whatever is newer. Timely stories decay in that queue; evergreen ones can resurface weeks later without warning.

Verification stalled. Something could not be confirmed to the outlet's standard: a claim without a source, a customer who would not go on record, a figure you could not show the working for. Reporters do not usually announce this — they simply stop, because the story cannot be published as drafted.

The reporter's situation changed. Reassignments, leave and departures strand in-progress stories with no handover.

The exclusive or embargo broke. If the same news appeared elsewhere first, or an embargo leaked, the piece lost the thing that made it worth running. This is the one cause where the damage is often on your side of the table, and it is worth understanding the terms properly before you offer either — embargo vs exclusive sets out what each one actually commits you to.

Your news got overtaken. A larger event in the same space made your announcement a footnote. Editors make that call quickly and rarely explain it.

How long should you wait before following up?

Match the wait to what the story needs, not to your anxiety.

For a dated story — an event, an embargoed announcement, an earnings tie-in — the window is short. If the date passes with nothing published, follow up within a couple of days, because after that the story is no longer live and the conversation is about the next one.

For an undated feature, give it one to two weeks past any date they mentioned before checking in. Pieces sit in queues, and a chase after four days signals you do not understand how newsrooms work.

If they asked you for something and you sent it late, follow up promptly with an apology and everything they need in a single message. That is a repair, not a chase, and it is the one situation where speed clearly helps.

Send one follow-up. If that goes unanswered, stop. A second and third chase does not surface a story; it costs you a contact who will remember the name next time.

What to put in the follow-up

The chase that works does not ask about the story. It gives the reporter something to say yes to.

Keep it to a few lines, reference the specific piece you discussed, and add one new, useful item: a fresher figure, a customer who has now agreed to speak, an image they did not have, or a development since you spoke. Then make the exit easy — say plainly that if the story has moved on, that is completely fine and you will not chase again.

That last sentence does more work than anything else in the email. It removes the awkwardness that keeps a reporter from replying to a message they cannot say yes to, and it is why this version gets an honest answer far more often than "just checking in on the below."

Three things to leave out: any suggestion that coverage was owed, any reference to time you spent on the interview, and copying in an editor. The first two read as entitlement, and the third goes over the head of the person you want to work with again.

How to stop it happening on the next story

Most of these failures are set up at the moment of the yes, when everybody is enthusiastic and nobody is specific.

  • Ask what they still need and when. One sentence — "what else do you need from me, and by when?" — converts a vague yes into a checklist with a deadline.
  • Confirm the timing they are working to. Not to hold them to it, but so your follow-up lands after their window rather than during it.
  • Have the assets ready before you pitch. Images at print resolution, correct titles, a named customer who has already agreed. Nothing stalls stories like waiting on your own approvals.
  • Line up sign-off in advance. If legal or an exec has to approve every quote, build that into your timeline; a reporter's deadline will not wait for your Tuesday review.
  • Answer fact-checks the same day, even partially. "Confirmed on the first two, checking the third" keeps the piece alive.
  • Keep the relationship separate from the outcome. A reporter whose story got spiked is a reporter who already believes your news is interesting — that is worth more than the placement you lost. Building that kind of standing over time is the subject of our media relations guide.

FAQ

Can I just ask a journalist whether my story is still running? Yes, once, and phrased so a "no" is easy to give. Something like "is this still on your list, or has it moved on? Either is fine" gets a straight answer far more reliably than an open-ended check-in.

Should I pitch the same story to another outlet if it never ran? Usually yes, once it is genuinely dead — the date passed, or they told you it was dropped. If you offered an exclusive, honour its terms first. And if you are pitching a second outlet while the first still has it, say so.

Does giving an interview mean coverage is coming? No. Reporters gather far more material than they publish, and interviews frequently become background rather than quotes. Treat an interview as strong interest, never as a placement.

What if the reporter has left the outlet? Do not simply forward the thread to whoever replaced them. Repitch from scratch to the person who now covers the beat, with a short note that you had been working with their predecessor.

Is it worth asking why the story was dropped? It is worth asking once, neutrally, framed as wanting to pitch better next time. Some will tell you, and the answer is usually more useful than the coverage would have been — it tells you what that desk actually wants.

Should I send the release out on the wire instead? That is a different job. Distribution creates a public, indexed record of the announcement; it does not produce the original piece you were waiting for. Do it if the news needs to be on the record — not as a substitute.


A yes that produced nothing is normal, recoverable, and usually explained by the newsroom rather than by you. Reread the thread, check what was asked for, send one useful follow-up — and keep the contact. For more on turning interest into published coverage, read the guides at PR Rush.

Comments are disabled for this article.