Proactive Government: Services That Reach Citizens First

A single mother in Cairo qualifies for a child subsidy she has never claimed, because claiming it means a morning off work, three photocopies, and a queue at an office that closes at 2pm. A pensioner in Riyadh is owed a healthcare rebate that expires unclaimed every year, because nobody told him it existed. This is not a failure of eligibility policy. It is a failure of design — and it is entirely fixable.

Proactive government flips the default: instead of citizens applying for what they are owed, the state offers it first and lets them opt out. That single reversal — from "come and ask" to "here it is, tell us if you don't want it" — is the difference between a service that exists on paper and one that actually reaches people. It is also one of the most consequential applications of behavioural science to public administration in the past two decades, and it is where public-sector CX is now heading.

What is proactive government, and how is it different from digital government?

Digital government means you can now do on a screen what you used to do at a counter. Proactive government means the state initiates the service before the citizen thinks to ask. The distinction matters because most "digital transformation" programmes in the public sector have digitised the request, not removed it. A citizen still has to know a benefit exists, judge themselves eligible, gather documents, and submit a form — just through an app instead of a window. The queue moved online; it did not disappear.

A proactive service uses data the state already holds — tax records, civil registry entries, school enrolment, health records — to identify who qualifies for what, and then delivers the benefit, the reminder, or the renewal automatically. The citizen's role shifts from applicant to recipient. Denmark and Sweden pre-fill tax returns using employer and bank data, so most citizens simply confirm a number rather than compile one from scratch. Estonia's digital infrastructure, built around the X-Road data exchange layer, allows agencies to trigger services such as automatic registration of a newborn for a personal ID and healthcare cover the moment a birth is recorded, without a parent filing anything. Nobody applies. The state already knew.

Why do eligible citizens miss services they are entitled to?

Because the friction is not laziness — it is cognitive load, and cognitive load has a name in behavioural science: sludge. Coined by the American economist Richard Thaler and popularised by the legal scholar Cass Sunstein in his 2021 book Sludge: What Stops Us from Getting Things Done (MIT Press), the term describes friction that works against a person's own interest — the opposite of a helpful nudge. A benefit form that demands a document the citizen must request from a different agency is sludge. A renewal window that closes without warning is sludge. A website that requires the same identity verification three separate times is sludge.

The scale of the problem is well documented. In a landmark field experiment with the US Internal Revenue Service, the economists Saurabh Bhargava and Dayanand Manoli found that a large share of eligible households failed to claim the Earned Income Tax Credit not because they didn't qualify, but because of psychological frictions in the claiming process itself — confusion, perceived complexity, and the sheer effort of engaging with an unfamiliar bureaucratic process. Their study, "Psychological Frictions and the Incomplete Take-Up of Social Benefits," published in the American Economic Review in 2015, showed that a simplified, shorter notification letter substantially increased take-up compared with the standard IRS notice, even though eligibility hadn't changed at all — only the effort of understanding it had.

The public administration scholars Pamela Herd and Donald Moynihan gave this phenomenon its academic name in their 2018 book Administrative Burden: Policymaking by Other Means (Russell Sage Foundation). They argue that the compliance costs a government imposes — the time, the paperwork, the psychological toll of feeling surveilled or judged — are not neutral administrative detail. They are policy choices that quietly determine who actually receives a right that, on paper, belongs to everyone equally. A generous benefit with a punishing application process is not a generous benefit. It is a benefit for whoever has the time, literacy, and patience to survive the process.

Every form a citizen must fill in twice is a tax the state charges on its own goodwill.

What does proactive service delivery actually look like?

Strip away the technology and a proactive service always does one of three things: it removes the application step entirely, it pre-fills what the citizen would otherwise have had to gather, or it reaches out before a deadline is missed rather than after. In practice:

• Automatic enrolment — a citizen is registered for a service the moment a triggering life event occurs (a birth, a job loss, a retirement), based on data the state already holds, rather than waiting for an application.
• Pre-filled forms — tax, subsidy, or renewal forms arrive with known fields already completed from cross-agency data, turning a compilation task into a confirmation task.
• Predictive outreach — the state contacts a citizen before a licence lapses, a document expires, or a payment is missed, using the lead time to prevent the problem rather than resolve it afterwards.
• Single-disclosure data sharing — a citizen who has already proven an income level or family status to one agency should never be asked to prove it again to another, with appropriate consent controls in place.
• Passive renewal with active opt-out — a service continues automatically unless the citizen actively cancels it, rather than lapsing automatically unless the citizen actively renews it.

That last item is where the behavioural economics becomes explicit. Thaler and Sunstein's foundational argument in Nudge (Yale University Press, 2008) is that defaults are never neutral — whatever a system does when a person does nothing shapes the outcome for the vast majority of people, because most people do nothing. A renewal that defaults to "continue" harvests loss aversion in the citizen's favour: nobody has to fight to keep something, only to actively give it up, and people are reliably slower to give things up than to claim them in the first place. A renewal that defaults to "lapse" harvests the same bias against the citizen. The choice of default is a policy decision disguised as a technical one, and most governments make it by accident.

How do you actually build a proactive government service?

The switch from reactive to proactive is not a single IT project — it is a sequence of design decisions, each of which can stall the whole effort if skipped. A practical build order looks like this:

1. Map the citizen journey, not the department's process. Start from the life event — birth, bereavement, unemployment, relocation — and trace every touchpoint a citizen crosses regardless of which agency owns it. Most proactive opportunities live at the seams between departments, which is exactly where nobody is currently accountable.
2. Identify the trigger data that already exists. Before building anything new, audit what the state already knows. Civil registries, tax records, and enrolment systems usually contain enough signal to identify eligibility without a single new form.
3. Design the default, deliberately. Decide, explicitly and with legal sign-off, whether the service defaults to "on" with an opt-out or "off" with an opt-in — and document why, because this single choice determines take-up more than any awareness campaign that follows.
4. Build the consent and correction layer before the automation. A citizen must be able to see why they were selected, correct wrong data, and decline the service, in plain language and in under a few minutes. Skipping this step is the single most common reason proactive pilots collapse under public backlash.
5. Pilot with a bounded cohort and a human fallback. Launch with a defined group, a case-officer safety net for edge cases, and a published error-correction path before scaling nationally.
6. Measure take-up and time-to-benefit, not just satisfaction. Traditional CSAT tells you how happy people were with the interaction they had. It says nothing about the people who never had the interaction at all because they never knew to look for it.

This is also where mapping the citizen journey properly earns its keep — because the seams between agencies are invisible on any single department's process map, and that is precisely where proactive opportunities and administrative burden both hide.

What breaks when governments go proactive?

Three things, reliably, and each has a design answer rather than a technology answer.

Trust breaks first when data use feels surveillant rather than helpful. A citizen who receives an unprompted message referencing their income or health status can feel watched rather than served, even when the intent is generous. The fix is transparency at the point of contact: state plainly why the citizen is being contacted, which data triggered it, and how to object — every time, not buried in a privacy policy nobody reads.

Accuracy breaks second, because triggers are only as good as the records behind them. A civil registry with a stale address, or a tax record that hasn't caught up with a change in employment, will misfire. A proactive service that gets it wrong publicly is more damaging to trust than a reactive service that was merely slow, because the citizen did nothing to invite the error. Every proactive trigger needs a visible, fast correction path, and a case officer who can override the algorithm without a three-week ticket queue.

Equity breaks third, quietly, if the underlying data itself is unequal. Proactive systems work brilliantly for citizens who are already well captured in official records — formally employed, digitally registered, resident at a known address. They can silently exclude exactly the citizens most likely to need help: informal workers, the recently displaced, the digitally absent. A proactive strategy that isn't paired with a deliberate outreach channel for the undercounted simply automates yesterday's blind spots faster.

The OECD's work on digital government has repeatedly flagged this tension: the same data infrastructure that enables proactive, personalised service can just as easily entrench exclusion if governance and inclusion aren't designed in from the start, not patched on afterwards.

How should a government measure whether a proactive service is working?

Satisfaction scores measure the experience of people who showed up. Proactive government's entire point is reaching people who wouldn't have. That requires a different scorecard:

• Take-up rate against eligible population — not against applicants, but against everyone entitled, including those who never applied.
• Time-to-benefit — the gap between the triggering life event and the citizen actually receiving the service, which should shrink from weeks to days or hours.
• Opt-out rate and reason — a healthy proactive default sees low opt-out; a spike signals a trust or accuracy problem worth investigating immediately, not dismissing as noise.
• Correction volume — how often citizens have to fix data the state pushed to them, which is a direct proxy for register quality.
• Equity delta — take-up among digitally underrepresented groups compared with the general population, tracked deliberately rather than assumed away.

Institutions that have run this kind of behavioural diagnostic at scale — the UK's Behavioural Insights Team, established within the Cabinet Office in 2010 — built their entire practice on the principle that small, well-tested changes to how a service is framed, defaulted, or timed move outcomes more reliably than large communications campaigns urging citizens to "be aware." Awareness campaigns ask the citizen to work harder. Proactive design asks the system to work harder instead, which is the correct direction of effort for an institution meant to serve, not to test its citizens' persistence.

Where does this leave a public-sector leader building the case internally?

Rarely on strong footing with a pure efficiency argument, because proactive delivery is not primarily a cost play — the data pipes, consent layers, and case-officer fallbacks needed to do it responsibly cost real money before they save any. The case that holds up is a legitimacy case: a right that citizens cannot easily exercise is not fully a right, and an agency that only ever appears when it wants something from a citizen — a fine, a tax return, a compliance check — earns a different relationship than one that occasionally appears to give something first. That asymmetry compounds. Every proactive touchpoint that lands well is a small, credible signal that the state is paying attention on the citizen's behalf, and that signal is worth more to institutional trust than any single satisfaction score.

Building that case usually starts with an honest look at where the current model sits. A structured CX maturity assessment against the touchpoints citizens actually cross — rather than the org chart departments already have — tends to surface the seams where proactive opportunities are being missed, long before anyone commissions a new platform to fix it.

A different question for the next budget cycle

Most public-sector CX conversations still ask "how do we make it easier for citizens to find us?" That is the wrong question for a service built on data the state already holds. The right question is: why is the citizen doing the finding at all? A government that has to be found has already lost the moment that mattered. A government that shows up first — with the subsidy pre-approved, the renewal already actioned, the reminder sent before the deadline rather than the penalty after it — is not being generous. It is simply using what it already knows, on the citizen's behalf, instead of against them. That is the entire discipline in one sentence, and it is worth building a strategy around rather than a pilot.

Renascence works with public-sector institutions across the region on exactly this shift — from reactive counters to proactive, citizen-first service design, built on applied behavioural economics and grounded in real citizen feedback rather than assumption. If your agency is weighing where to start, our team is a useful first conversation — get in touch.