Itineraries: Routes, Days and Honest Promises

Model a journey as a route plus day-by-day plans, offer 6- to 14-day options, and say clearly what is confirmed later.

15 Oct 20264 min read#Itineraries#Content design#Tourism

Lesson 5 of 10 · Tourism Tech · built from Nora Travels, Nora Labs, Mahesh Travellers and my hospitality sites

An itinerary is the product a traveller actually buys. It needs a shape a page can render and a promise it can keep.

Example — the Itinerary schema

ExampleTypeScript

export interface Itinerary {
  id: string;
  slug: string;
  title: string;
  duration: string;      // "10 Days / 9 Nights"
  badge: string;
  tagline: string;
  idealFor: string;
  coverImage: string;
  route: string[];       // ordered stops
  days: { day: number; title: string; description: string }[];
}

Example — suggested journeys on Mahesh Travellers

Journey	Length	Route
Culture & Kandy escape	6 days / 5 nights	Sigiriya → Polonnaruwa → Kandy → Negombo
Sacred hills & tea country	8 days / 7 nights	Kandy → Nuwara Eliya → Seetha Eliya → Horton Plains → Ella → Negombo
The island discovery	10 days / 9 nights	Sigiriya → Kandy → Nuwara Eliya → Ella → Udawalawe → Galle
Sri Lanka, a little slower	14 days / 13 nights	Sigiriya → Kandy → Nuwara Eliya → Ella → Udawalawe → Galle → Weligama

Plus a nine-stage signature route — Airport → Sigiriya → Polonnaruwa → Kandy → Nuwara Eliya → Ella → Udawalawe → Galle → Airport — where each stage opens to show places, activities and the overnight stop.

Writing rules that build trust

Start from the guide's own plan — Mahesh's nine stages came from his handwritten itinerary.
Show the route as arrows first; details second.
State what is confirmed later: dates, hotels, transport, guiding, availability and inclusions.

Try it yourself: open a journey on Mahesh Travellers and compare the route line with the day-by-day dialog.