The 10 PM Report: Five Minutes to Know Your Bus's Whole Day
Every evening the AI passenger report lands in your inbox — here's what's in it and the three questions worth asking before you turn off the light.
The report lands at 10 PM whether you look or not
By the time you are brushing your teeth, your bus has already finished its last run of the day, parked up, and gone quiet. And whether you glance at your phone or not, the daily passenger report has already landed in your inbox — every trip, every stop, every boarding, counted and logged while you were doing something else entirely.
That is the point of it. You were not standing on the curb in Orange Walk counting heads, and you were not riding the route from Belmopan to check the conductor's math. The cabin camera and the AI counter were. The report is what they saw, written down, waiting for five minutes of your evening.
What's actually in it: trips, boardings, alightings, the day's gallery
Open it and you will find the day broken into trips — each run of the route, start to finish, timestamped. For every trip, the report shows boardings (how many people got on) and alightings (how many got off), counted from the cabin dashcam footage, not from a conductor's tally sheet or a ticket stub count.
Below the numbers sits what we call the gallery — still images pulled from the cabin camera across the day, a visual record of who was riding and when. It is not there to replace the numbers. It is there so that if a number looks strange, you can actually look at the bus instead of guessing.
Put together, you get a full shape of the day: how many trips ran, how many people rode each one, and a picture to check it against. That is the whole report. No fuel figures, no driver score, no diagnostics — just who was on your bus, and when.
Where the fare estimate comes from — and what it isn't
Next to the boarding and alighting counts, you will see an estimated fare figure. It is worth understanding exactly what that number is, because it is easy to misread.
The estimate is calculated from the distance each passenger travelled — boarding stop to alighting stop — run through the fare settings you configured for that vehicle. It is a calculation, not a count of money collected. It does not know what the conductor actually charged, whether a student fare applied, whether someone rode free, or whether a note changed hands instead of coins.
Think of it as what the trip should have earned if every passenger paid the standard fare for the distance they rode. It is a baseline — a number to compare against, not a cash total to bank on. The value is in the gap between this estimate and what actually came in at the end of the night, not in the number by itself.
Question one: does the trip count match what the driver told you
Start here, because it is the fastest check. If your driver said four runs to San Ignacio and back, the report should show four trips. If it shows three, or five, that is worth a question before you move on to anything else.
This is not about catching anyone out. Trips get merged, routes get cut short because of a mechanical issue or bad weather on the Hummingbird, a last run gets added to cover a gap. The report just tells you what actually happened, so your evening conversation with the driver starts from the same facts instead of two different memories of the day.
Question two: do boardings and alightings make sense for the route
Next, look at the shape of the numbers against the route itself. A run through Belize City at 7 AM should look busier than the same run at 2 PM. A long-distance trip to Punta Gorda should show boardings clustered at the main stops, not spread evenly across nowhere in particular.
You are not doing forensic accounting here — you are doing a sense check. Does the pattern look like a normal day on this route, or does something stand out? A trip with almost no boardings on a route that is usually full. A huge spike in alightings at a stop that is normally quiet. These are not accusations. They are questions, and the gallery is right there to answer most of them in a glance.
Question three: is there a gap that needs a phone call tonight, not tomorrow
The third question is the one that actually changes what you do before bed: is there anything here that cannot wait until morning?
Most nights, the answer is no. The numbers look like a normal day, the trip count matches, and you close the app. But some nights something sits wrong — a trip that is missing entirely, a boarding count that is far out of line with what the driver reported, a gallery image that does not match the route you expected. On those nights, a short call or a WhatsApp message tonight, while the day is still fresh for everyone, saves a longer argument tomorrow when nobody remembers the details the same way.
That is the real value of reading the report at 10 PM instead of catching up on Sunday. Small gaps get caught small.
Five minutes, every night, no surprises on payday
None of this requires you to sit with a spreadsheet or chase anybody down every evening. Most nights it is a genuine five minutes: open the report, check the trip count, glance at the boarding pattern, close the app. The nights it takes longer are exactly the nights it is supposed to take longer.
What you get for that five minutes is something a lot of bus owners in Belize have never had before: a plain, same-day record of what your bus actually did, independent of anyone's memory of the day. Payday stops being the moment you find out something was off three weeks ago. You find out tonight, while it still matters.