All modules Leadership & Analytics

Transport Reports software for Indian schools

Route usage and fees

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

Transport Reports in a school workflow

Filter-aware example

School scopeSelected periodAuthorised columns

Evidence fieldSourceReview state

Expected-vs-boarded reconciliation per bus tripScoped school recordReviewable

Route utilization and live seat availabilityScoped school recordReviewable

Manifest CSV gated as an explicit data-egress permissionScoped school recordReviewable

Fleet and crew compliance-expiry work-listsScoped school recordReviewable

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

Route attendance reconciles who was expected against who actually boarded, per trip — surfacing no-shows and unexpected boarders daily. Route-360 shows utilization and seats left; the bus manifest CSV (stop, student, guardian phone) is gated behind an explicit export permission because PII rides that file.

The school problem

School teams need a dependable way to handle Transport Reports: Route usage and fees. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Route usage and fees.

Expected-vs-boarded reconciliation per bus trip
Route utilization and live seat availability
Manifest CSV gated as an explicit data-egress permission
Fleet and crew compliance-expiry work-lists

Operational result

What your school gets

Route utilisation, expected-versus-boarded, manifest and fleet-expiry evidence for daily transport review.

Access and ownership

Who typically uses it

Transport manager
Fleet coordinator
Principal
School administrator

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

Included from Starter

A fixed library of school reports with tables, charts and CSV or XLSX export.

A plan that includes Reports, plus configured transport/trip records
Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

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.

Does Transport Reports work on its own?

Transport Management, Transport Fees, Attendance Reports, Export Excel 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 Reports?

A plan that includes Reports, plus configured transport/trip records. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Transport Reports?

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

How do we confirm the plan and implementation scope?

Transport Reports is included from Starter in the current public plan matrix. Final rollout scope, services and external dependencies are confirmed in your written proposal.

See the Leadership & Analytics workspace Compare plans and commercial costs

See it in your school context

Run transport reports the connected way.

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