OSHC Pickup, School Transport and Child Handover Software for Australia

A child may move from class into OSHC, leave with a parent or authorised nominee, board school transport, travel to sport or be collected by another family. SchoolsOut connects the current plan across those transitions so educators, school staff, transport teams and carers understand who is responsible next.

The product sits beside school administration, childcare subsidy, billing and fleet platforms. Its role is the child-logistics layer: book, expect, coordinate, travel, arrive, authorise, release and confirm.

An OSHC booking establishes expected attendance. Providers still need to know whether the child arrived from school, whether the family reported an absence, who is authorised to collect, whether the carer is delayed and when the child left care. SchoolsOut keeps those states in one operational flow.

Casual and recurring bookings, same-day changes, parent notifications and release history support ordinary family flexibility. The service retains control of booking cut-offs, collection procedure and regulatory responsibilities.

Australian policies commonly distinguish parents and carers from other people authorised to collect. Staff need today’s approved context rather than an old paper list or a message known only to the office. Temporary delegates and emergency backup collectors should be visible to the people responsible for release.

SchoolsOut supports authorised and delegated pickup, multiple children and changed collectors. Court orders, disputed authority and identity concerns remain with the service or school’s documented escalation process.

Australian school-transport buyers already expect live vehicle location, pickup and drop-off information and parent alerts. SchoolsOut connects those signals to the child’s expected journey and receiving carer. GPS describes the vehicle; boarding, disembarkation and completed handover remain distinct events.

Absence, not travelling today, a changed destination, delay or missing carer should each trigger a clear next action. The operator continues to run routes, vehicles and drivers while SchoolsOut coordinates the child and family layer.

Start with one OSHC service, school, route or afternoon collection period. Map bookings, school-to-care transfer, absences, authorised nominees, staff roles, late collection, transport status and manual fallback.

Test an unreported absence, delayed carer, temporary collector, siblings with different plans and a family without a working phone. A useful pilot proves calm exception handling before wider rollout.