Tour pages and itineraries that answer every question

Why a structured itinerary beats a long description

Many operators keep itineraries as a block of text: Day 1, a paragraph, Day 2, another paragraph. It reads well enough, but nothing can be checked, mapped or reused. When you shorten a trip by a day, you edit the text by hand and hope the PDF, the website and the guide's notes still agree.

In the trip builder every day is made of items: a drive, a flight, a stay, a meal, a permit or a note, each with its own times, places, distance and ascent. Because the data is structured, Tourtify can draw the map of each day, draw an altitude profile when days have a maximum altitude, build the itinerary PDF and warn you about problems before travellers see them.

Worked example: one trek, a 12-day and a 14-day option

Take a high-altitude trek you sell in two lengths. You create one tour with two options, Classic 14 days and Express 12 days. In the builder you plan all 14 days, then open the two acclimatisation days and set them to belong to the 14-day option only. The website then shows one itinerary per option, and travellers comparing the two can see exactly which days are dropped.

Adding items is quick. Under the timeline you type /flight KTM-LUA 06:30 and the builder adds a flight at 06:30; /drive Pokhara 5h adds a five-hour drive; /hotel adds a stay. Saved places carry their coordinates and altitude, so the map and the profile build themselves.

Now suppose day 6 climbs from a lodge at 3,440 m to one at 4,410 m. That is 970 m of gain in one night above 3,000 m, and the Checks panel flags it, because it is more than the 500 m the check allows. If you enter 13 days on a 14-day tour, or leave a night without a place to sleep, those are flagged too. You decide whether to change the plan or accept the warning.

Who sees what: travellers, guides and your team

Each item has a visibility setting. Traveller items appear on the website and in the PDF. Guide and team items are for the people running the trip, such as the meeting point for porters. Internal items are seen only by your office, for example a reminder to reconfirm a domestic flight.

This lets you keep one itinerary instead of three documents. The common alternative, a public itinerary plus a separate operations sheet, tends to drift apart over a season. The trade-off is discipline: check the visibility of each item when you add it, because a supplier phone number marked for travellers will appear in the PDF.

Reuse with the library, and what reuse does not do

Days most of your tours share, such as an arrival day with an airport transfer and a welcome dinner, can be saved to the library and dragged onto any tour. Small groups of items can be saved as a block.

Inserting from the library makes a copy. That is deliberate: editing one tour never changes another by accident. It also means that if your arrival hotel changes, you update each tour that uses that day. Keep library days for the parts that rarely change, and expect to edit the rest per tour.

Versions protect you from the opposite problem. Every published itinerary is kept, so you can compare a version with what is live, or restore last season's plan into the draft.

Common mistakes to avoid

Leaving days untitled: a day without a title must be fixed before publishing. Skipping maximum altitude on days: without it there is no altitude profile on the tour page. Putting visa, fitness and cancellation notes inside day items: those belong in Good to know on the Policies tab, where travellers look for them.

Finally, remember that the builder keeps a draft. Travellers see the published itinerary until you choose Publish, so a half-finished change is safe, but a finished change is not live until you publish it.