Media agency service standards that define classes before response times

Good media buying agencies service standards describe an observable result, its owner and what happens after failure. They should not promise constant availability or instant replies unless the agency has accepted that obligation in the contract. For a buyer in England, the schedule also needs working hours, time zone and any wider UK coverage stated plainly.

What to take away

Define service classes before response times

A reporting question, a broken tracking event and uncontrolled overspend do not deserve the same queue. Define classes such as routine request, material delivery issue and release-stopping incident. For each class, state the contact route, acknowledgement point, decision owner and update method. The parties can then negotiate times that match staffing and risk instead of copying an arbitrary target.

Avoid a single phrase such as "respond promptly". It cannot be measured. Likewise, an acknowledgement is not a resolution. The agency may confirm receipt while investigation continues, but the next update and responsible person should be clear.

Indicative service classes for an England-based media account:

These times are a starting point, not a fixed benchmark. The contract should adjust them for staffing, spend and risk. Core hours are 09:00 to 17:30 UK local time, Monday to Friday, excluding England and Wales bank holidays.

Use Europe/London, noting GMT in winter and BST in summer. Out of hours cover applies only to a release-stopping incident unless the contract says otherwise.

Sample clause for a release-stopping incident:

This is a template, not a promise. The parties must agree names, times and remedies in the contract.

Set standards around campaign decisions

The operating schedule should cover:

Each item needs acceptance evidence. That may be an approved brief version, platform export, issue record or sign-off. A meeting held on time proves only that the meeting occurred.

Make access and data duties testable

Specify account ownership, user access, removal of leavers, export formats and retention expectations. Give privacy duties their own decision path.

The UK Information Commissioner's Office online advertising guidance covers consent for storage and access technologies in ad delivery, tracking and profiling, and user information and control. Contract wording cannot make a technical setup compliant, so the campaign needs qualified review.

The agency should report a suspected data or access problem through the agreed incident route, naming who preserves records, who can suspend activity and who contacts the client's reviewer.

Cover content corrections without blurring responsibility

For influencer activity, the UK ASA and CAP guidance hub points brands, agencies and creators to material on disclosure and social advertising. A service standard can require documented review and rapid correction, but the appropriate current rule still depends on the execution.

If work includes reviews or endorsements, the UK Competition and Markets Authority collection identifies responsibilities for businesses, media agencies, creators and publishers. The contract should allocate evidence and approval tasks, and it should not imply that outsourcing removes the client's responsibilities.

Current wording sits on each regulator's website, so check the ICO guidance pages, the ASA advice online resource library and the CMA collection page before relying on it.

Review failure patterns, not only totals

Monthly reporting can show requests by class, missed acknowledgements, late resolutions, reopened issues and corrections. Raw totals need context because a busy launch and a dormant account differ. Examine repeated causes and whether an agreed remedy worked.

The useful remedy is tied to the failure. It might require a corrected report, restored access, another build check or a revised escalation path. Financial remedies and liability belong in reviewed contract terms, not an informal operations note. Revisit the standards when scope, channels, staffing or risk changes, and keep the old version with the approval record.

At each review, retire measures that nobody can evidence or act upon. Add a new obligation only when it can be evidenced and acted upon. That keeps the schedule usable during a real incident.

Before you act

Common questions

Why should service classes be defined before response times?

Because a reporting question, a broken tracking event and uncontrolled overspend do not deserve the same queue. Defining classes such as routine request, material delivery issue and release-stopping incident lets parties negotiate times that match staffing and risk instead of copying an arbitrary target.

What should a service standard cover for access and data duties?

It should specify account ownership, user access, removal of leavers, export formats and retention expectations. Privacy responsibilities need their own decision path. The standard should say who preserves records, who can suspend activity and who contacts the client's reviewer.

How should failure patterns be reviewed?

Monthly reporting can show requests by class, missed acknowledgements, late resolutions, reopened issues and corrections. Raw totals need context because a busy launch and a dormant account differ. Examine repeated causes and whether an agreed remedy worked, then tie the remedy to the failure.