Milestones

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Due against hit, side by side, so being eleven days late is a fact rather than a feeling.

A milestone is a fact about the project, not a piece of work — which is why there are five and not fifty.

Answers are we on track without anyone assembling a status report.

How it works

1
A handful of milestones are agreed at the start, usually five or fewer.
2
Hit is set when the thing happens, and the gap against Due is computed rather than judged.
3
The agent answers are we on track from the two columns without anyone assembling a report.
4
A missed milestone stays on the list with its real date, which is what makes the record useful later.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

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
Milestonerequired	text	The moment that marks progress. A fact about the project, not a task.
Duerequired	date	When it should happen.
Hitrequired	text	The date it actually happened, or Not yet. Both are answers.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Not a task list. If there are twenty, they are tasks and the wrong module is in use.
No dependencies — a milestone is an outcome, not a step.
Nothing recalculates the later dates when an early one slips; that is a Gantt chart.
Slippage is visible per milestone but not summarised across a portfolio.

Before it works

What you have to provide, if anything.

Nothing.
Agree the milestones before the work starts. Adding them afterwards produces a list that was always going to be met.

In practice

An agency reporting stages to a client every fortnight.

“Designs were approved on the nineteenth.”

What was said to the agent

What the agent built

The milestone marked hit, against a due date of the eighth.

What changed

The eleven-day slip was in the next report automatically. The conversation about the end date happened in August instead of October.

Better with

These do a different job on the same data. An agent can have all of them.

Gantt chartLive

Work runs over weeks or months, several tasks overlap, and a slip in one changes the finish date of others.

RoadmapLive

You want to tell customers or a team where the product is heading without committing to dates you will have to correct.

ReportsLive

Someone outside the day-to-day needs the picture periodically, with interpretation rather than raw figures.

Who uses this page

Event agency

Qualifies briefs, prices the obvious, and keeps every run-of-show and supplier straight.

Architect

Takes the brief properly, and keeps drawings, phases and approvals where you can find them.

Design studio

Takes the brief, shows the work, and keeps every project phase visible.

Consultant

Qualifies the engagement and captures the problem before the first conversation.

Questions

What data does the Milestones page use?

It reads milestone records the agent has collected. Key dates and their status. 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 list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

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.