How to Build a Media List from Coverage Data Instead of a Static Database

Why static lists go stale

Contact databases are useful for finding emails and phone numbers. They are weaker at answering "who is writing this story now."

Three things move faster than a quarterly list refresh:

Beat changes. A reporter who covered cloud infrastructure last year may now cover consumer apps. The byline history in recent coverage is more reliable than a static beat tag sitting in a profile.

Outlet moves. People change employers. A profile that still lists Outlet A while the byline is at Outlet B wastes a pitch cycle and burns goodwill.

Topic drift. Your category narrative shifts: speed to trust, price to reliability, feature to risk. Reporters who covered last quarter's frame may not be the right targets for this quarter's proof point. Coverage data shows who already entered the new frame, and who is still writing the old one.

None of that means you should throw away a contact database. It means the shortlist should be built from recent articles, then verified in the database you already use for outreach. For how to judge whether a clip is worth targeting at all, see coverage quality benchmarks.

Step 1: Define the story you are pitching

Write three lines before you open any tool:

1. Key message. The one proof point you want in the story, not five.
2. Topic. The category conversation you are entering (for example, "enterprise AI reliability in production").
3. Competitor narrative. The frame competitors are winning on right now (for example, "fastest time to pilot").

If you cannot name the competitor narrative, you are not ready to score an angle gap. Share-of-voice context helps here, start with What Is Share of Voice in PR? for the definition and competitive-set rules, and The New Share of Voice when themes and message frames matter more than raw mention counts.

Keep the pitch definition on one page. Every later filter, topic, outlet list, time window, should map back to those three lines. If a clip does not serve the message, the topic, or the competitor narrative, it does not belong in the coverage set.

Step 2: Pull the coverage set

Set a 60 to 90 day window. Shorter windows miss slow-burn trade coverage. Longer windows pull in reporters who have already moved on.

Include:

• Online and print articles where the topic (or competitor narrative) is central, not a passing mention.
• Podcasts and newsletters when those channels shape your buyers. Delve tracks podcast episodes and newsletter coverage alongside news and social, so include them when the beat lives there.
• Competitor coverage, not only coverage that mentions you. You need reporters who already write the category story.

Exclude:

• Wire reprints and syndicated duplicates once you have the originating byline.
• Passing mentions that only brush the topic.
• Outlets outside the tiers your team will actually pitch this cycle.

Inclusion rule to write down: "Article centers [topic] or [competitor narrative] in the headline, lede, or primary section, not a one-line name-check." Apply it consistently so the scorecard stays comparable across teammates.

In Delve, this step is a tracker (or filtered tracker view) scoped by date, topic, publication list, and media type, then triage into tracked coverage. Publication lists help you constrain to Tier 1 / trade / regional sets without pretending the list is a journalist contact book (publication lists, tracker management).

Step 3: Group by reporter and score

Export or review the coverage set and group rows by author + current outlet. One person, one row, even if they wrote four pieces. Shared bylines get one row per named author when you can attribute the piece; otherwise note the outlet and park the unnamed share.

Score each row. Keep the scale simple (0–2 or Yes / Partial / No) so two teammates grade the same way. Recency, topic fit, and stance are the three scores that decide who rises; angle gap and readership decide who you pitch first.

Reporter scorecard

Build the template once: a single spreadsheet with those columns, one tab per campaign, sorted by (topic match × recency) then readership. Add a second tab for "Dropped" so you keep an audit trail. Share it in your team drive; retire rows when Verify status = Drop.

Reporters with high topic match, a clear stance on the category, and a clear angle gap rise. Reporters with many articles but no gap fall, because they already wrote your exact proof point last month, unless you have a genuinely new development.

Step 4: Find reporters covering a competitor's narrative

Pull a second coverage set: articles that advance the competitor narrative, whether or not you appear. This is usually the denser set, competitors who are winning the frame generate more bylines than you do.

For each reporter:

1. Did they cover the competitor frame in the window?
2. Did they already cover your proof point?
3. If (1) yes and (2) no → they are an angle-gap target: they already care about the topic; you are offering the missing frame.

This is the practical answer to "which platform helps PR teams find reporters covering a specific competitor narrative?" Start with the competitor's coverage cluster, not with a keyword search for your brand name alone. The tool that already holds competitive coverage is the right place to run the cut; the contact database is where you look up how to reach the shortlist afterward.

Example angle-gap sentence for the scorecard: "Covered Competitor X's speed-to-pilot claims twice in 70 days; has not written the reliability / production-trust frame."

Step 5: Verify before you pitch

Do not send from the scorecard alone. Run this checklist on every Pending row, then mark it Verified or Drop:

Verification checklist

• Still writes for that outlet. Latest byline matches; author page or staff list still lists them.
• Date of last relevant article. Preferably within the last 30 to 60 days for a timely pitch; older bylines need a new hook.
• No conflict with past coverage. They have not already dismissed your category of proof in a way that makes this ask tone-deaf.
• Contact path is current. Email or preferred contact from your contact database or the outlet's masthead (this is where Muck Rack / Cision-style tools still earn their seat).
• One reason, one ask. The pitch-reason column becomes the first paragraph; if you cannot write it, the row is not ready.

Verification is where coverage-driven lists and contact databases meet. Coverage tells you who; the database tells you how to reach them.

Step 6: Keep the list alive

Treat the list as a living artifact, not a campaign souvenir.

Refresh cadence: re-pull the coverage set every two to four weeks while the narrative is active; monthly when it is quiet. Align the refresh with your SoV or pattern review so the shortlist and the measurement cut use the same window.

Retire rules:

• No qualifying article in 90 days → Drop or park.
• Outlet move without a new beat match → Drop.
• They published your exact proof point → Move to "nurture / update only," not cold pitch.
• Angle gap closed by a competitor placement → Re-score before the next send.

Archive the old tab. Do not overwrite history, you will want to see who you already approached.

Worked example

The following company, reporters, outlets, and article counts are fictional. They illustrate the method only. They are not real people, publications, or placements.

Pitch definition

• Key message: "Northstar Analytics' reliability SLA holds under peak load."
• Topic: enterprise analytics reliability in production.
• Competitor narrative: Competitor "QuickPlot" wins coverage on "dashboard live in a day."

Coverage window: last 75 days. Set size after triage: 42 articles (including two podcast episodes and one newsletter deep-dive that centered the competitor's speed frame).

Scorecard excerpt. Readership is left out here for width; the full template keeps it.

Reporters A and B make the short list, high topic match, usable stance, clear angle gap. Reporter C fails topic match for a national proof-point pitch even though the article count looks strong. After verification (still at outlet; contact path current; no hostile prior piece), the team pitches two people with a one-sentence reason each, not a 40-name spray from last year's database.

Where Delve fits

Delve is the coverage analysis layer in this method, not a journalist contact database.

Use Delve to pull and structure the coverage set: trackers across news, social, podcasts, and newsletters; filters by topic, publication list, sentiment, and readership; article-level analysis (summary, quotes, themes, message pull-through) so scoring is not guesswork from headlines alone. Publication lists scope outlets; they are not reporter contact books.

Delve is not outreach infrastructure. Keep Muck Rack, Cision, or your CRM for emails and pitch tracking, and use Delve for who is writing this story now and what angle is open. That hybrid is the same job split described on Delve vs Muck Rack.

If the bottleneck is turning coverage into a short, reasoned list, talk to Delve.