Trust Transition Plan

One planned move, timed around every contract end date.

A planned, phased school website migration for multi-academy trusts with several sites, several suppliers and a different end date for each. Schools join around their existing agreements, so the plan is built to keep you from paying annual website fees twice. There is no single launch day. Each school goes live as its own contract allows.

Where trusts start

Three things make a trust move hard. Most trusts are carrying all three.

None of them is a mistake. They are what a growing trust inherits, and they are exactly what a good plan is for.

  1. Several school websites

    Each school built its site in its own time, with its own builder and its own habits. Structures differ, so do standards, and few trusts have the whole picture in one place, from pages to documents to forms.

  2. Existing suppliers

    Every agreement has its own terms, its own notice and its own way of handing over. Domain names and email arrangements sit alongside them. Someone has to read it all, and know who holds what, before anything can move.

  3. Different contract end dates

    One launch day for every school would mean paying one supplier while starting another. So we do not plan around a launch day. We plan around your dates.

The plan

Five stages, in the order your contracts allow.

Scroll through the stages and watch the move take shape. Every school keeps its existing agreement until it ends, and the new site is ready to begin as it does.

  • Existing agreement, kept until it ends
  • One foundation for the whole trust
  • Each school's own identity
  • New site live, numbered by launch order

A schematic of the method, not a real trust. Your lanes are your schools and your dates.

  1. Understand the trust

    We start by listening. How the trust is structured, how decisions get made, who looks after each school's site today and what has frustrated people so far. Before a single page is planned. Then a practical, school by school inventory of what each site holds today.

    • What does each school's site hold today: pages, documents and forms?
    • Who looks after each school's domain name and email arrangements, and who has access? (Recording this does not mean either has to change.)

    A shared picture of the trust, in plain words.

  2. Map the contracts

    Every existing agreement laid side by side: what it covers, when it ends, what notice is needed and what has to be handed over. The end dates become the spine of the whole plan.

    • When does each agreement end, and how much notice does it need?
    • What has to be handed over at the end, and by whom?

    One schedule, built from your real dates.

  3. Design the trust once

    The shared foundation is designed centrally: structure, templates, accessibility standards and the way the trust presents itself. Built once, so every school that joins inherits it.

    • Who approves the trust-wide standards and templates?
    • Which decisions stay with the trust, and which belong to each school?

    Trust-wide consistency, decided in one place.

  4. Shape each school's identity

    Then each school gets its own look, its own voice and its own pages for its own community, inside the trust's foundation. A small village school should not look like a copy of a large secondary.

    • Who at each school signs off its content and look before launch?
    • Which pages do that school's families rely on most, so they get the most care?

    Schools that still feel like themselves.

  5. Build and launch in phases

    Schools are built and launched in the order their agreements end. Each one goes live as its previous supplier steps back, while the next is already in build. Our current offer is that annual fees activate when previous agreements conclude.

    • Before each launch, and again after it, do the key parent journeys, links and redirects from the old site work as planned?
    • Is each school's team trained and ready to look after the new site?

    A launch for every school, on a date that suits it.

One trust, many schools

Consistent where the trust needs it. Individual where the school does.

A trust wants to look like one organisation. A school wants to look like itself. The plan settles which decisions belong where, so nobody has to choose between the two.

Which decisions are made once for the trust, and which belong to each school
Area Decided once, for the trust Shaped by each school
Structure One shared way of organising a school site, so families and staff find things in the same place wherever they go. The pages and sections that school's own community actually needs.
Look and feel The design foundation: type, spacing, layouts and the way the trust presents itself. Its own identity inside that foundation, from imagery to the character of its pages.
Accessibility and standards Built into the templates once, so each school that joins starts from them. Its own content, kept in good order by its own team.
Voice How the trust speaks about itself and what it stands for. Its own news, its own words and the things only that school would say.
Sign-off and responsibilities Who approves the trust-wide standards and templates, and who looks after the shared foundation. Who at the school signs off its content and look before launch, agreed in advance.
A small village school should not look like a copy of a large secondary, and a trust should not look like a handful of unrelated sites.

Not paying twice

A move that follows your contracts, so the fees follow too.

Most of the worry in a trust move is money and timing. Which supplier is still owed, what starts when, and whether the trust is covering the same site twice. The plan is built so those questions have answers before anything is launched.

Moving a single school rather than a trust? Our guide to switching your school website provider without double paying covers it.

You get the people who built it, and fifteen years of doing this.

school websites launched
1,000+
compliance audits completed
2,500+
school staff trained
5,000+

Start with a conversation

Tell us which contracts end first. We will build the plan from there.

Bring a list of your schools and, if you have them to hand, the dates their agreements end and who looks after each school's domain name. It does not need to be tidy. Sorting it out is the first job, and you will be talking to the people who do it.