A person checks a public-service portal after sending the document an office requested. A green dot says the case is “in progress”. That could mean the file is in a caseworker’s queue, waiting for another agency, blocked by a missing attachment, or untouched because an automated transfer failed. The colour offers reassurance while withholding the one fact the person needs: what happens next.
Status is not decoration. It is a public promise about the condition of a case, who currently holds responsibility and what action is required. A useful tracker should expose a small, truthful state model rather than compressing administrative reality into red, amber and green.
A dot cannot carry a case
The strongest argument for a traffic-light display is serious. Public services are complicated, people do not want an internal workflow diagram, and a compact signal is easy to scan on a phone. A green state can mean that nothing is required from the applicant; amber can ask for attention; red can mark a deadline or failure. Used as a summary, this can reduce cognitive load and make a long process less intimidating.
The problem begins when the summary replaces the record. “In progress” often groups together states that have different consequences. One case may be moving normally. Another may be waiting for the person, although no usable request reached them. A third may be on hold pending information from another authority. A fourth may have exceeded its expected time but remain green because no system event changed its label. The same colour then describes different owners, deadlines and remedies.
This is not merely a content-design flaw. It is a modelling choice. Behind the portal, a case moves through a set of states. Each transition should follow an event: an application is received, identity is verified, evidence is requested, a response arrives, review begins, a decision is recorded. If the public label is detached from those events, it becomes an opinion about progress rather than evidence of it.
The minimum truthful state
A humane tracker does not need to reveal every back-office code. It does need to answer five questions in ordinary language. It should say what has happened, who or what currently holds the case, whether the person must act, which deadline applies, and how to challenge a state that appears wrong. Those answers form the minimum useful public state.
Consider “waiting for evidence”. The phrase is incomplete unless it identifies whether the authority is waiting for the applicant, a doctor, a municipality or its own records team. If the person must respond, the tracker should show what was requested, when the request was sent, when the response is due and how receipt will be proved. If another institution owns the next step, the display should not imply that the applicant is delaying the case.
The state also needs a time dimension. “Under review since 14 August” is more informative than “under review”, but only if the date marks a real transition. An expected range can help people plan, provided it is based on relevant cases and is revised when conditions change. A fixed progress bar that advances with time, regardless of work completed, turns uncertainty into false precision.
The distinction matters because people organise lives around administrative time. They may need to renew a document, preserve an appeal deadline, arrange care, answer a landlord or decide whether to call an office. A tracker that hides a stalled case does not merely fail to inform; it transfers the cost of uncertainty to the person.
Status has to follow the work
Technically, the portal should not invent status from a separate spreadsheet or a staff member’s occasional update. It should derive the public state from authoritative workflow events, while recording when and by which system or role each transition occurred. Where several organisations participate, the service needs agreed mappings between their internal states and the public model. “Sent to partner” cannot remain the final visible state if the partner rejects the transfer.
This is where a simple interface depends on difficult institutional work. Departments must agree which system is authoritative, what counts as a hand-off, how stale information is detected and who investigates disagreement. The UK Government Service Standard requires teams to provide a joined-up experience across the channels users need and to involve front-line operations in designing and improving those channels. It also warns against making telephone, paper or face-to-face routes harder to find merely to increase digital take-up. That is relevant to tracking: the person calling a helpline and the person opening a portal should encounter the same case state, not competing stories. The standard was last updated in December 2025.
A status transition should therefore be an auditable event, not a cosmetic edit. The service can retain the internal detail needed for diagnosis while showing the person a concise description. If an event is reversed, the history should remain visible: “evidence marked missing on Monday; receipt confirmed on Tuesday” is more accountable than silently returning the dot to green.
Correction is part of tracking
A tracker is most valuable when it is wrong, because that is when a person needs a route into the institution. A challenge control should let them identify the disputed state, attach or reference evidence, preserve any relevant deadline and receive a traceable response. It should not open an unconnected generic contact form that forces them to retell the case.
The responsible team also needs exception queues for cases whose state has not changed within an expected period, transfers that lack acknowledgement, and requests that were sent but not delivered. These queues require human authority. Staff must be able to inspect the underlying events, correct a mistaken status and protect the person from consequences caused by the service’s error.
There is evidence that better status information can reduce avoidable contact. In its December 2024 access-to-justice report, HM Courts & Tribunals Service described introducing a Citizen Hub for probate applicants after delays and older cases drove requests for updates. HMCTS reported that the share of emails seeking a status update fell from 50% to 27% after the hub launched in April 2023, while satisfaction with contact rose from about 60% to 65%. The same review found that people still needed to contact HMCTS when a case was stopped, and the service planned to expand the hub so they could see and respond to requests for more information. The lesson is not that a dashboard removes the need for people. It is that useful states reduce uncertainty, while ambiguous exceptions still require accountable help. HMCTS’s published assessment provides the operational context.
Measure truth, not tranquillity
A green-looking portal can suppress calls without improving the service. Success therefore cannot be measured only by logins, page views or fewer contacts. Teams should test whether displayed states match the authoritative record, how long cases remain in each state, how often deadlines are shown correctly, how many transfers lack acknowledgement, and how quickly disputed states are corrected. They should also examine unequal burdens: people using assisted, telephone or paper channels must not receive later or poorer information.
The counterargument remains that exposing more states may confuse users and constrain staff whose work does not follow a neat sequence. That risk is real. The answer is not to publish every internal queue. It is to design a small public vocabulary around responsibility and action, then allow plain-language detail underneath. Non-standard cases can be labelled honestly as requiring individual review, with a named route for contact, rather than forced into a misleading normal path.
A public status page should leave a person better able to act, not merely calmer for a moment. Technology can collect events, reconcile systems, calculate elapsed time and deliver updates. Human institutions must decide what each state means, accept responsibility for delay and give someone the power to correct the record.
If you want to follow Alkemata’s continuing work on public services that preserve human agency, return for the next article in this GovTech series.
Continue exploring
A truthful status begins with proof that the case entered the system at all. A Public Service Should Give You a Receipt examines what that first piece of evidence should contain and who must correct it when confirmation fails.
The remaining decision is deceptively concrete: which few public states will an authority commit to keeping accurate across every channel, and who can repair the promise when the displayed state and the person’s reality diverge?
