Family starts the trip
Parents see queue position, ETA, entrance, zone, and assigned lane.
Built from a family point of view, Bell2go connects parent arrival, student readiness, verified loading, and campus traffic flow in one mobile-first platform.
2 fictional students · 2 buildings
See how the parent app, staff tablet, and live operations dashboard work together without replacing staff judgment.
Bell2go replaces radio calls, paper signs, and parent uncertainty with one real-time dismissal plan.
Parents see queue position, ETA, entrance, zone, and assigned lane.
Each building receives an ETA-based readiness cue—even for siblings.
Approved lanes adapt to capacity while the one-way route stays fixed.
Staff confirm every student, vehicle/contact, lane, and safe departure.
See wait distributions, throughput, lane capacity, exception rates, and recommended staffing changes across every session.
Coordinate staging, lanes, verification, siblings, exceptions, and safe loading without radio noise.
Know when to leave, where to enter, where to load, and whether every child is ready.
Use public SSO or local accounts with mandatory MFA, tenant isolation, audit, and provider-neutral contracts.
Model the approved entrance, one-way circulation, staging path, loading zones, lanes, and exit as operational constraints.
Explore the platform →One vehicle trip can coordinate multiple students across different buildings, each with independent readiness and handoff.
See the sibling flow →Forecast congestion and recommend departure, lane, and staffing changes—without autonomously releasing students or changing traffic.
Read the safeguards →Live position ranges, ETA, entrance, zone, lane, and freshness for every active family.
Building-specific notifications, walking status, staging handoff, sibling coordination, and holds.
Capacity-aware assignments within school-approved one-way routes and loading constraints.
Human-confirmed student, contact/vehicle, correct lane, door-side loading, secure seating, and departure.
Wait, throughput, loading, fallback, and exception trends with explainable recommendations.
Pilot targets are validated against each school’s baseline. Bell2go never presents an estimate as a guarantee.
Plan a baseline reviewTarget reduction in pickup wait time
Target median curb loading time
Completed trips with verification
Shared plan for families and staff
Annual subscriptions are scoped by campus, enrollment band, and selected modules. Pilot outcomes inform the final rollout.
Map routes, roles, wait times, exceptions, policies, and systems.
Approve topology, zones, lanes, authorization, retention, and fallbacks.
Validate readiness, routing, communications, accessibility, and safety.
Annual platform access, onboarding, support, and agreed integrations.
Measure outcomes, tune staffing, and expand to events, walk-up, or buses.
Today we’re introducing a mobile-first platform designed to make dismissal calmer for families, more coordinated for staff, and more measurable for school leaders. Bell2go connects arrival visibility, student staging, approved campus routing, verified loading, and operational insight—while keeping people in control of every safety decision.
Target Head of School/Principal, COO/Operations, Transportation, and IT/Security with role-specific proof.
The 8-minute visibility gap — connect family uncertainty to queue and staging data.
Principal / Head of SchoolShow the two-zone, four-lane flow — share the 42-second product overview.
COO / OperationsSibling pickup without a second loop — demonstrate independent readiness in one trip.
Dismissal / Transportation20-minute campus review — discuss baseline, route constraints, and fallback.
Operations sponsorSecurity and pilot brief — send the datasheet and close with a scoped assessment.
IT / Security + sponsorNo. GPS, plate recognition, and predictions are advisory signals. Staff confirm readiness, identity, loading, and exceptions. A dismissal lead activates any live route-plan change.
The platform supports local email/password accounts, Google, Microsoft personal or organizational accounts, and Sign in with Apple—including private relay addresses. MFA is mandatory for every method, and sign-in never grants student access without a school-approved relationship.
Yes. Each person creates a separate Parent App account using their own email address and phone number. Both are verified, and the school must approve the guardian or delegate relationship before any student becomes visible. Forgot Password uses the registered phone number and a one-time SMS code.
One vehicle trip contains multiple students. Each child has an independent building, readiness, and handoff status, while the family keeps one queue position and one loading lane.
The last verified instruction is marked stale, and QR, NFC, rotating code, directory lookup, signage, and staffed manual dismissal remain available. No single dependency is required to release a student.
Provider-neutral OpenAPI and event contracts support attendance/SIS, identity, maps, notifications, and cameras through isolated adapters. Source-system identifiers remain intact.
The marketing site uses private Amazon S3 behind CloudFront. Application backends run in containers on managed cloud compute with a privately connected managed database. Local development uses synthetic data and isolated environments.
Annual subscriptions are scoped by campus, enrollment band, and modules, with onboarding, configuration, support, analytics review, and agreed integration coverage defined in the order form.
No. It is a pilot target. Every school establishes a baseline, confirms safe operating constraints, and measures actual median and p90 outcomes before broader rollout.