Docs Menu

Docs

How To Manage Transport Routes

Create, search, filter, and maintain transport routes from the Transport Routes setup workspace.

Search docs

Search by workflow, module name, or operational keyword.

Documentation search is ready.

Last updated: March 22, 2026

This guide explains how to use Transport Routes to maintain the route records that later connect vehicles, pickup points, and student transport assignments.

Short summary

The Transport Routes page is a setup workspace with a quick-entry form, route search, status filtering, a route table, and a route drawer for view or edit actions.

Best for

Transport coordinators and school operations staff who define route structure before vehicles and pickup points are assigned.

Requires

Access to Transport -> Transport Routes and permission to create, update, or delete route setup data.

Result

Route titles, vehicle counts, status, and route notes stay consistent across the rest of the transport workflow.

Before you start

  • Decide the naming pattern you want for route titles.
  • Confirm operators agree on which routes should stay active or inactive.
  • Avoid duplicate route names that describe the same travel corridor.

Transport -> Transport Routes

Step 1: Open Transport Routes

In the sidebar, open Transport and choose Transport Routes.

Step 2: Review the quick-entry setup form

The route form is designed for fast setup and currently includes:

  • Route Title as the required field
  • Number Of Vehicles
  • Status with an active-route toggle
  • Note

Use the note field for route-specific details that help staff distinguish similar route names later.

Step 3: Create a route

Enter the route title first, then complete the optional fields that matter for your current transport plan.

After you save, the route becomes available to related transport workflows such as:

  • vehicle assignment
  • route-pickup mapping
  • student transport assignment

Step 4: Search and filter the existing route list

Use the page controls to keep the route list manageable:

  • the route search box narrows the table by route title
  • the status filter lets you review active or inactive routes separately
  • reset clears the filter state and reloads the full list

Step 5: Review the route table

The route table currently exposes:

  • Route
  • Vehicles
  • Pickup Points
  • Status
  • Actions

Use the count columns to confirm whether the route is already connected to downstream transport setup before you edit or remove it.

Step 6: Use row actions for maintenance

The row actions support the normal maintenance cycle:

  • View to inspect route details
  • Edit to update the route record
  • Delete to remove a route after confirmation

When the route drawer opens in edit mode, it reuses the same core route fields instead of introducing a separate workflow.

Important note

Important: in the current local Smart School environment, the Transport Routes screen can fail before rendering because the route detail drawer watcher throws on first load. The route fields and actions documented here were verified from the Smart School source code and the related route-aware transport screens that still render correctly.

Verify the result

  • the route title is clear and not duplicated
  • the active or inactive state matches the intended operational status
  • the route appears in the route list after save
  • the route can be selected later from vehicle-assignment or route-pickup workflows

Troubleshooting

IssueLikely causeWhat to do
The route does not saveThe required Route Title field is emptyFill the route title before saving
Route counts look wrongVehicles or pickup points are not linked yetContinue with vehicle assignment and route-pickup mapping setup
Operators see duplicate route namesRoutes were created without a naming standardRename overlapping routes and keep one naming convention
The page does not render locallyThe current UI build hits a route-drawer runtime errorUse the related transport setup pages for cross-checking and record the blocker for the local UI fix

Related docs