Prep lists

A prep list is a checklist you can run repeatedly. Use one for a routine with several distinct steps, such as packing for a class or preparing a room before a call. The reusable list describes the routine; each run records what happened on that occasion.

Prep lists appear in the Tasks surface under Prep lists. They are separate from the ordinary Tasks, Completed, Recurring and Habits sections.

Create and edit a list#

Choose New prep list, give it a name and choose Create. Open its editor to change Name, Schedule and Tasks.

Enter a step in Add task and use Add or Return. A step can also have a description. Its Expected duration is optional; zero means no expected duration. The duration control accepts up to 240 minutes.

Use Link… on a step to attach supporting notes or DataJar entries. Linked material supplies a reference for that step. Linking a reference is different from copying its entire contents into the checklist label.

Add flow as task offers existing timed flows. This adds a step linked to that flow rather than inserting all of its individual timer steps into the prep list. You can also use Add flow from the expanded list. See timers and flows for creating the flow itself.

Edits to the prep-list template save as you work. Leaving the editor returns you to the list; it is not a review-and-commit dialog for a completed run.

Set the routine's schedule#

Repeat chooses the recurrence. Recurring lists expose weekday choices. Turn on Start time to choose Fires at. Stopwatch mode changes the running checklist's timing presentation.

The schedule describes the routine, not the due date of a separate canvas task. Changing it does not convert every prep step into a standalone task note.

Run the checklist#

Expand the prep-list row and start a run. The running view shows that run's checklist. You can mark items complete and inspect the details for a step.

The step's context actions include Defer, Skip and Reset. These distinguish a step you postponed, deliberately omitted, or returned to its initial state from one you completed. Use the state that describes what happened rather than checking every item solely to finish the run.

A linked-flow step can start its timed flow. Completing that flow can complete the linked checklist step. Keep an eye on the flow's own active and review states; selecting a flow reference is not the same as completing it.

Choose Finish to end the checklist run. This is the prep-list Finish action; the flow review dialog uses a different confirmation. The optional How was it? row accepts Good, Rough or a short written response. You can dismiss it without supplying an answer.

The idle list can show Last time information from an earlier run. That history belongs to a run of the list, while the template remains available for another run.

Review suggestions#

The editor offers Optimize from recent runs when run history is available. It creates proposals in Suggestions. It does not immediately rewrite the list.

Read each proposal's explanation and the referenced run count. Accept applies the proposed change and removes that proposal. Dismiss removes the proposal without applying it. Test starts a personal experiment based on its rationale; it is a different action from accepting a template edit.

If the optimisation button is disabled, run the list first so there is history to inspect. A list with no earlier runs has no timing history from which to suggest an adjustment.

Remove the template#

Delete prep list removes the reusable list. It is different from resetting a step during a run. Before deleting a list you still use, check whether you only need to rename it, change its schedule or remove a particular step.

The Programs workflow can create prep lists as support actions. Once created, those lists run in this native checklist surface. Pausing or removing a Program is not a substitute for editing the list's own schedule.