Staff HR and access governance
Corporate HR software was not built for a school timetable.
Two time-in-lieu engines, because teaching and education support staff accrue it differently — alongside leave, holiday check-ins, performance review cycles, and a role-based entitlement engine that grants and revokes system access as people arrive, move and leave.
Scattered HR spreadsheets, generic corporate HR tools, and manual IT onboarding emails.
myHR by Sprout
Time in lieu, reviews, holiday check-in and staff system access.
What it does.
Teaching and education support workflows, separately
Two time-in-lieu engines, because they are two different things: an acquittal model for teachers, a request and ledger model for education support staff.
Automated access lifecycle
A role-based entitlement engine works out exactly which system access to grant or revoke when someone joins, moves or leaves.
Review and feedback cycles
Performance review management with peer assignments, leader reviews and archived historical cycles.
Holiday check-in and directory
Location check-in for holiday work periods, alongside the school's organisational hierarchy.
HR and IT finally share one system that knows teaching staff and support staff work under different rules.
Shared platform
The part that makes the suite worth more than the app.
One staff record, shared across the suite.
myHR runs on the same staff record, the same sign-in and the same permission model as every other Sprout app. Staff do not maintain a second list of people, and a change made once is a change everywhere.
It connects to:
- Student information systems
- Learning management systems
- Single sign-on providers
Talk to us
The useful first conversation is about what you already run.
Tell us about your school.
myHR is available now. Schools often start with one app and add the rest as they go, which is exactly how Sprout is designed to be adopted. We will quote it against your enrolment and what you are already running.