What governance decides
Process says how work moves; governance says who has the right to decide at each point and what must be true before a decision is taken. The questions are concrete. Who may approve a price claim or a comparison with a competitor? Who may commit spend above the campaign budget? Who may publish to the main brand account, change the tag container (GTMTag management system.) or export a contact list? Who decides whether a new market follows the central brand guidelines or adapts them? And what record of each of those decisions must be kept?
When these questions have no written answer, they are answered by whoever is in the room, and the answers change with the people. That produces two opposite failures. In some teams, nothing goes out until the most senior person has seen it, and the queue in front of that person becomes the main constraint on the whole marketing operation. In others, anyone can publish anything, and the first sign of a governance gap is a complaint, a regulator's letter or a public correction. Written decision rights fix both: they let low-risk work move without senior sign-off and make sure high-risk work cannot avoid it.
Governance is also how a team shows its working. Data protection law, including the GDPR, expects organisations to be able to demonstrate compliance, not just to comply, and the UK regulator's direct marketing guidance sets out what marketers are expected to have in place. That is general direction, not legal advice; the practical point is that evidence has to be designed in, not reconstructed later.
Decision rights, compliance, access, model
Governance has four components. Each answers a different question and each has its own typical failure.
| Component | Question it answers | What it looks like when it works | Typical failure |
|---|---|---|---|
| Decision rights and approvals | Who may approve, spend or publish what? | An approval matrix by risk, applied the same way every time | Approval by seniority; everything reviewed by everyone |
| Compliance reviews | Does the work meet brand, legal, data and accessibility standards? | Reviews triggered by the content of the work, against written standards | Reviews from memory; legal sees work after it is built |
| Access and audit trails | Who can change each system, and can decisions be shown later? | Role-based access, reviewed regularly; decisions recorded on the work item | Former staff and agencies keep admin access; approvals live in email |
| Operating model | Where are standards set and where is work done? | A written split between the central function and the teams it serves | Every team invents its own rules, or the centre controls every post |
The first three are covered by the approvals guide, with further guides below on claims, approval audits, changes after approval and change freezesA set period around a peak when changes that are hard to reverse are stopped while routine, reversible work continues through an agreed route.. The fourth, the operating model, decides how the first three are distributed across a larger organisation, and has its own comparison.
The core guides
- Marketing approvals and compliance reviews builds an approval matrix by risk, then walks through brand review, legal and claims review, consent and data checks, accessibility, and the audit trails and periodic audits that make governance demonstrable.
- Centralised vs decentralised marketing operations compares the two operating models on consistency, speed, standards, tooling, data, local relevance and cost, and explains the hub-and-spoke arrangement most organisations end up with.
Several kinds of governance live in their own roots because they are technical or specialised. The automation governance guide covers automated journeys and workflows. The tag container governance guide covers who may change tracking. The content governance guide covers editorial standards and lifecycle. The approvals guide links to each where the boundary falls. For how governance sits alongside process and systems, start from the marketing operations hub.
Further guides
Further guides set out the operations function's own remit, put pre-approval and audit into practice, settle what happens when approved work changes, protect the busiest periods from risky changes and show how to bring in outside help without handing over the decisions:
- Writing a marketing operations charter — a tutorial for its purpose, what operations owns and does not, its customers and services, decision rights, measures and review.
- Building a claims library and substantiation file — a tutorial for collecting the claims already live, recording wording and evidence, approving each entry, linking it to intake and rechecking it.
- Auditing marketing approvals — a tutorial for sampling live work, checking each item had the reviews the matrix required on the version that went live, and fixing the causes.
- Handling changes to marketing work after approval — a guide to what counts as a change, which review each change reopens, how small fixes are confirmed, who decides, late changes and the record of each version.
- Planning a change freeze around peak periods — a tutorial for what a freeze covers, the dates, what stays allowed, the exceptions route and lifting it in order.
- Hiring and evaluating a marketing operations consultant — a guide to what stays with the business when an outside provider designs or runs the operating layer: the decisions and records it keeps, diagnosis, build and run scopes, questions and warning signs, acceptance tests and the handover at the end.
Governance that does not slow the team
The fear about governance is that it adds delay. Badly designed governance does, and the remedy is not to remove it but to make it proportionate. Four principles keep it light.
Match review to risk. Most marketing work carries little risk: a social post using approved assets, a routine email from an approved template. It should need no review beyond the launch check. Review effort belongs on new claims, offers, regulated products, new audiences and large spend. The approval matrix encodes this so that nobody has to argue it case by case.
Build checks into the route. A consent check that happens because the intake form asks about the data source is faster and more reliable than one that depends on a reviewer remembering. The same applies to naming and UTMURL tags identifying traffic source. parameters, accessibility checks in templates and claims flagged at intake.
Pre-approve what you can. Approved claim libraries, approved templates and approved asset sets let teams move quickly inside agreed boundaries. Review then focuses on what is new. The claims library tutorial builds the first of these: each claim in its approved wording, with its evidence, who approved it and a date to recheck it.
Measure the gates. Track how long each review takes and how often it returns work. A review that never returns anything is either unnecessary or not looking. Report these alongside the team's other operational measures rather than treating them as a KPIA metric tied directly to an objective. for reviewers.
A retail bank's marketing team rebalances review
The marketing team at Harbourside Bank, a regional retail bank, sent every item to compliance review, including social posts with no product content. Compliance had a queue of around 140 items and a turnaround of eight working days. The team introduced an approval matrix with three risk tiers: no product or rate content, approved product content reused unchanged, and new product claims or rates. Only the third tier went to compliance; the second used a library of pre-approved statements. Within a quarter, compliance volume fell to about 35 items a month, turnaround fell to three days, and the compliance team reported spending more time on the items that carried real risk.
Common governance problems
| Symptom | Usual cause | Guide |
|---|---|---|
| Everything waits for the same senior reviewer | Approval by seniority rather than by risk | Approvals and compliance |
| Legal or compliance rejects finished work | Claims and offers not flagged at intake | Approvals and compliance, Building a claims library |
| Nobody can show who approved a live ad | Approvals given in email or chat, not recorded | Approvals and compliance, Auditing marketing approvals |
| What went live differs from what was approved | Edits made after sign-off without going back to the review they affect | Handling changes after approval, Auditing marketing approvals |
| Former agencies still have admin access | No periodic access review | Approvals and compliance |
| Regional teams use different rules and tools | No written operating model | Centralised vs decentralised, Writing an operations charter |
| The central team is a bottleneck for local work | Execution centralised along with standards | Centralised vs decentralised |
| An automated journey sent the wrong message | Automation changes outside governance | Automation governance |
| Tracking broke after an untested tag change | No change control on the tag container | Tag container governance |
| Something breaks during the busiest trading period | Risky changes made just before or during the peak; no freeze and no exceptions route | Planning a change freeze |
| An outside provider built our procedures or approvals and nobody inside can change them | Documents, decisions or access held by the provider rather than the business | Hiring and evaluating a marketing operations consultant |
