What this module is for
Manage vehicles, compliance, routes, enrollments, crew duty, trip schedules, manifests, attendance, execution, GPS, and live tracking.
Prerequisites
- 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.
- Assign vehicle only after compliance passes.
- Create crew and crew duty.
- Configure routes and stops.
- Enroll students or staff.
Run daily trip
- Create trip schedule.
- Generate daily trip.
- Create manifest.
- Record transport attendance.
- Execute trip lifecycle until completed.
Operational detail
Permission checkpoints
- Vehicle, compliance, assignment, crew, route, enrollment, schedule, manifest, attendance, execution, and GPS surfaces have separate permissions.
- Vehicle assignment is blocked until vehicle compliance is valid through the canonical workflow.
- Trip execution lifecycle actions are protected and must not be skipped by direct data changes.
Field guidance
Keep insurance, fitness, permit, pollution/PUC, registration, and approval records valid for the assignment period.
Assign only a compliant active vehicle to a valid route, shift, or operational scope without overlapping conflicts.
Select eligible drivers and optional attendants through the crew duty workflow before scheduling trips.
Configure pickup/drop stops, order, timing, and route status before enrolling students or staff.
Generate manifests from active enrollments so transport attendance has the correct passenger list.
Move daily trips through the allowed stages until completed, with corrections only where the workflow permits.
Validation and system feedback
- All transport records are scoped to the authenticated school and current session where applicable.
- Expired or unapproved vehicle compliance prevents vehicle assignment.
- Duplicate or overlapping assignments, duties, schedules, and executions are rejected by the workflow.
- Downstream trip records should be created only after prerequisite records exist legitimately.
Common mistakes to avoid
- Trying to assign a vehicle before completing compliance.
- Creating schedules before routes, crew duty, and enrollments are ready.
- Using direct database changes to repair trip lifecycle state.
- Capturing screenshots that show registration or document numbers.
Recommended next steps
Screenshot plan
Final public screenshots will use synthetic QA data only. Sensitive values such as names, phone numbers, emails, admission numbers, document numbers, credentials, cookies, tokens, and internal IDs must be removed or redacted.
Important safety notes
Use normal Schoolixa workflows
Public docs explain user workflows only. They do not expose internal IDs, direct database operations, credentials, provider prompts, or private system configuration. Permission visibility in the interface does not replace server-side permission checks.