When to set event marketing service standards for English agencies

What to take away

Event marketing service standards are the written rules that say who does what, by when, and to what quality, when an agency delivers a campaign or an activation. Set the first written set before you sign the client contract or open the first build day, then review it at least once a year and after any incident. They matter more in England now because two regulators have made their expectations plainer. The ICO publishes training on electronic marketing consent, and the HSE keeps its incident reporting guidance current.

When to set the standards

Set the first written set before you sign the client contract or open the first build day, whichever comes first. That version covers consent, retention, incident escalation, ticketing and a named owner for each rule. No rule goes live while it exists only in someone's memory.

Then review on a fixed rhythm: at least once a year, and again straight after any incident or any campaign where something went wrong. Between reviews, no rule changes without a date and a name beside the change, so nobody works from a version they only half remember.

New starters, freelancers and suppliers receive the current version before their first day on site, and the owner named beside the rule signs the post-event report where the gaps surface.

Why standards drifted

Agencies often grow faster than their paperwork. A founder handles consent personally, then hands it to a junior with no written rule. Freelancers join for one campaign and guess the process, and the client sees inconsistent work.

Standards fix that drift. They also protect the agency when a campaign goes wrong, because the process shows what was checked and when. If you are rebuilding delivery from the ground up, the event marketing operations and delivery guide for 2027 sets out the wider operating model this article sits inside.

The rules that shape English delivery

Consent is the first standard to write down. Under the Privacy and Electronic Communications Regulations, marketing by email or text to individuals normally needs prior consent, and the ICO's training videos on PECR explain the exceptions and the records to keep. Put the retention period in the standard, not in someone's memory.

Incident reporting is the second: if an injury, disease or dangerous occurrence meets the reporting threshold, the responsible person must report it. The HSE's RIDDOR reporting guidance names the categories — deaths, specified injuries, injuries that keep a worker off for more than seven days, dangerous occurrences and reportable occupational diseases — and the deadlines that go with them. Deaths, specified injuries and dangerous occurrences are reported without delay, and an over-seven-day injury within 15 days of the accident.

A service standard should state who calls, who logs and who tells the client. Set the internal deadline earlier than the regulatory one, so the report is filed with time to spare.

Retention is easy to promise and hard to run. Say how long each list stays live and what evidence remains after deletion. A template line helps, for example records kept for 12 months and then reviewed by the owner.

Ticketing is the third. Most agencies run registration through a platform, and knowing the back office matters when something breaks on site. Eventbrite's help centre guides on check-in and refunds show the operational view an agency needs, and the written standard should say who can change a registration, who issues a refund and how the client is told.

The three standards, written out

Response time, consent handling and incident escalation come up in most client conversations, so write those three first, in a form a new starter could follow.

Response time

Name the channel, the owner and the target in working hours, then say who a missed target escalates to. A target nobody can measure is not a standard, so express the clock in hours rather than 'as soon as possible'.

Consent handling

For every contact, record the consent itself, the date, the source and what the person was told. Name who checks email and text marketing against PECR before a list is used, who actions opt-outs, and where the opt-out record sits beside the consent log.

Incident escalation

Set the order of calls: the person on site to the duty manager, the duty manager to the nominated reporter, and the client inside the same window. Name who speaks to HSE when an incident is reportable and who writes the record, and test the chain before every build day.

Who owns each standard

The owner is named beside the rule, not the team that drafted it. If that person leaves, the standard passes to a named successor before the handover closes.

Freelancers and suppliers should receive the relevant page with their contract, so nobody learns the process on site. Owners also sign the post-event report, where gaps surface.

Before and after

The before and after view is the test of any standard: clear before the campaign starts, evidenced once it ends.

How to write the standard

Keep it to one page per service. Name the owner, the action, the deadline and the evidence. A team paying £400 a month for a freelance coordinator still needs to know that the account director owns consent sign-off.

Test each standard against a real campaign. If a rule cannot be followed on a wet Tuesday in March, it is too vague. Rewrite it until a new starter could follow it without asking.

Review the standard after every launch, because gaps only appear once the doors open. The event marketing launch review in England explains how to run that review so findings feed back into the written rules.

Common questions

These are the questions delivery teams ask most often when they first write their standards.

Do small agencies need written service standards?

Yes. Size changes who owns each standard, not whether one exists. A two-person agency can still name a consent owner and an incident reporter, and clients increasingly ask to see the process before signing.

How often should standards be reviewed?

At least once a year, and after any campaign where something went wrong. Regulator guidance, suppliers and staff all change, so an annual review keeps the document honest.

What evidence should we keep?

Keep consent logs, incident records, supplier checklists and post-event reports. Store them together so a client question or a regulator query can be answered from one place rather than three inboxes.