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

Marketing Frameworks

Management by Exception

Management by exception explained: agree a tolerance for each plan line in advance, leave routine variation alone and escalate what breaks it, with an example.
Frameworkintermediate9 min readUpdated

What management by exception is

A marketing plan can move once it is live. Spend runs ahead of its phasing or behind it, a media line under-delivers, a conversion count drifts away from the order system, a cost per lead rises for a while and settles again. A team that reports every movement buries the one that matters among many that do not.

Management by exception sorts the movements in advance. For each line that matters, the team writes down what is measured, how far it may move from the plan before it counts as an exception, who handles the variation inside that range and who must hear when the line leaves it. Inside the range, the person doing the work adjusts, records what happened and carries on. Outside it, the exception travels along an escalation route agreed beforehand to someone who can move money, change the plan or accept the miss.

Three parts make it work, and each fails without the others: the tolerance, which says where routine ends; the delegated authority, which says what the person inside the tolerance may decide alone; and the escalation, which says who decides beyond it and how fast. A tolerance with no owner is an alarm nobody answers, and authority with no tolerance is either unlimited or second-guessed every week.

Where marketing teams already work this way

Several of the site's guides apply the principle. The table summarises where; each guide sets its own tolerances and checks.

Plan lineWhat the tolerance is set onWhere the range comes fromWho acts inside itWho hears when it breaks
Budget linesActual spend against budget or forecastAgreed with the finance business partnerThe line ownerFinance, in a written variance note
Media plan linesDelivery against the frozen baselineThe team's own experienceThe planner or buyerThe budget holder, in the weekly note
Measurement sourcesThe gap between two counts of one outcomeEarlier months with no known faultThe reconciliation's ownerThe same owner, who investigates and logs the finding
Live ads and keywordsResult against target over the agreed windowThe account lead's threshold documentThe paid media managerThe account lead, for a pause outside the threshold document or one that would empty an ad set or ad group
Service goodwillWhat an agent may offer without askingThe business's margins and past casesThe agentAn approver

The guide to tracking spend against budget agrees a threshold with finance below which no variance needs explaining, and the month-end close checklist explains in writing only the differences beyond it. The tutorial on managing a media plan while it runs writes a tolerance and the person who acts beside every line before launch and ends each week with a note naming the lines outside it. The tutorial on reconciling app install numbers works out each gap's normal range from earlier months with no known fault and opens an investigation once a gap moves beyond it. The SOP for pausing underperforming ads lets the paid media manager pause within thresholds the account lead owns, and the remedies and goodwill limits tutorial gives front-line staff an allowance to use freely and an approval route beyond it.

Setting tolerances before the work starts

Choose the lines. A tolerance belongs where a miss costs money, breaks a commitment or changes a decision. Lines nobody would act on do not need one.

Size it from consequence and history together. The consequence says how large a drift the business can carry until the next routine review; the history says how far the line normally moves when nothing is wrong. A tolerance tighter than the line's ordinary movement fires on noise, and one looser than the consequence allows fires too late. For a measure that must not be pushed too far while another improves, a guardrail metric already carries an agreed bound. No outside figure can size a tolerance for a particular business.

Cover both directions and the forecast. Money that will not be spent is an exception as much as overspend: a line whose budget pacing runs far behind plan may end the month with unused money or a burst of poor buying. And a line inside its tolerance today that will be outside it by the end of the period, on any honest forecast, is already an exception.

Write down the authority inside it. Say what the person running the line may decide alone: move money between similar lines, pause, rebook or wait. Where money is committed, the guide to setting spending authority sets who may commit what and how far, and the tolerance sits beside that spending authority rather than replacing it. The guide to delegating marketing work shows how the level of authority widens as the work comes back right.

Record it beside the line. A tolerance kept in someone's memory moves to suit the week. Put it in the plan, the tracker or the measurement plan, with the person who acts and the date it will next be reviewed.

Reporting and escalating exceptions

An exception report leads with the exceptions. For each one it gives the line, how far outside the tolerance it is or is forecast to be, the cause if known, what has already been done and the decision needed. Lines inside tolerance appear in a short summary, so the reader can see they were checked.

Silence must mean that a line was measured and sat inside its range, not that nobody looked. The data quality guide runs its weekly checks at a fixed time, writes the results down even when everything passes, and counts an unwritten tolerance among its common mistakes.

When a line leaves its tolerance, confirm the exception is real before explaining it. A fault in how something is counted can pass for a real shift in demand, and the guide to explaining metric changes clears tracking, definitions and the calendar first. Then the person with authority acts, accepts the miss or changes the plan, and logs the choice with its date.

Review the tolerances on a set date, not only when one breaks. A tolerance that keeps firing for amounts nobody acts on is too tight; one that never fired while the line drifted into trouble is too loose or set on the wrong measure. Adjust either openly, with the reason recorded, so tolerances do not move quietly to fit the result.

Worked example (illustrative)

Illustrative example — not a real result

A glassblowing studio sets its season's tolerances

Thilvumbren Glassworks, an invented glassblowing studio, sells glassware online and runs weekend taster classes. The owner used to read every channel report but now agrees four tolerances with the marketing lead, each written beside its line. Each paid line's spend may run up to 10 percent either side of the month's phasing. The analytics order count may sit between 2 and 6 percent below the shop's own count, the range seen over the previous 8 months. The owner hears when weekly class bookings run more than 15 percent either side of plan for 2 weeks running. Any move of money between lines larger than a fifth of a line's month goes to the owner.

In week 6 the note leads with 2 exceptions and confirms that the other lines were checked and sat inside tolerance. Paid social spend is 22 percent behind phasing because 2 ads were rejected in review; the marketing lead replaces them. The orders gap has widened to 11 percent; the check finds a checkout update that stopped the purchase tag firing on 1 payment route, fixed within 2 days. Class bookings are 9 percent short, inside tolerance, and get no meeting. After the quarter, the owner gives the smallest paid line, which fired 3 times for amounts too small to matter, its own wider tolerance.

Limits and criticisms

The principle is only as good as its tolerances. Set too wide, they hide a problem until it is expensive; set too tight, they flood the manager with exceptions until people ignore them.

Silence can mislead: unless the report says which lines were checked, a broken tag or a supplier who stopped reporting looks exactly like a line inside its range.

A slow drift can stay inside tolerance every week and still add up to a large miss; a tolerance on the period's running total, a run rule of the kind control charts use, or the ordinary review of the whole plan is needed to catch it.

It compares the work with the plan and says nothing about whether the plan was right. A campaign delivering exactly to a plan aimed at the wrong audience raises no exceptions at all.

Tolerances can become targets. When people are judged on how rarely their lines appear as exceptions, work is steered to sit just inside the edge and bad news arrives late, the pattern Goodhart's law describes for a measure that becomes a target.

And it flags what needs attention, not what to do, and depends on people escalating early. A team that fears blame may hold an exception back until it can be explained away, by which time some options may have gone.

Control charts supply the statistical side, a metric's ordinary range drawn from its own history, which is one way to size its tolerance; management by exception adds who acts inside and outside that range. The RACI matrix names who is responsible for each line and who is accountable when it breaks, so every tolerance has an owner and every escalation a destination. The KPI tree shows which driver moved when an outcome line becomes an exception, and its guardrails carry thresholds of their own. Scenario planning also agrees thresholds in advance, but its triggers watch signposts and move the team to a different prepared plan, whereas a tolerance governs routine drift against the plan already running. The marketing frameworks library lists the other measurement frameworks by the decision they serve.

Common mistakes

  • Choosing the range once the line is already off course. A tolerance agreed after the event only describes what happened; agree it before the work starts.
  • One tolerance for every line. A guaranteed media buy, a test budget and a data reconciliation need ranges of their own.
  • Watching only overspend. Underspend and under-delivery are exceptions too, and easier to recover when found early.
  • Treating silence as good news. Report which lines were checked, so missing data cannot pass for a quiet week.
  • No authority inside the tolerance. If every adjustment still needs approval, every movement still reaches the manager.
  • Never reviewing the tolerances. Ranges that keep firing, or stay silent while a line drifts into trouble, are adjusted openly with the reason recorded.

Frequently asked questions

How is a tolerance different from a target?

A target says where a line should end up; a tolerance says how far it may drift from the plan before it counts as an exception. A line can sit inside its tolerance and still fall short of its target, which is a matter for the regular review rather than an escalation. Keeping the two apart stops the tolerance becoming a second target that the work is steered to sit just inside.

Where should the size of a tolerance come from?

From the consequence of a miss and from the line's own history. Ask how large a drift would cost real money or change a decision if nobody acted until the next review, then check how far the line normally moves when nothing is wrong, so ordinary variation does not set it off. Budget tolerances are agreed with finance; delivery and data tolerances are recorded next to the line they govern, in the plan or the measurement plan, together with whoever acts on them.

Does management by exception mean the manager stops looking at the work?

No. The routine report still arrives, but it leads with the exceptions and keeps everything else brief, and the manager checks from time to time that a quiet line is inside its tolerance rather than unmeasured. The tolerances themselves are reviewed on a set date, because a tolerance that keeps firing for amounts nobody acts on, or never fires while its line drifts into trouble, is telling the team something about how it was set.

Terms used on this page

Frameworks

Where this page is used

Also related

Related