In a private school that collects its pupils, transport is still often held in a spreadsheet and in one person's head. The Scoliom Scolarité transport module holds the vehicles and their capacity, the routes and their stops, the driver assigned, and each pupil attached to a stop — and the office finds a pupil's route and stop in a moment when the family calls.
Scoliom handles school transport: the pupils, the stops, the routes and the seats — and what expires (insurance, roadworthiness inspection) or gets spent (fuel logs). It does not geolocate vehicles and holds neither servicing nor repairs: it is not fleet-management software.
Each bus is described once: its number of seats, but also its insurance and its roadworthiness inspection. The capacity acts as the limit; the expiry dates surface on their own.
The morning round is written once: its stops, in order. A route can be duplicated for the evening rather than typed again.
The driver is attached to the transport, and each pupil to a stop. A family that moves house changes stop : nothing else moves.
A family asks for its child's stop? It is in the pupil's record and on the route list, with no binder to search. In the family space, transport appears in the payment schedule, as a subscribed service.
The vehicle's capacity sets the rule.
Each route shows the pupils assigned against the seats available. When a round approaches saturation it becomes visible before term starts — while you can still decide to open a second route, not on the day twelve children are waiting at the roadside.
Two distinct things, connected.
Running the service (who gets on where) and the subscribed service are two sides of the same pupil record. Transport is one of the school services a family subscribes to, with its own rate : it joins the payment schedule like the rest of the fees, with no separate ledger.
A forgotten insurance costs a bus.
Each vehicle carries the dates of its insurance and of its roadworthiness inspection : the platform flags what has expired, and by how many days. Alongside, fuel logs — odometer, litres, amount — give the distance covered and the cost per kilometre. These amounts are informational : they enter neither the cash desk nor the families' payment schedules.
Better said now than later.
Scoliom does not geolocate vehicles and holds neither servicing, nor repairs, nor parts : it is not a fleet-management tool. The stop times themselves are indicative — nothing enforces them. The module stops where the carrier's own trade begins.
No, and we would rather say so before the demonstration than after: Scoliom does not geolocate vehicles. The module holds the school side of transport — routes, stops, seats, pupils, the driver assigned — as well as the insurance and roadworthiness expiry dates and fuel logs kept for information. Position tracking, for its part, calls for equipment on board and for a trade other than ours.
Transport is a subscribed service, like the school's other services: the family subscribes for the year, at a rate you set, and the amount joins its payment schedule along with the rest of the fees. So you know at any moment which pupil uses transport, at what rate, and where they stand on payments — without keeping a second file alongside.
Not in its own space: the stop is kept by the school, in the pupil's record and on the route list, and the office finds it in a moment when a family calls. In its space, the family sees transport in its payment schedule, as it is a subscribed service.
No. Vehicles, routes and stops are described once and stay in place; a route can be duplicated rather than rewritten. From one year to the next, what really changes is the pupils assigned — and a family that moves house is simply attached to another stop.
A remote demonstration is enough to see a route and its stops, a vehicle and its seats, a pupil assigned and the transport service in the payment schedule — on fictional data.
No commitment · Reply within 48 working hours