Series departures, 24 departures and one change

You run a seven-day tour. It departs every Saturday from April to September, which is 24 departures. In February, the hotel on night three tells you they're closing for renovation in June.

How many places do you need to make that change?

I'm Eric, from TripCreator. This is episode five, and it's for group travel: fixed departures, seat-in-coach, and anyone who sells the same trip many times on different dates. In the trade we call those series.

In the next twenty minutes I'll explain why series break spreadsheets faster than anything else in travel, walk through setting up a season in TripCreator, follow that season through a busy week, and finish with the ways series operators most often lose money, and how to avoid them.

A series is one trip sold many times. It's the same route and the same structure, on different dates, drawing on a shared pool of rooms and seats.

That sounds simple, but it's where spreadsheets break down fastest. Usually there's a master sheet for the trip, then a tab or a file for each departure, then a separate sheet tracking how many seats are sold on each date. So one change becomes 24 changes. And because rooms and seats are counted by hand, one mistake becomes an overbooking. You find out when 32 people arrive at a hotel holding 30 beds.

The pressure is also very uneven. In the quiet months it's manageable. In peak season, bookings, changes and cancellations arrive every day, and the spreadsheet that worked in February starts to crack in July.

TripCreator models a series the way you already think about it: one master trip with many departures.

You build the trip once. That's the master, with its days, hotels, coach and guide. Then you generate the departures from date rules, for example "every Saturday from April to September".

Now, the hotel closing in June. You make the change on the master, and you choose which departures it applies to. In this case that's the June departures, not all 24. The change goes out to those departures, and the rest stay as they are.

One change, made once, applied where it belongs.

Let's walk through setting up that season from scratch.

Step one: build the master trip. Seven days, the route, the hotels, the coach, the guide, the included excursions. Each one is a product from your library, placed on its day, with the descriptions and photos guests will see.

Step two: generate the departures. You set the rule, every Saturday from the first of April to the end of September, and the 24 departures appear, each with its own dates.

Step three: set the capacity. For each departure, you hold allotments with your suppliers: rooms at each hotel, seats on the coach, places on the boat trip. These are the limits of what you can sell.

Step four: check the prices. Peak weeks often cost more than shoulder weeks, because the hotels charge more. Because the departures draw their prices from your products and their seasons, each departure is priced for its dates.

Step five: publish. The departures appear for sale, and capacity starts counting down as bookings come in.

That's an afternoon's work for a whole season. In the spreadsheet world, it's usually a week, and it's never quite finished.

The second thing a series needs is capacity, and this is the part that prevents overbookings.

In TripCreator you hold allotments against each departure: rooms at each hotel, seats on the coach, places with an activity provider. As you sell, those allotments are used up.

Here's the important idea. Every departure has a bottleneck. It might be the hotel with only 12 rooms, the coach with 49 seats, or the boat trip with room for 40. Whichever is smallest decides how many people you can actually sell. TripCreator works that out for you, so the number you can sell is the real number, not the coach capacity when the hotel is already full.

That sounds like a small thing. It isn't. Many overbookings happen because someone looked at the coach and saw empty seats, without noticing that the hotel on night three was already full.

Once you have departures and capacity, you need to see them. That's the availability matrix.

It shows every departure in one view: how full each one is and what's left. You can spot at a glance that the July departures are nearly full and the late-September ones need a push.

From there you drill down. Click into one departure to see its bookings, then into a booking to see who's travelling. Then back up to the full season. It's the view a series operator usually tries to build in a spreadsheet and can never quite keep up to date.

Let's fast-forward to a week in July and see how the season behaves when it's busy.

Monday: twelve bookings arrive across five departures, some from your website, some from agents, some by phone. Each one uses up allotment on its departure, and the matrix updates as they land. Nobody is updating a seat count by hand.

Tuesday: the 19 July departure hits its bottleneck. The hotel on night three is full, even though the coach still has seats. The departure stops selling, and your team sees it in the matrix. They can ask the hotel for more rooms, or point new customers at the following week.

Wednesday: a family of four cancels from the 2 August departure. Their rooms and seats go back into the allotment, and that departure is selling again.

Thursday: a couple on the 26 July departure asks to change from a double to two singles. The rooming list for that departure updates, and the single supplements are applied.

Friday: you check the late-September departures. They're slow. You decide to put them in front of your agents and promote them on your website. You can see the problem in September while it's still July, which is exactly when you can still do something about it.

That's a normal peak week. None of it involves reconciling spreadsheets.

Let's talk more about rooming, the job everyone in group travel dreads.

In TripCreator, the room types travellers book, whether twins, doubles or singles, feed straight into the rooming list for that departure. Single supplements are applied automatically when someone books a single room. You don't calculate them by hand and then forget one.

So the rooming list and the price come from the same booking, and they agree. When the hotel asks for the rooming list two weeks before arrival, it's already there.

Many group operators run two kinds of business on the same route. Seat-in-coach is where individual travellers buy seats on a scheduled departure. Private groups are where a whole group books its own version of the trip.

TripCreator handles both side by side. A private group can be built from the same master trip as your scheduled series, with its own dates and its own pricing. You aren't maintaining two copies of the itinerary for the two kinds of sale.

When a departure is ready, you publish it.

Agents and guests can then book seats directly, and capacity updates as they book. You don't get phone calls asking "are there still seats on the 14th?", because the answer is on the page.

How online booking works in detail, including widgets, checkout and payments, is the subject of episode eight. For today, the point is that the departures, the capacity and the selling are all one system. The seat sold online and the seat sold over the phone come out of the same allotment.

One more group that should hear this: seasonal operators.

If you run a fishing river with beats and rods, a lodge with fixed weeks, or a programme of fixed-date tours each year, your business is a series too. Each season is a set of departures with fixed capacity, sold in advance.

The same tools apply. Seasonal operators use them to run a whole season from one grid, with the rules that limit what can be sold enforced as bookings come in.

Let me share four ways series operators commonly lose money. Most of them aren't about software at all, but the right tools make them much easier to avoid.

The first is overbooking. Selling a seat you don't have, because the counts were out of date or someone looked at the wrong limit. The cost isn't only the hotel room you have to find at the last minute. It's the customer who remembers it. Letting the bottleneck decide what you can sell removes most of this risk.

The second is seeing slow departures too late. A departure that's half-empty two weeks before it leaves is hard to rescue. The same departure seen two months earlier can be promoted, merged or rethought. That's why the season view matters: it shows the problem while there's still time.

The third is forgotten supplements. A single traveller books, someone forgets the single supplement, and the margin on that booking disappears. When supplements come from the room type rather than from someone's memory, they aren't forgotten.

The fourth is inconsistent changes. A hotel changes on the master, but two departures were edited by hand earlier and don't get the update. Or they get it when they shouldn't. Choosing exactly which departures a change applies to keeps the season consistent without flattening the departures you deliberately made different.

Here are the questions series operators most often ask.

"Can different departures have different prices?" Yes. Departures draw their prices from your products, including seasonal rates, so a peak-week departure is priced as a peak week.

"Can one departure be different from the rest?" Yes. You can change an individual departure, for example a different hotel on one date, without changing the master. And when you do change the master, you choose which departures follow.

"Can agents sell our departures?" Yes. Agents can sell seats, and those seats come out of the same allotment as everyone else's. Episode seven covers agents in more detail.

"What about a departure that doesn't reach its minimum numbers?" That's a business decision, and it stays yours. What TripCreator gives you is the early warning. You can see which departures are below where they should be, while there's still time to act.

So far we've talked about series from your side. But your hotels, coach companies and activity providers live with your series too, and the way you run it shapes your relationship with them.

Think about it from the hotel's point of view. They've given you an allotment of twelve rooms on every Saturday from April to September. What they want from you is simple: accurate numbers, on time, and a rooming list they can trust. What they often get is a flurry of emails in the final two weeks, a rooming list with last-minute changes, and the occasional request for two extra rooms on a night they're already full.

When your season lives in one system, you can be the operator suppliers like working with. You know your numbers for every departure at any moment, so you can tell the hotel early when a date is selling slowly and they may want the rooms back. You can tell them early when a date is selling fast and you'd like more rooms. And the rooming list you send comes from the bookings themselves, so it's right the first time.

That matters more than it sounds. Suppliers have long memories. The operator who sends accurate numbers early is the one who gets the extra rooms in a busy week, the better rate next season, and the benefit of the doubt when something goes wrong.

Here's another benefit that's easy to miss: this season teaches you how to plan the next one.

In the spreadsheet world, last season's information is scattered across files and inboxes. Working out which departures sold out, which struggled, and how early people booked is a research project, so most operators plan next season from memory and instinct.

When the whole season lives in one place, you can actually look. Which departures filled first? Which ones needed a push? Did the June departures sell later than the July ones? Which hotel was the bottleneck most often?

Those answers turn into decisions. Perhaps you add a second weekly departure in July, because the Saturdays sold out by March. Perhaps you drop the last two September dates, because they struggled two years running. Perhaps you ask the hotel on night three for fourteen rooms instead of twelve, because it was the bottleneck all summer.

And when you set up next season, you're not starting from nothing. You start from this season's master trip, generate next year's departures, and set the allotments based on what you learned. The new rates come through from your products. Your season gets better every year, because each year is built on real information from the last.

One last practical point before we wrap up: what happens when lots of people are selling the same seats.

In a typical series business, seats are sold by your own team on the phone, by guests on your website, and by agents in other countries. In the spreadsheet world, each channel has its own idea of how many seats are left, and they disagree. Agents are given a fixed number of seats to protect against overbooking, which means seats sit unsold with one agent while another agent is turning customers away.

When every channel sells from the same allotment, that problem disappears. Your team, your website and your agents all see the same availability, because there's only one. A seat sold by an agent in Germany at 3pm is immediately unavailable to your website at 3:01. And because each booking records who sold it, you can see how each channel is performing across the season.

Today's takeaway: a series is one trip sold many times, so manage it as one trip. Build the master once and generate the departures from it. Push changes to the departures they belong to. Let allotments and the bottleneck decide what you can sell. Watch the whole season in one view. And let the rooming list and the price come from the same booking.

The question from the start of the episode, "how many places do you need to make that change?", should have one answer: one.

If you'd like to see series departures in action, the link is in the show notes, along with a link to book a demonstration where we'll set up a season with you.

Next time: self-drive and multi-day tours. Day five, 280 kilometres, two waterfalls and one guesthouse.

I'm Eric. Thanks for listening.