Concept

Public authority

Published 3 June 2026

Public authority is not only exercised through visible commands or decisions. It can also be shaped by systems that classify, validate, route, explain, or repair.

Public authority is often imagined as something visible.

A law is passed. A permit is granted. A benefit is refused. A court gives a ruling. A public body sends a letter with a decision, a reason, and a route for objection.

Those moments matter. They are still central to public life. But they are not the only places where public authority becomes practical.

Before a decision can be made, a person may need to be recognised by a system. A claim may need to fit a category. A document may need to count as valid proof. A record may need to match another record. A portal may need to route the request to the right place. A register may need to make information visible. A mistake may need a path for correction.

None of this looks like power in the traditional sense. It may look administrative, procedural, or technical. But these arrangements can shape whether people can act, be seen, prove something, ask for help, or challenge what has happened.

Public authority is not only about command. It is also about the recognised capacity to organise public life: to classify, validate, include, exclude, route, authorise, refuse, explain, or repair. In many cases, that authority is exercised through formal institutions and visible decisions. In others, it depends on background systems that make those decisions possible.

A digital identity system does not need to issue a final decision to matter. It may affect whether someone can enter a process at all. A public register does not need to adjudicate a dispute to matter. It may affect what becomes visible, reliable, or actionable. A portal does not need to make policy to matter. It may still shape what route is available, what information is requested, and where responsibility appears to sit.

The point is not that every administrative tool exercises public authority. A routine system can remain a routine system. The point is that some systems become part of how authority works in practice.

This matters because public authority should remain answerable: to affected people, to oversight bodies, and to the public institutions responsible for the system.

It is not enough for a system to be efficient, secure, or convenient. Those are important qualities, but they do not settle the public question. A system can be efficient and still make responsibility hard to locate. It can be legally authorised and still be difficult for affected people to understand. It can be technically reliable and still leave people with no practical way to correct a mistake.

The public question is different:

Can affected people understand what happened?
Can an error be corrected?
Can a decision, route, or outcome be questioned?

These questions are not only technical questions. They are questions about justification, responsibility, and public trust.

Different fields notice different parts of the problem. Law and public administration help identify rules, procedures, duties, and institutional responsibilities. Infrastructure studies notice the standards, categories, and background arrangements that often become visible only when something breaks. Political theory asks when authority is justified, answerable, and open to challenge. Civic technology asks whether tools that promise access or participation actually support people in practice. Research on street-level bureaucracy shows how policy becomes real through everyday implementation and discretion; this note asks how digital and administrative systems now shape some of the conditions under which that implementation takes place.

The concern is not public authority as an abstraction. Nor is it technology as a neutral tool. The concern is with the arrangements through which people and institutions encounter each other: records, forms, portals, registers, credentials, workflows, standards, and routes of correction.

This does not mean that every system failure is a crisis of legitimacy. Some failures are ordinary errors. Some are usability problems. Some are implementation issues that can be fixed without changing the underlying arrangement.

But when a system repeatedly shapes who can be recognised, what proof is accepted, which route is available, where responsibility can be found, or how a mistake can be repaired, the question becomes larger. The system is no longer only a tool sitting behind public authority. It is part of how public authority is organised.

A useful question is therefore:

When a system helps public authority work in practice, how can people understand it, question it, and hold the responsible bodies answerable for how it works?

That wording matters. A system is not the final bearer of public responsibility. Institutions remain responsible for how systems are designed, governed, used, explained, and corrected.

This question does not claim that every digital system transforms public power. It asks where public responsibility should follow the systems that increasingly organise public and civic life.

Lineage

This note draws on theories of public authority and legitimacy, on public-administration work on how formal authority becomes practical through routine implementation, and on European good-administration principles as a limited institutional reference point.

Sources and further reading

Policy anchor

Article 41 of the EU Charter is used here only as a limited European reference point for good administration by EU institutions, bodies, offices and agencies. It should not be read as a universal legal test for every public-facing or socially relevant system.