Ordinary afternoon
Every journey home,connected.
ReadyBell connects school pickup, dismissal, carpools, and community bikepools in one safer, calmer experience.
Scroll to follow an afternoon through the neighbourhood.
An aerial view of a quiet neighbourhood surrounding a school. Roads lead toward a pickup lane and a bike path runs alongside. The school clock approaches dismissal time.
The problem
Dismissal should not begin with confusion.
Cars arrive out of order. Parents call the office to ask whether their child has been told. Teachers work from a paper list and a walkie-talkie. Carpools are coordinated in group texts that go stale, with no confirmation that anyone was actually collected.
- Cars arrive in whatever order they reach the lane
- Parents have no channel to the teacher
- Teachers run dismissal from a paper sign-out sheet
- Substitutes have no context on who may collect which child
- Carpools rely on group texts with no confirmation step
- Authorized-pickup lists sit on paper, unchecked at the curb
The pickup area grows busy. Cars queue out of order, disconnected messages appear between families and the school office, and congestion builds around the school.
ReadyBell Pickup
From departure to safe handoff.
One tap when a parent leaves. A traffic-aware ETA. A live queue the teacher can act on in seconds. Every stage visible to both sides at once.
A parent taps “Leaving Now”. A route draws from their home to the school. The teacher's queue reorders by arrival. The child moves through accepted, packing, ready, and picked up, and the completed pickup is recorded.
ReadyBell Bikepool
Safer rides. Stronger communities.
Families form small private groups that ride, walk or scoot to school together. One parent leads a given ride; the others follow its progress and get their children back with an auditable handoff.
The view moves to a neighbourhood bike path. A parent volunteers to lead the afternoon ride and chooses a meeting point. Children are checked in, the group departs together, and families follow its progress until every child is handed off.
One connected ecosystem
One ReadyBell ecosystem.
Whether students arrive by car, carpool, bike, or family pickup, ReadyBell keeps every journey organized and visible.
The camera rises above the neighbourhood. A parent driving, a carpool, a bikepool group and the school's own dismissal board are all active at once, each connected back to the school.
Two products, one ecosystem
Choose the journeyyou want to see.
Schools run both, or either. They share an account model, a design system, and the same rule: nothing is claimed until the server confirms it.
School dismissal and student pickup management
Real-time pickup coordination. Parents signal they are arriving and get a traffic-aware ETA; teachers work a live queue sorted by urgency; administrators run approvals, rosters, broadcasts and analytics from the same app.
iPhone, iPad, and Mac.
How it works
Leaving now
The parent taps once and picks which children. The app takes a single GPS fix — never background tracking.
Traffic-aware ETA
MapKit returns a drive time and distance for right now. It is computed once per request, not polled.
The teacher is told
The request lands in the teacher's queue with the parent's name, sibling avatars, an ETA chip and a live countdown.
Worked in one tap per stage
The teacher advances the child through the lifecycle. The server rejects any skipped step.
Safe handoff
If someone other than the requesting parent arrives, staff check them against the child's authorized list from the request detail.
Recorded
The completed pickup joins the school's history and its 7-day analytics.
What it does
Live arrival visibility
A five-step status timeline with a live countdown, visible to the parent and the teacher at the same moment.
Organized teacher queues
Active requests sorted by urgency, with a landscape Pickup Lane board that splits Ready for Pickup from Getting Ready.
Carpool with confirmation
Invite another parent at the school, they accept, and the receiving parent explicitly confirms the child was collected — closing the loop instead of guessing.
Authorized pickup persons
Parents maintain up to ten approved people per child. The list is server-enforced and visible to staff at the moment someone unfamiliar arrives.
Delegate pickup
Name, relationship and phone declared per request. The teacher sees an amber banner with tap-to-call.
Emergency broadcast and lockdown
Typed broadcasts to a chosen audience, and a one-tap lockdown that blocks new pickup requests school-wide and alerts every parent.
Roster-verified onboarding
New accounts are cross-checked against the school's uploaded roster. A mismatch flags for review rather than blocking; a name collision locks the account and raises a duplicate alert.
Arrival prediction
Ahead of any request, the teacher's device scores each child from that family's own pickup history. Predictions at or above 0.72 confidence surface as a point estimate or a range, and are withdrawn the moment a real request arrives.
Administrator oversight
Approvals with roster status, role changes, invite codes, dismissal windows, substitute coverage, and a 7-day analytics view with a CSV dismissal report.
Designed for every participant
Everyone sees exactlywhat they need to.
One tap, then certainty.
Say you are leaving and watch the handoff happen. Keep the list of people allowed to collect your child. Join a Bikepool and follow the ride home.
ReadyBell Pickup and Bikepool
Live tracking
What a parent sees after tapping Leaving Now
Requested
Parent sends the request
Accepted
Teacher acknowledges
Packing
Child is getting ready
Ready
Waiting at the door
Picked up
Handed to the adult
Completed
Recorded
The countdown and each stage update for the parent and the teacher at the same moment.
Safety and privacy
These are the guarantees the software actually enforces. Each one corresponds to a rule in the shipping product, not an aspiration.
Who can do what
- Identity, role and pickup-state writes happen only on the server — no client, including an administrator's, writes them directly.
- Every Bikepool write re-reads role and membership inside its transaction, so permissions changing mid-request cannot be exploited.
- Authorization is checked before anything is revealed about the object, so an endpoint can never be used to probe a child's pickup list.
- Cross-school access is refused everywhere, including analytics, export and the assistant.
What is known about a child
- Children are never login-capable. A Bikepool child record has no email, phone or password field at all.
- A parent sees their own children by name, plus an anonymous count of the other riders. Only that ride's leader sees its full roster.
- Reads of sensitive information are recorded without copying the information itself.
Location
- Pickup takes a single GPS fix when a parent taps Leaving Now. There is no background or continuous tracking, by design.
- Bikepool stores no location history at all. Tracking is live only, starts when a ride starts, and stops when it ends.
- No child's device is ever tracked.
A record you can trust
- Handoff records are immutable — a correction is a new audited action, never a second write over the first.
- Approvals, role changes and broadcasts are logged with actor, target and timestamp.
- Notifications are dual-pathed: a push attempt and a durable in-app record, so a failed push never means a missed message. The interface distinguishes queued from sent from failed rather than claiming delivery.
ReadyBell does not display security certification badges it has not been awarded. For a school's procurement review, we will answer a data-protection questionnaire directly.
Read more about safety and privacyBring every school journey together.
See how ReadyBell can simplify dismissal, pickup, carpools, and Bikepools for your community.
Every child. Every pickup. Every journey.