All modules Campus Operations

Transport Management software for Indian schools

Routes, stops, and vehicles

Feature identity
Transport Management
An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Transport Management in a school workflow

Campus Operations

01
Required context
Routes, stops, vehicles, crew and student allocations must be confirmed before rollout.
02
Supported work
Geocoded routes and stops with pickup/drop times and geofence radii.
03
Reviewable result
A connected route, stop, fleet, crew and rider operation with capacity, compliance-expiry and trip evidence visible together.

Example record

Transport Management

Authorised view

Geocoded routes and stops with pickup/drop times and geofence radii
Fleet + crew masters tracking RC, insurance, permit, PUC, fitness and licence expiries
Seat-safe allocation with FIFO waitlists and prorated monthly billing, GST-aware
Live trips: GPS pings with an honest live/stale badge, boarding log, SOS and parent alerts

Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

Geocoded routes and stops, a fleet and driver/attendant master with document-expiry alerts, and seat-capacity-aware student allocation with prorated monthly transport fees (GST handled). The live layer adds GPS trip tracking, an append-only boarding safety log and “your child boarded” WhatsApp alerts.

The school problem

School teams need a dependable way to handle Transport Management: Routes, stops, and vehicles. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Routes, stops, and vehicles.

Geocoded routes and stops with pickup/drop times and geofence radii
Fleet + crew masters tracking RC, insurance, permit, PUC, fitness and licence expiries
Seat-safe allocation with FIFO waitlists and prorated monthly billing, GST-aware
Live trips: GPS pings with an honest live/stale badge, boarding log, SOS and parent alerts

Operational result

What your school gets

A connected route, stop, fleet, crew and rider operation with capacity, compliance-expiry and trip evidence visible together.

Access and ownership

Who typically uses it

Transport manager
School administrator
Fleet coordinator
Accountant
Parent or guardian

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Campus Operations catalogue capability

Routes, stops, vehicles, crew and student allocations
Compatible location input for live bus tracking
Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Flagship workflow deep dive

Routes, Fleet, Riders & Trip Evidence

Know which bus, which stop, which child.

Run geocoded routes and stops, a fleet and crew master that tracks document expiry, and seat-capacity-aware student allocation with prorated monthly transport fees. Where a compatible location feed is configured, live trips add GPS positions with an honest live-or-stale badge, an append-only boarding log and configured parent alerts.

Interactive operating model

From route design to boarding evidence

Follow one child from the allocated stop to the alert their guardian receives.

Illustrative workflow · no customer data

Stage 1 of 5

Route published

Stops, timings, geofence radii, vehicle and crew are defined for the route.

Control point

Capacity and crew are attached to the route, so later checks have something to enforce.

Evidence retained

Route, stop and assignment records.

Core workflows and features

The operational work behind the promise

Geocoded routes and stopsDefine each route's stops with pickup and drop times and a geofence radius, so a route is a real operational object rather than a line in a notice.
Fleet master with compliance datesTrack each vehicle's registration, insurance, permit, pollution certificate and fitness expiry in one place, with alerts before a document lapses.
Crew records and licencesHold drivers and attendants with their licence validity, and link a crew member to a login only through the explicit link action.
Seat-safe allocationAllocate a student to a route and stop against the vehicle's seat capacity, with a waitlist when a route is full instead of a silent over-allocation.
Prorated transport billingBill transport monthly, prorated from the allocation date and GST-aware, through the same invoice-led fee path as the rest of the school's dues.
Live trip positionsShow a running trip's reported positions where a compatible location feed is configured, with a badge that says plainly whether the feed is live or stale.
Append-only boarding logRecord boarding events as an append-only log, so the question of who boarded which bus is answered from evidence and not from recollection.
Configured parent alertsSend boarding and trip alerts to allocated riders' guardians through the school's configured channels, subject to consent and opt-out controls.
Crew-scoped app accessGive a driver or attendant only the minimal capture rights their job needs, without opening the student directory or any fee data to them.
Emergency signallingRaise an SOS from a running trip so the school office sees the vehicle, route and crew involved without hunting for the right phone number.
Transport reportingReview routes, occupancy, allocations and transport dues together, so a route decision is made against both capacity and collection reality.

Operational controls, honest signals

Capacity and expiry are enforced; location is only ever reported.

Seat limits, document-expiry alerts and prorated billing are deterministic rules over the school's own records. The live layer reports what the configured feed actually supplies, and says when it is stale.

Block an allocation that would exceed the vehicle's configured seat capacity and offer a waitlist place instead.
Alert on registration, insurance, permit, pollution and fitness expiry before the date passes.
Prorate the monthly transport charge from the allocation date through the standard invoice path.
Label a trip's position feed live or stale rather than showing an old position as current.

Human boundary

The platform does not drive, dispatch or certify a vehicle. Live tracking depends on a compatible location input the school supplies, boarding evidence is recorded by the crew, and parent alerts are sent only through the school's configured channels with consent and opt-outs respected.

Key daily uses

What the school team does here

Publish a route with its stops, timings and assigned vehicle and crew.
Allocate a student to a stop and see the seat position that allocation consumes.
Check which vehicle documents expire this month before a trip is scheduled.
Follow a running trip and answer a parent's boarding question from the log.
Reconcile transport dues against the riders actually allocated this month.

Used by

Transport manager
Fleet coordinator
School administrator
Accountant
Driver
Bus attendant
Parent or guardian

Actual access follows the school's plan, role permissions and record scope.

Measurable operating indicators

Metrics to track — not guaranteed ROI

Establish a baseline before rollout, agree the reporting period, then compare the school's own source evidence.

Seat utilisation

Allocated riders against configured seat capacity per route

Shows where a route is over-subscribed or running well below the cost of operating it.

Compliance headroom

Vehicles and crew whose documents expire inside the next review window

Turns statutory expiry into a scheduled task instead of a roadside surprise.

Trip evidence coverage

Trips with a live position feed and boarding entries against trips run

Distinguishes a genuinely tracked operation from one where the feed was never configured.

Prerequisites and availability

Confirm the operating context before rollout.

Core transport capability · live tracking needs a compatible location input · alerts need configured channels

Routes, stops, vehicles, crew records and student allocations entered before a trip means anything.
A compatible location input for live trips; the platform does not supply tracking hardware.
Configured messaging channels, templates and consent handling for any parent alert.
Transport fee heads configured if monthly transport charges should be billed and collected here.
Crew logins are created through the explicit link action; a crew record alone is not an account.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Do you provide GPS devices for our buses?

No. Live trips display what a compatible location input your school configures actually reports, with a badge that says plainly whether the feed is live or stale. The platform supplies no tracking hardware and never shows a stale position as current.

Can more students be allocated than a bus has seats?

No. Allocation is checked against the vehicle's configured seat capacity, and a full route offers a waitlist place rather than accepting a silent over-allocation. Monthly transport charges are prorated from the allocation date.

Does Transport Management work on its own?

Transport Fees, Transport Reports, Parent App, Emergency Alerts are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling Transport Management?

Routes, stops, vehicles, crew and student allocations. Compatible location input for live bus tracking. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Transport Management?

No AI capability is asserted for Transport Management. Its documented work remains controlled by school records, roles and permissions.

How do we confirm the plan and implementation scope?

Plan inclusion and rollout scope depend on the live plan matrix, readiness state and your school's written proposal. The demo team will confirm the applicable boundary before rollout.

See the Campus Operations workspace Compare plans and commercial costs

See it in your school context

Run transport management the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.