From system struggles to sustained stability.

Plymouth Learning Partnership provides shared services to schools across Plymouth, Devon and Cornwall, including Supply Plus, their managed supply teacher and staffing system. When the agency responsible for the system decided they could no longer support it, PLP were left needing a new partner, fast. A developer within their own team recommended Jump24.

This wasn't a system we could learn from documentation alone. Supply Plus sat at the centre of how PLP's schools access staff, so understanding it properly meant understanding more than the code.

We started with understanding, not action. Before touching anything, we looked at how the system worked, how it integrated with PLP's wider business, and what it meant day to day for the team who relied on it.

With that understanding in place, we planned a hosting migration to AWS, provisioned using Terraform. We scheduled the move for a quiet period, so the transition had minimal impact on PLP and the schools depending on the system.

Once the migration was complete, our role shifted to ongoing support. Not just fixing issues as they arose, but working with PLP to shape features that helped their team work more efficiently. We also helped them put together a business continuity plan: a clear, reviewable playbook covering what could go wrong and exactly what to do if it did.

We turned an unsupported system into one PLP can rely on. Supply Plus moved to modern, resilient hosting without disrupting the schools and staff who depend on it every day.

Beyond the migration, PLP gained something they hadn't had before: a plan. A business continuity playbook means the risk of losing support again isn't just managed reactively, it's planned for. Combined with ongoing optimisation, the system now works harder for their team, not just alongside them.