Skip to documentation content
Schoolixa Documentation
Campus Operations

Transport

Manage vehicles, compliance, routes, enrollments, crew duty, trip schedules, manifests, attendance, execution, GPS, and live tracking.

Audience
Transport managers, admins, drivers/crew supervisors
Last reviewed
September 2, 2026

Overview

Manage vehicles, compliance, routes, enrollments, crew duty, trip schedules, manifests, attendance, execution, GPS, and live tracking.

Before you start

  • Vehicles and compliance records prepared
  • Routes and stops configured
  • Transport permissions assigned

Main screens

Vehicles Vehicle Documents Vehicle Assignments Crew Routes Enrollment Schedules Daily Trips Manifests Attendance Execution GPS

Step-by-step workflows

1

Prepare transport setup

  1. Add vehicle and safe compliance documents.
  2. Assign vehicle only after compliance passes.
  3. Create crew and crew duty.
  4. Configure routes and stops.
  5. Enroll students or staff.
2

Run daily trip

  1. Create trip schedule.
  2. Generate daily trip.
  3. Create manifest.
  4. Record transport attendance.
  5. Execute trip lifecycle until completed.

Operational detail

Permission requirements

  • 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.

Vehicle compliance

Keep insurance, fitness, permit, pollution/PUC, registration, and approval records valid for the assignment period.

Vehicle assignment

Assign only a compliant active vehicle to a valid route, shift, or operational scope without overlapping conflicts.

Crew duty

Select eligible drivers and optional attendants through the crew duty workflow before scheduling trips.

Routes and stops

Configure pickup/drop stops, order, timing, and route status before enrolling students or staff.

Manifest

Generate manifests from active enrollments so transport attendance has the correct passenger list.

Execution lifecycle

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.

Safe use

Keep documentation and support privacy-safe

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.
  • 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.
  • Verify compliance
  • Create crew duty
  • Prepare schedule
  • Run daily trip