One door. Everyone walks into their own building.
One address and one sign-in for staff, students, parents, governors, inspectors and hirers.
What you see is decided entirely by who you are.
Staff
A role-shaped dashboard: their classes, their approvals, their register widget, their own progression.
Students
Skills passport, timetable, balanced homework, house standing, and evidence they log themselves.
Parents
Live view of the day, absence reporting, self-renewing consent, payments and conference booking. Siblings together.
Governors and inspectors
Scoped, time-bound, read-only views with every access logged and no export by role alone.
Their job, not the whole product.
A role-shaped dashboard: their classes, the register widget, their approvals queue, their own pay scale and progression. A form tutor and a finance lead sign in at the same address and would not recognise each other's screen. Nothing on it is decoration: every tile is a thing that person is expected to act on today.
Something they open willingly.
Parents get a live view of the day rather than a static timetable PDF, absence reporting that reaches the register directly, consent that renews itself, payments and conference booking. Siblings appear together under one login, because that is how families think. Students get a skills passport worth collecting, a balanced homework load and a house they actually belong to.
Full functionality
Every workflow below is specified with its trigger, its actor, the screen it happens on, the step sequence, the permissions and the edge cases.
01One address, one sign-in
- Staff, students and parents sign in with the identity they already have, through Google Workspace.
- No second password, no separate app to hunt for, no portal sold separately from the thing it is a portal to.
- What appears after sign-in is decided entirely by role, scope, clearance and purpose.
- The same address works on a phone, a laptop and a school display.
02The parent app
- Live view of the day: attendance, the timetable as it actually is today, and any change to it.
- Absence reporting that reaches the register, the office and the tutor at once.
- Consent that renews itself on a cycle, with a clear record of what was agreed and when.
- Payments for fees, trips, canteen and transport in one place, with the balance visible.
- Conference booking across siblings, so a family books once rather than three times.
- Messages in the family's preferred language and channel, with per-channel consent respected.
03The student app
- Skills passport with eighteen strands on one radar, updated from lessons, activities and life outside school.
- Evidence logged by the student, verified by staff, which is what makes it worth collecting.
- Timetable, homework with the workload already balanced, and house standing.
- Age-appropriate scoping, so a Year 3 view and a Year 12 view are genuinely different products.
04Governors and the board
- A scoped portal with the papers, the dashboards and the compliance position, without access to individual children.
- Board packs generated from live data rather than assembled the weekend before.
- Attendance, admissions, staffing and finance trend views at the level a governor actually governs at.
- Every grant is time-bound and logged, including a governor's.
05Inspectors and external parties
An inspector arriving with short notice needs evidence, not a tour of the file server.
- A read-only, purpose-scoped view opened for a defined window and closed automatically.
- Evidence mapped to the performance standards rather than to the school's own folder structure.
- Every read logged, which protects the school as much as the inspectorate.
- No export without a separate, named permission.
06Hirers, clubs and the community
- Facility hire enquiries, bookings, invoices and access, scoped so a hirer sees only their booking.
- Extra-curricular sign-up with capacity, staffing and consent handled in the same flow.
- Community events published to the website and check-in handled by scan.
- Safeguarding requirements attached to the booking rather than to somebody's memory.
07Notifications and consent
- WhatsApp, email and push through one queue, with per-channel consent held per person.
- Language preference respected, per recipient, not per school.
- Quiet hours and urgency rules, so an emergency message is not competing with a newsletter.
- Delivery and read state recorded against the record that sent it.
More of the platform
The school website publishes from the records that own the answer, so the site cannot contradict the school.
Two hundred specified trigger points, and a platform that treats Workspace as its identity, document and classroom layer.
Role, scope, clearance and purpose. Four layers, nine grant events, six revocation triggers.
See it running on real data.
A working demonstration on a live database, walked through by the people who built it. Forty minutes, no slide deck.