Timeline · reads trip
Travel plan
Segments of a journey.
A run of events in order, along a single line.
14–16 Oct
Lyon
TGV 06:52 from Gare de Lyon
16–18 Oct
Turin
Train, 4h, change Chambéry
18–20 Oct
Milan
Train, 1h50
20 Oct
Return
Flight MXP–CDG 19:40
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Where you are each night and how you get between, which is the level flights are booked at.
Coarse on purpose — the per-day detail belongs in an itinerary.
Somebody at home can see which city you are in, which is most of why it exists.
How it works
- 1
A trip is laid out by legs — where you are each night and how you get between.
- 2
Coarse on purpose; the per-day detail belongs in an itinerary.
- 3
Somebody at home can see which city you are in, which is most of why it exists.
- 4
Overlaps between a travel leg and a commitment are visible before booking.
Best for
A schedule someone reads top to bottom — a run-of-show, an itinerary.
Not the right choice for
Comparing parallel workstreams; that is a Gantt.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Datesrequired | text | The leg, as a range. Nights rather than hours. |
| Whererequired | text | The city or place for those nights. |
| Travel | text | How you get there, in enough detail to book from. |
| Staying | text | Where you sleep, which is the other half of a trip plan. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- No booking or pricing; it records a plan rather than making one.
- No timezone handling across legs.
- One traveller. A group with different legs needs a plan each.
- Expenses are separate — this does not total the trip.
Before it works
What you have to provide, if anything.
- Nothing.
- Pair with Itinerary for the days that need detail, and Expenses if the trip is billable.
In practice
A founder doing a three-city trip in a week.
“Lyon the fourteenth to the sixteenth, then Turin, then Milan.”
What the agent built
A trip laid out by dates with travel and accommodation per leg.
What changed
The Turin to Milan leg turned out to overlap a meeting. It was found while booking rather than on the platform.
Better with
These do a different job on the same data. An agent can have all of them.
A day is planned in detail for someone else to follow, with times and places they have not been to before.
The business runs on appointments or dated commitments and someone needs to see the shape of the month rather than a list.
Small spending happens constantly and gets reconstructed painfully at tax time because nobody logged it when it happened.
Questions
What data does the Travel plan page use?
It reads trip records the agent has collected. Segments of a journey. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a timeline the wrong choice?
Comparing parallel workstreams; that is a Gantt. It is best for: a schedule someone reads top to bottom — a run-of-show, an itinerary.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Places & logistics
- Oberkampf — 48 rue Oberkampf, 75011
- Marché des Vosges — Place des Vosges, 75004
- Café Bellevue — 12 rue de Charonne, 75011
Map / locations
Pinned places.
The Long Room
80 standing, 50 seated
Open, pillars
Atelier, 2nd floor
24 seated
Workshop, benches
Courtyard
120 standing
Outdoor, covered half
Meeting room
10 seated
Boardroom, screen
Venues
Candidate locations.
09:00
Coffee and briefing
Oberkampf
10:30
Roastery tour
Atelier Nord
12:30
Lunch
Café Bellevue
15:00
Cupping session
Oberkampf
Itinerary
Day-by-day plan.
- 1 — Café Bellevue, 75011
- 2 — Hôtel Vasari, 75004
- 3 — Marché, 75004
Routes
Paths between places.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free