ItinerWiz
ENFR
Join as a Founding Operator

Guides · ItinerWiz

How to plan skippers and guides for peak season

Peak-season rosters fail in three places. Time off arrives late, certifications are forgotten, and one skipper ends up on every trip. Collect time off early, write what each tour needs, plan whole weeks rather than single days, and check for gaps every morning.

Updated

Why peak-season rosters break

In May the roster fits on a whiteboard. In July you run three times as many departures, two seasonal guides start, one skipper’s licence renewal is pending, and everyone wants a day off for the same festival. The roster lives in a spreadsheet and a group chat, and gaps show up at 7:00 on the dock.

Three things break most rosters:

  • Time off arrives late. Someone mentions a wedding in passing; nobody writes it down until the week of.
  • Qualifications are forgotten. A guide is put on a trip that needs a skipper, or a certification the tour requires.
  • One person carries the season. The most reliable skipper gets every trip nobody else can cover, until they stop being reliable.

The method

  1. Write what each tour needs. Per departure (one skipper) or per guests (one guide per six guests). Include certifications.
  2. Collect time off early. Ask the whole crew for known dates before the season opens, and keep collecting.
  3. Set regular working days. Who works weekdays, who works weekends, and which hours.
  4. Plan weeks, not days. Fill a week or two at a time, so you see the pattern across the season rather than one day’s puzzle.
  5. Name the reason when one person doubles up. A skipper who also guides a small group is sometimes the right call. Write down why, so it stays a decision rather than a habit.
  6. Check gaps every morning for the next three days, while there is time to call someone in.
Diagram

From tour needs to an applied plan

  1. Tour crew needs → Proposed crew and resources
  2. Working days and time off → Proposed crew and resources
  3. Proposed crew and resources → Gaps named per departure
  4. Proposed crew and resources → You replace or skip
  5. You replace or skip → Applied

What each tour needs, plus each person's working days and time off, feed a plan for a date range. The plan proposes crew and resources per departure and names gaps in plain words. The operator replaces or skips any proposal, then applies the plan.

The planner proposes; you review and apply. Gaps are named per departure, in plain words.

How ItinerWiz supports it

ItinerWiz is the operating platform for independent experience businesses. In ItinerWiz:

  • Tours state their crew needs, per departure or per number of guests, along with the boat capabilities and stock they need.
  • Working days and time off per person. Registering time off previews the departures it would leave short, before you confirm; time off that breaks nothing says so.
  • The planner proposes, you apply. Over a date range, it proposes crew and boats grouped by departure. You can replace or skip any single proposal, and applying restates what will change first. A plan whose warnings cannot be checked cannot be applied.
  • Gaps in plain words. What the plan cannot cover is named per departure, for example “no Skipper free (0 of 1 found)”.
  • Double roles need a reason. By default one person fills one need per departure. A deliberate double role is accepted only with a reason, which stays visible on the departure.
  • Pay rules set once. Rates per crew role and tour, with weekend days, night hours and holidays for premiums. Confirm a departure with the crew who worked and the pay report follows, with a CSV export.
  • Certification expiry alerts (Pro). You hear before a certification runs out, not on the morning of the trip.
  • Crew see their own schedule. A crew member who signs in sees the departures they are on, and team members can read their team’s calendar.

You stay in charge

The planner proposes and you apply. Working-hour limits stay with you and your advisers. Crew read their schedule when they sign in, and you can text them a change by SMS.

Where to go next

Run the method on next month: needs per tour, everyone’s known time off, then one week planned at a time. If a boat goes down mid-season, the same habits help; read handling a boat breakdown. For the vocabulary, see what a tour operator is. To plan your own season in it, join as a Founding Operator or see pricing.

How far ahead should I plan crew for high season?

Collect time off and working days before the season starts, then plan a week or two ahead and confirm the next three days each morning. Planning single days the night before is where gaps slip through.

How do I avoid burning out my best skipper?

Make it visible. Count each person's departures per week, and when someone covers two roles on one trip, record why. A pattern of reasons shows you where to hire.

Does ItinerWiz build the roster automatically?

It proposes crew and boats over a date range. You review each proposal, replace or skip any of them, and apply. Nothing is assigned until you apply.

Does ItinerWiz work out crew pay and working-hour limits?

It works out crew pay. Pay rules with weekend, night and holiday premiums apply to the departures you confirm with the crew who worked, and the pay report exports as CSV. Working-hour rules stay with you and your advisers.

Run your tours, not your spreadsheets.

One flat price, and we never take a cut of what you sell. Founding Operators get 40% off any paid plan for 24 months, then today's price stays locked for as long as they stay.

Join as a Founding OperatorSee pricing