The gold standard of public sector assisted digital services is not a certificate or an impressive dashboard. Assisted digital services help people use online public services when they need additional support. Their gold standard is not having someone fill in a form for the user; it is secure, respectful assistance that enables legitimate service completion.
Begin by identifying the barrier the person wants help with and agreeing what the helper may do. Good support makes the service reachable while keeping choices, consent and sensitive information under the user’s control.
The Problem in Plain English
A resident is eligible for support but cannot complete an online identity check. An authorised assistance channel can help navigate the process while preserving personal information and decision rights.
An identity-check barrier should trigger an approved support or exception route, rather than an improvised workaround. The helper’s task is to explain and facilitate the process while leaving identity decisions to the authorised service.
What a Gold Standard Requires
- An agreed support goal based on the user’s actual barrier and preferred level of help
- Clear consent for assistance, with the user able to review choices before submission
- Private credential entry and approved verification or delegation procedures
- Helpers who explain their limits and refer decisions to the authorised service
- Accessible support and workable authorised alternatives when the online route fails
- Checks that distinguish an attended session from a submitted application or resolved need
- Safe interruption procedures that protect information and prevent duplicate submissions
- Follow-through on unresolved referrals without making independence a condition of access
Assistance Should Be Understandable
Explain the steps, requirements and outcome in plain language so users know what is being done on their behalf.
Before touching a device or entering information, explain the proposed help and ask the user to choose how to proceed. Before submission, invite them to review the answers and explain the intended result in their own words.
Protect Credentials and Privacy
Support must follow approved verification and delegation procedures. People should not be encouraged to reveal passwords to untrusted helpers.
Observe a practice session using test information. The helper should explain where credentials are entered without asking the user to disclose them or retaining copies. If the approved route cannot verify identity, escalate rather than bypass the check.
Build Capability Where Appropriate
Assistance can help users learn useful digital skills without assuming everyone must become fully independent.
Offer a choice between guided practice and more direct authorised assistance. Ask whether the user wants to try a step themselves, and respect a decision to continue receiving support; independence is not a condition of access.
Alternative Routes Matter
Some cases require a non-digital or specialist pathway. The system should not trap users in repeated failed online attempts.
Test a case in which the online route is unsuitable because of an access need or repeated verification failure. Staff should identify an available authorised alternative, explain how to reach it and avoid sending the person back to the same failing screen.
Measure Resolved Outcomes
Count successful applications and correct decisions, not only assistance sessions.
Follow an assisted case beyond the appointment. Distinguish a saved draft, a received submission and a service decision. Check whether the user knows what remains to be done and whether unresolved needs have an accountable follow-up route.
Break-Test: An Assistance Centre Loses Network Access
Can urgent cases be managed safely and records reconciled after restoration?
Run an outage exercise with test cases. Stop steps that require a live verification service, explain what can safely continue and use only approved temporary records. On restoration, reconcile those records before submission to avoid duplicates or missing consent.
The Operating Loop
1. Understand the starting position
Ask what the person is trying to achieve and what is preventing progress. Consider language, accessibility, device access and confidence without assuming the same barrier affects every user.
2. Define the next useful outcome
Agree on a practical outcome with the user: understanding a requirement, completing a permitted step or reaching the right specialist. Explain what assistance can and cannot decide on their behalf.
3. Select a proportionate intervention
Choose an approved support route suited to that barrier and the user’s preference. Guidance, an accessible channel or specialist assistance may be more appropriate than repeatedly attempting the same digital task.
4. Execute with clear responsibility
Explain each consequential step, maintain privacy and let the user review their information and choices. Record only the support information needed under the service’s procedures and identify responsibility for any referral.
5. Measure and review
Check whether the intended service step was completed and whether the user understands its result. Record unresolved barriers separately from attendance counts, and ask whether the level of help respected their wishes.
6. Correct and preserve learning
Fix recurring barriers in instructions, accessibility or referral arrangements. Retest the support pathway with realistic cases, and retain only the learning needed to improve it rather than unnecessary personal details.
The handoff should carry the support need and agreed next step through an authorised channel. It should not require the person to surrender control of their account or repeat unnecessary sensitive information to each helper.
The Gold Standard Scorecard
- Successful service completion: distinguish attended sessions, submitted applications and resolved service needs; identify cases still awaiting a decision or further action.
- Privacy and security: check observed practice for private credential entry, authorised delegation and appropriate handling of any temporary records.
- Assistance availability: review whether users with different access and language needs can reach a suitable channel and what waits or failed referrals they encounter.
- User comprehension: ask users to describe what was submitted, what they agreed to and what happens next.
- Exception resolution: check whether cases outside the standard online pathway reach an authorised decision-maker and receive an explained next step.
- Service continuity: rehearse an interruption and verify safe resumption, reconciliation of permitted records and avoidance of duplicate submissions.
A shorter session is not necessarily better assistance. Compare completion and unresolved barriers across support needs, and include whether people understood and controlled the action taken. Do not treat continued reliance on help as a failure.
The Break-Test
Imagine a user cannot complete verification and a helper offers to use the helper’s own account instead. Can staff recognise that this changes who is acting, stop the workaround and locate an authorised alternative? Test whether the person receives a clear next step without being pressured to share credentials.
What Students and Professionals Can Learn
Map a supported application from the user’s perspective and mark where permission, privacy and understanding matter. Role-play asking for help, reviewing answers and declining a suggested step. Compare service completion with session counts to see why inclusion needs more than a throughput measure.
Sources and Connected Knowledge
How to Be the Gold Standard of Public Sector Assisted Digital Services
Assisted digital services succeed when people can obtain legitimate help without losing agency over their choices or information. Make support understandable, use approved verification and delegation, provide workable alternatives and follow unresolved needs through to a clear outcome.