Outlook
Part of Why rising automation and ASA enforcement reshape PPC agency buying decisions
How to map PPC agencies risk scenarios using named data sources
How to pair PPC agencies risk scenarios with named data sources and observable update triggers, so each review happens before budgets are committed.
What to take away
- Use five columnsscenario, source, trigger, owner and score band.
- Name a specific page or dataset for every scenario before you score it.
- Give each scenario an observable trigger that forces a review.
- Keep six to ten live entries, each with one named owner.
- Retire scenarios that never fire at the annual review.
How to structure each row
Start with four columns, then add a score band. The owner is a named person, not a team. The source is a specific page or dataset rather than a publisher label.
| Column | What goes in it | It fails when |
|---|---|---|
| Scenario | One sentence, no acronyms | It names a category, not an event |
| Source | A specific page or dataset | It names a publisher |
| Trigger | Something you can observe | It says "review regularly" |
| Owner | One named person | It names a team |
| Score band | Low, medium or high, with a written definition | The band is left undefined |
The trigger column is where most registers fail. A trigger must be something you can watch happen, such as a client cutting the retainer by a set percentage or a platform changing its targeting options.
The PPC agency audit checklist shows how to test whether a named source holds up across a whole account.
If a scenario cannot be tied to a named source and an observable trigger, move it to a watch list.
Risk register columns
- Scenarioone sentence, no acronyms
- Sourcespecific page or dataset
- Triggerobservable event
- Ownernamed person, not team
Example: one completed row
Scenario: a platform removes a targeting option the account relies on. Source: LinkedIn audience targeting guidance. Trigger: the option list on that page changes. Owner: paid search lead. Score band: medium likelihood, high impact.
Field / Worked entry
- Scenario
- A platform removes a targeting option the account relies on
- Source
- LinkedIn audience targeting guidance
- Trigger
- The targeting option list changes
- Owner
- Paid search lead (one named person)
- Score band
- Medium likelihood, high impact
Which named sources anchor the register
Three published sources do most of the work for UK advertisers.
Digital ad spend comes first. The IAB UK digital adspend research is published annually and includes search advertising figures, so it anchors demand-side scenarios.
Compliance evidence comes second. The ASA rulings database is updated as rulings are published, and each entry shows how a real ad was judged. A few rulings in the client's sector turn copy risk into a named scenario with a precedent.
Targeting assumptions come third. LinkedIn's guidance on audience targeting options is the page to cite when a scenario depends on how a platform defines an audience, and it is revised when the product changes.
Add client-specific sources on top rather than instead. Contract terms, conversion data and platform changelogs belong in the register beside the published three.
Line triggers up with publication dates rather than guesswork. The PPC agencies 2027 trends data and sources page sets out which datasets refresh when.
What triggers should force an update
A trigger prompts a revisit, not a panic. Set three tiers.
- Immediatea platform removes a feature your campaigns rely on, or a ruling lands against a business in the client's sector.
- Quarterlyspend data is refreshed, or the client's conversion data moves outside an agreed band.
- Annualthe planning cycle restarts and every scenario is re-scored.
The annual review is the one teams skip. It is also where scenarios that never fired get retired.
How do you score without inventing numbers?
Use bands, not false precision. Low, medium and high are enough, provided you write down what each band means for that client.
As an illustration, one client might define low as a change under 5% of monthly spend, medium as 5 to 15%, and high as above 15%. Those thresholds come from that client's own data, so label them as illustrative.
Where a figure appears, attribute it. If you cannot, label it as an illustrative example, such as a team paying £400 a month for a tool a scenario assumes will be replaced.
Scoring works better with two people who disagree. A single scorer tends to rate their own scenarios as unlikely.
The owner column carries as much weight as the source. The PPC agencies budget template data and sources note explains why every line in a plan needs a named person behind it.
Checklist before the register goes live
- One sentence defines each scenario, with no acronyms.
- Every scenario names a source page, not a publisher.
- Every scenario has an observable trigger and a named owner.
- Score bands are written down.
- Any monetary figure is attributed or labelled as illustrative.
- Retired scenarios are removed at the annual review.
Run the register past the person who owns the client relationship before it is shared, so the triggers match what they can actually watch.
Common questions
How many scenarios should a register hold?
Six to ten live entries. Beyond that, owners stop reading them and the register stops being used.
Can one scenario carry two sources?
Yes, but name the primary source first. If the two disagree, record that disagreement as a note in the row.
What happens when a trigger fires but nothing changes?
Record the review and close it. A logged no-change decision shows the register is being maintained.
Should clients see the register?
Usually yes, in summary form. Sharing the scenarios and triggers sets expectations about what you will raise, and when.
