Turing Scheme 2.0 – Email Verification

During Hypercare for the UK’s Turing Scheme, a security flaw was identified: some email clients auto-activated accounts without user action. I contributed to designing a new, GDS-compliant email verification flow under a two-week deadline. Working closely with content, BA, and dev colleagues, I produced 12 peer-reviewed iterations aligned with GOV.UK One Login patterns, covering both happy and error paths. The final flow closed the vulnerability, balanced usability with compliance, and restored confidence in a high-profile programme under intense political and media scrutiny.
The Turing Scheme 2.0 is the UK’s global programme for studying and working abroad, introduced as the post-Brexit replacement for Erasmus. Capita assumed delivery in April 2022 after the previous supplier withdrew, inheriting incomplete systems, political scrutiny, and significant media interest.
The project was huge in scale and complexity:
Timeline pressure: MVP had to go live by July 2022, just four months after mobilisation
High visibility: The scheme was regularly covered in national press as a symbol of post-Brexit opportunity/ or failiure depending on publication
Volume: By the end of the first cycle, the service was supporting over 41,000 participants and 512 institutional applications.
I worked on Turing Scheme 2.0 as a UX Designer and Researcher from concept to completion, shaping end-to-end journeys for applications, appeals, change requests, reporting, and payments — all aligned to GDS standards and WCAG compliance.
Within this massive programme, one particularly urgent issue arose during Hypercare: the need for a secure email verification flow for new registrations.
During the Turing Scheme 2.0 Hypercare phase, the Ops Team identified a flaw: some email clients auto-replied in a way that activated accounts without user action. This created a security risk at the point of registration.
The team urgently needed a code-based email verification flow, aligned with GDS patterns and precedents from GOV.UK One Login, that could be designed and implemented rapidly while addressing edge cases.
Security flaw: Auto-replies activating accounts without user action
Compressed timeline: Fix required during Hypercare while the live service was running
Edge cases: Expired codes, incorrect email addresses, and repeated requests
Compliance: Required to mirror GDS standards and GOV.UK One Login (Beta)
Iteration under scrutiny: Multiple stakeholder reviews in a compressed timeframe
The design process was deliberately fast-paced but structured, balancing co-design with compliance checks to keep the solution both usable and secure.
Co-design & iteration
I worked closely with a Business Analyst, a UX Content Specialist, and a Developer through a series of rapid co-design sessions. These workshops gave us space to test assumptions, challenge each other’s solutions, and refine the flow step by step. To anchor our work, we benchmarked against the GOV.UK One Login (Beta) journey, ensuring we weren’t inventing patterns in isolation but aligning with wider government standards.

Iteration of design - Composite view of all 12 design iterations created during Hypercare. Reflects the rapid collaboration between UX Designers, Content Specialists, Business Analysts, and Developers to refine flows, messaging, and error handling under tight deadlines
Design considerations
Not every idea made the cut. We trialled different approaches to validation and error recovery, discarding those that would have created friction or contradicted live GOV.UK precedents.
This mix of exploration and constraint kept the design simple enough for first-time users, while robust enough to close the security loophole.
various unhappy paths
The following screens illustrate a series of unhappy path flows, covering the most common error scenarios users might encounter during email verification. Each flow was designed to maintain clarity, provide recovery options, and ensure users were never left without a clear route forward.
Peer review & validation
Each iteration underwent structured peer review, with input from the Head of UX Design, a Lead UX Designer, and a Usability Consultant. Their feedback loops were critical in shaping and refining the final solution.
Accessibility was checked against WCAG standards
Tone of voice and error messaging were evaluated for clarity
Compliance was cross-referenced against GDS and One Login guidance
This cycle of design, review, and refinement ensured that the final journey was not only functional but credible to both end-users and stakeholders.
Outcome
The new verification journey delivered a secure, GDS-compliant fix to a live security flaw, while keeping the user experience simple and consistent with the rest of the service. Approved by UX leadership and endorsed by both the Ops Team and the Department for Education, the flow balanced speed of delivery with careful handling of edge cases such as expired codes and incorrect email addresses. By resolving the issue quickly without adding friction, the team not only closed a vulnerability but also strengthened confidence in a programme already under intense scrutiny.
The work on Turing Scheme 2.0’s verification journey highlighted how even small features carry weight in large-scale government programmes. A single flaw in account creation had the potential to undermine trust in the service, but applying GOV.UK standards and rapid peer-reviewed iteration ensured the solution was both credible and effective. It was a reminder that user-centred design is as much about resilience and confidence as it is about usability.
Big programmes hinge on small details: a single flaw in email verification posed reputational and operational risk.
Standards give confidence: aligning with GOV.UK patterns accelerated decision-making and won stakeholder trust.
Iterate fast, review often: 12 iterations in two weeks, grounded by peer review, avoided costly missteps.
Building on the verification work, the team focused on refining the wider Turing Scheme 2.0 experience through user feedback, improved reporting, and new operational tools — ensuring the service could scale while staying aligned with GDS standards and national priorities.