Most ops meetings drift to 45 minutes. With 8 buckets, ETA discipline, and the right weekday comparison, yours can collapse to 6 — and start deciding instead of describing.

The Daily Ops Briefing: a 6-minute format that actually fixes things

Most fleet operations meetings are supposed to take 15 minutes. They take 45. By the time the third bus is discussed, half the room is on their phones, the maintenance head is arguing with the spares clerk about a quote from last Tuesday, and the marketing seat — who only came to ask about the Goa weekend buses — has quietly walked out. The GM glances at yesterday's revenue, frowns at the dip, and the whole room spends ten minutes panicking about a number that was never going to match Sunday's anyway.

I have sat in that meeting. I have run that meeting. And the honest truth is, the problem is not the people in the room. The problem is that the meeting has no structure, no agenda that survives past the first off-road bus, and the wrong comparison sitting at the top of the screen. Fix those three things and the meeting collapses from 45 minutes to 6 — and starts actually deciding things instead of describing them.

This is the format we built into Fleetain's Daily Ops Briefing page, and it is the same one Konduskar Travels runs at their depots at 11 AM every morning. Here is how it works, and why each part of it earns its place.

The three things a good ops meeting must do (and most don't)

Strip everything else away. A morning fleet briefing exists to make exactly three decisions, in this order:

1. What comes back on the road today. Which off-road buses can realistically be released by evening dispatch, and what is the one blocker for each?
2. What pulls offline. Which on-road buses have a complaint serious enough that running them tonight is a bigger risk than holding them back?
3. What to chase. Which vendor needs a phone call, which PO needs a signature, which payment needs to be released by the end of today so that tomorrow's meeting is shorter than this one.

If a topic does not feed into one of these three decisions, it does not belong in the 11 AM. Yesterday's revenue does not. The cleaning roster does not. Last week's accident report does not. Send those over WhatsApp. The 11 AM is for decisions only.

Why "yesterday vs today" is the worst comparison

The most common bad habit in Indian bus operations meetings is opening with: "Yesterday we ran 84 buses, today we are running 79, why?" It feels like a sharp question. It is not. It is a noisy question.

Sunday is not Monday. A Pune–Mumbai schedule that fills 11 trips on a Friday evening will not fill 5 on a Tuesday morning. Bengaluru–Chennai loads differently on a long weekend. Hyderabad–Vijayawada has a corporate Monday-morning spike that no Sunday can match. If you compare Monday to Sunday and panic about the dip, you are panicking about the calendar.

The fix is small and the difference is enormous: compare today against the same weekday last week. Monday vs last Monday. Saturday vs last Saturday. That comparison strips out day-of-week seasonality and leaves you with the only signal that matters — is something genuinely worse than it should be, or is the calendar just doing what the calendar does?

During Goa season, during Diwali rush, during the Ganpati surge — the same-weekday-last-week comparison is the only one that does not lie to you. Fleetain's KPI strip uses it by default. Yesterday is not available as a comparison from the briefing page, and that is deliberate.

The 8 buckets the meeting actually needs

Every off-road bus, every morning, falls into one of eight buckets. Not twelve. Not five. Eight. Each bucket has one trigger and exactly one action verb the meeting needs to commit to:

• 🚨 Breakdown / Accident → recover the bus. Where is it, who is going, when does it reach the workshop?
• 📦 Parts / Vendor → chase the delivery. Which vendor, what was promised, who is calling them after the meeting?
• 💰 Payment / Quote → approve the PO. The bus is waiting on a signature, not on a spanner. Get it signed today.
• 🛠 Workshop (IWO/OWO) → release for service. The work is done or nearly done — who confirms roadworthy, and by when?
• 👷 No Manpower → find a driver. Bus is fit, crew is not. Reassignment call lives here.
• ⚠ Critical Complaint → inspect today. Driver flagged something serious last night; the bus runs only after a fitter signs off.
• 🛏 Halt / Parking → decide use. Bus is fine but parked. Is it a spare, a reserved hire, or genuinely idle and losing money?
• 🟢 On-Road → no action. Skip it in the meeting.

The discipline is that every off-road row in the briefing carries exactly one of these tags, and the conversation for that bus is whatever the verb is for that bucket. Nothing else. If a bus is in Parts/Vendor, the meeting does not relitigate whether the workshop should have caught the issue earlier. That is a different meeting.

The 6-minute run sheet

Here is the literal agenda. Time-boxed. Same every day. The page is structured to walk in this order so the chair is just scrolling top to bottom.

• 0:00 – 0:30 — KPI strip. On-road count today vs same-day last week. Total money blocked across off-road fleet. Count of buses planned to come back today. Three numbers. Thirty seconds.
• 0:30 – 2:00 — Top 5 lowest health-score buses. The table is sorted ascending by health score (0–100). You are not walking the whole fleet. You are walking the five buses that are bleeding the most. Each row shows the "why off-road" bullets so nobody has to ask "what's wrong with it again?"
• 2:00 – 4:00 — Bottleneck-bucket walk. The operator confirms or overrides the auto-classified bucket on each row using the ✏ Update status button. The algorithm gets you 80% of the way; the operator's confirmed call is what the meeting commits to.
• 4:00 – 5:00 — ETA commitments captured. Every off-road bus walks out of the meeting with an Expected Back date. "MH-14-XX-1234 back on the road by Wed evening, PO #1234 with VendorX, owner: Suresh." Typed into the row, not into a notebook.
• 5:00 – 6:00 — Slipped commitments review. Yesterday's ETAs that did not happen are auto-flagged at the bottom of the page. Each one gets thirty seconds: why it slipped, new ETA, or escalate.

Six minutes. The chair does not need to be charismatic. The format does the work.

Three rules that make this meeting stick

The format only holds if you protect it with rules. We use three.

Rule 1: the operator's confirmed bottleneck overrides the algorithm. Fleetain auto-classifies the bucket from the latest workshop and complaint data, but the human in the meeting has the final say. If the system says "Workshop" and the operator says "no, it's actually Payment — the quote is sitting with accounts," the operator wins. That override is what the next 23 hours of follow-up will be based on.

Rule 2: every off-road bus must have an Expected Back date. No exceptions. "Don't know" is not an answer. "End of week" is not an answer. A specific date, even if it is wrong, is better than no date — because a wrong date is a commitment you can review tomorrow, and "don't know" is a bus that quietly stays off-road for eleven days.

Rule 3: any ETA that slips for two consecutive days escalates to the GM. One slip is life. Two slips in a row is a pattern, and the meeting is not the right place to fix it. The page flags these automatically; the chair does not have to remember.

What the data captures that the whiteboard never did

The whiteboard version of this meeting — the one most depots have been running for years — loses everything the moment the cleaner wipes it down. The new format keeps three things the whiteboard never did:

• Slipped-commitment history per bus. Over a month, you can see which buses keep promising a return date and missing it. That is usually not a bus problem; it is a vendor or process problem.
• Vendor reliability over time. "VendorX promised Tuesday, delivered Friday" — once is a story, twelve times is a sourcing decision. The data is now sitting in the row, not in someone's memory.
• Recurring root causes per bus. The Repair History modal opens from the meeting page itself. When someone asks "when was this battery last replaced?" the answer is one click away, not a WhatsApp thread to the workshop in-charge. This connects directly to a serious Zero Breakdown Strategy — you cannot prevent the next failure if you cannot see the last three.

Making the meeting walkable for the maintenance and marketing seats

The same table reads differently depending on which chair you are sitting in, and that is a feature, not a bug.

The maintenance head is reading the "why off-road" bullets and the workshop/parts buckets. Their job in the next six minutes is to commit ETAs and flag the buses that need a fitter to look at them before evening dispatch — directly tied to the live Vehicle Complaint Management queue from last night's drivers.

The operations head is reading the on-road count and the Halt/Parking rows. Their job is to decide which spares cover which routes tonight and which idle buses can be repositioned.

The marketing seat is reading the same-weekday-last-week comparison and the Goa-season / Diwali-rush buses. Their job is to know whether tonight's load is genuinely soft or whether the calendar is just being honest.

The accounts seat, when they attend, is reading the Payment/Quote bucket and the money-blocked total. Their job is to walk out with a list of POs to clear before lunch — and to confirm which work orders are stuck waiting on their signature.

Same table. Four different reads. Nobody is sitting through someone else's agenda.

FAQ