Operations
Part of What event marketing operations means for agency delivery teams
How to split event marketing team roles when the work spans data and sources
How to divide event marketing team roles when data, sources and compliance sit across several people, plus a scoring rubric and ownership questions.
What to take away
- Split event marketing team roles by decision, not by job title, so every source has one named owner.
- Keep data requests, legal duties and creative judgement in separate hands where the campaign allows it.
- Use a short scoring rubric to test each proposed role before you advertise it internally.
- Record who owns each source and when it was collected, so a later review can trace the claim.
Criteria for mapping roles
This list assumes a UK agency or in-house events team running campaigns for English clients. It covers roles that touch data, sources, legal duties and reporting, not venue logistics or stand build. Apply your own headcount and client contracts as the filter, and treat the order below as a sequence.
The wider operating model sits in the event marketing: operations and delivery guide, which covers how delivery, quality and ownership are divided before roles are advertised.
How to split the work into roles
Split by decision, not by job title. Write down every decision the campaign needs someone to make, then give each decision one owner.
- List the decisions.For a campaign built on attendee data and external sources: what we collect and on what lawful basis; which numbers we may use; how an attendee request is answered; how crew fatigue is handled during build week; and who holds platform access and certification.
- Find the collisions.Two decisions collide when they pull against each other — approving a new form field and deciding a deletion request is the clearest case. Colliding decisions sit with different people.
- Give each decision one owner and one deputy.The owner decides; the deputy steps in during leave. A decision with two owners is a decision nobody makes.
- Write the handover.One page per role: the decisions it owns, the systems it can access, and the route it escalates on when the client and the agency disagree.
- Test it before you advertise it.Score the role against the rubric below; anything that fails the ownership or authority test goes back to the previous step.
Where headcount is tight, merge roles that do not collide. Data and source ownership can sit with one person; the attendee rights decision should not sit with whoever approves new collection.
Role 1: campaign data lead
One person owns the register of attendee data: what was collected, on what lawful basis under the UK GDPR and the Data Protection Act 2018, and where it is held. They approve new fields before a form goes live, and they check that any email or tracking pixel added to the campaign also meets PECR.
Give this role the authority to refuse a data request, or the register becomes a document nobody updates. For example, a team collecting 4,000 badge scans across a two-day show needs one person deciding which fields are retained.
Role 2: source and citation owner
This role keeps the evidence trail for every external number used in a pitch or report: dates, publishers, exact page.
Where a claim rests on a survey, the owner checks the sample and the question wording first. If the trail is weak, the claim is dropped rather than softened.
Role 3: attendee rights handler
Attendee requests to see or delete their data need a named handler and a logged process. The ICO's guidance on subject access requests from event attendees sets the one-month response window and the identity checks that apply. The handler should work from that page rather than memory.
Keep this separate from the campaign data lead where headcount allows. One person approving new data collection should not also decide on deletion requests.
Role 4: staff wellbeing contact
Event delivery runs on long days and tight turnarounds. The HSE's guidance on stress and mental health at work for agency staff sets out employer duties. This role turns those duties into rota limits, handover rules and an escalation route during build week.
Name the contact in the delivery plan, so crew know who to raise a problem with.
Role 5: skills and platform owner
This person owns the team's platform accounts and keeps certifications current. On the registration side that means knowing who holds admin rights on Eventbrite or Cvent; on the marketing side, who can send from the CRM, such as HubSpot or Salesforce. For paid social delivery, LinkedIn's advertising certifications are one recognised route, and the role owner tracks who holds which certificate and when it lapses.
Pair it with a written handover, so a campaign does not stall when the holder is on leave.
Scoring rubric for each role
Score every proposed role from 1 to 5 against each test below. A role scoring below 3 on ownership or authority needs redesign before it is filled: write the description around the decisions the role owns, the authority it carries, its named deputy and the route it escalates on.
| Test | Question to ask | Score 1 to 5 |
|---|
Role scoring rubric
- Ownershipone person, not a team
- Authoritycan refuse or stop work
- Traceabilityoutsider follows decision trail
- Covernamed deputy for leave
- Review pointdate to revisit role
The tests to score against:
- Ownershipdoes one named person make the decision, not just do the task?
- Authoritycan that person refuse a request or stop a release without asking permission?
- Separationdoes the role avoid approving both the collection and the deletion of the same data?
- Coveris a deputy named who can take the same decisions during leave?
- Evidenceis every decision logged, so a later review can trace the claim?
- Capacitydoes the owner have the time in the campaign schedule to do it?
How the roles connect
The five roles form a chain: data lead, source owner, rights handler, wellbeing contact, skills owner. Break the chain and the gap shows up as a missed request or an unverifiable number.
Worked through on the two-day show above: the 4,000 badge scans still need one named approver for the fields retained, a separate person answering deletion requests, and, where the team has the headcount, a third holding the source trail. With no third, the data lead takes the source trail and the rights handler stays independent of them. The wellbeing contact and the platform owner are the two roles most often left unnamed until build week, when they are hardest to fill.
Five-role chain
- Campaign data lead
- Source and citation owner
- Attendee rights handler
- Staff wellbeing contact
- Skills and platform owner
Before you publish role descriptions, check whether the launch itself needs a compliance view. The event marketing launch review in England sets out what that check covers and who signs off the campaign before it goes live.
Common questions
Who owns attendee data in an agency campaign?
The client usually holds the controller duty and the agency acts on instruction, but the contract decides this. Name the person who answers requests either way, so attendees are not passed between two organisations.
Can one person cover data and source ownership?
Yes in small teams, provided the same person does not also handle deletion requests. If they do, add a second reviewer for rights cases.
How often should the rubric be rescored?
At each campaign review point and whenever a role changes hands. A score that has not moved in a year usually means the tests are answered from memory rather than evidence.
