UK primary school
A 15-staff primary gets 5 hours a week back
5 hours a week of rota time, for £790 a year. Net saving about £13,646 a year after the Starter plan, 15 seats.
Read the study →Built by teachers · 30-day free trial · No card required
SchoolRota is UK school duty rota and cover software for primary, secondary and MATs. Log an absence and the board proposes who can step in, with reasons. Publish, and every midday supervisor, TA and office colleague gets a clear PDF rota they can open without logging in. Duty, lesson cover, lunch sittings and intervention sessions on one board.
The problem
Schools already run a rota. It lives in a spreadsheet, a printout on the staffroom wall, and one person's head.
At 07:40 the phone rings. Someone is off. The rota person opens the spreadsheet, works out who is free, who has already covered twice this week, and who cannot be moved off the gate. Then they rewrite it, print it, and hope nobody misses the update.
Intervention sessions are what get dropped. A TA is pulled to cover a class, the ELSA group does not run, and six weeks later nobody can say how many sessions actually happened.
Senior leaders ask for coverage and fairness, and get a recollection instead of a record.
The people are not the problem. The spreadsheet is. SchoolRota works out the cover, keeps the record, and gives staff one clear version to open.
What it saves
Figures modelled on published UK leadership pay and US BLS administrator wages. The rota is specialist work today, done early and under pressure. After setup, anyone in the office can run the day.
UK primary school
5 hours a week of rota time, for £790 a year. Net saving about £13,646 a year after the Starter plan, 15 seats.
Read the study →UK secondary school
8 hours a week of cover time, for £1,790 a year. Net saving about £23,131 a year after the Large plan, 88 seats.
Read the study →UK multi-academy trust
35 hours a week across five schools, for £3,490 a year. Net saving about £86,346 a year after the XL plan, 193 seats.
Read the study →Hours and money from the SchoolRota case studies, using STPCD 2025/26 (England excluding London) and US BLS May 2024 administrator wages, minus the matching annual plan. Your school will differ.
The product
The screens below use your school's duty areas, staff, preferences and session names. A small primary, a large secondary and a trust of twelve schools set it up the same way.
| Session | Who | When | Planned | Ran | Missed | Last missed because |
|---|---|---|---|---|---|---|
| ELSA · Y3 group | R. Brooks | Tue 13:30 | 6 | 6 | 0 | Never missed |
| Thrive · 1:1 | D. Okafor | Mon, Thu 09:15 | 12 | 9 | 3 | Pulled to lesson cover |
| Nurture group | J. Lewis | Daily 14:15 | 30 | 27 | 3 | Staff absent |
| Phonics catch-up | J. Lewis | Mon to Fri 11:00 | 30 | 25 | 5 | Pulled to lunch sitting |
| PPA · Y6 | S. Khan | Wed 13:00 | 6 | 6 | 0 | Never missed |
| Speech and language | M. Hill | Fri 10:00 | 6 | 5 | 1 | Pulled to gate |
Three kinds of work, one board
A break duty, a same-day lesson cover and a weekly ELSA group are different jobs with different rules. SchoolRota keeps them distinct, then puts them on the same board so a cover swap does not wipe a named session.
Gate, corridor, break, staggered lunch sittings. Set the weekly pattern once. Each day starts worked-out, and you only change what is different.
Log who is off. See what it touches: lessons from the imported timetable, duties, sittings. Ranked proposals with reasons, TAs before leadership, never a clash.
ELSA, Thrive, nurture, phonics, PPA. Timetabled as weekly blocks, protected from casual cover, and counted: planned, ran, missed and why.
How it works
Four steps, one record. One person owns the rota and decides. SchoolRota proposes cover, publishes it and keeps the history. Everyone else mainly receives the published rota.
A name, a reason, a time window. SchoolRota checks the imported teaching timetable, today's duties and any named sessions, and lists every post that now needs a person.
Proposals arrive ranked and explained: who is free, who is a TA, who has already covered this fortnight, who would clash with a duty or an ELSA group. Accept, swap, or pick anyone you like. Optional assistant suggestions stay in draft until you approve.
Publishing locks today's board, records who changed what, and notifies the people affected. Publish again later and the previous version is still there.
No login, no app to install. A clear PDF for the whole staff (Word if preferred), a personal calendar feed for those who want one, and Microsoft 365 write-back for schools that live in Outlook.
Morning all. Mr Patel is off today. Mrs Khan has Y4 09:00–10:00, Mrs Hill has lunch sitting 1. Everything else as the weekly pattern. The PDF is attached.
37 features · every plan
You define the duty areas and times, whether that is one playground or six corridors. It is not a teaching timetable builder. You can import teaching slots so cover works around lessons.
Define playground, dining hall, gate, corridor, bus bay or anything else, each with its own times, minimum and ideal headcount, and whether a lead is required.
Feeding KS1 at 11:45 and KS2 at 12:20? Add both times to the dining hall or playground and staff each one, or split a single sitting so one person covers the first half and someone else the second.
Set the pattern once per weekday and reuse it all term. Change the template and future days follow.
Mark who is asked Often, Sometimes, Only if needed or Never for duty, and let staff grades carry their own ask order so leadership are not first in the queue.
Tag qualified staff, such as first aiders, and require that capability on the slots that need it.
Record recurring weekly blocks so cover suggestions work around them: PPA, phonics, class cover, and named SEND or intervention sessions such as ELSA, Thrive, nurture or speech and language. Type your own name if you need it.
The small-group sessions your teaching assistants run each week, from phonics catch-up to ELSA and nurture. See who is running what each day, record any that did not happen, and see planned, missed and ran counts by session name.
Mark inset days, closures and non-term dates so nothing is scheduled when school is shut.
Log sickness, training or appointments in seconds, with partial-day times and an option to recompute the affected day straight away.
When a teacher is off, see uncovered lessons, allocate cover (including supply), and keep those choices through day rebuilds.
On a proposed draft, replace staff who clash with teaching or weekly blocks using clearer eligible cover, with reasons you can show a colleague.
Disagree with a suggestion? Swap anyone in or out of a draft slot before you publish. Changing the live board is designed to be quick when staffing shifts mid-morning.
When the only option is someone you would rather not use, the board says so instead of hiding it.
Book supply staff for a date range and have them appear in the candidate pool for that school and day.
The Today board refreshes as revisions are published, so the office and duty leads are not looking at stale information.
An optional start-of-day summary to the office, duty leads and SLT covering the day ahead.
Record when a session or duty did not happen, and why. See planned, missed and ran counts by session name (for example ELSA), filter to interventions only, and download a CSV. It tracks staff time, not pupil attendance.
A report in your school's colours showing what was missed and why, sent to the people you choose. Friday afternoon by default, with the day and time up to you, and quiet weeks send nothing.
Every member of staff gets their own duties by day, week or month, on phone or desktop.
Staff subscribe once and published duties (and optional teaching lessons) appear in Outlook, Google Calendar or Apple Calendar automatically.
Email and in-app alerts when a day goes live, plus an optional PDF rota emailed to staff on the board so they have a clear document without logging in.
See a person's duties, lessons and weekly blocks together, so it is obvious why they were or were not picked.
Bring your staff list in from CSV, including grade, cover preference and first-aid status, with a preview before anything is saved.
Import lessons from CSV so duty cover steers away from teaching time. Supports week A/B cycles and unmatched-staff review. Native MIS connectors and scheduled refresh are coming soon.
Paste last year's duty rota or an untidy spreadsheet and AI drafts the duty areas, times and staff list for you to check. It suggests, you approve, and it can be switched off entirely.
Included on new schools with a daily usage allowance. Day-to-day chat can record absences, arrange cover, fix double-bookings, list which interventions run on a day, summarise what was missed, and publish. Every change is previewed and approved; cover still follows your rules engine. Turn it off in Admin if you do not want it.
Day and week packs as PDF, Word, Excel and print layouts, clear enough to understand at a glance without logging in.
Optionally email the PDF (or Word) rota to staff on the board as soon as you publish, with a short message and the attachment.
Publishes, assignment changes, imports and admin actions are all recorded with who did what and when.
Load a clearly fictional sample school to train the office team without touching your real rota.
Owner, admin, duty lead, office, staff and viewer, each seeing only what they need. Admins can be limited to specific schools in a trust.
Sign in with Microsoft Entra ID, Google Workspace or Okta, so staff use the account they already have.
Create, update and deactivate accounts automatically from your identity provider, including mapping people to the right school.
Set publish rules for teaching clashes and class-cover gaps, choose calendar sync scope (duties, teaching or both), and turn teaching timetable or class cover on or off per school.
Your logo and colours across the portal, exports and email, so it looks like your school rather than ours.
A step-by-step wizard tuned to your school type, with progress saved so you can finish it over several sittings.
You pay for staff on the rota, not for the people organising it.
Optional AI
Optional chat can draft absences, cover and publishes for you to check. Cover still comes from your rules, with reasons you can explain, not from a model choosing who supervises children.
Every AI output is a draft. You see it, change it, and approve it before a single record is written, and each run is recorded in the audit log alongside the model that produced it.
Integrations
Published duties (and optional teaching lessons) can go into the calendars staff already check. Sign-in and staff records can come from your identity provider. Import the teaching timetable so cover does not clash with lessons.
Duties in Outlook, without anyone retyping them. Published duties can flow into staff Microsoft 365 calendars, or any calendar app through a personal subscription link.
Published duties (and optional teaching lessons) are written straight into staff Outlook calendars as events, and updated or removed automatically when the rota changes. It runs one way, from SchoolRota into Microsoft 365, so a duty cannot be deleted from someone's phone by accident.
Every member of staff gets a private subscription link from their My schedule page. Paste it into Outlook, Google Calendar or Apple Calendar and their duties (and optional teaching) appear alongside everything else, refreshing on their own without any IT involvement.
Sign-in and staff accounts, without a second password. School login and automatic staff sync are included on every plan rather than held back for an enterprise tier. Set it up once for the school or the whole trust.
Staff sign in with their school Microsoft account. No extra password to forget, and leavers lose access the moment their account is disabled.
The same school login flow for schools and trusts running on Google.
Any standards-compliant OpenID Connect provider can be configured with an issuer URL, client ID and secret.
Accounts are created, updated and deactivated automatically from your directory, so the staff list keeps itself current.
Map directory groups to SchoolRota roles, so your office team and duty leads get the right access without manual admin.
Trusts can send people to the right school using group names or directory attributes, which matters when staff work across sites.
Timetables and staff lists, brought in cleanly. Your MIS stays the system of record. SchoolRota reads what it needs to steer cover and never writes pupil or class data back.
Import lessons from a CSV export so duty cover works around teaching and weekly blocks, including week A/B cycles. Unmatched staff go to a review queue instead of being skipped.
Native connectors and scheduled teaching-data refresh are on the way. Today you import a CSV export from your MIS. SchoolRota never writes that data back.
Upload the staff list you already keep, with a preview of every row before anything is written.
Lesson times you import are used only to steer cover. SchoolRota never writes pupil or class data back, so your MIS remains the system of record.
Excel, Word, PDF and print packs mean the rota can still go on the staffroom wall or into a governor report.
Setup import and optional assistant chat call the OpenAI API. Only the text you paste or the operational request context is sent, never pupil data or your full rota history, it is not used to train models, and AI can be switched off for your school.
Notifications and the morning pack are sent from your school's branding, with a reply-to address you choose.
Tell us what you run, whether that is Entra ID, Google, SIMS, Arbor or a pile of spreadsheets, and we will tell you honestly what connects today.
MATs and groups
For UK multi-academy trusts, federations, diocesan groups and international school groups. Each school keeps its own duty areas, rota and daily board. Sign-in, billing and reporting stay central. A secondary and five primaries can sit in one organisation, each set up its own way.
Sign up as a group with two or more schools, or add sites as you grow. Each keeps its own duty areas, weekly template and daily board.
Run a primary and a secondary under one organisation. Each school gets its own school-type profile, duty area presets and setup wizard, so nobody is forced into a shared model that does not fit.
Central staff move between schools in one portal without logging out. Links, exports and notifications stay tied to the right school.
One school login and automatic staff sync setup for the whole group. Map people to schools with directory attributes or group names, and leavers lose access as soon as the directory says so.
A school office manager sees only their own school. Group-wide roles see everything. You decide who sits where.
Supply staff sit in a shared pool and can be dispatched to a school for a date range, without duplicate records or a second seat.
Roll coverage, unfilled posts and duty load up across every school, or drill into one. Compare schools over the same dates for a leadership or board report. Each school still keeps its own view of missed duty and intervention sessions.
Lesson cover and clash-aware resolve run at each school. Optional AI chat is available per site if you want it. Central roles can still see cover pressure across the group.
Microsoft 365 and Google Calendar sync and staff calendar feeds are configured once, with sync scope for duties and teaching, and branded exports carry each school's own logo and colours.
A single subscription and seat pool across every school. Someone who works at three of them still counts as one seat.
Getting a group started
For larger organisations we can help with onboarding, including school login, staff sync and site setup before you go live.
Choose a multi-site organisation at signup and name each site. The portal and school login setup cover the whole organisation.
Pick a school-type profile per site (primary, secondary, all-through, etc.), then complete duty areas, staff and the weekly template. Site admins only see their own school's data.
Set up school login and automatic staff sync once for the group. Map groups to roles and to individual schools, following our runbooks for Microsoft Entra ID, Okta or Google Workspace.
Publish the first week at one school, let the office team settle in, then repeat. Group analytics start filling in as each school goes live.
Safety and data protection
Staff names and rota data are school data. The points below are how the product actually works, not a slogan on a security page.
Production runs in London on Fly.io, with encrypted volumes and TLS everywhere. Every customer's data sits in the UK region today. We are the processor; your school is the controller.
Cover asks teaching assistants before office or leadership, respects each person's stated preference, and never places anyone on two things at once. The rules are yours and visible.
Every publish, swap and absence is recorded with who did it and when. Revision history stays with the day, so "what did the rota say at 08:00" always has an answer.
The SchoolRota assistant is off until you turn it on. Anything that changes the rota shows a preview and needs your approval. Cover still comes from the rules engine, not the model.
Intervention tracking counts staff time: which sessions were planned, ran or were displaced. Pupil names never need to enter the system. Nothing is used to train AI models.
Duty areas, lunch sittings, session names, preferences and branding are per-school configuration you can change on any day. Sign in with Entra ID, Google Workspace or Okta.
Evidence
Once you publish, you have a record: unfilled posts, who covered how often, when the day went out, and how many intervention sessions ran. Filter by school or across a trust. Weekly missed-session summaries go to the people you choose, in your school's colours.
Counts of staff time. Never pupil-level data.
Early feedback
Changes stay small, the PDF is the version staff keep, and support staff stay first in line for cover.
Changes that used to mean rewriting the whole rota can now be handled in a few clicks.
The published PDF gives staff one clear version they can open, print and keep.
It keeps support staff at the centre of cover decisions while leaving the final choice with us.
Who runs it
Most schools have one person who owns the rota and thirty who need to read it. Guided setup, cover policy and calendar sync get you live. If the first configuration feels like a lot, we can help.
Office manager, deputy or SENCO. Opens a worked-out board at 07:40, adjusts, publishes. In the modelled 15-staff primary, that is 240 hours a year back.
Asked first for cover, asked fairly, and never double-booked. A PDF and an optional calendar feed. No login required.
Know who is covering and when their TA is being pulled. Fewer corridor conversations, fewer surprises at 09:00.
ELSA, Thrive and nurture on the same board as duty, protected from casual cover and counted every week. Staff time only: no pupil is named and it is not an attendance register.
For pupil SEMH check-in and inclusion evidence, see Inclusion Loop.
A term view of coverage, fairness and publish time. A PDF for governors. Sign-off on cover decisions if you want it.
Each school keeps its own board. Sign-in, billing, a shared supply pool and reporting stay central. Seats counted once per person.
Small primaries, large secondaries, special schools, nurseries and all-through schools. Breakfast and after-school sit on the same board as break and lunch, and terminology adapts per phase.
UK pricing
GBP checkout for UK schools. A seat is a person on the rota, not a login. Admin and viewer logins are unlimited. School login, the AI assistant and reporting are on every plan. Try your own data for 30 days with no card, then choose monthly or annual card payment. One trial per school; school or trust email required.
A small primary or a single site with one rota person and a handful of TAs.
The typical primary or small secondary: duties, lunch sittings, lesson cover and a full intervention timetable.
Secondaries and large primaries with a bigger support team and more moving parts each morning.
Seats count the staff who appear on your rota, so a person who works across three schools in a trust still counts once. Seat limits are hard caps rather than surprise overage charges: if your staff list outgrows the plan, move up a tier whenever it suits you. The trial itself does not ask for a card. Currency follows your school country (GBP for UK and Ireland, USD elsewhere). UK schools can start their trial online. Annual card subscriptions cost the equivalent of ten monthly payments. Our savings examples put these prices next to what the rota currently costs in leadership time.
FAQ
Email us. We usually reply within one working day, UK hours. Or start a trial and set your portal up when it suits you.
hello@schoolrota.comYes. It is written for English and UK schools: duty rota language, midday supervisors, KS1 and KS2 lunch sittings, MATs, STPCD-priced case studies, GBP checkout, and production hosting in London. US schools can use the same product with roster wording.
Support staff rota software for schools, built by teachers for teachers. It runs break and lunch duty, staggered children's lunch sittings, same-day duty and lesson cover, and intervention and PPA sessions on one board. Suggestions are clash-aware, and staff get a PDF rota they can use without logging in. You keep a weekly template, turn it into a daily board, and confirm cover before anyone is notified. Optional AI chat can speed up the same jobs when you enable it. It does not build your teaching timetable, but you can import teaching slots so cover works around lessons.
Schools that run a support staff duty rota, typically one designated rota person (or small office team) who sets up and publishes, while other staff mainly receive the published rota. It works for primary, nursery, secondary, special and school groups. Breakfast and after-school sit on the same board as break and lunch.
There is a guided wizard with optional AI help to draft duty areas from an existing rota, plus admin controls for cover policy, teaching timetable and calendar sync. Many schools finish in under an hour; if setup feels fiddly, paste what you have and review the draft, or contact us for help getting live.
It is optional and off until you turn it on. Chat can record absences, prepare and publish days, assign or replace cover, list uncovered lessons, auto-fill lesson cover, resolve teaching clashes, list which interventions run on a given day, say how many were missed and whether named sessions such as ELSA ran, and explain the board. Anything that changes the rota shows a preview and needs your approval. Cover picks still follow your rules, not a black box. You can switch it off and the board still works.
Open Log in on schoolrota.com and enter the school name, the short portal name (for example riverside), or paste the address from your welcome email. That takes you to your school’s own sign-in page. We do not look up accounts by email on the main site.
One 30-day trial per school, with no card required and up to 500 active staff. Verify a school or trust email and create your password to start. Choose a monthly or annual card plan in Admin when you are ready. If you do not subscribe, you can still view and export existing rotas, but editing and publishing stop.
In UK and EU regions, with production hosted in London. Each school's data is isolated from every other customer, and a data processing agreement is available before you go live. Syba LLC holds Cyber Essentials certification.
Yes. Add two times to the dining hall or playground (for example KS1 from 11:45 to 12:25, then KS2 from 12:20 to 13:00) and staff each one, or split a single sitting so different people cover each half. Staff lunch breaks are a separate setting that takes someone off duty, so the two never get mixed up. SchoolRota does not record which children ate.
Yes. Add them as weekly blocks on the staff timetable: ELSA, Thrive, LEGO-based therapy, nurture, SEMH support, EBSA reintegration, or a name you type yourself. That person is then booked for the window, so cover does not put them on the playground at the same time. If a session is dropped, staff record why. Missed work then shows planned, missed and ran counts by session name, for the dates you pick, up to today. SchoolRota records staff time only. It does not name pupils, hold an EHCP or SEND register, or act as a pupil attendance register.
For pupil SEMH check-in and inclusion evidence, see Inclusion Loop.
Yes, as staff time. Interventions here means the small-group catch-up sessions that run to a weekly pattern: phonics, reading recovery, speech and language, maths catch-up. You add them to the timetable, see them on the daily board alongside duty, and record when one did not happen and why. The people you choose get a weekly summary by email, Friday afternoon by default, and you can change the day and time or turn it off. Quiet weeks send nothing. SchoolRota does not record which pupils attended, so it is not an attendance register.
Contact
Questions about a group rollout, calendar and school login setup, data protection, or just want a walkthrough? Pick the address that fits.
Read our security practices and data processing agreement, or browse the documentation.
30 days free, no card, full product on your own data. Set the portal up when it suits you, publish your first day, and see what 07:40 feels like when cover is already proposed.