Data PR · Jun 25, 2026 · 10 min read · by the Revelle Editorial team

Giving a newsroom a data story it can run

Every PR team that has ever sat on a pile of internal numbers has had the same hopeful thought: surely a journalist would want this. The booking volumes, the survey responses, the year-over-year shift in customer behavior, the regional breakdown that nobody outside the company has ever seen. The instinct is right. The execution is usually wrong. What lands in the reporter's inbox is a press release with a percentage buried in the third paragraph, a link to a forty-page report, and a subject line that promises "exclusive data" without saying what the data actually shows. The reporter does not have time to mine it. They move on.

Giving a newsroom a data story it can run is a craft, and it is different from doing research. The research produces a finding. The craft turns that finding into something a tired editor can pick up at four in the afternoon, understand in thirty seconds, and publish before deadline without having to call you back three times. The difference between those two things is where most data-led PR fails. The numbers are fine. The packaging is not. This piece is about the packaging, because that is the part you control and the part that decides whether your work becomes coverage or becomes a forgotten attachment.

Start with the finding, not the dataset

A dataset is not a story. A story is one sentence that a person who does not work at your company would repeat to a colleague. "We surveyed people about their finances" is a dataset. "Half of renters under thirty have given up on ever owning a home" is a finding. The first is something you did. The second is something a reader feels. When you cannot reduce your data to a single sentence that contains a surprise, a number, and a clearly named group of people, you do not yet have a story. You have homework that is not finished.

The discipline here is brutal and worth it. Take your richest report and force yourself to write the one headline a national outlet would run. Not the headline you wish they would run, the one they actually would. If the honest answer is "this confirms what everyone already assumed," then the data is real but the story is weak, and no amount of design will save it. Journalists are looking for tension: something changed, something is worse than expected, two groups diverge sharply, a trend reversed. If your numbers contain that tension, lead with it and lead with it hard. If they do not, the most useful thing you can do is keep looking through the data for the cut that does, rather than dressing up the cut that doesn't.

One more thing about the finding. It has to be defensible against the obvious follow-up question. If you claim a record, a reporter will ask "compared to when?" If you claim a surge, they will ask "from what base?" Decide your answer before you send anything, because a finding that collapses under the first email reply is worse than no pitch at all. It costs you the story and a little of your credibility for the next one.

Show your method before they ask

The fastest way to lose a serious reporter is to give them a number with no way to verify how you got it. Good journalists are professionally suspicious of company data, and they should be, because most of it is marketing dressed as research. You earn the benefit of the doubt by volunteering the method up front, in plain language, before anyone has to drag it out of you.

That means a short, honest note on the basics. How many people or records the data covers. When it was collected. How they were reached or where the records came from. Whether it is a representative sample or a self-selected slice of your own customers, because those are very different claims and an editor will treat them very differently. If it is your own internal transaction data, say so plainly; first-party operational data is often more interesting than a survey precisely because it reflects real behavior rather than stated intent, but only if you are upfront that it represents your customers and not the whole market.

The reason this matters beyond ethics is purely practical. A reporter who can see your method can write the caveat sentence themselves: "according to a survey of two thousand adults commissioned by the company." That sentence is what lets a careful outlet run your number at all. If you hide the method, you force them either to email you and wait, which kills your deadline, or to drop the story, which kills your coverage. Make the caveat sentence easy to write and you remove the single biggest reason careful outlets pass on company data.

Give them a visual they can actually use

A chart in a press release is not the same as a chart a newsroom can publish. Most are useless to a reporter because they cannot be lifted: they are screenshots locked inside a PDF, they carry your logo across the corner, they use brand colors that clash with the outlet's house style, or they pack five trends into one cluttered frame so no single point reads clearly. Editors will not redraw your chart for you. They will either run something clean or run nothing.

The visual that travels is simple and self-contained. One clear point per chart. A title that states the finding rather than describing the axes, so it makes sense even when republished out of context. Labels readable at the small size a story actually uses. And critically, supplied in a format a newsroom can drop in or quickly remake: a clean image plus the underlying numbers in a basic table, so their own graphics desk can rebuild it in house style if they prefer. The branding question is worth being honest about. A subtle credit line is reasonable and most outlets accept it. A chart that functions as an advertisement will be cut, and you will have spent design budget making something nobody can run.

Think about what the visual is doing for the reporter. It is proof that the finding is real, and it is a shortcut that saves their graphics team an afternoon. When you make their job easier, your story competes well against the dozen others fighting for the same slot. A genuinely good chart can be the reason a story runs at all, because it lets an editor fill a visual hole on the page and tell a story in the same move.

Write the quote they will actually use

Every data story needs a human voice, and the quote is where most company commentary goes to die. The reflexive instinct is to use the quote to praise the company, to thank stakeholders, or to restate the number that is already in the chart. None of that gets printed. A reporter uses a quote to add interpretation, context, or a forward look that the data alone cannot provide. Your job is to supply exactly that and nothing else.

The strongest quotes do one of a few things. They explain why the finding happened, drawing on expertise the journalist does not have. They say what it means for ordinary people, translating the abstract number into a consequence. Or they make a measured prediction about where the trend is heading. What they never do is sound like a brochure. "We are proud to release this important data" is filler that a sub-editor deletes on sight. "This is the first time we have seen demand fall in a category that grew through every previous downturn, and it tells us households are now cutting things they once treated as essential" is a quote that earns its place, because it adds something the reader could not have worked out alone.

Attach the quote to a real, named person with a credible title, ideally a founder or a senior operator who can speak to the underlying reality rather than a generic spokesperson. This is where a strong founder as a source changes the economics of the whole effort, because a named human with genuine authority makes the story citable and gives the outlet a face to attribute the analysis to. Offer that person for a short follow-up interview and say so in the pitch. Many of the best data stories grow well beyond the original release once a reporter gets ten minutes with someone who actually understands the numbers.

Package it so a deadline editor can move fast

Assume the person reading your pitch has eleven minutes before their next meeting and forty unread emails behind yours. Everything about how you package the story should respect that constraint. The finding goes in the subject line and the first sentence, not the fourth paragraph. The method sits in a short, scannable block they can quote from directly. The visual is attached and ready, not "available on request." The quote is right there, pre-cleared, with the spokesperson's name and title. And there is one clearly named contact who will answer the phone today, not a generic press address that routes to a queue.

The structure that works is almost boring in its predictability, which is the point. Headline finding. One or two sentences of context that explain why it matters now. The key numbers, no more than three or four, because a wall of figures reads as noise. The method note. The quote. The visual. The contact. If a reporter can read your email top to bottom and have everything they need to file, you have done the job. If they have to assemble the story from pieces scattered across an attachment and a microsite, you have made them do work they will not do, and the story dies of friction rather than weakness.

This is also where relationships compound. The reporter who has run your data before, found it solid, and never been embarrassed by it will open your next email first. That trust is built one clean, accurate, easy-to-use story at a time, and it is far more durable than any single placement. The way you treat a reporter's deadline today decides whether they treat your finding as a gift or as a chore next quarter.

Match the angle to the outlet before you send

The same dataset can support several different stories, and the mistake is sending one generic version to everyone. A national consumer outlet wants the human stakes and the surprising headline. A trade publication wants the operational detail, the segment breakdown, the implication for the industry. A regional outlet wants the local cut: what does this look like in their city, their state, their patch. The data is the same; the cut you lead with is not. Sending the right slice to the right desk is the difference between a pitch that feels written for them and one that feels mass-mailed, and reporters can tell the difference instantly.

This is where deciding between trade and national coverage shapes the work before you have written a word. National coverage is loud and brief; trade coverage is narrow but reaches the exact people who buy what you sell, and it often carries more weight with the audience that actually converts. A serious data story usually deserves both, told two different ways, rather than one flattened version that fits neither well. Decide which outcome matters more for this particular finding, build the lead cut around that audience, then prepare the secondary cut for the other tier rather than hoping one version stretches to cover both.

The whole discipline comes down to a single shift in posture. Stop thinking about what you want to announce and start thinking about what a reporter needs to file. The finding has to be a real surprise that survives the obvious question. The method has to be visible so a careful outlet can run it. The visual has to be liftable so a graphics desk can use it. The quote has to add something the data cannot. And the package has to be assembled so a person under deadline can move without calling you back. Get those five things right and you are no longer pitching a story. You are handing a newsroom something it can run, which is the only version of data PR that actually works, and the only version a busy editor will thank you for sending.