School transport management connects each bus, van, driver, and route to a visible daily record. In Kenya in 2026, that operating discipline matters even more because the new school transport rules bring sharper attention to licensing, safety equipment, inspections, records, and vehicle telematics.
Technology is only one part of the answer. A school still needs clear responsibility for vehicle readiness, driver records, route release, incident response, maintenance, and communication. Tracking helps when it sits inside that process; a map by itself does not create a safe or accountable transport operation.
This article is operational guidance, not legal advice. The implementation of new rules can change through official notices and transition guidance. Confirm current requirements directly with NTSA or a qualified adviser.
The Traffic (School Transport) Rules, 2026 were published as Legal Notice No. 11 of 2026. The instrument states that most provisions commenced on publication, while Rules 13 and 14—covering reflectorised stop-signal arms and vehicle telematics—were to commence on July 1, 2026.
The Ministry of Roads and Transport describes the framework as covering several connected operating areas:
For a school or independent provider, the practical lesson is simple: compliance evidence cannot live in one person's memory or a file cabinet that the transport desk rarely sees. The vehicle, driver, route, inspection, maintenance, and expiry records need clear owners and a repeatable review process.
Make school-route readiness visible before the bus leaves.
Kora brings school route records, bus and driver assignment, live vehicle visibility, fuel, maintenance, incidents, and document-expiry tracking into one operations workspace.
A transport team cannot control what it has not recorded accurately. Every bus or van should have one current record with registration, operating status, assigned driver, odometer, service posture, open defects, installed tracker, and document-expiry dates.
Driver records should make the relevant identity, licence, role, status, contact details, and expiry dates visible to authorised staff. Store uploaded documents privately and use time-limited access rather than public links. A school transport record may involve sensitive information, so access should follow job responsibility, not convenience.
The morning run is a high-pressure window. A short release check should tell the transport coordinator whether the planned vehicle and driver are ready before students begin boarding. At minimum, verify:
If a critical defect or expired record blocks release, the system should make the reason explicit. The coordinator can then assign another ready vehicle or escalate the problem instead of discovering it after departure.
A school route is not a freight trip. It should use school-route language and keep the record focused on movement, readiness, and exceptions. A useful operating record contains:
Keep data collection proportionate. An operations platform can manage the bus, driver, route, expected load, and movement record without becoming a student information system. Student attendance, named passenger manifests, and guardian communication require their own product and privacy design; do not assume a fleet platform includes them.
Telematics combines a vehicle device, connectivity, location or sensor data, ingestion, storage, and a workspace where authorised people can act on the information. Buying a tracker without defining the operating workflow creates another screen to watch rather than a control system.
Ask these questions before selecting or installing a system:
Kora can receive live vehicle positions and supported telemetry from compatible installed trackers, but a school should independently confirm that a proposed device, installation, and data setup meet the current technical and regulatory requirements. Hardware, installation, and managed connectivity should also be scoped transparently rather than hidden inside a software claim.
A checklist has little value if a defect is recorded and then forgotten. When a driver or transport coordinator reports a safety issue, the workflow should keep that issue tied to the vehicle, create maintenance work where necessary, assign an owner, and record the repair outcome.
Service intervals should use current odometer or date context, not memory. The transport coordinator needs to know which vehicles are approaching service, which are in the workshop, which are waiting for parts, and which are ready for the next route. That same view helps the school plan substitutes before a breakdown disrupts the morning run.
A delay, breakdown, collision, or route safety concern needs a durable record: time, vehicle, driver, route, location, description, evidence, response owner, and resolution. The first priority is always people and immediate safety. The operating record comes next so the school can coordinate recovery and later understand what happened.
Keep communications factual. A location trail or timestamp can support the review, but it does not explain intent or assign blame. Use the evidence to reconstruct the event and improve the process—not to make automated conclusions about the driver.
Do not begin with a fleet-wide hardware purchase. Begin with accurate records and one route that the team can operate consistently. Over the next 30 days:
The pilot should answer operational questions: Did the vehicle leave ready? Could the school see the movement status? Were exceptions captured? Did defects reach maintenance? Could the team find the right documents without searching? Expand only after those basics work reliably.
The rules create a framework for school transport provider and vehicle licensing, vehicle safety requirements, driver and attendant responsibilities, inspections, operating records, telematics, stop-signal equipment, and how school transport services are operated. Schools should read the published instrument and confirm current NTSA implementation guidance.
The published instrument is dated February 13, 2026. It states that Rules 13 and 14, covering reflectorised stop-signal arms and vehicle telematics, were to commence on July 1, 2026, while the other rules commenced on publication. Operators should confirm current enforcement and transition guidance directly with NTSA.
School bus tracking software should show the assigned vehicle and driver, the planned school route, whether the position is live or delayed, movement history, route start and close times, and operational exceptions. It should also limit location access to authorised staff and remain useful when connectivity is unreliable.
No. Kora currently focuses on school route records, bus and driver assignment, vehicle tracking, fuel, maintenance, incidents, and document-expiry visibility. It does not currently provide a parent app, guardian alerts, student attendance, or a student manifest workflow.
No. Fleet software can organize vehicle, driver, route, maintenance, incident, tracking, and expiry records, but it does not issue licences, perform inspections, certify equipment, or guarantee legal compliance. Schools and providers remain responsible for confirming and meeting current requirements.
Read the published instruments and confirm current implementation guidance directly with the relevant authority before making legal or procurement decisions.
School routes need operating evidence, not another disconnected screen
Kora gives school transport teams a profile-shaped workspace for school routes, bus and driver assignment, movement visibility, fuel, maintenance, incidents, and document-expiry tracking.
