Transport
Manage vehicles, compliance, routes, enrollments, trip schedules, daily assignments, passenger lists, transport attendance, GPS, and live tracking.
Overview
Manage vehicles, compliance, routes, enrollments, trip schedules, daily assignments, passenger lists, transport attendance, GPS, and live tracking.
Before you start
- Vehicles and compliance records prepared
- Routes and stops configured
- Transport permissions assigned
Main screens
Step-by-step workflows
Prepare transport setup
- Add vehicle and safe compliance documents.
- Configure routes and stops.
- Enroll students or staff.
- Prepare employee transport profiles or external transport staff records.
Run daily trip
- Create and activate a trip schedule with optional usual vehicle and staff.
- Open Trips for the required working date.
- Review the actual vehicle, staff, and passenger list; replace unavailable resources for that trip.
- Start trip and record transport attendance.
- Complete the journey.
Operational detail
Vehicle compliance
Keep insurance, fitness, permit, pollution/PUC, registration, and approval records valid for the trip date.
Daily vehicle and staff
Choose available, compliant resources for the dated trip. A daily replacement leaves other dates and the schedule unchanged.
Usual vehicle and staff
Optionally set usual resources on the trip schedule. Review each dated trip and replace unavailable resources when needed.
Routes and stops
Configure pickup/drop stops, order, timing, and route status before enrolling students or staff.
Passenger list
Trips prepare passengers from eligible route enrollments and stops. Approved full-day leave remains visible as On leave, with transport attendance not applicable.
Execution lifecycle
Move daily trips through the allowed stages until completed, with corrections only where the workflow permits.
- All transport records are scoped to the authenticated school and current session where applicable.
- Expired or unapproved vehicle compliance prevents vehicle assignment.
- Conflicting vehicle or staff assignments across overlapping trips are rejected.
- Downstream trip records should be created only after prerequisite records exist legitimately.
- Trying to assign a vehicle before completing compliance.
- Starting a trip without reviewing its vehicle, driver, and passenger list.
- Using direct database changes to repair trip lifecycle state.
- Capturing screenshots that show registration or document numbers.
Safe use
These guides explain normal user workflows only. Do not share passwords, OTPs, tokens, cookies, private student identifiers, payment details, raw internal IDs, provider configuration, or stack traces in support messages or screenshots.
- Trying to assign a vehicle before completing compliance.
- Starting a trip without reviewing its vehicle, driver, and passenger list.
- Using direct database changes to repair trip lifecycle state.
- Capturing screenshots that show registration or document numbers.