Checklist

What it does

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

A fixed sequence run identically each time, then reset — the items never change, the run does.

Who did it and when is recorded per run, which is what makes it evidence rather than a habit.

Required and optional steps are distinguished, so the important ones are not buried.

How it works

1
The steps are fixed and do not change between runs; what changes is whether today is complete.
2
Each run records who did each step and when, which is what makes it evidence rather than a routine.
3
A missed required step is visible immediately rather than at the end.
4
The checklist resets for the next run, keeping the history.

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
Steprequired	text	One action in a fixed sequence, phrased so anybody could do it.
Requiredrequired	choice	Yes or No. Distinguishing the two is what stops the important steps being buried.
Done byrequired	text	Who did it on this run, or Not yet. Recorded per run, not per item.
At	time	When. Turns a habit into evidence.

What it does not do

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

One sequence per checklist. A different opening routine for weekends is a second checklist.
No conditional steps or branching.
Nothing enforces order, so a step can be marked before the one above it.
No photographic evidence attached to a step.

Before it works

What you have to provide, if anything.

Write the steps once and resist adding to them. A twenty-step checklist stops being followed.
Pair with Check-ins if who was on site matters as much as what was done.

In practice

A café with an opening routine that varied by who was on.

“Fridge temperatures, grinder, float, pastries.”

What was said to the agent

What the agent built

A four-step checklist with required flags, reset each morning.

What changed

The float count was missed twice in the first fortnight and both were visible immediately. It stopped being missed.

Better with

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

To-do listLive

The work is a sequence of small independent things and nobody needs to know what stage each is at.

PlaybooksLive

The same situations recur and get handled differently depending on who is on shift.

Check-insLive

Presence needs recording at the moment it happens, for safety, billing or simple accountability.

Who uses this page

Tutor or school

Answers parents’ questions and captures the level, subject and availability that matter.

HR team

Answers the policy questions that fill your inbox, without anyone having to ask a person.

Accountancy firm

Answers the deadline and paperwork questions, and chases what you are still missing.

Driving school

Answers price, availability and test questions while you are in the car.

Questions

What data does the Checklist page use?

It reads task records the agent has collected. Steps to complete. 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.