Timeline · reads event
Itinerary
Day-by-day plan.
A run of events in order, along a single line.
09:00
Team briefing
Atelier Nord
11:30
Guests arrive
60 covers
13:00
Service begins
Main hall
16:30
Breakdown
Crew of 4
How it works
- 1
Dated items are sorted and spaced by how far apart they actually are.
- 2
Gaps stay visible, so an empty fortnight looks like an empty fortnight.
- 3
Each entry expands in place for its detail.
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.
Questions
What data does the Itinerary page use?
It reads event records the agent has collected. Day-by-day plan. 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
- Atelier Nord · 2.1 km
- Salle des Fêtes · 4.8 km
- Marché · 7.3 km
Map / locations
Pinned places.
Seasonal tasting menu
Canapé selection
Service — per waiter
Glassware hire
Venues
Candidate locations.
09:00
Team briefing
Atelier Nord
11:30
Guests arrive
60 covers
13:00
Service begins
Main hall
16:30
Breakdown
Crew of 4
Travel plan
Segments of a journey.
- Atelier Nord · 2.1 km
- Salle des Fêtes · 4.8 km
- Marché · 7.3 km
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