Talk to us

Several companies or fleets in one set-up

Run the transport of several schools, colleges or companies in one set-up. Each Entity sees only its own vehicles, stops, routes, riders and runs, and a group transport head can look across all of them.
PLANSFrom Growth

The problem it solves

  • A group of schools keeps one spreadsheet per school, and nobody sees the whole fleet.
  • One school's office staff can open another school's riders and parents' numbers.
  • Each branch wants its own delay limit and its own people told, but the system has one setting for all.
  • A route code R1 means a different bus in each school.

How it works

  1. Each school, college or company is an Entity. We add the Entities your agreement covers.
  2. Each Entity keeps its own stops, routes, riders, runs and no-transport days, and its own Transport settings.
  3. Office staff are allowed in one Entity or several. Those in several pick the Entities to work in at the top of the screen.
  4. Every list shows the records of the Entities ticked there. A group head ticks them all; stops, routes and no-transport days can be grouped by Entity.

Everything it does

Kept apart per Entity

  • Vehicles, stops, routes, riders, route runs and the riders on each run
  • No-transport days and spreadsheet imports
  • Alerts, trips, papers, bookings, checklists, fuel and service records, as your plan has them
  • Route codes and boarding card numbers are unique within an Entity, so two schools can both have R1

Settings of each Entity

  • The Transport tab: Plan Runs Days Ahead, Delay Alert After, Also Tell About Not Riding, Average Road Speed and your plan's feature settings
  • Its own time zone, used for the planned times of its runs
  • Its own approval chain for vehicle bookings (Scale); a new Entity gets a copy of the main one
  • Its own notification settings, or the group's until you give it its own

People across Entities

  • A rider has one record in each Entity they ride in
  • Staff work in the Entities ticked on their user
  • Lists of stops, routes and no-transport days can be grouped by Entity; the riders list can show an Entity column
  • A role applies in every Entity the user may work in

Who uses it

Group transport headWorks in all Entities and compares them in one list.
Transport office of one schoolWorks in its own Entity and sees nothing of the others.
Transport administratorKeeps each Entity's Transport settings.

Where you use it

  • Web: the Entity switcher at the top of the back office
  • Web: Administration > Users & Entities > Entities, the Transport tab of each Entity
  • Not split inside an Entity: there are no depots or sub-fleets within one Entity; a second fleet is a second Entity

What you control

Settings

  • Allowed Entities per user
  • Each Entity's Transport tab: Plan Runs Days Ahead 1, Delay Alert After 15 minutes, Average Road Speed 25 km/h
  • Each Entity's time zone

Approvals

  • Vehicle booking (Scale): one chain per Entity

Questions

Can the group head see all schools' runs at once?

Yes. Allow them in every Entity and tick all of them at the top of the screen. The lists then show every school's records together.

Can a school's office see another school's riders?

No, unless their user is allowed in that school's Entity. Each record belongs to one Entity.

Can each school have its own settings?

Yes. Each Entity has its own Transport tab, time zone, booking approval chain and notification settings.

We have two depots in one company. Can they be kept apart?

Not inside one Entity. Group routes by vehicle or driver, or set up each depot as its own Entity.

Can a person be office staff in one Entity and a driver in another?

Not yet. A role applies in every Entity the user may work in.

Related features

See your own routes on the map.

Send us your stops and routes and we will show you a demo with them.