Unifying 40+ citizen services into one digital portal

Public-sector expectations have changed faster than most government technology estates. Citizens who bank, shop and travel through a single app now expect the same immediacy from public services — and national digital agendas increasingly mandate it. The authority we partnered with had grown its digital footprint service by service over more than a decade. Each programme had delivered something useful in isolation, but the cumulative result was forty disconnected systems with their own logins, forms, design languages and support teams.

For citizens, the experience was fragmented and opaque. The same personal information was requested again and again; application status was invisible once submitted; and many journeys still ended with a trip to a service centre to present a document the authority already held. For staff, the cost was hidden but substantial: officers spent their days re-keying data between systems, chasing approvals over email, and answering phone calls that existed only because the online channel offered no visibility.

The technology constraints were equally real. Several systems of record were long-lived back-office applications that could not be retired on a programme timeline, procurement and data-residency rules limited where workloads could run, and security and audit requirements were non-negotiable. Any solution had to respect those constraints, not wish them away.

We began with a structured discovery rather than a technology decision. Over an intensive assessment phase we mapped all forty services end to end — the citizen journey, the data each one consumed and produced, the back-office systems behind it, and the true processing cost. That inventory let us prioritise pragmatically: high-volume, high-frustration services with clear rules went first, so the programme delivered visible value early and built political and public confidence.

The architectural decision that shaped everything else was to treat the portal as an orchestration layer over the existing systems of record, not a replacement for them. A shared API gateway and integration layer would expose legacy capabilities through clean, governed interfaces, while a digital-identity service gave citizens one credential across every journey. This avoided a high-risk big-bang rewrite and meant individual back-office systems could be modernised later, on their own timeline, without disrupting the citizen experience.

Design was treated as a first-class discipline. We co-designed journeys with citizens and frontline officers, wrote to plain-language and accessibility standards (WCAG 2.2 AA), and supported full Arabic and right-to-left layouts from day one. In parallel we planned the human side of the change — training, internal communications and a cross-departmental governance board — because a portal that staff do not trust or understand quietly fails regardless of its engineering quality.

The portal itself was built as a set of micro-frontends on a shared design system, so each service team could ship independently while citizens experienced one coherent product. A digital-identity and single-sign-on service underpinned every journey, with step-up multi-factor authentication applied only to sensitive transactions to balance security with friction.

Behind the interface, a workflow and business-process engine replaced the email-and-spreadsheet approvals that had dominated before. Applications were routed automatically against defined rules, with service-level timers, escalations, document automation and e-signature built in. Integration was handled through an enterprise integration layer (MuleSoft) that connected the portal to legacy back-office systems, the national payment gateway and authoritative registries — moving to event-driven patterns where the underlying systems allowed, and resilient request/response where they did not.

Everything ran on a cloud-native platform (Azure) provisioned through infrastructure-as-code and orchestrated on Kubernetes, with in-country data residency, blue-green deployments and full observability. Security and governance were engineered in rather than inspected at the end: encryption in transit and at rest, role-based access control, complete audit trails, privacy-by-design data handling, and automated accessibility and security testing in the delivery pipeline. A real-time analytics layer (Power BI) gave programme leaders live visibility of volumes, cycle times and drop-off points — turning the portal into a continuous improvement instrument, not just a transaction channel.

Twelve months in, forty services were live behind a single front door. Manual requests fell by roughly 70% as citizens completed transactions online that had previously required staff intervention, and journeys that once took weeks were completing in days — many of them instantly. Citizen satisfaction reached 4.7 out of 5, and the channel was available around the clock rather than during office hours.

The operational impact was as significant as the experiential one. Officers were redeployed from data entry to complex casework that genuinely needed human judgement, and call-centre volume dropped as status visibility removed the most common reason citizens picked up the phone. Because the platform was built around reusable service templates, the authority could onboard additional services in weeks rather than commissioning a new system each time — turning what had been a capital programme into a repeatable capability.

Crucially for a public-sector client, governance improved alongside experience. Every transaction carried a full audit trail, accessibility was demonstrable rather than assumed, and data remained within the required jurisdiction — strengthening the authority's compliance posture while it modernised.

The defining lesson of this programme is that orchestration beats replacement. By wrapping rather than ripping out legacy systems, the authority modernised the citizen experience quickly and de-risked the deeper changes still to come. Digital identity proved to be the true foundation — once citizens had one trusted credential, every subsequent service became dramatically simpler to deliver.

Two further lessons travel well to any large public organisation. First, accessibility and language are not enhancements to add later; in a public context they determine whether a service is usable at all. Second, sequencing by citizen value — not by organisational convenience — is what sustains momentum and trust through a multi-year programme.

The lasting value is institutional. The authority did not just digitise forty services; it acquired a platform, a delivery model and a governance capability for continuously bringing services online. That future-readiness — the ability to add the next service quickly, securely and accessibly — is the outcome that will compound for years.