How to diagnose reporter fit and pitch quality before sending
A practical guide to RunPR reporter-fit reasoning and Empathy Adversary feedback: what is examined, how to interpret it, and where human approval remains mandatory.
Does this reporter fit the angle, and is the draft respectful, supported, and ready for human review?
Pitch diagnostics have two distinct jobs. Reporter-fit reasoning explains why a journalist surfaced for the story. The Empathy Adversary reads the resulting draft from a busy reporter’s perspective and identifies objections before a person decides what happens next.
Neither diagnostic is permission to send. They are evidence and criticism attached to a draft.
Reporter matching compares the angle with recent, visible evidence.
RunPR ranks matched reporters against the pitch angle and shows the reason each match surfaced. That reasoning can include beat history, recent coverage, byline recency, and outlet fit. Recent articles stay available as context, and pitches can be grounded in the reporter’s latest bylines rather than a generic beat label alone.
The Empathy Adversary stress-tests the pitch, not the reporter.
The draft is reviewed for issues a working journalist would notice: a product-first or buried lede, weak or unclear ask, generic personalization, unsupported claims, missing evidence, prescriptive framing, questionable timing, and whether the pitch offers genuine reader value.
Feedback is stored as a verdict—send, revise, or do not send—plus objections, severity, reasoning, and suggested changes when available. RunPR can apply a revision and re-check it, but the criticism remains review material rather than a guarantee of quality or response.
A review packet with the rationale beside the draft.
- A ranked reporter match with outlet, coverage context, relevance score, and an explanation of why the journalist surfaced.
- Recent byline context used to judge whether the angle belongs in the reporter’s current work.
- A grounded pitch draft shaped by the source story, client facts, recent bylines, and the team’s voice profile when configured.
- Empathy Adversary feedback with verdict, objections, severity, reasoning, and suggested revisions.
- An approval artifact that a person can edit, hold, reject, approve, export, or annotate according to the configured workflow.
Read fit, factual support, and empathy feedback as separate gates.
Start with “why this reporter”
Open the cited bylines and verify that the recent work actually supports the stated match. A broad beat match is weaker than a recent article that directly overlaps the angle.
Then inspect the factual spine
Every material claim, number, credential, and timing detail should trace back to the source story or approved client context. A fluent draft with an unsupported core claim is not ready.
Use objections as editorial prompts
A “revise” verdict means the draft needs work, not that every suggestion must be accepted verbatim. A “do not send” verdict blocks RunPR dispatch; the right response may be a factual fix, a different reporter, a different angle, or no outreach.
Do not turn the output into a probability
Reporter fit and Empathy feedback do not predict coverage, interest, opens, or replies. This diagnostic does not claim to track or score journalist replies.
Verify the match, repair the draft, and make an explicit decision.
- Read the match reason and at least the most relevant recent byline. Remove the journalist if the overlap is superficial or stale.
- Check the source story, client facts, and every material claim in the draft. Delete or qualify anything unsupported.
- Work through high-severity Empathy objections first, then decide which medium and low suggestions improve the pitch without flattening the team’s voice.
- Confirm the subject, recipient, timing, embargo, ask, sender identity, and approval route.
- Edit, hold, reject, export, or approve. If the evidence does not support the angle, choose no send.
See fit reasoning and criticism beside the same illustrative draft.
The live RunPR homepage example pairs an ApexLab funding pitch with a “Why this reporter” panel and an Empathy Adversary review. The fit reason points to the reporter’s recent AI-infrastructure funding coverage; the criticism calls out a first-party margin claim, embargo timing, and prescriptive framing. The example is labeled illustrative, while live matching uses the team’s actual stories and reporters.
See the feature overview for the full monitor-to-approval workflow.
Fit and critique depend on the evidence available to the system.
- Reporter profiles and bylines can be incomplete, stale, ambiguous, or changed after collection.
- A beat or outlet match cannot reveal current assignment load, private editorial plans, conflicts, preferences, or availability.
- Relevance scoring and Empathy review are model judgments. They can miss nuance, overstate an objection, or produce a plausible but unhelpful suggestion.
- A voice profile can shape style, but it cannot make an unsupported claim true or substitute for source evidence.
- No score or verdict predicts whether a reporter will engage, cover the story, or view the pitch favorably.
- Outcome information such as delivery, opens, or later coverage belongs to separate downstream evidence—not the pre-send diagnostic.
A person remains accountable for recipient choice, claims, wording, and approval.
RunPR automates preparation and coordination. It does not turn a match or a favorable critique into send authorization. A human must review the recipient, evidence, draft, timing, and approval state. RunPR’s dispatch path enforces sending readiness and safety; the default approval boundary records a decision without inventing permission to deliver.