A contact list is not a collection plan
Emergency contacts, parental responsibility and today’s expected collector are related but different information. Staff need the appropriate current context without exposing unnecessary family data at the collection point.
SchoolsOut connects standing relationships, temporary delegation and the live plan to the physical handover.
Pause when the person and plan do not match
An unfamiliar or unexpected collector should not be resolved through memory or social pressure at a busy gate. The child remains supervised while staff use the setting’s verification and escalation procedure.
The workflow can make the conflicting plan visible, support contact with the appropriate parent or carer and record the eventual release outcome.
Support family flexibility without losing control
Grandparents, childminders, nannies, neighbours and separated households are part of normal collection life. Delegation needs a clear scope, effective period and review path.
SchoolsOut supports configured authorised and temporary collectors; it does not automatically interpret custody restrictions or substitute for professional decisions.
Review the whole collection point
A pilot should observe how children are staged, how adults announce arrival, which staff check permission, where exceptions wait and how the final child is reconciled.
Start with one location and include a dead phone, delayed adult, sibling split and changed collector.
Frequently asked questions
Can SchoolsOut distinguish an emergency contact from today’s collector?
Yes. The product position distinguishes standing relationships, the current plan and the adult who actually collects.
What if an unexpected person arrives?
Staff pause release and follow the setting’s verification and escalation process. SchoolsOut provides current context and supports the record; it does not make the judgement automatically.
Does it support temporary collection permission?
Temporary and delegated collectors are supported within configurable organisation rules.
Is there a manual fallback?
Manual and no-app fallback processes are part of the supported operating model and should be tested during the pilot.