Atmora Tech

Industry

Public services that work on any device

Digital services that work for everyone who has to use them, including on a five-year-old phone.

Context

Technology in Public Sector

We deliver citizen-facing services, case management, and the integration work that lets departments check a fact once instead of asking for it four times. Public delivery has constraints private work does not: accessibility is a legal duty rather than a preference, procurement shapes architecture, records retention and disclosure obligations outlive the contract, and the service must work for someone on a low-end handset with a poor connection.

We build to open standards and hand over source, documentation and running infrastructure as a deliverable, not as a negotiation at the end. We do not bid for work whose commercial value depends on the buyer being unable to leave; if a proposal requires proprietary formats or an undocumented data model to stay competitive, we are the wrong supplier and will say so during procurement rather than after.

63%
fall in incomplete applications after journey and content redesign
1.8s
median page load on a throttled 3G connection and a low-end handset
100%
of source, infrastructure code and documentation handed over at contract end

Challenges

What actually keeps this sector awake

Not generic disruption — the specific constraints that shape every technology decision here.

  • Accessibility as a tested legal obligation

    WCAG 2.2 AA conformance has to survive assessment with real assistive technology, not an automated scan. Retrofitting a service built without it typically costs more than the original build of the affected journeys.

  • Legacy systems and contractual lock-in

    The system of record is a decade-old application whose supplier owns the data model and charges per interface. Any modernisation plan has to start by extracting a usable schema before it can even be estimated.

  • Retention, disclosure and audit duties

    Records must be retained for statutory periods, produced for information requests, and redacted correctly. Services designed without this store personal data indefinitely and cannot answer a subject access request without manual trawling.

  • Identity and eligibility across departments

    Confirming who someone is and what they qualify for means checks across organisations with different assurance levels and legal bases. Users abandon at the point where they are asked for evidence a department already holds.

Approach

How we address them

  • Accessibility built into the pipeline

    Automated checks in continuous integration plus scheduled manual testing with screen readers, magnification and keyboard-only journeys, with findings tracked as defects. Content is written and tested for reading age alongside the interface.

  • Case management on an open data model

    Configurable workflow, full audit history, retention schedules enforced by the platform, and redaction support for disclosure. The schema is documented and exportable so a future supplier can pick it up without an archaeology project.

  • Legacy extraction with a costed exit

    Read-only replication out of the incumbent system into a documented store, new services built against that, and write-back reduced function by function. Every step leaves the department better placed to change supplier.

  • Identity and eligibility orchestration

    Checks composed against existing authoritative sources with the legal basis recorded per data flow, and journeys designed so the user is asked only for what genuinely cannot be verified another way.

Services

Relevant practices

Products

Platforms used in this sector

Proof

Work in this sector

Start a project

Tell us what is
breaking.

We reply within one working day, and the first call is with an engineer who would actually work on it — not an account manager. If we are not the right studio for the problem, we will say so on that call.

Start a project