If a Digital Government System Gets Your Name Wrong, Who Helps You Fix It?

There is a simple question that every government technology project should answer before its launch: what happens when the computer is wrong?

An individual's name may be misspelled. A family record may not match a school document. A citizen may be unable to receive a one-time code because an old phone number is still attached to an account. A form may reject a valid address. None of these examples requires a scandal to become serious. When the digital system controls access to an important service, a small mistake can become a large barrier.

Africa needs better digital public infrastructure. It also needs a right-sized, affordable and understandable way for people to correct the records on which that infrastructure depends.

Efficiency is not the same as fairness

Digitising a process can reduce paperwork, improve consistency and make some services easier to access. But technology can also make mistakes travel faster if multiple agencies reuse the same inaccurate record.

The World Bank's work on digital delivery systems highlights the importance of grievance-redress mechanisms, data governance, interoperable systems and accessible service channels. That combination matters because an efficient service which cannot acknowledge a problem is not genuinely accountable.

Consider a fictional parent submitting an application through an online portal. The system rejects the child's document because of a difference in spelling. The parent does not know whether to approach the school, a civil registry or the technology contractor. Each office points to the other. The problem is not simply bad software; it is missing responsibility.

This scenario is illustrative. ITBank is not alleging that it occurred at a particular government agency in Cameroon, the Democratic Republic of the Congo, Chad or the Republic of the Congo.

Five rights a useful digital service should respect

A clear explanation. Tell the applicant what information was used, why a step failed and which authority can correct it. 'Invalid request' is not an explanation.

An accessible correction route. Allow people to report errors and submit appropriate evidence. The route should not require expensive travel merely to correct a mistake introduced by the system.

Human review when it matters. Where a decision affects access to essential services, provide a route to someone authorised to examine unusual cases and explain the result.

Privacy and safety. A complaint desk should not expose private documents in a public queue or require people to send passwords to an unofficial messaging account.

A record of what happened. Issue a reference number, estimated next step and clear way to follow up. People need to know whether their complaint has been received and what to do if it is unresolved.

These are proposed editorial principles, not a claim that every country already guarantees them in the same form.

Not everyone has the same route online

A person who communicates in a local language, someone with a visual disability, an older adult and a worker using a shared phone may each face different barriers. A portal designed for a modern laptop can exclude people who are otherwise eligible for the service.

This is especially important beyond the best-connected districts. Public institutions should test service completion across devices, languages, accessibility needs and connectivity conditions before treating an online launch as evidence of universal access.

An offline or assisted channel may remain necessary. That is not a failure of digital transformation; it is responsible transition.

A practical citizen-service scorecard

Community organisations can evaluate a public portal without collecting anyone's confidential records. With permission, try to find its eligibility rules, identify the help channel, locate the complaint procedure, test whether information is understandable on a phone and see whether the site provides a safe recovery path after a failed attempt.

Publish the results fairly, distinguish observed problems from untested assumptions and offer the institution a chance to respond. Follow up when a service improves. Accountability should reward corrections, not only expose mistakes.

What should governments and suppliers measure?

Report rates of successful applications, unresolved complaints, corrections completed and user satisfaction across different channels. Make it possible to see where a person drops out of the process and whether a service reaches the intended population.

A contractor may celebrate software uptime while a citizen still cannot complete a single necessary transaction. Both perspectives matter, but the public outcome should come first.

The larger point

Digital government has the potential to make interactions with institutions less confusing, less expensive and more transparent. That promise is weakened if the person affected by an error has no practical remedy.

A good public portal is not the one that never admits an error. It is the one that helps people recover when errors happen.

The question for our community: When an important online service fails, is there a person or process that genuinely helps you finish the task—and how could that experience be improved?

ITBank Community Voices — editorial perspective. Country examples describe relevant audiences, not verified incidents or interviews in those countries.