A launch list built from last spring's spreadsheet
An account executive is asked to pull a media list for a client launch on Thursday. The quickest route is the list from the last campaign for that client, which sits in a shared drive folder called Media Lists FINAL. It has 140 names. Some were exported from the media database, some were added by hand by someone who has since left, and a few came from a business card at an event.
The release goes out. Eleven emails bounce. Four more come back with out-of-office replies saying the journalist has moved to another title and giving a new address. One goes to a freelancer who stopped covering the sector a year ago and replies, politely, asking to be taken off. The executive fixes the addresses in their copy of the spreadsheet, but the old list in the shared drive stays exactly as it was, ready to fail again for whoever uses it next.
Why a list decays faster than anyone updates it
The journalists are not the problem. Desks change, titles merge or close, staff writers go freelance, and beats shift after a reorganisation. That movement is normal. What makes it hurt is how agencies store lists.
- Each campaign list is a copy, so a correction made in one list never reaches the others.
- Bounces and out-of-office replies land in one person's inbox and are read, not recorded.
- The media database subscription is updated by its provider, but the exported spreadsheet is a snapshot from the day it was downloaded.
- Hand-added contacts, often the most valuable ones, exist nowhere except the spreadsheet.
- Nobody owns the list after the campaign ends, so nobody is responsible for keeping it right.
Tools such as Cision, Muck Rack, Roxhill or Vuelio keep their own records reasonably current. The gap is between those records and the dozens of spreadsheets your team has made from them.
What a stale list does to a campaign
A bounce is the visible part. The quieter cost is a release reaching the wrong person on a title, being ignored, and the account team concluding the story did not land when it never reached the right desk. Journalists who receive pitches outside their beat remember the agency name, and not kindly.
There is also time. Executives rebuild lists from scratch because they do not trust the old ones, which means the same research is done again for every campaign, and the notes from the last round are lost each time.
How we build a list that stays current
What we build is one contact record per journalist, with lists that point to those records instead of copying them.
- We import your existing lists and match duplicates by email, name and title, with a review screen for the uncertain matches rather than an automatic merge.
- Each journalist gets one record: current title, beat, email, phone, social handles, the source of each field and the date it was last confirmed.
- Campaign lists become saved selections of those records, so correcting an address once corrects it everywhere.
- We connect the mailbox used for sending releases, read bounces and out-of-office replies, and turn them into flags on the record. An out-of-office that says someone has moved is parsed into a suggested new title and address for a person to accept.
- Where your media database has an API or a regular export, we compare it with your records and list the differences, such as a changed title or a new beat, for someone to approve.
- Before a list is used, it shows a health summary: how many records were confirmed recently, how many have open flags, and which ones have never been checked.
| Signal | Where it comes from | What happens |
|---|---|---|
| Hard bounce | Sending mailbox | Record flagged, address marked unusable |
| Moved-on auto reply | Sending mailbox | Suggested new title and address for review |
| Title or beat change | Media database export or API | Difference listed for approval |
| Opt-out reply | Sending mailbox or team member | Record suppressed from all lists |
| Not confirmed in a long time | Record date | Shown on the list health summary |
We keep your media database as the research tool. The record we build is the agency's own memory of who it actually works with, and it sits alongside the subscription rather than replacing it.
Pulling a list on a normal Tuesday
The executive searches for the client, picks last campaign's selection, and sees that nine records carry flags. Three have suggested new addresses from auto replies, already matched to the right person. Two show a title change from the database. Four have not been confirmed for a long time and are highlighted for a quick check.
They spend a few minutes resolving those, add two new names from their own research, and send. The two new names go into the shared records, so the next person to build a list for this sector sees them too. Nothing has to be remembered by anyone.
Is your agency here?
- Your shared drive has several versions of the same media list with different dates in the file name.
- Bounces are fixed in someone's copy of a spreadsheet and nowhere else.
- Executives rebuild lists from scratch because the old ones cannot be trusted.
- Contacts added by hand exist only in one campaign file.
- Nobody could say when a given journalist's details were last checked.