Freeze the offer and first-use journey as one review object
Capture the sales promise, plan, checkout, confirmation, receipt, welcome sequence, tasks, status messages, help, recovery, and feedback path for the same version and audience. Name the owner who can block launch. An onboarding audit cannot pass while the commercial page and operation describe different realities.
Use pass, revise, escalate, and stop. Stop when delivery, price, renewal, access, support, or a material prerequisite contradicts the offer. Escalate regulated, financial, privacy, rights, or accessibility questions. Mark unknown as unresolved, never as implied pass.
Evidence: GOV.UK Design System; UK Government Digital Service; UK Financial Conduct Authority
Points 1–4: promise, status, record, and immediate action
Point 1 inventories the claims and conditions that shaped the customer's decision. Point 2 states whether order, payment, application, account, or access is complete, pending, failed, or duplicated. Point 3 provides an appropriate reference and transaction or service record. Point 4 gives the smallest necessary next action and who owns it.
Test all major states with authorized data or prototypes and document what was actually observed. Do not claim a real purchase or completion when only a design review occurred. Protect sensitive information on confirmation pages and shared devices.
1. Decision-shaping promises are mapped.
2. Completion or pending state is unambiguous.
3. Reference and required record are available.
4. Immediate next action and owner are clear.
Evidence: GOV.UK Design System; UK Government Digital Service
Points 5–8: prerequisites, sequence, effort, and timing
Point 5 lists mandatory equipment, documents, software, permissions, skill, language, payment, and data. Point 6 orders tasks by dependency and separates optional work. Point 7 states setup, learning, maintenance, and customer effort. Point 8 gives evidence-based time ranges and explains uncontrolled dependencies.
Any prerequisite that materially changes fit should also appear before purchase. Allow save and return where appropriate. Avoid exact duration when manual or third-party events dominate. Tell customers what pauses progress and what happens when an estimate passes.
5. Material prerequisites are visible before and after purchase.
6. Task order and optional branches are explicit.
7. Human effort is represented honestly.
8. Timing range, dependency, and delay response are defined.
Evidence: GOV.UK Design System; UK Government Digital Service
Points 9–12: progress, support, accessibility, and privacy
Point 9 maps every progress label to an actual event and next owner. Point 10 provides a consistent help location, channel, hours, response expectation, reference, and escalation. Point 11 reviews keyboard, screen reader, zoom, captions, language, cognitive load, and non-digital alternatives with appropriate expertise. Point 12 limits data requests to stated service purposes and protects records.
A moving indicator is not evidence of progress. W3C guidance on consistent help informs one accessibility aspect but does not certify conformance. Record the scope and methods of any access review rather than using an unsupported accessible label.
9. Customer-facing progress is evidence-backed.
10. Help and escalation are predictable.
11. Access barriers and alternatives are reviewed.
12. Data collection is necessary and explained.
Evidence: UK Government Digital Service; W3C Web Accessibility Initiative
Points 13–15: error recovery, interruption, and human handoff
Point 13 provides specific error language, preserved work, and a recovery action. Point 14 tests interruption, return, lost credentials, missing messages, failed payment, and unavailable documents. Point 15 transfers context between automation and people so the customer does not repeat the entire story.
Define high-impact escalation and service ownership. A workaround is not a permanent pass when it excludes customers or repeats the same failed channel. Record unresolved recovery risks and launch conditions explicitly.
13. Errors explain cause boundary and recovery.
14. Interrupted journeys can resume safely.
15. Human escalation preserves relevant context.
Evidence: GOV.UK Design System; UK Government Digital Service; W3C Web Accessibility Initiative
Points 16 and 17: feedback route and change control
Point 16 links repeated confusion, abandonment, duplicate action, early cancellation, and support reasons to the promise or process owner. Point 17 assigns triggers and downstream locations for offer, terms, workflow, support, accessibility, privacy, or product changes. Feedback without decision ownership does not close the loop.
Maintain version, evidence date, issue, impact, owner, action, deadline, and recheck. Correct the earliest source of an expectation gap, then rerun dependent steps. Preserve only data appropriate for service improvement and applicable privacy duties.
16. Feedback has a responsible correction owner.
17. Material changes reopen affected audit points.
Evidence: UK Government Digital Service; UK Financial Conduct Authority
Approve a bounded start experience and schedule revalidation
Ask an uninvolved reviewer to state what was bought, whether it succeeded, what comes next, required effort, timing, help, and recovery. Compare the response with the evidence record. Approve only the named audience, product, version, channel, and jurisdictions. A favorable total cannot offset a hard contradiction or inaccessible critical path.
Recheck by 2027-02-10 and sooner after a point-17 trigger. GOV.UK sources are official service-design references, FCA material is a scoped financial-services example, and W3C is an independent accessibility authority. None turns this audit into legal or conformance certification.
- Pass the frozen journey only.
- Revise when current operation supports narrower expectations.
- Escalate regulated or specialist questions.
- Stop when promise, access, recovery, or ownership fails.
Evidence: GOV.UK Design System; UK Government Digital Service; UK Financial Conduct Authority; W3C Web Accessibility Initiative
Sources and further reading
These references informed this article. A source supports a claim; it does not imply endorsement of TenMultigure or any future product reference.
- Confirmation pagesGOV.UK Design System · Accessed August 10, 2026
Supports the release points for completion state, transaction record, next step, timing, contact, and feedback using an official UK pattern.
- Set up and manage user supportUK Government Digital Service · Accessed August 10, 2026
Informs the audit of support demand, channels, escalation, handoff, service ownership, evidence, and improvement from recurring onboarding issues.
- About the Consumer DutyUK Financial Conduct Authority · Accessed August 10, 2026
Adds a scoped UK financial-services perspective on understandable information and lifecycle support without defining universal onboarding duties.
- Understanding Success Criterion 3.2.6: Consistent HelpW3C Web Accessibility Initiative · Accessed August 10, 2026
Provides independent accessibility context for predictable help placement while not certifying the audited path against WCAG or other standards.
Reviewed by TenMultigure Editorial Team. See an error or a source that has changed? Tell the editorial team.
Review method: AI-assisted desk research with editorial checks. Reviewed ; next scheduled review . Rebuilt TM-285 as a seventeen-point onboarding release audit covering promise, state, prerequisites, effort, progress, support, accessibility, recovery, feedback, and change control.