# How a school bus company moves off WhatsApp

> School bus companies usually run on messaging groups, spreadsheets and the phone. As the fleet grows, that setup breaks in three places: seeing a trip that has gone wrong in time, giving schools and parents the right update, and keeping documents, changes and payments on record. The safe order for the switch is to map today's work first, then run the software alongside the old way for a while.

URL: https://corrplus.net/blog/school-bus-company-going-digital/
Updated: 2026-11-20
Corrplus Team

## How does a school bus company run today?

Most school bus companies run their day on three tools. Messaging groups carry communication with drivers, escorts and often parents. Spreadsheets or paper lists hold students, stops, payments and documents. The phone handles everything urgent: a parent asks where the bus is, operations calls the driver, the school asks about a delay.

In a small fleet this works, because everything lives in a few people's heads. As the number of vehicles and schools grows, the same setup slows under its own weight. This post describes how to recognise that point and how to switch without putting morning trips at risk. The examples are from Türkiye, where the School Bus Regulation and KVKK, the data protection law, set the rules.

## Where does the messaging and spreadsheet setup break?

It usually breaks in three places.

**Seeing a trip that has gone wrong in time.** When a vehicle breaks down, a student is not at the stop or a trip runs late, the news lands in a group as a message. Who has it, who took it and whether it was solved are invisible. The problem is often noticed only when a parent calls.

**Giving the school and parents the right update.** Türkiye's School Bus Regulation requires operators to notify the school, on the same day, of any change to escorts, main and backup drivers and vehicle plates. On a morning when a backup driver covers a route, that notice is easy to miss when it depends on the phone and memory. A 2021 amendment also requires operators to keep to the maximum travel time set by the school; measuring that needs a record of actual trip times.

**Keeping documents, changes and payments on record.** Driver and escort fitness reports are renewed every year and psychotechnical reports every five years; vehicle inspections and insurance follow their own calendars. Payments and arrears sit in another spreadsheet. When these are not connected, an expired document or an overdue payment can go unnoticed.

## When is it time to move to software?

Fleet size alone is a poor test. If two or three of these are true, the setup is ready to change:

- Between 7:00 and 8:30 in the morning, operations can do nothing but answer the phone.
- A trip that has gone wrong is usually noticed when a parent or the school calls.
- Document end dates or payment arrears depend on one or two people's memory.
- At the end of the month you cannot say how many trips ran to plan, how many were late, or why.
- Parents' phone numbers and addresses sit in groups everyone is in, or in shared spreadsheets.

The last point is not an efficiency problem but a compliance one. KVKK requires personal data to be relevant, limited and proportionate to its purpose. In a setup where everyone sees everything, that principle is almost impossible to apply.

## How should the switch be planned?

Many [digital transformation](/glossary/digital-maturity/) projects struggle because the new tool is expected to replace the old way overnight. In school transport the cost of that is high: the morning trip cannot wait. A safe switch has three steps.

1. **Map today's work.** Which information lives where, who updates it, who gets told? Gather student, parent, stop, vehicle, driver, escort, school and payment lists in one place. This step surfaces missing phone numbers, duplicate records and unchecked addresses; cleaning them up before the switch makes every later step easier.
2. **Run in parallel.** Use the software alongside the old way for a while. Keep the phone and groups open; drivers record attendance in the app and operations follows problems in the software. Measure what changes: how many calls came in this morning, and how many problems were seen before a parent called?
3. **Move to one channel.** At the end of the parallel period, send school and parent updates from the software and keep the groups for emergencies only. Archive the old spreadsheets so two records do not drift apart.

Drivers are usually the ones who find the switch hardest. The fewer taps the app needs, and the less a dropped connection loses, the easier it is accepted.

## What should you look for in software?

Some tools on the market are mainly vehicle tracking: they show where the bus is on a map. That is useful, but the question that wears a bus company down is different: what went wrong, who will fix it, who will tell the parents? Look for answers to these questions:

| Question | Why it matters |
|---|---|
| Does work that has gone wrong rise to the top, and can you see who took it? | The problem is seen before a parent calls |
| How many taps does the driver need for attendance, and does the record wait when there is no connection? | Field use keeps going |
| Can the end-of-trip check that no child is left on board be skipped? | The in-vehicle check the regulation requires |
| Are there warnings for document end dates, and can a vehicle with a lapsed document be assigned? | Inspections and safety |
| Do schools and parents see only data about themselves? | Proportionality under KVKK |
| Where is data stored, and how does it come back to you at the end of the contract? | Lock-in and data security |
| Who handles setup, list import and training? | The switch does not disrupt the school term |

Our own product, [okulservisi.app](/products/okulservisi/), answers most of these questions from setup onwards: it plans the switch in three steps of setup, a week of parallel use and real use; the product team handles list import and training, and the phone and messaging groups stay open during the parallel week. Trips running to plan show as a single number, and work that needs attention rises to the top of a numbered queue.

## Where to start

1. Write down one morning from start to finish: which calls came in between 6:30 and 9:00, which messages went out, and when each problem was noticed.
2. Gather student, parent, stop, vehicle and staff lists in one file and mark the gaps.
3. Identify whose memory document and payment tracking depends on.
4. Compare two or three products against the table above, using the same questions.
5. Start the switch between terms or before a new term rather than mid-term, and run in parallel for at least a week.

Moving field operations from a chain of calls and messages into one record is at the heart of our [digital transformation strategy](/services/digital-transformation-strategy/) and [workflow automation](/services/workflow-automation/) work. If you run a similar field operation outside school transport, we can map today's flow together in a [free call](/contact/).

## Frequently asked questions

### When should a school bus company switch to software?

When the morning phone calls leave operations unable to manage anything else, when a trip that has gone wrong is only noticed once a parent calls, or when document and payment tracking depends on one or two people's memory. Fleet size alone is not the test; the same problems appear with five vehicles, but they grow with every vehicle added.

### Why are messaging groups not enough?

A message in a group is not a record: you cannot see who took the problem, when it was solved or who was told. Everyone sees everything, which can conflict with the proportionality principle for personal data such as parents' phone numbers and addresses. When the message is lost, so is the trail.

### How long does the switch take?

It depends on the product. Student, vehicle, staff and route lists are imported first, then drivers and parents are invited. Keeping the old way open for a while and running the software in parallel is the safest way to switch without putting morning trips at risk.

### What is the most important question when choosing software?

Whether it shows your day's work or only where the vehicle is. A live map is useful, but the real question is who owns the problem and when the school and parents are told. Also ask about data security, retention, and how your data comes back to you when the contract ends.

## Sources

- [Resmî Gazete, Okul Servis Araçları Yönetmeliği (School Bus Regulation), 25 October 2017, No. 30221](https://www.resmigazete.gov.tr/eskiler/2017/10/20171025-2.htm)
- [Resmî Gazete, Regulation amending the School Bus Regulation, 25 August 2021, No. 31579](https://www.resmigazete.gov.tr/eskiler/2021/08/20210825-8.htm)
- [Mevzuat Bilgi Sistemi, Law No. 6698 on the Protection of Personal Data (KVKK)](https://www.mevzuat.gov.tr/mevzuatmetin/1.5.6698.pdf)
- [okulservisi.app, How it works: from setup to daily use](https://okulservisi.app/nasil-calisir)
