Spaces

A weekly chat review for school and staff bus operators

This checklist tells a school or staff bus operator what to look at each week in the conversations the AI agent handled. It keeps stop times right, handovers quick and routes under control.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

A route is never really finished. A road closes, a school moves its bell, a plant adds a night shift, and a stop time that was right in September is wrong by November. Your chats show these changes first, because the people riding your buses mention them before anyone updates a sheet.

Set aside twenty minutes, ideally on a Friday afternoon after the last run. Read a handful of chats from each route, then work through the list. Keep a note of what you changed so next week starts from a clearer place and the next person covering can see it.

Tick each one as you go. 0 of 10 done.

[ ] Read five chats from your busiest morning route.
[ ] Check every chat handed over to a person.
[ ] Look for any wrong stop time the agent gave.
[ ] Note questions the agent could not answer.
[ ] Look for repeated complaints about one driver or run.
[ ] Check messages sent during delays or closures.
[ ] Update the notes for road works, new riders and changed bells.
[ ] Confirm safety handovers got a phone call, not only a chat.
[ ] Check that no chat was left unanswered over a weekend.
[ ] Write down one change to make before next week.

Reading the chats like a dispatcher

You are not marking the agent. You are reading what riders and families are living through. If three parents asked about the same stop in one week, a sign at that stop may be missing, or a time on the sheet may be off by a few minutes.

Pay special attention to the first sentence of each message. It usually holds the real worry, even if the rest rambles.

Keep a simple weekly log

A short note is enough, and it helps when staff change.

  • Date and route reviewed.
  • Wrong or missing answers found.
  • Notes updated and who updated them.
  • Any chat that needed a follow-up call.

FAQ

How many chats should I read each week?

Five to ten per busy route is usually enough to see patterns. Always read every chat that the agent passed to a person, because those are the sensitive ones.

What should I do if the agent gave a wrong stop time?

Fix the route note straight away, then check other chats for the same mistake. If a parent acted on it, a person should contact them to put things right.

Who should do the weekly review?

Ideally the transport manager or a senior dispatcher who knows the routes. They can tell at a glance whether a stop time or a rule sounds wrong.

More free tools for school and staff bus operators

Read the guide: Answer parents and employers about the bus before the morning rush.