Operations
Part of Operating a lead network as explicit states with visible failure queues
How to review a lead network launch with synthetic fixtures and no-go tests
A guide to reviewing a lead generation network launch: synthetic fixtures, six no-go tests, incident evidence, suppression checks and rollback clearance.
What to take away
- A launch is a hold until the operator can produce dated, recorded results for every no-go test; the verdict is a documentary status, not a design opinion.
- The no-go set covers a valid request, a duplicate, a stale item, an out-of-scope location, a missing provenance field and a sensitive field.
- Synthetic fixtures are the default, and quarantine must catch a record with no source before it reaches a buyer.
- Each gate needs a named owner; who owns each decision inside a lead generation network team maps the sign-off.
The verdict rule and the evidence that flips it
A launch review returns hold when no dated test result can be produced, however polished the design looks. Proceed needs five records on file: the test plan, the fixture log, the trace with rule versions and timestamps, the failed-gate register with clearances, and the exit reconciliation.
Proceed is a documentary status. If the trace, the owner and the clearance cannot be produced on request, the verdict stays hold.
A review that names no network, no reviewer and no test access cannot conclude proceed; ask for the product record, the test dates and the raw results before you rely on it.
Speed, quality or volume claims need substantiation; the CAP Code treats unproven objective claims as misleading.
The six no-go tests and the evidence each must produce
Run each row against a marked fixture and record the outcome, rule version and owner.
The six no-go tests
| Test | Fixture | Pass evidence | Fail symptom |
|---|---|---|---|
| Valid request | Complete synthetic lead | Trace of collection, matching and disclosure, with timestamps | No trace or no rule version |
| Duplicate | Same lead twice | One billable unit, second flagged | Two buyer disclosures |
| Stale item | Lead past the claim window | Block or credit under the window | Buyer charged after expiry |
| Out-of-scope | Postcode outside the area | Quarantine event logged | Silent match to another buyer |
| Missing provenance | No source record | Quarantine, no match | Entry into the matching pool |
| Sensitive field | Health note in free text | Field flagged, route blocked, owner alerted | Detail passed on unchanged |
The billable unit in each row must match the definition held in the five contract records that define a lead, its data and its exit, or the test proves nothing.
Fixtures: synthetic by default
Synthetic records are marked so they cannot be mistaken for genuine requests. Where a narrow test needs personal information, record the authority, necessity, fields, access, retention and deletion first. Do not copy production leads for realism.
The ICO's lead collection guidance supports checking source, transparency and buyer-side evidence. Add one fixture with no provenance and confirm it enters quarantine instead of matching.
Example of a gate failing on evidence
A synthetic request falls outside the buyer's claim window and is routed to that buyer. The system must block the transfer, keep the attempted event and alert the named owner. A manual send that bypasses the block is a no-go.
Exercise an access or integrity incident and capture detection, containment, affected records, decisions, notifications considered, recovery evidence and restart authority. The NCSC's incident-management guidance treats plans, people and technical capability as connected; a clean exercise still cannot promise future security.
Objection, suppression and the service record
Submit a marketing objection and check every route that reads the record. ICO right-to-object guidance explains why targeted marketing stops while limited suppression data may remain. Confirm that suppression does not erase an unrelated service request, and that finishing the service does not start a promotional sequence.
Buyer-facing networks name the unit they sell before they sell it. The comparison of Bark, Checkatrade and MyBuilder is a reference point when your own network states its lead definition and claim window.
Rollback and restart sequence
- Disable the affected collection or disclosure route.
- Preserve evidence and contain pending records.
- Notify the responsible parties named in the plan.
- Obtain written clearance from the owner of each failed gate.
- Reconcile the population on restart and confirm exports are readable.
Operations may coordinate restart only after every clearance is recorded. An unreadable export or an unresolved live queue is a no-go for exit readiness.
Pre-launch checklist
- Named reviewer and authorised fixtures in place.
- Synthetic records marked as not genuine.
- No-go tests run for duplicates, stale items and sensitive fields.
- Suppression checked against unrelated service requests.
- Export reconciled and deletion verified.
Common questions
Does a completed checklist approve a launch?
No. A tick records that a step was attempted, not that the system passed. Only the trace, the fixture log and the clearance record support a proceed verdict.
What changes the verdict from hold to proceed?
Dated results for every no-go test, a named owner per gate, recorded clearances and a readable exit reconciliation. Missing one of those keeps the launch on hold.
What must rollback preserve before restart?
Evidence of the failed event, the pending records it touched, the decisions taken and the clearance from each specialist owner. Restart follows written clearances, not a verbal all-clear.
Which rules apply to lead collection and objection?
ICO guidance covers lead collection and the right to object, UK GDPR supplies the lawful basis, and the CAP Code requires substantiation for objective claims.
