Designing Government Digital Services Citizens Complete on the First Attempt

Citizens complete a government digital service on the first attempt when the service tells them up front whether they qualify and what they will need, asks only for information it cannot already know, and confirms clearly what happens next. Most e-government UX failures in Saudi Arabia and the UAE come from the gap between how a ministry is organised and how a citizen thinks about their task. Closing that gap is the whole discipline of government digital services design.

Start from the citizen’s task, not the department’s form

A citizen does not want to submit an application under service category four. They want to renew a licence, register a newborn, sponsor a dependant or appeal a fine. Every one of those tasks crosses internal boundaries: eligibility sits with one team, payment with another, verification with a third.

Good government digital services design starts by mapping the task as the citizen experiences it, from the moment they realise they need to do something to the moment they are certain it is done. That map exposes the hand-offs where people get lost, the questions asked twice and the steps that exist only because two departments never agreed who owns them. Vision 2030 and the UAE’s federal digital agenda both frame public services around life events for exactly this reason. It is how people think.

Tell people whether they qualify before they start

The most common cause of abandonment is discovering, several screens in, that you were never eligible, or that you need a document you do not have. A short eligibility check at the start, written in plain Arabic and English, saves the citizen’s time and the agency’s processing cost.

The check should ask the fewest possible questions, explain the outcome and, when the answer is no, say what the person can do instead. A list of what they will need (documents, reference numbers, approvals from other agencies) belongs on the same page. People who know what to expect finish. People who are surprised stop.

Ask only for what you cannot already know

National ID sign-in across the Gulf means a service can know who the citizen is, confirm their residency status and pull verified details without asking for them. Every field that could be pre-filled and is not is a question the citizen has already answered to the state. The Digital Government Authority in Saudi Arabia and the digital government bodies in the UAE both push agencies towards this once-only principle. The design job is to make it visible on screen.

Show the pre-filled data, let people confirm or correct it, and explain where it came from. Ask for documents only when no other agency holds them. Where an upload is genuinely required, accept a photo from a phone camera, show the user what a good image looks like and tell them immediately if it is unreadable rather than rejecting the application days later.

Design the bilingual experience as one service

Arabic and English versions of a government service are often built by different teams at different times, and it shows. The Arabic version lags behind, labels truncate, and the help content exists in only one language. A citizen switching language should find the same service at the same step with the same data.

That means designing both directions from the first wireframe, choosing Arabic typography with the same care as the Latin, deciding how numerals, Hijri and Gregorian dates and currency appear, and writing Arabic copy rather than translating English. It is the same discipline we applied when we designed the bilingual digital experience for World Defense Show in Saudi Arabia.

Write for the moment of doubt

Citizens stall at specific points: a field label they do not understand, a status they cannot interpret, an error message that tells them something is wrong without saying what. Content design is not polish applied at the end. It is the part of e-government UX that decides whether someone finishes or calls the contact centre.

Practical rules that hold across agencies:

• Use the words citizens use, not the legal names of forms, and keep one term for one thing across the whole service.
• Write error messages that name the field, state the problem and give the fix.
• Explain why each piece of information is requested, especially anything sensitive.
• Make the next step obvious on every screen, including the last one.
• Treat the PDPL in Saudi Arabia and the UAE’s data protection framework as content requirements, not just legal ones. Consent has to be understandable to be meaningful.

Make status visible after submission

Completion does not end at the submit button. A citizen who does not know whether their request was received, who will look at it, or when they will hear back will phone, visit or resubmit, and each of those costs the agency more than the original transaction.

The confirmation screen should state what was submitted, give a reference, explain the stages the request will pass through and say how the person will be notified. Status tracking should use the same stage names as the confirmation. Notifications, whether by SMS, app or email, should be specific enough that the citizen never needs to log in just to find out that nothing has changed.

Design for the counter and the call centre too

Not every citizen will complete online, and the service should not treat them as failures. Older residents, people with limited literacy in either language, visitors who do not read Arabic and anyone whose case is unusual may end up at a service centre or on the phone. The digital design should make those channels work better, not route around them.

Give front-line staff the same view of the case the citizen sees, so a conversation can pick up where the screen left off. Let a citizen start online and finish at a counter without re-entering anything. Recurring call-centre questions are the cheapest usability research an agency will ever get; review them regularly and feed them back into the content.

Measure completion, not launches

Agencies tend to measure digital transformation by the number of services online. Citizens measure it by whether the service worked. The measures that matter are first-attempt completion, time to complete, the share of requests that bounce back for missing information, and the volume of contact-centre calls about a service that is supposedly self-serve.

If an existing service is live and the numbers look poor, a structured UX audit will usually find a handful of specific causes (an unclear eligibility step, a document upload that fails on phones, an Arabic version that lags the English) faster than a redesign programme will. Our government practice is built around this kind of evidence-led citizen experience design across Saudi Arabia, the UAE and the GCC.

Frequently asked questions

What is e-government UX?

E-government UX is the design of public digital services around the citizen’s task rather than the agency’s structure. It covers eligibility, identity and sign-in, data pre-filling, bilingual content, form design, status tracking and how digital channels connect to counters and call centres.

Why do citizens abandon government digital services?

Usually because they discover too late that they are ineligible or missing a document, because they are asked for information the state already holds, or because an error message or status label is unclear. Each of these is a design problem with a known fix.

How do you measure whether a government digital service works?

Track first-attempt completion, time to complete, the proportion of requests returned for missing information and contact-centre volume about the service. Pair the numbers with usability testing in Arabic and English to understand why people stop.

Working on a citizen service in Saudi Arabia, the UAE or the wider GCC? Talk to us about making it one citizens finish first time.