Managing school transport today means juggling between tools.
Transport teams know it: school transport is the only segment where families expect full transparency — and where tools have never kept up.
A spreadsheet for student records, an external registration tool, a messaging platform — three contexts to keep in sync.
Agents answer 30–50 calls per day at back-to-school: "Did my child get on the bus this morning?"
Student personal data travels in CSV files shared by email — no traceability, no documented GDPR compliance.
The driver has no view of expected students at each stop: impossible to spot a missing child before departure.
One tab in your existing Pysae. Everything consolidated: registration, files, routes, messaging, real-time validations.
Families know in real time where the bus is, whether their child boarded, and receive a notification at each stop. Calls disappear.
Personal data is isolated from the AVL, retained per legal durations, with every access timestamped and logged.
The driver screen lists expected students at each stop with their photo. Badge updates propagate in under 2 seconds.
In French agglomerations, school transport often accounts for 30–40% of trips on an urban and peri-urban network. Yet it's the only component that has never had native integration in operations tools. Pysae School is the first answer built from the AVL itself.
School integrates into the Pysae platform.
Not standalone software. One more tab, connected to the data you already have — GPS positions, trip states, on-board validations.
School relies on the Operations module already deployed. GPS positions, trip states and on-board validations are consumed in real time — no redundant configuration, no synchronisation to maintain.
What Pysae School does for you.
Four pillars, designed for agglomeration mobility teams, families and drivers.
Manage, not just consult.
Real-time dashboard, complete student files, validation workflows and prioritised alerts — from a single screen.
Supervision dashboard
Enrolled students, active subscriptions, 24h validations, anomalies — indicators refreshed continuously. Critical incidents accessible in one click.
Student files & workflow
Filterable table: identity, photo, geocoded address, school, badge, route, subscription status. Pending dossiers handled from the file. Every change timestamped and attributed.
Validation history
Answer definitively "Did my child take the bus?" — date, time, GPS, stop, route, vehicle, driver.
Parents see — without calling.
A dedicated responsive web app connected to the AVL in real time. Sign-in by email/password or FranceConnect, multi-child support.
Real-time GPS tracking
Bus position on the route, ETA to home stop, vehicle plate and trip state — pulled directly from the AVL, no recalculation on the School side.
Boarding/alighting history
All of the child's validations, timestamped and geolocated. Filterable by day, week, month, inbound or outbound.
Push & email notifications
Alert on boarding and as the bus approaches the home stop. Parent-configurable. No dependency on a proprietary mobile app.
No child left behind at a stop.
A dedicated screen inside Pysae Driver — the embedded app already in use. Auto-activates only on trips flagged as school trips.
Expected students at the stop
Auto-detection by geofencing. Photo, first name and school for each student expected at the approaching stop. No manual entry.
Update in under 2 seconds
On badge scan, the student moves from "expected" to "boarded" via the Pysae message bus. Target latency < 2s. No driver action needed.
Reporting & dispatch
Direct access to dispatch, departure confirmation, absence or incident reporting sent to the authority's services.
Communicate, target, measure — from Pysae.
Email and SMS campaigns to families, targeted by route, school or subscription status, with real-time delivery tracking.
Targeted campaigns
Recipients selected by route, school or status. Email and/or SMS from a single interface. Reusable drafts for recurring campaigns (back-to-school, disruptions, card collection).
Built-in performance tracking
Email open rate, SMS delivery rate, unsubscribes — viewable directly in the module, without exporting to a third-party marketing tool.
Native business use cases
Route disruption alerts, card collection reminders, back-to-school info. Full send history per family.
One student record. Three perspectives.
Each actor accesses the data with the right privilege level and the ergonomics suited to their use.
Agglomeration
- → Centralised view of the student population and validation workflows
- → Supervision dashboard with prioritised alerts
- → Targeted email & SMS messaging to families
- → GDPR compliance, logging and restricted export
- → CSV / JSON / Registration portal imports
Family
- → Real-time bus tracking on the map
- → Child's validation history (boarding/alighting)
- → Configurable push & email notifications
- → FranceConnect sign-in, multi-child management
- → ETA to home stop and vehicle identification
Driver
- → List of expected students at the stop (photo + name)
- → Real-time badge update (< 2s)
- → Expected / Boarded / Total counters
- → Absence or incident reporting to authority services
- → Direct dispatch access from the school screen
Student data, without compromise.
Three import channels to feed the repository, and an architecture isolated from the AVL to protect personal data from the ground up.
Registration Portal
Authoritative sourceFamily registration portal included in the module, or synced with the agglomeration's portal. Daily SFTP feed + webhook for real-time updates.
CSV / JSON / XLSX import
Batch loadingLoading files from operators or agglomeration services. Log of the last 7 imports always available: imported rows, error rows, retries.
Manual entry
Individual casesCreate or edit one-by-one for cases outside the automated flow. Every action timestamped, attributed and logged — with full modification traceability.
What the authority gains every day.
Results based on feedback from mobility services and operators already equipped. Actual values depend on fleet size and network.
Indicative targets based on mobility service and operator feedback. Actual results depend on student fleet size, network and existing tooling.
Two new components. Two services already in production.
School builds on the Operations module already deployed and extends Pysae Driver — without touching your existing foundation.
Everything you need to know before requesting a demo.
Questions mobility teams always ask — answered straight.