Spent on Yes: A Consent Budget for UK Privacy Design
Photo: person dismissing cookie consent banner on a laptop screen at a desk, via www.kevinashleyphotography.com
There is a particular fatigue that sets in around the fourth permission request of a shopping session. The banner has been dismissed, the app has asked for notifications, the checkout has offered to remember the card, and the newsletter prompt has arrived before the confirmation page. Each request is individually defensible. Together they describe an organisation that has not counted the cost of asking.
Consent is treated in most design guidance as a moment: a screen, a toggle, a compliant arrangement of buttons. What that framing misses is accumulation. A UK consumer moves through dozens of consent moments a week, and the willingness to read carefully is a finite resource that is spent whether or not anyone is tracking it.
The case for a budget
The consent budget is a simple idea with awkward consequences. It holds that every person arrives at a service with a limited tolerance for decisions about permissions, and that each ask draws down the balance. Once the balance is low, subsequent requests are not read; they are cleared. That behaviour is not apathy. It is a reasonable response to a queue of decisions that appear interchangeable.
The awkward consequence is that adding a well-designed consent screen can make the overall experience worse. A team can produce the clearest cookie dialogue in its sector and still contribute to fatigue if the wider journey already contains six other asks. Judging consent design per screen rewards local polish and ignores cumulative load.
The ledger nobody keeps
Ask a UK retailer or subscription service how many consent decisions a typical customer makes in the first month, and the answer is rarely available. Requests are owned by different teams: marketing owns the newsletter, product owns notifications, legal owns the cookie banner, payments owns the saved-card prompt, and the app team owns the permission dialogue. Nobody holds the running total.
A consent ledger, even a crude one, changes the conversation. Map every ask across a first purchase and the following thirty days. Note the channel, the purpose, whether it is genuinely optional, and whether the user can proceed without answering. Most teams find between eight and fifteen asks in that window, several of which serve overlapping purposes.
Withdrawal as a first-class path
UK data protection law places withdrawal on the same footing as consent, yet the design rarely reflects that. Sign-up is a single toggle in a welcoming flow; withdrawal is buried three levels into a preference centre, sometimes requiring an email to a team that responds in five working days.
A more honest approach treats the withdrawal path as the design constraint. If a permission cannot be revoked in roughly the same number of steps it took to grant, the original grant was not really consent. Where marketing consent is bundled with account creation, the unbundling should be visible at the point of withdrawal, not only at the point of sign-up.
Measuring fatigue across the journey
Existing metrics measure the consent moment, not the person. Acceptance rates, banner interaction times and opt-in percentages tell a team how a screen performed; they say nothing about whether the customer is still reading.
Useful alternatives include counting asks per journey rather than per screen, tracking the phrasing people use in complaints and support contacts when they discover what they agreed to, and monitoring the rate at which users later undo a permission. A high reversal rate is a signal that consent was granted under duress of poor design rather than genuine preference.
It is also worth measuring the silence. If a preference centre has a large proportion of users who never open it, that is not necessarily satisfaction. It may be learned helplessness, accumulated over years of interfaces that made the default path the only navigable one.
A UK reading of the rules
The regulatory environment rewards this shift. The Information Commissioner's Office has repeatedly emphasised clear, informed and freely given consent, and enforcement action against confusing banner design has concentrated minds. The Digital Markets, Competition and Consumers Act adds pressure on misleading subscription traps, including the paths by which people leave a service. Taken together, the direction of travel is towards treating the whole lifecycle of a choice as the unit of design.
There is a temptation to read this as a compliance exercise: add a withdraw button, keep a log, move on. That would be a mistake. The organisations that get this right will be the ones that treat consent as a scarce resource rather than a marketing opportunity.
What to do on Monday
Begin with the ledger. Pick one customer journey and count the asks. Assign one owner to the sequence, not just to the screens. Decide which requests can be deferred until they are actually needed, which can be merged, and which can be removed altogether. Then test the withdrawal path with someone who has never seen the product, and watch how long it takes them.
The consent budget will not appear in a design system, but it shapes every interaction a UK customer has with a permission request. Treating it as a real constraint is the difference between a compliant interface and a respectful one.