cutePR

Media shortlist guide

Choose the journalists who have a reason to care.

A small launch rarely needs a long list. It needs a handful of people whose current work, readers, and format give the story somewhere credible to go. A fashion editor planning a product page, a local writer covering independent makers, and a reporter examining supply chains may all cover the same industry. They need three different stories, and one may have no reason to cover this launch at all.

This method starts after the launch brief is settled. It uses a fictional accessories label, Atelier Nacre, introducing a repairable everyday bag in one market. The names and outlets below are invented. Replace every assumed fit with a recent, dated piece of editorial evidence before anyone sends a pitch.

By cutePR · Published

Write the story boundary before searching for names

Put the verified launch facts on one line: product, availability, market, price, usable photographs, spokesperson, and what is genuinely new. Then write a second line for claims you cannot yet support. For Atelier Nacre, the repair service may be documented while a broad sustainability claim is not. The latter stays out of the pitch. A shortlist cannot repair a weak or inaccurate brief.

The PRSA Code of Ethics puts accuracy and truthful information at the centre of professional practice. Apply that standard to selection as well as copy: if the only reason for including a reporter is an old keyword match, mark the fit as unverified. Muck Rack's 2026 journalist survey also distinguishes a beat match from relevance to the audience's community. Its sample is mostly North American, so use that finding as a prompt to inspect the actual publication, not a universal benchmark or a prediction that a particular pitch will succeed.

Brief fieldFictional launch valueCheck before outreach
NewsRepairable everyday bagWhat changed compared with earlier products?
AudienceUrban readers buying fewer, longer-lived accessoriesWhich outlet actually serves them?
AvailabilityFrance, from 22 OctoberStock, retail link, and embargo confirmed?
EvidenceRepair terms, product images, maker interviewCan each claim be shown or sourced?
Excluded claimNo lifecycle impact figureRemove unsupported environmental shorthand

Find a recent editorial reason for each candidate

Start with outlets that reach the intended audience, then inspect their actual sections and formats. Search for recent work by the person you hope to approach. Note the title, date, link, audience question, and whether the journalist still covers that area. A named writer may have moved desks; an outlet may have replaced its shopping page with service journalism. Check the publication's contributor page or current byline when roles are uncertain.

Separate outlet fit from person fit. A publication can be promising while its particular correspondent is wrong for this story. Conversely, a freelance writer may produce a relevant column across several outlets; the assignment context still matters. If you cannot identify a current editorial opening, keep the outlet for later research rather than guessing an address or using a generic pitch as a substitute for fit.

  • Record one recent article or recurring format that explains why the outlet belongs on the list.
  • Record the person, current role, market, language, and source of the contact information separately.
  • Review stated submission rules, contact preferences, past interactions, and exclusions before choosing an action.
  • Write a one-sentence reader benefit; if it sounds identical for every outlet, research again.

Use a fit review grid, not a prestige ranking

Give each candidate a decision and a reason. The grid below is a fictional review, not a claim about real journalists. Its categories are deliberately qualitative. A large outlet with no relevant slot should not outrank a smaller one whose readers can use the story. A strong subject match is still insufficient if timing, geography, product availability, or a contact restriction fails.

Review the rows before outreach, with the launch owner if someone else approves the story. For every yes, be able to point to a current piece, a specific angle, and the material needed to report it. For every hold, name the missing evidence and who will resolve it. For every no, record the reason without judging the journalist. The result is a short, defensible work queue rather than a list of addresses.

All outlets and launch details are fictional. Copy the columns, then replace the clues with dated real evidence.
CandidateRecent editorial clueReader fit and possible angleDecision
Threadline, product editorRecurring practical bag reviewsPrice, capacity, repair terms; images readyYes: verify current editor and format
Quartier, local writerProfiles of neighbourhood makersWorkshop access and local jobs; interview pendingHold: confirm visit and spokesperson
The Loom Ledger, trade reporterMaterials and sourcing investigationsNo substantiated supply-chain changeNo for this launch
Weekend Atlas, travel editorPacking guides for short tripsPossible utility angle, but bag dimensions unconfirmedHold: complete product facts

Turn the shortlist into a manual outreach queue

For each approved row, prepare a tiny brief: who this is for, the one editorial opening, the factual news, the proof attached or available on request, and the operator's next action. Check whether another colleague has already approached the same person about the same launch. Resolve overlaps before outreach so one journalist does not receive two versions of a story from your team.

Keep a separate status for research, approval, drafted, sent manually, replied, and closed. The shortlist is a decision document; it is not evidence that any message was sent or any coverage was earned. Revisit it when availability, editorial plans, or the story itself changes. A previously rejected row can become relevant for a later, better evidenced angle, while a previously approved one can become unsuitable after a beat change.

Sources & methodology

Ready to connect your PR files?

The founder helps you get started and handles the agreed initial migration. Your feedback helps shape what comes next.

Request access

Preferential pricing during the beta, then standard pricing announced in advance.