Three facts that shorten many answers
- The system resequences dismissal; it removes no step from it.
- The outcome depends on school policy as much as on the software, and probably more.
- The manual path always remains — any vendor promising to eliminate it is promising what they cannot deliver.
The questions
The answers below are ordered by what is actually asked, from cost through to operational detail.
Frequently asked questions
What does a school dismissal system cost?
Cost has three parts: software subscription (usually per student or per school annually), hardware (screens and display points), and setup plus training. A fair comparison between vendors covers three-year total cost of ownership — including training new staff intakes, scaling, and data export on exit — not the first-year price alone.
Does the system track guardians all the time?
It should not. Sound design limits location use to the dismissal window and the defined geofence, records the crossing event rather than the journey trail, and deletes location records after a published retention period. Ask the vendor for that period specifically, in writing.
What happens if the internet drops during dismissal?
Automatic calling stops and the school reverts to its manual path. That is why a written, rehearsed outage policy is required: who declares the switch, how manual calls are issued, and how records are reconciled once service returns so no audit gap opens.
Does every guardian need a smartphone?
Full benefit requires the app, but the system must remain usable for those without one through a manual call from the dashboard. If a large share of your community lacks smartphones, factor that in before purchase — the impact will be smaller than advertised.
How many screens does a school need?
The count follows pickup points and student gathering areas, not floor area. The working rule: one screen at each pickup point, and one at every gathering area audio calling does not reach clearly. Classrooms near speakers may need only a teacher notification.
How does the system verify who collects a child?
By registering authorised collectors in advance with documented guardian consent, so the staff role shifts from personal judgement to matching against a record. This is completed by temporary authorisation for emergencies, recorded custody restrictions, and an immediate notification to the guardian at the moment of handover.
Does it work with school buses?
Yes, by the same logic: the bus location is treated like a guardian location, so students are prepared before it arrives. The effect is larger here because a bus serves a whole group at once.
Does it integrate with our school management system?
That depends on both systems exposing an API. Ask specifically: which data is synchronised (students, classes, guardians), how often, and who bears the cost of re-integration when either system is upgraded. Get the answer in the contract, not the proposal.
What happens to our data if we terminate?
The contract must state three things: the format in which your complete data is exported, a deadline after which the vendor's copy is deleted, and a mechanism by which you verify the deletion. Missing any of the three means you do not really own your data.
Does it reduce the staff needed?
The goal is not fewer people but a changed role: from issuing repetitive manual calls to verifying identity and completing a safe handover. Verification should never be rushed, and the system gives staff the time to do it properly rather than hurriedly.
When do we see a measurable effect?
Operational effect appears within weeks of stabilising a full grade — provided you measured a baseline before starting. Without a baseline you remain in an argument of impressions that cannot be settled.
Is it suitable for small schools?
If your dismissal finishes in minutes with no queue, the system has nothing to improve and its cost returns nothing. Value appears where there is genuine congestion or a regulatory need for a documented handover record.
Read next: