Self-drive, day 5 and 280 kilometres

It's 8:15 in the morning on day five of a self-drive holiday. A couple is standing next to a hire car outside a guesthouse. Today it's 280 kilometres, two waterfalls, a lunch stop and a new guesthouse tonight. And one of them is asking the other: "Where's the email with today's directions?"

I'm Eric, from TripCreator. This is episode six, and it's for self-drive and multi-day tour operators. Today's idea: once the guest lands, your itinerary is the guide.

Over the next twenty minutes I'll explain why self-drive is harder than it looks, walk through a ten-day trip from enquiry to the guest's phone, share some practical advice on designing self-drive days that work, and cover the mistakes that generate the most "where do we go today" emails.

On paper, a self-drive trip is the simplest product in travel: a car, a route and a bed each night.

But think about what that couple actually needs that morning. Where to drive and roughly how long it takes. What to stop and see on the way. The address of tonight's guesthouse. The voucher for the boat trip at 3pm. And who to call if the car makes a strange noise.

On an escorted tour, the guide carries all of that. On a self-drive trip, nobody does, except your itinerary. So the itinerary has to be a guidebook, a map and a booking confirmation at the same time, and it has to work on a phone in a car park.

TripCreator was built with self-drive in mind, and that shows in four places: how you plan, how you package, what the guest carries, and how you reuse your best work.

The first is how you plan. Self-drive trips are designed around a route, so TripCreator lets you plan route-first.

You lay out the trip day by day, with the driving legs, the stops and the overnight stays, and you see it on a map as you build. You can tell immediately when day five has too much driving or when two nights in one place would make more sense.

When you move things around, the dates follow. Move a day and the days after it shift with it. You don't go through the itinerary re-dating everything by hand.

The second is putting everything in one trip. A self-drive package is a mix: car hire, accommodation for every night, and activities along the way.

In TripCreator, all of those go into the same itinerary. They can come from your own suppliers in your product library, or from providers you've connected. The car, the eight guesthouses and the boat trip are all on the right days, and the price builds up as you go.

So when the guest asks "what would it cost with a four-by-four instead?", you swap the car and see the new price straight away.

Let's follow one trip all the way through. A couple emails in March. They want ten days in early June, they've seen your highlights route on your website, but they'd like an extra night by the coast and a bigger car.

Step one: you copy your ten-day highlights template. The route, the guesthouses, the descriptions, the map and the day-by-day guide are all there already.

Step two: you set their dates and the number of travellers. The prices update for early June.

Step three: you make their changes. You add a night at the coastal guesthouse and the days after it move along by one. You swap the standard car for the larger one, and the price changes with it.

Step four: you look at the driving. The extra night actually helps, because it splits what was the longest driving day into two easier ones. You can see that on the map, and you mention it in the proposal, because it's the kind of detail that shows you know the route.

Step five: you send the proposal. It's the same live itinerary page we talked about in episode four, so they can read it on their phones, show it to friends, and come back to it.

Step six: they say yes. The bookings go out to the car company and the guesthouses from the same trip, and the vouchers come from the same data.

And in June, when they're standing in a car park on day five, the page they open is the one they fell in love with in March. Only now it's their guide.

Let's look more closely at the guest's phone, which is probably the most important part of self-drive.

The itinerary you send isn't a static document. It's a page that works on a phone. Each day shows where to drive, what to see on the way and where to sleep, with the addresses, the vouchers and your contact details.

So back to our couple in the car park. They don't search their inbox. They open the trip, tap day five, and everything is there: the route, the waterfalls, the lunch stop, tonight's guesthouse and the boat voucher.

That's the difference between a guest who feels looked after and one who feels abandoned with a hire car. And it shows up in your reviews.

Let me step away from software for a few minutes and share some practical advice on designing self-drive days. It comes from watching many self-drive itineraries, and the reviews they produced.

First, be honest about driving time. Guests underestimate how tiring driving in an unfamiliar country is, especially on the wrong side of the road. A day that looks like three hours on a map can easily be six with stops. Plan for the stops, not the map.

Second, give each day one clear highlight. A day with six "must-sees" leaves the guest feeling they missed things. A day with one highlight and two optional stops leaves them feeling they did everything.

Third, think about light and season. In winter, in northern destinations, daylight is short. A day that works in June can be unsafe in December. Make sure the day's driving fits the daylight at that time of year.

Fourth, put the practical details where they're needed. Fuel stops on remote stretches, the last supermarket before a quiet area, the time the guesthouse reception closes. These details belong on the day they matter, not in a general information section nobody reads.

Fifth, leave room for weather. A flexible half-day near a key highlight lets guests swap things around if the weather turns.

All of that is your expertise, not software. But when it lives on the products and days of a template, you write it once and every guest benefits from it.

There's a direct operational benefit too. Every self-drive operator knows the emails that come in during the season. "Where do we pick up the car?" "What's the address tonight?" "Did we book the whale watching for today or tomorrow?"

Each of those is a few minutes of someone's time, often in the evening or at the weekend. When the answers are on the guest's phone, many of those emails never get written. In peak season, that's a lot of hours.

And when something does change mid-trip, say a guesthouse has a problem and you move the guests somewhere else, you change it in the trip, and the guest's page shows the new guesthouse and its address. There's no need to send a new document and hope they find it.

The fourth place self-drive shows is templates. Most self-drive operators have a set of signature routes: the eight-day ring road, the ten-day highlights, the winter week.

In TripCreator you turn your best routes into templates. When an enquiry comes in, you copy the template, set the dates and the number of travellers, swap a hotel if needed, and the quote is done. The descriptions, the map and the day-by-day guide come with it.

That turns a two-hour quote into a ten-minute one, and the quality stays the same whoever on your team builds it. A new colleague in their first week can send a proposal that reads like it was written by your most experienced planner, because it was.

Self-drive packages also sell well online, because they're easy to understand: a route, a length and a price.

With TripCreator, you can put a self-drive package on your own website with live pricing, either on fixed dates or with flexible start dates. The guest picks a date and the number of travellers and sees the real price. Episode eight goes into how that works.

Here are three mistakes I see that generate most of the support emails self-drive operators get during the season.

The first is vague directions. "Drive to the north coast" isn't a direction. The guest needs the name of the place they're driving to and an address they can put into a map.

The second is scattered vouchers. A voucher in one email, a confirmation in another, a booking reference in a PDF. When the guest has to search, they write to you instead. When every voucher sits on the day it's needed, they don't.

The third is not saying who to call. When the car has a flat tyre on a quiet road, the guest needs to know immediately whether to call the car company or you. Put the right contact on the right page.

If you run guided multi-day tours rather than self-drive, most of this applies to you too.

The main difference is that you have a guide and a vehicle. In TripCreator, you add those as resources on the trip and send them their own day-by-day link. That covers where they need to be, who's in the group and what's booked each day. Your guide reads the same trip as the guest, from their own point of view.

Here are the questions self-drive operators usually ask.

"Do guests need to download an app?" No. The itinerary is a page that opens on their phone from a link.

"Can we change the trip after they've left?" Yes. Change it in the trip, and the guest's page shows the change.

"Can we sell our routes on our website and still tailor them?" Yes. The same template can be sold as a package online and copied and tailored for an enquiry. Both start from your best version of the route.

"We have hundreds of guesthouses. Do we need to load them all first?" No. Start with the ones on your most popular routes, and add the rest as they come up. And episode nine covers how AI import can read your existing documents to speed that up.

Let me read you a self-drive day the way a guest should see it on their phone. It's the best way to show what "the itinerary is the guide" really means.

"Day 5: The south coast. Driving today: about 280 kilometres, roughly four hours at the wheel, plus stops. Allow a full day.

Leave by nine. The first waterfall is about an hour along the coast road, with parking right by the path. You can walk behind the falling water, so bring a waterproof layer.

Twenty minutes further on is the second waterfall. It's bigger and busier, so if it's crowded, enjoy the view from the car park and move on.

Lunch: the small café in the next village is our favourite. The soup is excellent, and it's the last good food stop for a while.

Boat trip: at 3pm, check in at the harbour fifteen minutes early. Your voucher is below.

Fuel: fill up in the village after lunch. There are no fuel stations for the next 90 kilometres.

Tonight: a farmhouse guesthouse ten minutes off the main road. Reception closes at 9pm, so call them on the number below if you're running late. Dinner is served at seven and is included.

If anything goes wrong with the car, call the car company first on the number below. For anything else, call us."

Notice what's in there. Honest driving time. One highlight with a tip. A short alternative if it's busy. Food. The voucher, on the day it's needed. A fuel warning in the right place. The reception closing time. And who to call. That's the guide in the guest's pocket. And because it lives in your template, every guest who takes that route gets the same care.

Many self-drive operators sell the same region in very different seasons, and that's where templates really earn their keep.

Take a coastal route. In summer, it's long days, late light and every road open. In winter, it's short days, the possibility of closed mountain roads, and driving that has to finish before dark. The highlights might be the same, but the trip isn't.

The mistake is to sell the summer itinerary in winter with a few dates changed. Days that worked with eighteen hours of light become risky with five.

The better approach is to keep separate summer and winter versions of your signature routes. The winter version has shorter driving days, more nights in each place, and different notes: road condition links, winter driving advice, what to do if a road closes. Both versions draw on the same products, so when a guesthouse's rates change, both versions follow.

When an enquiry comes in for February, you start from the winter template, and your expertise about winter driving is already built into the trip.

After watching a lot of self-drive businesses, I've noticed a few habits that the best ones share.

They treat the itinerary as a product, not a document. They improve it every season based on what guests asked about. If three guests asked where to eat on day five, the next version of day five says where to eat.

They design for the worst moment, not the best one. They imagine the guest tired, in the rain, with a weak phone signal, and make sure the essential information is easy to find.

And they stay reachable without being needed. The guest knows exactly who to call, but the itinerary is good enough that they rarely have to.

None of those habits depends on software. But software can make them much easier to keep, by giving your best thinking a permanent home.

Today's takeaway: in self-drive, once the guest lands, your itinerary is the guide. Plan it route-first, so the driving makes sense. Put the car, the stays and the activities in one trip, with one price. Make sure it works on the guest's phone, day by day, with the practical details on the day they're needed. And turn your best routes into templates so every quote starts from your best work.

The result is fewer "where do we go today?" emails and more five-star reviews that mention how easy it all was.

If you'd like to see a self-drive itinerary the way a guest sees it, the link is in the show notes. Open it on your phone and imagine you're in that car park.

Next time: agencies, OTAs and multi-brand groups. Your products, their products, one margin.

I'm Eric. Thanks for listening.