Life after the whiteboard

Adventure Idaho · 2024–present

For years we ran the whole operation off a whiteboard. Every trip, every guide, every van, in dry erase marker. It worked right up until it didn't, and it never told anyone anything it knew. This is what replaced it, and what it actually looks like to use.

What it replaced

A wall-mounted whiteboard holding one week of rafting operations in hand-written marker: columns for Monday through Saturday, launch times with guest counts, crew assigned per trip, driver and van assignments, and colored lines tracking multi-day trips across days. — One week, in marker. Trips, crew, drivers, vans, shuttles.

The dispatch board: a multi-week grid of rafting trips with launch times, guest counts, and crew status, above a row of live counters for guests out today, guests in the next seven days, trips still needing a lead, and rentals awaiting a decision. — The same week, in the system.

Same operation, same week. The whiteboard could show you the plan. It could never tell you the van you just wrote down was already ninety miles away.

The board

Every trip carries a status the whole crew can see. Cleared, still needs a lead, something changed since it was set up. The counters across the top are the questions somebody used to answer by counting the board by hand: how many guests are out today, how many next week, what still needs filling.

On a phone, where the crew actually reads it

The same dispatch board on a phone: a week of trips as stacked cards, each showing launch time, guest count, day number of a multi-day trip, and a cleared or open status, with a movements row underneath for driver runs. — The same board, on a phone.

Nobody waits for one person to text the plan out. A guide standing at the ramp can see the same thing the office sees.

Underneath it there is a real permission model, because a schedule is not one document everyone should see all of. The crew view is open to the team, so nobody has to log in to find out what they are doing tomorrow. The manager views sit behind access tiers, set separately for pay, permissions, reporting, and who is allowed to move a person from one assignment to another. A lead sees what a lead needs. Nobody turns up a pay rate because they opened the board to check their own week.

That is the part that actually changed the mornings. Assignments used to be a 45 minute write-up, and then a meeting to read it out loud. Now there is neither. The team checks it themselves. The safety briefing still happens, because that was never the part a screen was going to replace.

Assigning crew

The crew grid with a guide-assignment popover open: a role selector, the two trips that guide could fill that day with guest counts, a button to put them on store for the day, and buttons to mark a paid break day or a full day off. — Click a guide into an open role, put them on store, or mark a day off.

The edit-crew panel for a multi-day trip: a checklist flagging that the jetboat is not confirmed and the crew is short two of four, lead and other guides staged as removable chips, a suggested guide, and a button to propose a crew and rig for a person to confirm. — The faster way. The panel tracks what is still open on a trip, and proposes who fits. Surnames redacted.

You can move people by hand, one at a time, the way you would slide a magnet around. Or you can let it propose a crew and a rig and then confirm it. Either way it only offers people who are actually cleared for that water and actually free that day.

What each guide sees

The crew schedule: one row per guide with role badges beside each name, and one column per day showing the trip that person is leading or guiding, driver runs with the assigned vehicle, travel and training days, and time off. — One row per guide, one column per day. The badges are the roles each person is cleared for.

Guides check their own week instead of texting to ask. Time off, training days, and driver runs all sit in the same grid as the trips, so there is one version of the week and everybody is reading it.

Movements, vehicles, and trailers

A trip panel opened from the crew grid, showing the guest count, the lead guide and driver slots, the assigned vehicle and trailer, a manifest summary with waiver counts, buttons to print the checklist, and a line confirming no conflicts on this trip. — One trip, opened up: who is leading, who is driving, which vehicle, which trailer, and whether anything collides. Surnames redacted.

Every trip carries its rig with it. Which van, which trailer, who is driving, and when it has to leave to make the put-in. That used to be a separate line of marker on a separate part of the board, and it was the first thing to go stale.

Tasks, and the things that break

Anyone can report a problem, by text or a form, and it becomes a tracked task with a category, a priority, the piece of gear it belongs to, and a person's name on it. If it needs buying, one checkbox puts it on the shopping list so it rides to town on the next supply run.

So far that has carried 130 issues, closed 97, and put 69% of them on a specific person. Of the 14 things that reached the shopping list, 9 were vehicle or trailer safety parts: a jack, a battery, wipers, a tire tool. The things that get forgotten until they strand a trip.

Food, coolers, and packing

A cooler packing sheet for one night of a multi-day trip: frozen, refrigerated, and dry sections with each item, quantity, and unit, a packed and verified checkbox for each, and a pull list organised by meal alongside prep-ahead notes. — One cooler, one night, one trip. Frozen, refrigerated, dry, with a pull list by meal.

What goes in which cooler, for which trip, for how many people, with a box to tick when it is packed and another when someone has checked it. The counts come off the trip, so a group that grows from twelve to eighteen changes the food list too.

Time off the board actually respects

A crew time-off request posted automatically into the management channel with the requested dates, the reason, and a link through to the underlying record. — A request lands in the same model that builds the schedule. Name redacted.

A whiteboard shows you today. It cannot tell you four people asked for the same weekend in August, or that the guide you just put on a five-day leaves on day three. Requests land in the same place the schedule is built, so an approved day off cannot quietly get assigned.

The collision it catches before the ramp

A week of trips with status flags: a legend defining red as a hard conflict, yellow as needing attention, and green as all clear, above trip cards showing cleared trips, trips still open on crew, and guest counts that have changed since the trip was set up. — Red is a real collision. Yellow needs a person. Green is cleared.

A double-booked guide, a van committed in two places, a trailer that cannot be on two rivers at once. It flags them the moment they are created, not at the boat ramp the next morning. This is the part a whiteboard can never do, because a whiteboard cannot check itself.

None of that runs on its own. Underneath it there is a layer that reads what the crew already says and works out what each message means for the schedule, and how the whole thing is built, including the AI layer and updating the board by talking instead of clicking. There is also the capacity problem, and why that engine can only advise.

Every outfitter I talk to has a version of this whiteboard. If you run one and want this built for your operation, that is what I do for other companies, in small fixed-scope engagements. Or just get in touch.