Reviews
Part of Reviewing lead networks starts with finding out who actually offers the service
Selecting a lead network with recovery and exit proven before signature
Use this lead network selection checklist to verify identity, provenance, configured tests, non-compensating gates, rollback and exit evidence.
Use this lead generation networks selection checklist after defining the English territory, service category, recipient type and acquisition model. It is an acceptance gate, not a vendor score. One failed critical control stops the decision even if every convenience feature looks attractive.
What to take away
- Treat the checklist as an acceptance gate, not a vendor score, and stop on any failed critical control.
- Reconcile the trading name, contracting entity, company number and invoice entity before signing anything.
- Quarantine any route where provenance is absent, disclosure is misleading or suppression does not reach destinations.
- Keep security, accessibility, privacy and consumer assurance gates separate rather than averaging failures into a commercial score.
- Limit any proceed decision by category, territory, configuration, volume and review date.
1. Resolve identity and scope
Resolve identity and scope
- Procurement owner:match the trading name, contracting entity, company number, invoice entity and data-processing parties. Record the applicable terms version.
- Service owner:describe whether the offer is an introduction, directory, contact record, managed campaign or hybrid. Define supported territory and exclusions.
- Stop:do not contract if the responsible entity or supplied service cannot be reconciled.
Companies House records help with filed identity but do not verify service quality or submitted information. Recheck them on publication or signature day.
Identity and scope checks
- Match trading name, entity, company number
- Record applicable terms version
- Describe offer type and territory
- Define supported territory and exclusions
- Stop if entity or service cannot reconcile
2. Reconstruct provenance and recipients
- Privacy owner:obtain the collection wording, timestamp, source, purpose, named recipient or category, onward-sharing history and objection record for an authorised sample.
- PECR reviewer:assess each intended channel and subscriber type separately. A service request is not blanket permission for later marketing.
- Test:use synthetic or properly authorised fixtures to demonstrate recipient disclosure, an objection, a duplicate and a suppression update.
- Stop:quarantine the route when provenance is absent, disclosure is misleading or suppression does not reach the intended destinations.
The ICO's lead generation guidance makes proportionate buyer checks central when information is bought, rented or otherwise obtained.
Provenance and recipient checks
- Obtain collection wording and timestamp
- Assess each channel and subscriber type
- Test disclosure, objection, duplicate, suppression
- Quarantine route if provenance absent
- Quarantine if suppression does not reach
3. Challenge operations and billing
- Operations owner:map submitted, quarantined, validated, matched, disclosed, accepted, rejected, credited, complained, suppressed and exited states.
- Finance owner:identify the exact chargeable event, currency, VAT treatment, evidence window, credit route, renewal notice and dispute owner.
- Synthetic tests:send an ineligible category, a duplicate and a wrong-recipient case. Reconcile their state logs with a non-monetary test billing export.
- Stop:block release when events cannot be reproduced or a disputed charge cannot be tied to an agreed unit.
Do not populate a business case with supplier testimonials or an assumed conversion rate. A working billing export says nothing about lead quality or causal value.
Operations and billing challenge
- Map all operational states
- Identify chargeable event and credit route
- Send ineligible, duplicate, wrong-recipient tests
- Reconcile state logs with billing export
- Block release if events not reproducible
4. Keep assurance gates separate
- Security reviewer:inspect access, encryption, logging, subcontractors, incident duties, recovery and deletion evidence. The NCSC's supplier assurance questions provide a structured enquiry set, not a certification.
- Accessibility reviewer:test the key submission, correction, complaint and exit journeys against the buyer's requirements. W3C's WCAG 2.2 standard supplies testable criteria, but conformance needs evidence from the actual interface.
- Consumer and advertising reviewers:examine presentation, material qualifications and objective-claim substantiation.
- Stop:do not average a security, accessibility, privacy or consumer failure into a commercial score.
5. Prove recovery and exit
- Technical owner:export the agreed fields and event history, then restore the pre-test configuration.
- Records owner:verify retention rules, deletion procedure, suppression continuity and evidence ownership after termination.
- Commercial owner:confirm termination assistance, format, deadline, cost basis and surviving obligations in the executed terms.
- Stop:retain the current safe state if rollback fails or exit would strand records needed for complaints, suppression or audit.
Decision record
For every gate, write pass, fail, unknown or not applicable; cite evidence; name owner and reviewer; set an expiry date. The final verdict must state tests actually run and areas left untested.
Limit any proceed decision by category, territory, configuration, volume and review date. Reopen all material sources before publication and after a service or terms change. Qualified reviewers can approve a bounded trial, but cannot promise compliance, service quality or return.
Before you act
- Reconcile entity identity and record the applicable terms version.
- Obtain collection wording, timestamp, source, purpose and objection record for a sample.
- Map operational states and identify the exact chargeable event and credit route.
- Run synthetic tests for ineligible, duplicate and wrong-recipient cases.
- Export agreed fields and restore the pre-test configuration.
- Write pass, fail, unknown or not applicable for every gate.
Common questions
What should happen if a critical control fails?
One failed critical control stops the decision even if every convenience feature looks attractive. The checklist is an acceptance gate, not a vendor score, so a single failure blocks progress regardless of other strengths. Record the failure with evidence, owner, reviewer and expiry date.
How should a buyer test provenance and suppression?
Use synthetic or properly authorised fixtures to demonstrate recipient disclosure, an objection, a duplicate and a suppression update. Quarantine the route when provenance is absent, disclosure is misleading or suppression does not reach the intended destinations. Assess each intended channel and subscriber type separately under PECR.
What must be proven before relying on a supplier?
Prove recovery and exit: export the agreed fields and event history, then restore the pre-test configuration. Verify retention rules, deletion procedure, suppression continuity and evidence ownership after termination. Retain the current safe state if rollback fails or exit would strand records needed for complaints, suppression or audit.
