Context
The Cam Academy Trust needed a repeatable way to deliver school websites. Each school brought different stakeholders, content, branding and integrations, while the trust needed consistent technology, quality and long-term support.
Treating every school as an isolated build would have repeated cost, risk and decision-making. The better product was a shared platform with a clear path from approved design and content to a dependable launch.
The challenge
The programme had to preserve each school’s identity without recreating the technical solution each time.
It also had to coordinate multiple dependencies: stakeholder decisions, signed-off design data, content readiness, cloud provisioning, databases, domains, deployment, forms, indexing, quality checks and handover.
My role
I gathered and clarified requirements, coordinated stakeholders and developers, translated signed-off designs into reusable patterns, and defined the hosting, database, deployment, validation, launch and handover process.
My role was to hold the programme together. That included sequencing decisions, making risk visible, giving specialists a clear delivery model and ensuring that a launch was not treated as complete until the operational checks passed.
Platform decisions
The delivery model combined:
- Reusable templates and configuration rather than separate technical foundations.
- Cloud hosting and managed databases provisioned to a known standard.
- GitHub Actions for repeatable deployment.
- Explicit validation gates before launch.
- Checks covering configuration, templates, integrations, forms, security and indexing.
- A documented handover into support and maintenance.
School-specific content and decisions remained stakeholder-approved. The platform automated repeatable technical work, not organisational judgement.
Outcome
Eight school websites launched from 20 to 27 April 2026.
The outcome was not only eight live sites. The trust gained a reusable platform and a documented rollout process that made subsequent delivery more consistent and supportable.
Exploring the next experience
A staging AI search prototype was later created for trust content. Its purpose is to explore whether users can ask natural-language questions across a complex information estate.
It remains a prototype while governance, privacy, content authority and operational questions are assessed. It is not presented as a production feature.
Evidence and limits
The case study demonstrates coordinated multi-site delivery, reusable platform thinking and controlled launch. It does not claim that stakeholder content work was automated or that the staging AI search has passed production governance.