VANTAGEFRIDAY · 7:42 AM
An SLSO called in sick at 7:42.
By 8:10 the day was re-covered, the changes were on staff phones, and the evidence had already written itself. Vantage plans SLSO support for continuity and absorbs the on-the-day mess.
One SLSO away.
By the end of the day the same board becomes the record: sessions marked delivered as they happen, absences reason-coded, nothing to reconstruct later.
01 · WHO IT’S FOR
The coordinator
Builds the roster once, for continuity. When a student is marked absent, the roster automatically moves the SLSO to the backup student — no more manual roster rebuilds.
The SLSO
Opens a phone and sees now, next and later: which student, which room, what the support plan asks for. Marks support delivered in one tap & can note observations in real time.
School leaders
See coverage, clashes and continuity live. Every hour of support, tagged with a reason and a date — so when funding is questioned, the evidence is already built.
02 · THE WEEKLY BUILD
Coverage is planned, not hoped for.
A weekly roster that keeps the same SLSO with the same student wherever staffing allows, inside your staff hours and student plans. The coverage figure updates in real time — so as the roster changes, it stays accurate. The continuity figure updates live as backup students are used or manual changes are made, meaning these decisions are deliberate, not accidents.
03 · COVER, DECIDED BEFORE THE BELL
The 7:50 scramble, absorbed.
Mark a staff member away and Vantage ranks who should cover each session — by continuity with the student, funding context and availability. Same-room options are suggested first. One decision per session, then the day republishes to staff phones.
04 · THE RECORD, AS IT HAPPENS
Accurate reporting, when you need it.
Support staff mark what was delivered as it happens. Delivered sessions, absences and reason codes accumulate into planned-versus-delivered hours by funding code and NCCD level — export-ready reports on demand, because delivery and observations are logged in real time.
05 · ON A PHONE, IN A CORRIDOR
The day has to make sense on the go.
SLSOs don’t sit at desks. My Day shows the current session, the next one, the room, and the one action that matters — mark delivered. If a student is away, that’s one tap too, reason-coded for the record.
- Can an SLSO see who they’re with next, from the playground?Yes.
- Does marking support delivered take more than one tap?No.
- When will the coordinator know if Period 3 wasn’t delivered?Real time.
06 · WHO HOLDS THE DATA
The boring parts, in writing.
The short version is below — for the full documentation, refer to the trust centre.
| Data residency | Student records are held in Australia: the database (Supabase) and the application compute (Vercel) both run in the Sydney region — details in our sub-processor list. |
|---|---|
| Access | School-scoped. Staff see their school; support access is separated and audited. |
| Changes | Draft before publish. SLSOs act only on the published roster. |
| The record | Delivered support, overrides and reason codes are kept with dates and actors. |
| Timetable | Daily work starts from your timetable import, not hand-rebuilt data. |
BOOK A DEMO
Bring the messy version of your timetable.
A 20-minute demonstration, on your own structure: the weekly build, a staged 7:50 scramble, and the record it leaves behind.