Why reusable checklists beat memory
The strange thing about repeated work is that practice makes it less safe, not more. The first time you host guests, you plan carefully, because you are nervous. The fortieth time, you wing it, because you are not. Confidence is exactly the condition under which steps get skipped, and the skipped step is never a random one. It is the boring one: the thermostat, the mail hold, the follow-up email.
A written checklist moves the remembering to a better moment. Rebuilding a list at 10pm the night before a flight means doing recall under pressure, tired, with the clock running. Building it once, on a calm afternoon, means doing that work exactly one more time in your life. Every run after that is reading, not remembering, and reading does not degrade when you are stressed.
There is a quieter benefit too. Psychologists call the pull of unfinished business the Zeigarnik effect: open loops keep claiming attention until they are closed or parked somewhere you trust. A checklist you believe in closes the loop early. The trip stops humming in the back of your head a week out, because the knowing is no longer your job.
How to build a checklist template that works
Write it right after a run, not before one. The night you get home from the trip, the hour after the client call, the day the post goes live: that is when the missing step is fresh, because you just tripped over it. A checklist written before the first run is a guess. A checklist written after the third run is a record.
Make each line one action, starting with a verb. Bathroom is not a step, it is a region. Wipe the sink, restock the towels, check the spare toothbrush: those are steps, because each one can be done and then be done with. If a line needs a paragraph to explain, it is two lines.
Keep it short. A dozen steps is about the ceiling; past that, people skim, and skimming is how checklists fail. If the real workflow is longer, split it by phase, prep and day-of and wrap-up, and treat each phase as its own pass.
Finally, mark what changes between runs. In a packing list, the destination and the dates change; the chargers do not. In a client onboarding, the client and the plan change; the welcome email does not. Separating the variables from the constants is what turns a one-off list into a template, and it is the step most people skip.
What deserves a checklist first
The rule of thumb: anything you do more than three times a year that has more than four steps. That is precisely the territory where memory feels reliable and is not. Below that, a list is overhead. Above it, the rebuild tax compounds quietly every time.
The usual suspects at work: client onboarding, from contract to kickoff. Publish day, the eleven small steps between draft done and actually live. Meeting prep, reread the last notes, agenda into the invite, recap sent after. Month close, invoices out, receipts in, subscriptions eyeballed.
Households have the densest ones. Trip packing. The guest-arriving sweep: sheets, groceries, the entry closet. The leaving-for-a-week routine: thermostat, plants, spare key, hold the mail. The kid-birthday sequence, invitations through thank-you notes. None of these are hard. All of them have a step that gets dropped exactly once a year, at cost.
How routines work in Matters
In Matters, a reusable checklist is called a routine, and the way you make one is honest: you do the work once. Run the onboarding, pack for the trip, plan it as a normal project with normal tasks. When the shape is right, open the project and save it as a routine. Its steps become the template, and it waits on the Routines shelf in Explore, synced to every device you own.
Steps can carry placeholders in braces. A template step that reads send {client} the {tier} welcome pack is generic on the shelf. Run the routine with one line of particulars, Acme, enterprise, and it comes out as send Acme the enterprise welcome pack. Every run mints its own project, Acme onboarding, stamped on every task, so two clients never blur into one pile.
You do not even have to open the shelf. Say client onboarding for Acme into a capture, any capture, and Matters recognizes the invocation and runs the routine. Ten seconds later the steps are real tasks: in order, dated only where a step actually implies a date, the first one due today or tomorrow when the run starts now. They behave like everything else you capture, with reminders at hours you would accept.
Two details do more work than they appear to. Routines are capped at twelve steps on purpose, which enforces the ceiling that keeps checklists readable. And saving a project again under the same name replaces the old steps, so the template improves after every run instead of forking into five stale copies.
Is a routine the same as a recurring task?
No, and the difference is the trigger. A recurring task fires on the calendar whether or not the moment came: rent is monthly, so repeat suits it. A routine waits for the moment: the trip that got booked, the client who signed, the post that is finally ready. You start it when life does, and it stays silent the rest of the year.
Can one checklist adapt to each run?
Yes, and that is the part a notes-app checklist cannot do. The template stays generic, with placeholders where the details go, and each run gets specific: this client, this tier, this city. You are not copying a document and doing find-and-replace. You are handing over one line of particulars and getting back concrete tasks.
What happens if I run a routine twice?
Nothing doubles. Matters checks what is already open before filing, so a routine run twice does not plant its steps twice. And if the particulars contradict the template badly enough that no sensible run exists, it files nothing and says so, which beats twelve confident wrong tasks.
How do I build my first routine?
Pick the list you rebuilt most recently, the one you always slightly dread. Do that work once as a project in Matters, tidy the steps while the missing one is fresh, and save it as a routine. Next time, it is one sentence. Matters is free for 14 days, no card needed, and the charger will make the trip.