MAT rota software. One board per school, one seat pool.

• Site-scoped access so a primary only sees its own board
• Shared Entra, Okta or Google school login across the trust
• Cross-site supply when you choose to allow it
• One invoice and one seat pool instead of five spreadsheets

Built for English trusts

A typical five-school MAT mixes two small primaries, a larger primary and a secondary. Each site still needs a named rota owner. SchoolRota gives them the same product, then lets a central officer see what is published without owning every playground post.

Security trusts already ask for

London hosting, a standard DPA, Cyber Essentials on Syba LLC, SSO and optional SCIM. Staff never share one login to a spreadsheet.

What it does not replace

A central officer does not take over every playground. Each school keeps a named rota owner and only sees its own board, unless you allow cross-site supply. The 35 hours is the five-school example, not a survey of trusts. Pay rates in that example come from the STPCD 2025/26 for England outside London.

Common questions

Is this only for MATs?

No. Federations, diocesan groups and international school groups use the same multi-site tools. UK trusts are the usual starting point.

Do we pay per school or per person?

Plans are priced by rota staff seats across the organisation, not by the number of schools. Admin and viewer logins are unlimited.

Can one primary see another school's rota?

Not by default. Access is scoped to the site. A trust lead can see what is published across schools without opening every post.

Where does 35 hours a week come from?

Each of the five schools in the worked example is at least at the 5-hour primary floor, the secondary is higher, and central staff spend more time chasing PDFs. The trust case study shows the split.

See also duty rotas, cover, federations and groups, the five-school example and UK pricing.