Case Study · Amazon LBA4 · 2025/26

Six interns. One neurodivergent job coach. A better way to get through the working day.

Six neurodivergent young adults started work inside Amazon LBA4 alongside a neurodivergent job coach supporting them through the same working days. Together, they encountered the things that can make a workplace unnecessarily difficult: unfamiliar routines, changing expectations, knowing what happens next, remembering tasks, interpreting unwritten rules, knowing when to ask for help and trying to explain afterwards how the day had actually gone.

We didn't begin by building an operating system. We began by trying to make the next working day easier. That work became My Work Buddy, created by AbilityBridge and shaped through the real experience of the people using and supporting it. AbilityBridge OS grew around it afterwards — giving job coaches, employers and providers the professional tools needed to coordinate better support around the person.

Provider
Aspirations Doncaster
Employer
Amazon LBA4
Programme
Supported internship
Go-live
May 2026
A real
deployment

The situation.

In September 2025, Aspirations Doncaster started its first supported internship cohort at Amazon's Doncaster fulfilment centre (LBA4): six young adults aged 18–24, all with an Education, Health and Care Plan, working a full week inside a live operation alongside Amazon associates.

The programme is structured around supported internship principles — workplace-based learning, real job tasks, and a clear progression path toward paid employment. Each intern rotates through different departments at LBA4 (Fluid Load, Receive, Reception, Manual Sort), supported by a dedicated job coach, named mentors, and an Employer Programme Lead on Amazon's side.

Like any large workplace, Amazon has its own rhythms, language, systems, routines and unwritten expectations. The job wasn't to shield interns from a real workplace. It was to give them enough structure, understanding and support to navigate one successfully — while progressively building independence. That distinction shaped AbilityBridge.

By January, it was clear the support infrastructure couldn't keep up with the programme. Attendance lived in a spreadsheet. Cohort communication ran on WhatsApp. Daily check-ins, mood, breaks, task progress, mentor visits, employer conversations and safeguarding moments lived in the job coach's memory and a printed planner.

"At any given moment I knew exactly how each intern was doing. I just had no way to prove it to anyone else."

The choice we faced.

The default option was a generic case management system. We looked at several. Each was built for a different problem — caseload management, social care reviews, education compliance — and would have forced the programme to bend around the tool.

The alternative was to build something. We started with one screen — the intern working-day flow — and shipped it into the live cohort.

First, we built around the working day.

The first priority was the person going to work.

My Work Buddy brought the working day together on the device already in their pocket. It helped make visible:

  • how the person was feeling as the day began
  • what their working day looked like
  • what happened next
  • routines and transitions
  • breaks
  • workplace tasks broken into clear visual steps
  • trusted people and routes to support
  • end-of-day reflection

Instead of expecting someone to hold an entire working day in their head, the support could be there when they needed it.

Then the programme grew around the person.

Once the individual experience was working, another need became obvious. Job coaches, mentors, employers and providers needed enough visibility of the working day to provide the right support without constantly interrupting it.

That became AbilityBridge OS — the professional layer around My Work Buddy, bringing together programme oversight, safeguarding, learning, employer collaboration, visual task creation, evidence and outcomes.

The working day became visible.

  • the person could see what happened next
  • quick check-ins provided a simple signal about how the day was beginning
  • routines and breaks became easier to anticipate
  • visual task guides reduced dependence on repeated verbal instruction
  • support was easier to find when needed
  • reflection captured how the working day actually felt
  • patterns could help prompt a supportive conversation when useful
  • growing independence became more visible over time

The programme benefits followed from there — attendance in one place, reporting, employer visibility, evidence and reduced administration — all enabled by AbilityBridge OS sitting around that individual experience.

6/6
Interns using My Work Buddy for their working day at the May 2026 full-week go-live.
1
Source of truth for attendance, replacing spreadsheets and printed registers.
~4hrs
Job coach time per week recovered from manual reporting and chasing.

The most significant change wasn't simply moving information from paper into software. It was that the working day became more visible. An intern could see what came next. A job coach could understand where support was needed without relying entirely on memory. A mentor could contribute. An employer could see progress. And small moments of growing independence began creating evidence.

For the first time, the programme could record not just whether someone attended work, but how they were learning to navigate work. Mood at check-in. Tasks completed. Mentor interventions. Employer feedback. Safeguarding notes. Reflection at end of day. All time-stamped, all role-attributed, all in one place.

That data didn't previously exist. Not because the job coach wasn't paying attention — it's because there was no way to capture it without slowing the work to a halt.

What we got wrong.

We're including this section deliberately. Case studies that don't admit limitations are marketing, not evidence.

Neuroinclusive design isn't achieved by putting the word "accessible" on a product. It comes from noticing when something creates unnecessary pressure, admitting it and changing the design.

What didn't land first time

The mood check-in. The first version asked every intern to explain why they were feeling whatever they reported — including on positive ratings. We learned quickly that asking an autistic intern to explain why they're "okay" implies something is wrong. Now cause prompts only fire on the two lowest ratings.

Lunch-end persistence. An early bug meant interns coming back from lunch could lose their state if the browser tab slept. We've since established a hard engineering rule: anything an intern might walk away from has to persist to the database immediately, not via an undoable timer.

The reporting layer is still missing. The data is there for SiQAF, EHCP progress reports, DWP returns and employer conversion evidence. The assembly layer that turns that data into the reports themselves is in development, not in production. This is the next major piece of work.

What's next at LBA4.

The Amazon LBA4 cohort continues through the 2025/26 academic year, with progression conversations starting in spring. The platform will pick up two more programmes in September 2026 — ASDA Carcroft and GXO Armthorpe — both delivered by the same Aspirations Doncaster team.

Each new site is a test of the platform: does it adapt to a different workplace, a different rotation pattern, a different employer programme lead? If it does, the case for AbilityBridge as a sector-wide platform starts to make itself.

Want to see it running?

If you run a supported internship programme — or you're scoping one — we'll show you AbilityBridge against real data, including the parts that aren't finished yet. No sales deck, no pretending.

Book a demo →Read our story