Timeline · reads event
Planning / schedule
A run-of-show / agenda timeline.
A run of events in order, along a single line.
07:30
Load in, unlock the hall
45m
08:15
Floor plan and chairs
1h 30m
09:45
Sound check
30m
10:30
Doors
—
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Blocks have length, so an overrun is visible before it cascades into the rest of the day.
Answers what happens when and what it is waiting on, which a calendar cannot.
Owners are named per step, so the handover points are explicit.
How it works
- 1
Steps are entered in order with a duration each, usually in one conversation.
- 2
The timeline lays them out by start time, with length drawn from the duration.
- 3
An overrun is visible as an overlap rather than discovered on the day.
- 4
Owners make the handovers explicit, which is where most day plans actually fail.
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 |
|---|---|---|
| Timerequired | time | When the step starts. |
| Steprequired | text | The action, as dictated: load in, sound check, doors. |
| Durationrequired | text | How long it takes. The field that separates this from a calendar. |
| Owner | text | Who is responsible, so the handover points are explicit. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- One day. A multi-day build needs a Gantt chart, which is about weeks.
- Durations are text, so nothing sums them or warns that the day does not fit.
- No dependencies between steps — order is implied by time, not enforced.
- No live progress. It is a plan, not a tracker.
Before it works
What you have to provide, if anything.
- Nothing. Usable from a single dictated run of show.
- Pair with Checklist for the steps that must be verified rather than merely scheduled.
In practice
An events crew running an install day.
“Load in at half seven, floor and chairs takes an hour and a half.”
What the agent built
A sequenced day with durations and owners, from load-in to doors.
What changed
Sound check was scheduled to finish fifteen minutes before doors. Seeing that written down moved load-in half an hour earlier.
Better with
These do a different job on the same data. An agent can have all of them.
The business runs on appointments or dated commitments and someone needs to see the shape of the month rather than a list.
The business puts on things people attend and needs the next few dates visible on the site without editing a page each time.
A routine must be performed identically each time and missing a step has consequences.
Who uses this page
Event agency
Qualifies briefs, prices the obvious, and keeps every run-of-show and supplier straight.
Conference organiser
Handles attendee questions at scale and keeps the programme, speakers and venue straight.
Wedding planner
Qualifies couples on date, budget and guest count before you give up a Saturday.
Festival organiser
Answers ten thousand ticket-holders at once, and keeps traders, stages and crew straight.
Questions
What data does the Planning / schedule page use?
It reads event records the agent has collected. A run-of-show / agenda timeline. 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 Planning & time
Fri 12 Sep — Autumn tasting
Events
Everything the agent schedules — dates, place, attendees.
4 Sep — Tasting — Maison Lauret
Calendar
Month/week view across all dated nodes.
Gantt chart
Tasks & phases with dependencies and durations.
Q3
Custom domains
Shipped
Q3
Module library
Shipped
Q4
Team accounts
In progress
Q1
Public API
Planned
Roadmap
Milestones across quarters/phases.
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