Digital divide and exclusion risk
Naming, before an agent channel launches, the populations it will fail, and committing outreach and a working alternative route for each. A population the channel will fail is provided for before launch instead of surfacing later in complaint and harm data.
The impact of agents
As government delivery moves onto agent-mediated channels, the existing divides of access, skills, affordability, trust, and relevance compound into an agentic divide between users with a capable agent and those without one.
The divides being compounded are already measured: the ITU puts roughly 2.6 billion people offline and rural internet use at 48 percent against 83 percent in cities, 7.9 million UK adults lack basic digital skills, and a third of those offline report difficulty reaching council and government services. Exclusion at the verification step is counted separately again, with survey estimates putting 243 million people at risk because their identity documents are non-standard, and 96 million whose appearance differs from their ID photo. Left unaddressed, that divide surfaces only after deployment, in complaint volumes and documented harm, once a cohort has already been failed.
What must be verified
Before and after it deploys an agent-mediated service, government needs to be able to account for who the service will fail and to show that those users still have a working route to the outcome. That account is what a user, an oversight body, or a court relies on to check that the agency knew who the agent channel would fail and kept a route open for them.
Protecting access
The people at risk here are every population an agent channel can lose: users with no affordable internet or capable device, users without the skills or confidence to direct an agent, users with a well-founded distrust of automation after past algorithmic harm, users with disabilities, and users without the legal capacity to act for themselves. As agent channels become the default, the risk to these populations ranges from outright denial, through deterrence, to being shifted onto a slower, lower-quality channel.
Keeping the path open
- Reach out proactively through the intermediaries those populations already trust: libraries, community organizations, community legal centers.
- Provide a non-agent route that delivers the same outcome.
- Disaggregate uptake reporting enough that an excluded cohort becomes a number someone must answer for.
Response surface
The populations an agent channel is likely to fail are named in advance, each with a committed alternative that later uptake reporting checks.
Naming who the channel will fail is the assessment’s job. A population it doesn’t name is a population nobody is answerable for.
Uptake is reported for each named cohort, not as a single average.
Maturity
- Established
For digital-divide research and measurement, which are mature.
- Emerging Headline
For extending that work to agentic exclusion specifically, which is still taking shape.
Precedents
UK public sector accessibility statements. The regulations require a public sector body to publish its compliance status against WCAG 2.2 level AA and to list its non-accessible content with the cause of each, pointing to an accessible alternative where one exists. The Government Digital Service monitors a sample, allows twelve weeks for fixes, and refers what is left to the equality regulator. A service is already required to name in public whom it fails, and what route it leaves them.
What carries over to agent use
The existing digital divide research provides the demographic and geographic map of who will be excluded from agent-mediated services. Every barrier to digital services is also a barrier to agent-mediated services, plus new barriers: the cognitive complexity of agent interaction, the trust deficit for AI among communities harmed by algorithmic systems, and the affordability of capable agents.
The research maps who is excluded today. Turning that map into an obligation, an assessment a service must complete before its agent channel launches, is the step with no operating precedent yet.
Where things go wrong
The failure mode is a system that serves some populations badly, confronted only after a cohort has been damaged. The assessment itself can also be gamed: completed as a checkbox before launch, or its uptake reporting aggregated so coarsely that a failed cohort disappears inside the average. Naming the at-risk populations before deployment, and reporting uptake disaggregated enough that each named population stays visible, keeps them inside the service rather than leaving them to be found among the harmed.
Sources
6 references
The instrument, the operating deployment, or the official record itself.
Writing about the subject rather than the framework itself, including vendor commentary.