Today's-ops dashboard: what one screen should show in a tour-operator back office
A manager spends half the morning assembling 'what's running today' from chats and a spreadsheet. How one screen turns four group-chats and a Google Sheet into a ten-second check.
Every seasonal tour operator has a morning ritual. Someone opens the drivers' WhatsApp. Someone else opens an Excel sheet with guide schedules. Someone else opens a separate sheet with hotel check-ins. Twenty minutes later, you have a picture of what's supposed to happen today. Forty minutes later, you have a list of what's already broken.
That morning picture costs zero in the product line and tens of hours in the team. And it's everywhere a tour operator doesn't have a single home for operations.
What an "operations dashboard" actually is
Don't confuse it with the CRM kanban. The kanban is about leads you want to convert into bookings. The operations dashboard is about bookings that are turning into physical events today: a 7:30 airport pickup, a 14:00 hotel check-in for a group of 6, a dinner for 12 at 19:00.
A useful rule: kanban looks forward (what we'll sell), the dashboard looks down (what we're doing right now).
What absolutely has to live on one screen
Minimum useful set:
Grouping by service type. Separate sections for pickups / transfers / hotels / activities / guides. Not a single mixed list, because each section has different owners and different anxiety sources. The driver shouldn't have to scroll past eight guide rows to find their pickup.
Time with minutes, not "morning / afternoon". If you have "morning transfers" you've already lost. A specific clock time is a contract with the supplier and with the customer simultaneously.
Pax count next to the service. How many people in the transfer, on the guide, at the dinner. Without it you can neither order a right-sized vehicle nor book the right table.
Supplier and resource on one row. "Guide Anna for the Kremlin tour, Ivanov family, 8 people, 14:00" — one row, one truth. Not "Anna has some Kremlin group" in one chat and "Ivanov family on Kremlin tour with a guide" in another.
Voucher status. Documents in hand: issued / delivered / consumed / cancelled. Without it, you find out about a cancelled service when the customer is already at the door.
Click-through to the booking. Every row should jump to the customer record, because when something goes wrong you want the lead's phone, allergies, and notes immediately.
What does NOT belong on the dashboard
The dashboard is not a kanban, not a finance report, not analytics. It does not host:
- Leads and inquiries (that's the inbox).
- Pipeline deals (that's the kanban).
- Margin and profit (that's analytics).
- Customer history (that's the guest record).
Every time you're tempted to "throw revenue numbers in there too", you're making the dashboard worse. One screen, one question: what's running, checking in, going on tour today.
What changes for the team
Two weeks after we rolled this out with a pilot operator, the morning standup shrank from 25 minutes to 8. Not because people talk less — because nobody's assembling a picture from scratch any more, the picture is already there.
Surprises haven't disappeared (and won't — it's tourism). But the shape of surprises shifted: from "oops, we forgot to book a vehicle" to "oops, the supplier cancelled a transfer two hours out". The second is normal business risk. The first is embarrassing.
Unexpected bonus: a new hire ramps in half a day instead of a week. Used to be that you had to memorise which chats to watch and which sheet to update; now — open one screen.
How it's wired in INITE Travel
In Phase 10 we shipped /operations — a screen that pulls every active booking whose departure window includes the requested date. Inside: five sections (pickups, transfers, hotels, activities, guides), time-sorted, voucher status on each row, link back to the booking record.
And — important — vouchers carry a QR code for suppliers. The supplier scans the code and lands on a public status page (issued / delivered / consumed / cancelled), no auth required. No more "is this voucher still valid?" phone calls — there's a QR, there's an answer in two seconds.
If you don't have a screen like this yet — make one. In Notion if you must. On a Trello "Today" board if you must. The "assemble the picture" ritual is the most expensive work an operator does and the only one they shouldn't be doing for a single minute.