Every lodge has a version of the same problem. One guide is pulling twelve trips a week. Two others are at eight. Someone else is at five and quietly furious about it. Nobody sat down and decided this was the plan, it just happened, incrementally, because of how assignments got made in the moment.
Fair rotation is one of those operational problems that looks simple from the outside and turns out to be genuinely hard to maintain in practice. But it matters more than most lodge owners realize, and not just for morale.
Why Rotation Matters
The obvious reason is fairness. Guides who feel like they're being favored, or overlooked, will tell other guides, and that shapes your team culture for the entire season. A guide who consistently gets the high-value trips, the big tippers, the prime float sections will pull away from peers who feel stuck with the leftovers. Over time, that gap calcifies into resentment.
But there's a less obvious business reason too. Guests who book with you more than once will sometimes request the same guide, and that's fine. But if one guide is carrying most of your trips, guests who can't get that guide start to feel like they're getting a second-tier experience. You end up with an invisible dependency on a single person, a star guide problem, where your operation's quality becomes contingent on one staff member showing up healthy and motivated.
Consistent rotation keeps your full roster sharp. Guides who guide more learn more, build better rapport with guests, and develop the kind of experience that makes your whole team better. Spreading trips more evenly is an investment in guide quality across the board.
Where Rotation Goes Wrong
The most common cause of uneven rotation isn't malice, it's convenience. When you're assigning trips quickly, you gravitate toward the guides you trust most, the ones you know are reliable. This creates a feedback loop: reliable guides get more trips, build more experience, become more reliable, get more trips.
A related problem is relationship-based scheduling. If you know Guide A personally or they've been with you longer, it's natural to give them the better assignments without consciously realizing you're doing it. This isn't favoritism in the malicious sense, it's just how human decision-making works under time pressure.
The record-keeping problem compounds both of these. If you're scheduling on a whiteboard or spreadsheet, you don't have an easy way to look back and see that one guide is at 40 trips for the season and another is at 22. You're making each decision in isolation, without the context of what's accumulated over weeks.
How to Think About Fair Rotation
The first principle is that fairness doesn't mean identical trip counts, it means trip counts that make sense given each guide's role, skills, and availability. A senior guide who works full-time should have more trips than a part-timer. A guide with a fly-fishing certification will naturally get more fly-fishing trips than a spin guide. These are appropriate differences.
What you're trying to prevent is unintentional imbalance, the senior full-time guide at twice the trips of an equally available peer, not because of expertise but because of habit.
Skill-based matching is worth building in deliberately. Rather than assigning whoever's available, think about which guide is the best fit for a specific guest's experience level and target species. This makes rotations feel intentional rather than arbitrary, and it often produces better guest outcomes.
Floating time is worth tracking separately. Complex groups, large families, mixed-skill parties, guests who need extra attention, take more out of a guide than a two-person technical float. If you're counting trips without accounting for difficulty, you're measuring the wrong thing.
Hookset's guide allocation board makes this easier to manage by surfacing trip counts in real time as you schedule. Guides who are running below the weekly average show in green; those above average show in amber; anyone at more than double the average shows in red. You don't have to run a report or count cells in a spreadsheet, the imbalance is visible while you're making the assignment. Free to start at hookset.io.
Building a Rotation System, Even Manually
If you're not ready to move to dedicated software, you can still build a workable rotation system with a few simple practices.
Keep a running trip count for each guide somewhere visible, a shared sheet is fine, as long as it's updated consistently after every assignment. The goal is that anyone scheduling trips can see the current state before making an assignment.
Set a rough target ratio at the start of the season based on each guide's expected availability. If you have four full-time guides, you'd expect roughly equal trip counts with some natural variation. Use that as a reference point when you notice counts drifting.
Review rotation counts weekly, not just at the end of the season. Problems that look minor after two weeks look major after eight. A quick five-minute check every Monday can catch drift before it becomes an entrenched pattern.
When you get a specific guide request from a guest, honor it, that's part of the relationship-based service you're offering. But track those requests separately and factor them into how you think about the guide's total load. A guide who's getting a lot of requests is a good problem to have; a guide who's getting a lot of requests and is also getting first crack at non-requested trips is an imbalance problem.
The goal isn't a perfectly equal spreadsheet. It's a system where the distribution is defensible, your guides understand how decisions are made, and nobody feels like the roster is being run on politics. That's achievable even without software. But the more trips you run and the more guides you have, the harder it is to maintain manually, and the more a purpose-built tool is worth the investment.