Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Risk Register

The single table of what could knock a marketing plan off course, each risk with a warning sign, an owner and a response prepared in advance.
StrategyconceptUpdated

Definition

A risk register is a single table of the events that could disrupt a marketing plan, one row per risk. The tutorial on building a marketing risk register puts the distinction simply: a plan describes what the business intends to do, and the register describes what could stop it and what will happen if it does. It is not a list of worries; each entry earns its place by being specific enough to watch for and to prepare for.

It sits between two neighbours. Quarterly planning names risks to particular initiatives, and scenario planning prepares for a few large uncertainties outside the business's control. The register is the standing document that collects the risks to the whole plan, inside the business and outside it, and keeps them current between planning sessions.

What each row holds

The tutorial writes every risk as a cause, an event and an effect, which separates risks that share an effect but need different responses, and scores it for likelihood and impact on a scale the team has defined for itself. The three columns that give the register its value are the ones a plan does not provide:

  • A warning sign. The early indication, agreed in advance, that the risk is starting to happen.
  • An owner. One named person per risk who watches the sign and triggers the response, so nobody has to work out whose problem it is.
  • A prepared response. What happens when the sign appears, drafted while there is time to think.

Likelihood rests on the business's own history and the judgement of the people closest to the risk. The tutorial is explicit that there is no published rate for how often most marketing incidents happen, so none should be borrowed.

In practice

  • Monthly review. A short monthly slot asks of each high-scoring risk whether its sign has appeared and whether its response is still ready. Risks that no longer apply are closed, so the register stays short.
  • Key-person risk. The guide to reducing key-person risk records the gaps that matter in the register, with an owner, so they are reviewed with the team's other risks rather than in a separate spreadsheet.
  • Operations work. The guide to prioritising operations work weighs risk items such as a missing consent check by their consequence, as the register does, not by how often they come up.
  • Crises. The guide to leading marketing through a business crisis ends by updating the register with what was learned.
  • External assumptions. The market and competitor research hub feeds the forces acting on the market into planning assumptions and risk registers.
Illustrative example — not a real result

A caterer writes the row it needed in its busiest month

Mibbletorn Caterers, an invented events catering company, takes most bookings through a form on its website. In December, its busiest month, a plugin update broke the form for 4 days before a customer phoned to ask why nobody had replied. Nobody knew who could fix it, and an estimated 30 enquiries were lost. In January the team built a register of 9 risks. The booking form row names the warning sign (no form enquiries for 24 hours on a weekday), the owner (the operations manager, with the web developer as named fixer), and the prepared response: a fallback form hosted elsewhere, a homepage notice with the phone number, and a rule that plugin updates wait until after the December peak.

A Crisis Plan is what the team opens when a situation outruns the register's prepared responses. A Holding Statement is a response that can be drafted in advance for reputational risks on the register. A Change Freeze is a common prepared response to the risk of a release breaking something around a peak. A Decision Log records what was decided during an incident, which the review afterwards uses to update the register.

Common confusions

  • A risk register is a list of worries. Each row needs a cause, a sign, an owner and a response; a worry with none of those is not yet a managed risk.
  • The register is the crisis plan. The register anticipates specific events; the crisis plan is for situations that outrun the routine.
  • It is built once with the annual plan. Without the monthly review it goes stale, and a stale register is not read when it matters.
  • Every risk needs a fix. Some risks are best accepted, and the register says so with the reason, so the decision is visible.

More terms to look up

Where this term is used

Related