Operations
Part of Before you promise a content delivery date, fix your agency operations
How to map content agencies team roles to data and sources
A practical guide to assigning research, source checks and sign-off across content agency team roles, with a checklist for UK content delivery teams.
What to take away
Mapping content agencies team roles to data and sources means naming, in writing, who finds each number, who checks it and who signs it off. Most disputes about agency research are ownership disputes, not evidence disputes.
- Agree your inclusion criteria firstwhich roles count, which source types count and which geography applies. This article covers UK roles and UK-regulated sources, with Scotland, Wales and Northern Ireland noted where rules differ.
- Give every recurring data point a named owner, a named checker and a named approver.
- Keep a source register so a claim traces back to a URL, a publisher and a date.
- Separate finding sources from approving them, because one person doing both hides errors.
Set your inclusion criteria before you map roles
A role map is only useful if you agree what goes in it. For a UK agency, count permanent staff, regular freelancers and any production partner whose work reaches a client deliverable.
Inclusion Criteria: Include vs Exclude
Include
- Roles
- Permanent staff
- Freelancers
- Regular freelancers
- Partners
- Production partners
- Sources
- Government data
- Guidance
- Regulator guidance
- Filings
- Company filings
- Platform docs
- Platform documentation
Exclude
- Roles
- Unattributed blog claims
- Freelancers
- Screenshots with no URL
- Partners
- No client deliverable
- Sources
- Unattributed claims
- Guidance
- No URL screenshots
- Filings
- Unattributed blog claims
- Platform docs
- Screenshots with no URL
For sources, count published government data, regulator guidance, company filings and platform documentation. Exclude unattributed blog claims and screenshots with no URL.
Competition and consumer protection rules apply across the UK. Some data protection and marketing rules are applied differently in Scotland, Wales and Northern Ireland, so record the jurisdiction each claim targets.
The five roles most agencies need
- Research leadfinds candidate sources and records the URL, publisher and publication date.
- Data stewardchecks each number against the source and flags anything stale. This should not be the person who found it.
- Editorial ownerdecides whether the claim is relevant to the client's audience and whether it belongs in the draft.
- Compliance reviewersigns off claims that touch competition or consumer protection. The Competition and Markets Authority enforces those rules across the UK, which is why this gate exists.
- Client account leadconfirms the client approved the claim and the wording before publication.
If you are rebuilding the wider workflow, the operations and delivery guide sets out the stages these roles sit inside.
Which source types each role may sign off
Not every role needs authority over every source. Let the research lead propose freely, but keep approval narrow.
Government statistics and regulator guidance need the data steward plus the compliance reviewer. Platform documentation can usually be approved by the editorial owner. A named client figure needs the account lead.
Email campaigns need particular care. The ICO's guidance on direct marketing using electronic mail explains consent and soft opt-in rules for content sent by email rather than published on a site.
Where a claim covers staff credentials, ask for the certificate itself. The CIM's Foundation Certificate in Professional and Digital Marketing is one entry-level qualification a team might cite, and the wording should match what is claimed.
Keep a source register that survives staff changes
A register is a simple table: claim, source URL, publisher, publication date, owner, checker, approval date. Store it beside the content calendar, not in a personal drive.
Review it quarterly, because sources move, guidance is updated and figures are revised. A register nobody revisits quietly becomes a liability.
When a client asks how a number was reached, the register should answer in under a minute.
Checklist for assigning roles to sources
- Inclusion criteria written down, covering roles, source types and UK geography.
- Every recurring figure has an owner, a checker and an approver.
- Finder and checker are different people.
- Source register holds URL, publisher, date and approval.
- Regulator guidance reviewed before any claim about performance or standards.
- Email distribution checked against ICO rules.
- Credentials verified from the certificate, not from memory.
- Register reviewed quarterly and after any rebrand or site migration.
If your agency is also revisiting its market positioning, the launch review in England covers how teams audit what they publish before a new service goes live.
Common questions
Who owns a data point if two roles disagree?
The approver named in the source register decides. If none is named, the editorial owner holds the decision until the register is updated.
Do freelancers follow the same source rules?
Yes, if their work reaches a client deliverable. Give them the register template and the inclusion criteria on day one.
How often should the source register be reviewed?
Quarterly is a workable baseline, plus an extra pass after any regulatory update or major site change.
Does this differ across the UK?
Competition and consumer protection apply UK-wide. Some marketing and data rules differ in Scotland, Wales and Northern Ireland, so record the jurisdiction for each claim.
