The gold standard of public sector digital inclusion concerns whether residents can actually use the service. Digital inclusion means people can participate in public digital services with appropriate access, skills, support and safeguards. Its gold standard is not requiring every resident to use an app; it is ensuring technology improves service without excluding legitimate users.
Start with a resident trying to complete a specific service, such as submitting an assistance application and receiving a usable receipt. Examine device access, connectivity, comprehension, accessibility and help at each step, including what happens after a failed attempt.
The Problem in Plain English
A resident qualifies for assistance but cannot complete a digital form because of device limitations or unfamiliar verification steps. The service is not truly inclusive until there is a secure, understandable route to completion.
A form that works on a staff laptop can still exclude someone using a shared phone with limited data. Record where the resident stops and whether a supported alternative carries the application forward without requiring them to repeat the same inaccessible step.
What a Gold Standard Requires
- A complete service route from finding eligibility information to receiving and understanding the outcome
- Low-bandwidth and small-screen journeys that retain entered work when a connection drops
- Accessible labels, instructions, error messages and confirmation screens across the whole transaction
- Assistance that explains the process without asking residents to disclose passwords or verification codes
- An authorised assisted or non-digital route for people unable to complete online
- Case references that let staff continue an enquiry across channels without unnecessary repetition
- Completion and abandonment evidence that includes people using assisted routes
- A named service owner who removes recurring barriers and checks the revised journey with users
Access Includes Devices and Connectivity
A service may be technically online while some people lack practical access. Design should account for the conditions in which users operate.
In an authorised test environment, complete a test application on a small screen with a slow connection. Check whether an upload can be retried, progress survives interruption and a readable receipt appears. Record unnecessary downloads and any step that assumes access to a second device.
Skills and Confidence Matter
Clear guidance and appropriate assistance can help people navigate services without making them dependent on unsafe informal help.
Ask a consenting participant to explain the next step after reading a sample verification instruction. A helper should demonstrate with test records and let the person practise, rather than take possession of their credentials. Check that the participant can recognise completion and find help without the helper prompting.
Accessible Design Is Essential
Readable interfaces, assistive technology compatibility and understandable instructions support people with different abilities.
Using a test record, navigate the form by keyboard and with the assistive technology the service supports. Check focus order, field labels, required-field explanations and announced errors. A submit button that works is insufficient if the user cannot discover why submission failed or hear the confirmation.
Alternative Channels Protect Continuity
Assisted and non-digital routes may be needed where appropriate. These should maintain legal, privacy and security requirements.
Walk a fictional case from a phone enquiry to an assisted appointment or approved paper route. Verify that staff can explain required evidence, record progress and return an understandable outcome. A phone number is not an alternative if it only tells the resident to use the inaccessible website again.
Measure Completion, Not Downloads
App installations or account registrations do not prove that people successfully receive services.
Distinguish starting a form, submitting it, receiving a decision and obtaining the service. Review abandoned attempts alongside completed cases and ask whether residents understood the outcome. Examine assisted journeys separately so a rising online completion rate does not conceal people diverted into an unresolved queue.
Break-Test: Digital Authentication Is Unavailable
Can urgent users obtain authorised assistance, preserve deadlines and resolve cases fairly?
Rehearse the outage with test cases rather than disabling live authentication. The service owner should identify which actions can be recorded for later processing and which must wait for approved identity checks. Staff should give a case reference, explain the next contact and avoid promising extensions they lack authority to grant.
The Operating Loop
1. Understand the starting position
Observe where residents encounter barriers: finding the service, reading eligibility, authenticating, providing evidence or understanding a decision. Include people using assistance and people who stopped before creating an account; enrolment data alone cannot show who never got in.
2. Define the next useful outcome
Select a concrete completion point, such as a resident submitting a valid application and retaining a receipt they can use to enquire later. Define what successful assisted completion looks like alongside independent completion.
3. Select a proportionate intervention
Match the remedy to the barrier. Compress an unnecessarily large download for poor connectivity; rewrite confusing evidence instructions; provide an authorised assisted route where the digital step remains unusable. Do not prescribe training for an interface defect.
4. Execute with clear responsibility
Assign responsibility for both the interface change and the assisted handoff. Give support staff the same current instructions as the website, a route to escalate blocked cases and a way to confirm that the receiving team accepted the case.
5. Measure and review
Test the revised journey with consent and test records, then review operational completion and unresolved cases using appropriate privacy safeguards. Compare the same journey before and after the change; record differences in case complexity or channel that affect interpretation.
6. Correct and preserve learning
Keep the successful fix in the service design and staff guidance. Add the barrier to future release checks, remove superseded instructions and recheck the end-to-end journey after changes to authentication, forms or evidence requirements.
A resident should not lose their place when moving from online self-service to authorised assistance. Keep the case reference and necessary progress available through the approved handoff, while limiting personal information to staff who need it.
The Gold Standard Scorecard
- Successful service completion: Count completed service outcomes against eligible attempts where observable, and state what the data cannot capture. Separate submission from actual receipt of the service.
- Accessible interface performance: Record whether users can finish key tasks with supported assistive technologies, including recovering from errors and recognising confirmation. Count unresolved blockers by task.
- Assisted-channel availability: Check whether the published help route can accept and progress a blocked case; examine waiting, repeat contacts and referrals that send residents back to the original barrier.
- User comprehension: Ask participants to explain required evidence, the next action and the meaning of the outcome in their own words, rather than merely rating whether the page looks clear.
- Security and privacy: Review whether assistance avoids credential sharing and whether test receipts, shared-device sessions and case handoffs expose unnecessary personal information. Use authorised test records.
- Resolution equity: Compare completion, repeat evidence requests and unresolved cases across channels and relevant access needs where data can be collected appropriately. Investigate differences before attributing them to users.
Publish the scope of each measure. A high completion percentage among signed-in users says nothing about residents unable to authenticate. Combine observed task tests, support evidence and service outcomes rather than presenting downloads as proof of inclusion.
The Break-Test
In a tabletop exercise, combine a connection failure during an evidence upload with a resident who cannot travel to a service counter. Can the support team locate the test case, explain which evidence was saved and offer an approved route that the resident can actually use? Pass only when the simulated resident can describe the next step and the receiving team has accepted responsibility; a referral alone is unfinished work.
What Students and Professionals Can Learn
Create a fictional public-service form and three user scenarios: a shared phone, an unreliable connection and keyboard-only navigation. Use invented records to attempt the same task in each scenario. Record the exact barrier, redesign one step and repeat the attempt. Compare completion and recovery, then write a short explanation of why the change helps without weakening identity or privacy safeguards.
Sources and Connected Knowledge
How to Be the Gold Standard of Public Sector Digital Inclusion
Digital inclusion is demonstrated when a resident can reach a service outcome through a route they can use, understand and trust. Keep digital access, practical assistance and non-digital alternatives connected, and treat repeated abandonment or referral loops as service defects to fix.