Digital public services deserve better than the queue

Citizens do not experience an administration's architecture. They experience its slowest form: the benefit application that asks for a document another agency already holds, the permit that takes eleven weeks because three systems exchange files by night batch, the change of address that must be declared four separate times. Behind nearly every one of these frustrations is not a policy choice but an integration gap, and integration gaps are solvable.

The principle has a name in European digital government circles: once-only. A citizen should provide a piece of information to the state once, and the state should be organized enough to share it with itself, lawfully and traceably. France's efforts around "Dites-le-nous une fois" and equivalent programs across the Union all point the same direction. The ambition is not new. What has changed is that the infrastructure to honor it is now ordinary.

Why it stalls

Agencies rarely lack the will to connect; they lack a safe, repeatable way to do it. Each inter-agency exchange tends to be negotiated as a bespoke arrangement: a legal convention, a point-to-point link, a format agreed by committee. The result is that connecting two systems takes eighteen months, so it happens rarely, so each occurrence remains exceptional, so it keeps taking eighteen months.

The once-only principle fails not for lack of goodwill, but because every exchange is built as if it were the first one ever attempted.

The legal caution is real, and misplaced

It would be unfair to blame the paralysis on timidity. The caution is legitimate: an administration handling citizens' data operates under strict rules, and an exchange that leaks or oversteps is a serious failure, not merely an embarrassing one. The instinct to review every connection heavily comes from taking that responsibility seriously.

But the caution is applied at the wrong layer. Reviewing each exchange from scratch does not make the data safer; it makes the exchange rarer, and it spreads the organization's diligence thin across dozens of one-off arrangements that each interpret the rules slightly differently. Safety concentrated into shared, audited infrastructure is both stronger and cheaper than safety re-litigated on every project. The way to honor the responsibility is to encode it once, where it can be enforced and proven, not to re-argue it every time two agencies need to talk.

What a governed platform changes

• Legal caution becomes executable policy: which data may flow to which agency for which purpose is enforced on every call, and the record proves it, which is precisely what data protection authorities ask.
• The second connection is cheap: once the pathway exists, the next exchange is a configuration and an approval, not a project.
• Sovereignty is preserved: the platform runs on infrastructure the administration controls, with evidence retained under its own jurisdiction.

Public bodies working with Waygrid have brought new inter-agency exchanges from months to weeks, without diluting a single control; if anything the controls became stricter, because they stopped depending on each project's diligence. The queue in front of the counter, physical or digital, was never a law of nature. It was an integration backlog. It can be worked down like any other.