Who owns each decision inside a lead generation network team

Lead generation networks team roles should be assigned by decision and evidence, not copied from an organisation chart. A small England operator may combine functions; it must still show who executes a task and who holds the relevant accountability.

What to take away

Assign lead generation roles by decision and evidence rather than copying an organisation chart.
A service decision owner approves scope and release but cannot overrule a failed legal or technical gate.
Where one person holds several functions, require an independent check for conflicted approvals.
Revisit the role map when a source, recipient, purpose, platform or contract changes.

Selection method

Date: 5 September 2026.

Scope: functions follow the enquiry journey; supplier job titles, salary data, staffing ratios and claims that every organisation must appoint a particular title are excluded.

1. Service decision owner

This function approves scope, state map, release, rollback and restart after every specialist clearance. It owns the overall operating result but cannot overrule a failed legal or technical gate. The Government Service Standard page on reliable operations is aimed at public services; its call for human-overseen testing and proportionate response is a useful prompt, not a private staffing rule.

Evidence output: release log and rollback decision record.

2. Collection and quality operator

This person maintains source registrations, quarantine, validation rules, fixture results and exception queues. They may correct an evidenced technical defect, but cannot decide a new use of personal information. ICO lead collection guidance gives the function a provenance and transparency checklist without prescribing a job title.

Evidence output: quarantine record and validation exception log.

3. Data and privacy decision owner

This function documents purposes, necessary fields, roles, disclosures, retention and objection handling. Legal accountability follows facts and law rather than the label on a RACI chart. The ICO's controller and processor guidance is under review. For the role map, treat controller or processor labels as provisional and record the facts and decisions that support each allocation.

Evidence output: DPIA and retention schedule.

4. Recipient and commercial owner

The commercial function approves buyer eligibility, billable units, acceptance evidence, credits, disputes, change and exit. It cannot create privacy or PECR permission through contract language. This owner reconciles recipient records and escalates contradictions rather than silently choosing the commercially convenient version.

Evidence output: acceptance evidence and credit dispute log.

5. Security and incident owner

This function assesses access, logs, supplier evidence, containment, recovery and deletion. NCSC's supplier assurance questions identify governance, incidents, data and contractual subjects for buyer review. They do not make a named security title mandatory or certify a provider.

Evidence output: incident log and supplier assurance record.

6. Accessibility owner

The accessibility function sets test scope across collection, correction, objection and complaint routes, records defects and controls retest. The W3C WCAG 2.2 Recommendation provides criteria, not proof that the configured service conforms.

The Equality Act 2010 and the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 are named UK reference points, but a private operator's own duties still need qualified review.

Evidence output: accessibility defect register and retest record.

7. Complaint and communications owner

This person receives complaints without making the individual diagnose the parties, preserves evidence and coordinates a plain response. The ICO's complaint-handling guidance describes acknowledgement and investigation expectations. Any public quality or availability statement also needs separate advertising review against CAP's substantiation guidance.

Evidence output: complaint log and acknowledgement record.

Worked example: a two-person England operator combines the service decision owner and commercial owner in one person. The second person runs collection and quality and acts as privacy decision owner.

When the combined owner wants to approve a buyer that asks for a new lead purpose, the second person performs an independent check and records a DPIA. The release log stays empty until that check is signed off.

Before you act

Name a primary and deputy for every function.
Record each decision boundary and evidence output.
Set a review interval and emergency authority.
Require independent checks for conflicted approvals.
Revisit the role map when sources or contracts change.

Common questions

How should a small operator assign lead generation roles?

Assign each role by decision and evidence, not by an organisation chart. A two-person operator can combine functions, but it must name who executes each task and who holds accountability. The Before you act checklist covers the fields to record.

What can the commercial owner not do through contract language?

The commercial owner handles buyer eligibility, billable units, credits, disputes and exit. Contract wording cannot create privacy or PECR permission. Contradictions go to the relevant decision owner rather than the commercially convenient version.

When should the role map be revisited?

Revisit it when a source, recipient, purpose, platform or contract changes. A combined role still needs an independent check for a conflicted approval. The map records decisions and evidence, not a ranking of job titles.