Who Sees What in School Transport Software

The transport in-charge, drivers and attendants, front office, accounts and owners each see only their own share of the same transport record. What a user opens depends on the job assigned to that login.

Share your requirements

Different jobs, one record

School transport is shared among people who rarely sit in the same room. The attendant is on the bus, the in-charge is on the phone, and accounts is at a desk. Each of them works from the same route, trip and fee records, so a stop change entered by the front office reaches the attendant’s list.

What each role sees

For the transport in-charge

Routes, buses, drivers, today’s trips and any trip that has not started. When a bus breaks down, the bus and the children mapped to it can be moved to another route from the same screen.

For drivers and attendants

The morning trip, its stops in order, the children due at each stop and the boarding marks. Nothing more is shown on that screen, so a driver does not see a database.

For the front office

Fee raised and collected, dues by route, mid-term admissions and stop change requests, all from the same records the in-charge uses.

For accounts

Collections by term and mode, concessions given, and what fuel and repairs cost per bus against route income.

For principals and owners

Trips run against trips planned, children boarded against children mapped, collection against what was raised, and papers falling due.

Schools and operators

A school running its own fleet gives each of these roles to its own staff, and the school decides who holds which login. A school that hires vehicles from an operator keeps the student mapping, boarding record and fee, while the operator’s staff run the buses. A transport operator carrying children for more than one school sees its routes by school. Who holds which login is agreed during implementation.

What the institution decides

Which logins exist and what each can open
Who may change a child’s stop
Who may give a concession
How drivers and attendants receive their login
Which owner or principal sees fleet-wide figures

FAQ

Frequently asked questions

What does a driver see?

A driver sees the day’s trip, its stops in order and the children due at each. A driver does not see the student database.

Can a school that hires buses use it?

Yes. The school keeps the mapping, boarding and fee records, and the operator’s staff can be given logins for the trips they run.

Can accounts see the cost of each bus?

Yes. Accounts sees what fuel and repairs cost per bus against route income, from the fuel logs and upkeep records.

Can an operator carrying several schools use one system?

Yes. Routes and children are kept by school, and how views are split is agreed during scoping.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

A senior engineer reads your answers. Nobody phones first.
Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.