Platform overview

The SchoolsOut Child Handover Platform

SchoolsOut coordinates the operational period between the end of a formal activity and a child reaching the correct next person or destination.

No generic feature tour. Start with the workflow, exception or handover problem your team needs to solve.

Children move from a school campus toward parents, transport and supervised activities at the end of the day.
Different next destinations. One connected period of responsibility.

One connected responsibility

Support the people carrying a child through the end of the day

01Families

Manage changing plans, journeys and collection through a more coherent process.

02Operational teams

Share the current context across school, activity and transport roles.

03Organisations

Connect the events that establish where responsibility moved and when.

SchoolsOut workflow

A shared operational view across every handover

Workflow illustration based on verified capabilities—not a fabricated product screenshot.

01Coordinate
Current plan

Staff and families work from relevant information.

02Act
Live status

Each role progresses its part of the workflow.

03Confirm
Release record

The handover remains available for review.

A workflow, not a collection of badges

The platform combines school dismissal, parent changes, authorized pickup, arrival announcement, multiple pickup modes, live dismissal, notifications, transportation visibility, GPS, booking, car sharing, messaging and reporting.

Some capabilities require configuration or a particular operating model. SchoolsOut does not claim biometric verification, AI route optimization, financial settlement or automatic legal compliance.

Tools for organizations and families

Staff use a browser-accessible dashboard to manage student and parent information, delegations, requests and live dismissal. Parents use the app to submit changes, receive notifications and announce arrival in supported pickup flows.

Transportation and wider family-coordination tools extend the system beyond the school gate.

Built for several handover settings

The shared problem appears in public, private, charter and international schools, after-school providers, camps, sports academies, tutoring and enrichment settings, and transportation operations.

Language, terminology and workflow must be adapted for each setting. A UK collection process should not be described as a US carline, and a Middle East driver or nanny handoff may need different roles.

Implementation starts with process mapping

A useful rollout begins by documenting current pickup modes, decision owners, change deadlines, authorization rules, exception paths, communications and required records.

The demo and pilot process should then validate the real workflow, identify configuration needs and avoid promising functionality that is not available.

Frequently asked questions

What systems can stay in place when we adopt SchoolsOut?

Your student information, billing, payroll, routing and wider administration systems can remain. SchoolsOut focuses on the operational child journey and handoff between them.

Can one deployment support families working in Arabic and English?

Yes. Arabic localization and right-to-left presentation are supported alongside English. Terminology and workflows should still be agreed with the people using them.

Can carline, walkers, buses and after-school groups use different handoff stages?

Yes. Multiple pickup modes can follow workflows appropriate to their operation while remaining connected to each child’s current plan.

What should we bring to the first workflow review?

Bring the systems you use now, each pickup mode, change deadlines, authorization rules, exception paths and the record staff need after release. That makes integration and configuration requirements concrete.

A practical next step

See how SchoolsOut fits your handover workflow

Show us how children move through your organization today. We’ll focus the conversation on the workflow you actually need.