Illustrative photograph of school leaders reviewing plans together

A shared direction. A distinct voice for every school.

Name: rel-ease
Rating: 5.0

Give your multi-academy trust a connected way to manage school websites and communications. Central teams gain authorised access to separate school accounts, while each school keeps its identity and local voice.

Discuss your trust’s setup Explore re-group

One trust. Distinct schools.

When websites and approvals sit in separate places, central teams spend time finding the right person and the right version. re-group connects the accounts so trust colleagues can support each school in its own working context.

Your trust account

Set shared direction. Organise linked accounts, authorised access and approved brand guidance.

Authorised oversight and approved shared guidance

A
School A
- Own identity
- Website
- People
- Resources
B
School B
- Own identity
- Website
- People
- Resources
C
School C
- Own identity
- Website
- People
- Resources

Illustrative account structure. Each school has a separate working context. Access follows assigned permissions; school notes and project material do not automatically become shared knowledge.

The rel-ease website viewed on a phone, built with Web Studio

School websites with a familiar welcome.

For a parent checking an open-evening date on the way home, the best website gets them to the right answer. Web Studio helps each school make its information clear on the phones families actually use.

School logos, colours, photographs and stories can be distinct, with shared brand guidance providing direction. Teams edit on a desktop and preview smaller screens before publishing.

Shown here: rel-ease’s own mobile website, built with the same native Web Studio blocks.

Explore Web Studio

Detail of a real Site Optimiser finding, with a recommended next step and actions to review or view the page

Website oversight, made practical.

An authorised trust colleague can open a school’s account and check its published rel-ease website, including Web Studio pages. Site Optimiser highlights details such as missing headings, search descriptions, image alternatives and page destinations.

Use the findings alongside your team’s review of admissions dates, policies and governance information. Staff decide what needs changing and check the published result.

Shown: a detail from a real finding from rel-ease’s own website. These checks support human oversight; they do not certify DfE compliance or replace legal review.

From a shared brief to a local welcome.

Trust-wide communications still need a local voice. Take an admissions campaign: agree the shared direction, then give each school room to make its own invitation.

Prepare the message
Use re-think to shape the brief and draft copy. Each school adds its dates, photographs and local welcome using its own account context.
Planning · re-think
Review the right version
Bring the material into a re-flow project. Invite the relevant people to comment, request changes and record an approval decision against the work.
Feedback · re-flow
Publish with purpose
A team member publishes the agreed school page. Add a form or event booking where useful, and promote it through configured marketing channels.
Publication · your team

Useful thinking. Clearer decisions.

Staff stay responsible for the facts, the school’s voice and what goes out. Approval in re-flow does not automatically publish or send anything.

re-think

Talk through a plan, start with a Springboard activity and return to saved drafts in My Work.

Explore planning and content

re-flow

Keep project files, versions, feedback and review decisions close to the work.

Explore review and approvals

Three moments when it makes a difference.

Familiar work, with a clearer way through.

Open evenings across the trust

Families get the right date, booking details and a welcome from their school. Central teams keep sight of the agreed message. The campaign feels connected without making every invitation identical.

A website review that leads somewhere

Open each school’s active-site checks and review its public information. Turn findings and outdated content identified by staff into amendments to agree, publish and check.

A new school joins the network

Create or link its account, agree access and provide the relevant shared guidance. Keep the school’s branding and local context while its team and trust colleagues prepare and review the new website.

Start with a few schools. Build from there.

Begin with connected school accounts and websites. Add planning, review, forms or events when they have a clear job to do. Introduce the setup school by school.

The website builder is free while using rel-ease. Hosting, paid modules and provider charges are separate. Activate what you need, pay for the modules you use, with no contract.

Discuss the account structure and costs for your trust with us. re-flow is available now; its pricing has not yet been finalised.

Questions before you start.

Can each school keep its own website and identity?

Yes. An existing external website can stay in place while you use other rel-ease tools; its editing stays with its current platform. Schools using Web Studio can each have their own website, logo, colours and local content within separate accounts.

How does central oversight work, and can trust staff help?

re-group connects a parent trust account to linked school accounts. Authorised trust owners and administrators can enter a school’s account to support its work, using the tools enabled there. Access follows the account relationship and assigned permissions.

Is information kept separate between schools?

Each school has its own account context, people, resources and business knowledge. School notes and project material do not automatically become shared knowledge. Approved guidance can be provided to the relevant schools, while central access follows assigned permissions.

Can we begin with websites and add other modules later?

Yes. Start with connected accounts and school websites, then activate additional tools when a specific need emerges. We can discuss the modules and costs for your first group of schools.

Does rel-ease replace our MIS or specialist education software?

No. rel-ease supports public websites, communications, planning and shared review work. Keep your MIS and specialist education systems for the jobs they already do. We can discuss any integration requirements separately.

How could we move our existing school websites?

Discuss the existing sites, content, domains and who maintains them with us. We can work through a phased approach and what would need to be rebuilt or moved before agreeing a plan. An external website does not transfer automatically into Web Studio.

How do we handle website information and approvals?

Use Site Optimiser to check the school’s published rel-ease pages, alongside staff checks of dates, policies and required information. re-flow keeps versions, feedback and approval decisions with the work. A team member then publishes the agreed changes. Responsibility for accuracy and publishing requirements stays with your trust.

Let’s work through your school network.

Discuss the account structure, the first schools to involve and the work you want to make easier. Bring your current setup and priorities; we can explore a practical starting point for your trust.

Discuss your trust’s setup