Foundations
Press release distribution demand signals: logging and rejecting a lead
Log press release distribution demand signals from announcement occasions, reject each lead with a written check, and convert it only on an authorised decision.
What to take away
- A press release distribution demand signal is a retrievable public record of an announcement occasion that raises one operational question and carries a check that can reject it.
- Log the publisher, source date, geography, observed event and rejection reason for every signal.
- Record silence as unknown, never as evidence of need or of no need.
- Search volume, job adverts, supplier surveys, directories and global forecasts are not signals.
- Only an authorised brief, procurement or documented internal decision moves a lead to an opportunity.
Announcement occasions worth logging
Press release distribution demand starts with an announcement occasion: a product launch, a funding round, a leadership change, an event or award, or a response to an incident. The occasion earns a log entry only.
It does not show that the organisation needs a distribution service, holds budget or will buy. Each occasion leaves a record anyone can retrieve. The table pairs the occasion with that record, the question it raises about announcement workflow, and the check that rejects the lead.
| Occasion | Retrievable record | Question it raises | Reject if |
|---|---|---|---|
| Product launch | The organisation's dated newsroom or product page | Is a new objective claim about to go out? | No evidence owner |
| Funding round or ownership change | A Companies House filing or the company's own statement | Who approves the wording and the recipients? | No named approval owner |
| Leadership change | Companies House officer records | Does the organisation run its own communications? | Head-office entry only |
| Event or award | The organiser's published programme or shortlist | Is the placement paid, owned or independent? | Payer or placement unknown |
| Incident or correction | The organisation's published notice | Who can authorise a correction? | No authority named |
The scope is organisations operating in England, and UK-wide sources keep their UK geography. Search volume, job adverts, supplier surveys, directories and global forecasts are excluded, because none of them gives an English operating organisation a record of its own.
Five records that test an occasion
Once an occasion is logged, five public records show which check to run. Each has an authoritative retrievable source, a specific operational question and a check that can reject the lead. The order follows the workflow, not merit or demand.
| Record | Source | Question it raises | Reject if |
|---|---|---|---|
| Reporting population | ONS business activity release | Has an eligible buyer group changed? | No English operating site |
| Commercial recognition | CAP Code section 2, rule 2.1 | Is paid placement mixed with editorial outreach? | Payer or placement unknown |
| Objective claims | CAP Code section 3, rule 3.7 | Is evidence held before a claim goes out? | No evidence owner |
| Contact sources | ICO business-to-business marketing guidance | Has a contact source or purpose changed? | No lawful-basis assessment |
| Accessible formats | Government inclusive communication guidance | Is a format gap visible? | No user-tested output |
Fields to log for each signal
A log turns a hunch into something a second reviewer can check. Five fields are enough, and each one answers a question the reviewer would otherwise ask.
- Publisher and source date, so the record can be found again and its age is known.
- Geography and the observed event, stated as what happened, not what it might mean.
- Buyer hypothesis and contact owner, so someone is named to test it.
- Next evidence required, written as one concrete item.
- Rejection reason, filled in if the check fails.
Leave a field blank when the record does not give it. A blank is honest, and a guessed entry spreads into later decisions. Silence from a contact is the same: record it as unknown, not as a yes or a no.
Applying the rejection check
The check should be written before the record is read, not after. Otherwise a keen researcher will find a way to keep every lead alive.
- Confirm an English operating site and buying authority.
- Obtain the content, the control relationship, the payer and the placement.
- Identify each objective claim, its evidence owner and the sector reviewer.
- Map source, recipient type, purpose, channel and lawful basis.
- Ask intended users which formats they need and test the output.
Examples show the line. A new local unit in an English city with its own marketing function is worth an interview, while a registered-office move is not. Stop if a change is only a head-office entry or a broad industry label.
A record with no rejection check is a note, not a signal.
Reading the ONS and ICO records without overreading them
Two of the five records are easy to overread. The ONS business activity release gives numbers of enterprises and local units from a snapshot of the Inter-Departmental Business Register taken on 14 March 2025.
A defined change in an eligible buyer frame can justify fresh interviews about announcement workflows. It is not evidence of communications demand, so the interview, not the statistic, tests the hypothesis.
The contact record needs the same care. The ICO's business-to-business marketing guidance says that using publicly available personal data to send marketing, even in a business context, requires compliance with the UK GDPR.
A new media list, database or outreach purpose can therefore expose a governance task. Map source, recipient type, purpose, channel and lawful basis, and remember that a public address is not consent.
The commercial and claims records
CAP Code section 2, rule 2.1, requires marketing communications to be obviously identifiable as such. A buyer mixing paid placement with editorial outreach may need to redesign its process. The need concerns labelling, not guaranteed reach, and the advertising rules set out the questions in order.
CAP Code section 3, rule 3.7, expects documentary evidence before an objective claim is distributed or submitted for publication. A new product statement, a comparison against a rival or a test result quoted in a headline can all trigger an approval review. Where the sector is financial, the FCA expects promotions to be clear, fair and not misleading.
For each claim, identify its evidence owner and the sector reviewer. Stop release activity when substantiation or authority is absent, and record the gap for the next reviewer.
One lead, from log to decision
A logged signal remains a research lead until someone with authority acts on it. Take a new local unit in an English city, found in a public record, with its own marketing function.
- Log the publisher, source date, geography and the observed event: a new local unit.
- Write the hypothesisthe unit may need a route for approved announcements.
- Name the contact ownerthe unit's marketing lead, who is asked for one interview.
- Run the rejection checkis there buying authority, and who is the payer?
- Stop and record the reason if the lead fails. Otherwise wait for a brief.
Only an authorised brief, procurement or documented internal decision should move it forward. Draft the hypothesis on a card before it hardens, and keep it testable with buyer hypothesis cards.
Once a lead has converted, the bounded commercial tests are the next step. The market size note explains why no top-down total can replace this bottom-up work, and the entry checklist shows what else must be in place first.
Common questions
Does a new ONS release prove communications demand?
No. It shows a changed population of enterprises and can justify interviews. Demand appears only when a named decision owner confirms a problem.
What turns a research signal into an opportunity?
An authorised brief, a procurement process or a documented internal decision. Until one of those exists, the record stays a research lead.
How should silence be logged?
As unknown. A missing reply is neither evidence of need nor evidence of no need.
When should I stop pursuing a lead?
When the rejection check fails: no buying authority, no payer or placement, no evidence owner, no lawful-basis assessment or no user-tested output.
