Who is accountable for what in creator discovery, without inventing job titles

Begin by asking which decision must be owned when a creator record or campaign step is uncertain. A workable allocation makes weak hand-offs visible without pretending every organisation needs the same structure. The accountabilities below may be combined only where capacity and conflicts permit; they do not prescribe job titles.

The map describes a workflow, not a staffing plan

Weak version. Read the accountabilities as a universal organisation chart, a ranking of roles, or proof that a particular workplace has been assessed. That turns a decision-allocation method into a hiring prescription and suggests that team structures or employment arrangements have been examined when they have not.

Better version. Keep the map within its evidence limits: it concerns one English buyer workflow for creator discovery and campaign governance, with UK-wide or England-specific limits. The evidence is dated 6 September 2026. Inclusion required a distinct decision supported by current official guidance; sales, generic management and mandatory job titles were left out.

Keep technical controls attached to named decisions

Weak version. Let security and accessibility sit between teams, or assume a platform login is enough to control access. With no named owner, nobody may be clearly responsible for permissions, logs, incidents, recovery, usable tasks or retesting after a service change.

Better version. Separate security ownership from accessibility review where that helps. Security covers least privilege, logs, incidents and recovery; accessibility review checks usable tasks and retesting. SaaS security guidance supports monitoring and managing configuration changes. Test the actual service, and make delivery hand-offs explicit.

Make the creator record traceable before it travels

Weak version. Accept a creator record because its fields look complete, even when the field meanings, sources or conflicting claims cannot be checked. A tidy entry can then be mistaken for proof of authenticity or suitability, although the person maintaining it has not certified either.

Better version. Assign an evidence custodian to maintain definitions, provenance, claim labels, timestamps, conflicts, corrections and evidence expiry. The custodian blocks records when source or status cannot be traced, without certifying authenticity or suitability. Apply record quality checks, and keep record admission separate from contact permission.

Separate rights clearance from campaign approval

Weak version. Treat visible material as cleared for every planned use, or accept a creator representation as proof of authority. This skips separate checks on source access, database rights, content rights and the scope of permission, then leaves campaign approval carrying an unresolved rights question.

Better version. Give a rights reviewer responsibility for source access, database and content rights, representation, and permission for each intended use. Copyright guidance can frame ownership questions but does not clear an asset. Keep unresolved creator authority with this reviewer rather than passing it to the campaign approver.

Approve the final material, not the platform response

Weak version. Assume that platform acceptance means an asset is ready to publish. That shortcut can leave incentive records, claim evidence, advertising recognition, disclosure accessibility and correction arrangements unchecked, even though those decisions concern the actual campaign material.

Better version. Make the campaign approver accountable for incentive records, claim proof, advertising recognition, accessible disclosure, final assets and correction plans. Platform acceptance remains a separate decision. Use the disclosure policy to distinguish editorial status, incentives and AI labelling from platform decisions.

Require a contact decision before outreach

Weak version. Treat access to discovery information as automatic permission to contact a creator, or ask a general reviewer to approve outreach without checking its purpose and route. This merges discovery and communication decisions, leaving the reason for a permitted contact unclear.

Better version. Assign a qualified reviewer to assess purpose, lawful basis, roles, transparency, individual rights, retention, subprocessors, transfers and contact routes. Apply UK compliance guidance to the workflow. ICO accountability and governance guidance can inform the privacy review; discovery access and outreach remain distinct decisions.

Route possible under-18 involvement away from routine approval

Weak version. Ask a campaign approver to infer a creator age from an incomplete profile, or absorb an unresolved safeguarding question into ordinary campaign approval. Guessing turns uncertain profile information into an unreliable answer and avoids the decision that the uncertainty requires.

Better version. Give a safeguarding decision owner responsibility for possible under-18 involvement. They do not guess age; they route actual facts to licensing or other responsible bodies. Department for Education guidance on child performance applies in England, but does not settle what an individual profile means. Keep licensing decisions with the relevant responsible bodies.

State the purchase purpose and the measure of completion

Weak version. Assume a platform purchase transfers responsibility for the problem, permitted purpose and final decision to a supplier. Without a baseline, the team also lacks a comparison point for judging whether the tool or surrounding workflow helped; platform activity can be confused with campaign outcomes or causal claims.

Better version. Name a buyer accountable for the problem, permitted purpose, manual baseline and final-state decision before procurement. Start with a buyer decision first, then compare against workflow costs. Give a records and measurement owner responsibility for service measures, evidence reconciliation, export and verified closure.

Make exceptions stop at a decision owner

Weak version. Let challenges circulate informally, or restart work when an issue is merely acknowledged. Without a clear route, it is uncertain who must act, which approval is affected and whether the evidence behind a decision has changed.

Better version. Name an exception owner before live work. Route each issue to the decision lane able to resolve it, and restart only after correction and fresh approval from affected lanes. The signals below keep evidence, authority, safeguarding and security decisions distinct.

Keep accountability separate from employment classification

Weak version. Use this allocation to declare someone an employee, determine tax status or set the right team size. It provides no staffing ratio and does not assess an individual working arrangement, so none of those conclusions follows from the map.

Better version. Employment status depends on contracts, agreements and working reality; tax status is a separate question. Named employment and tax advisers must review the facts. Capacity, separation of duties and cover during absence remain buyer decisions supported by workload evidence. This map assigns decisions, but does not determine worker classification.