One platform for the school transport day, from the overnight plan to the report.

STAGE 01

Setup

Trayvar opens the account with you. Your team then adds the fleet, the schools and the children.

• Access is provisioned by Trayvar: we create the account for your operation or your school, and you add your own managers.
• Vehicles and drivers are added in the dashboard, each vehicle with its capacity and an optional home base where it parks.
• Schools carry their campuses and bell times. A school running its own buses starts with itself and its campuses (for schools); an operator adds every school it serves (for operators).
• Children are imported from a spreadsheet or added one at a time, each with a school, class, home location and times by day of the week. NFC cards are issued from the dashboard.

STAGE 02

Hubs and routes

Each night the optimiser turns the children into routes. Each morning someone approves them.

• Nearby homes are grouped into pickup hubs, or each child is collected from home where the school expects door-to-door. Hub and door pickup can run side by side.
• The optimiser sequences every route against vehicle capacity, boarding time, bell times and road distances, with traffic taken into account where it matters.
• Afternoon runs split by dismissal time, so kindergarten, primary and secondary each go home on their own run.
• Plans are reviewed on the Plan page and approved route by route or all at once. Runs that would share a driver or a vehicle at the same time are flagged before approval.

STAGE 03

The run

Drivers run the route from an Android app built to keep working when the signal does not.

• The driver app holds the day's route offline and syncs when coverage returns. It is built for 2G and for the phones drivers already carry.
• Each child taps an NFC card to board, and the pickup is recorded with its time and GPS location. Drivers mark absences at the stop.
• A panic button reaches the operator's Live screen at once.

STAGE 04

Parents

Parents hear from Trayvar on WhatsApp, the channel they already use. There is no app to install.

• Messages go out when the child is picked up, when the bus is close and when the child is dropped off. When a route runs late, the operator sends its parents the new time.
• Messages go only to parents who have agreed to receive them. Every message is logged as delivered, not delivered or not sent, with the reason, and the logs appear in the reports.

STAGE 05

Live

The operations team watches the morning on one screen while it happens.

• Every route shows its progress on the map, and each pickup arrives in the activity stream as the driver records it.
• Each route is scored against its target time: on time if it finishes no more than ten minutes after it, otherwise the number of minutes late. A route that cannot be timed says so rather than guess.
• Children who were scheduled but not confirmed aboard are counted as unconfirmed, so the team closes the gap during the day.

STAGE 06

Reports

Every period closes with a report built from the same records the day produced.

• The operations report covers routes run, on-time performance, pickups against schedule, load factor, absences, missed pickups, unconfirmed children, planned and measured distance and parent messages, then breaks each down by run, driver and school.
• The school service report gives one school only its own routes and children, under the operator's name, and lists the exceptions rather than every child. Nothing about money appears in it (how operators use it).
• Both print as designed PDFs for any date range. For operators, revenue and fleet costs sit alongside, and the MarginCOS export carries the commercial data into a deeper margin analysis.