The AI prep checklist explained

An AI prep checklist is the short list of three to five preparation steps that Composed generates automatically the moment you add an event on iPhone. A dentist appointment gets “Bring insurance card.” An international flight gets “Verify passport valid 6+ months.” A dinner reservation gets “Confirm the reservation.” Each task has a checkbox, read-only informational tips sit alongside them, and a readiness score from 0 to 100% tracks how much of the prep you’ve done. It is the layer that sits between knowing an event exists and actually being ready for it.

This is the feature most calendars skip entirely, and the gap is the whole reason Composed exists. A calendar tells you when the orthodontist appointment is. It says nothing about the referral form sitting on your counter that you needed to bring. The prep checklist is the answer to a question your calendar never asks: now that this is on the schedule, what do you have to do before it so that showing up isn’t a scramble.

Where the tasks come from

The tasks come from an AI model that reads the event you just created and infers what a prepared person would do beforehand. When you add “Dentist Thursday 2pm,” Composed sends the title, category, date, and how many days away it is to its AI prep checklist engine, which returns three to five steps fitted to that specific event type. You don’t fill out a form or pick from a menu. You add the event the way you always would — often by voice — and the checklist appears.

The generation happens once, at creation. That’s a deliberate constraint worth understanding: the checklist is not a chatbot you converse with, and it doesn’t keep regenerating as the date approaches. It’s a one-time, high-quality first draft of your prep, which you then own — you can check items off, and the readiness score responds. The point is to spend zero effort getting from “event exists” to “here’s a reasonable prep list,” which is exactly the moment most people’s preparation quietly fails to happen at all.

Context-aware examples

The checklist is context-aware, meaning the same feature produces genuinely different lists depending on what kind of event it reads. This is the part that makes it feel less like a template and more like a prepared friend glancing at your calendar. A few real shapes:

  • Dentist Thursday → “Bring insurance card,” “Note any tooth sensitivity to mention,” “Confirm the appointment time.” Small, specific, the things you’d kick yourself for forgetting in the waiting room.
  • Flight to London next month → “Verify passport valid 6+ months,” “Check baggage allowance,” “Set an out-of-office.” The passport-validity one is the canonical example, because almost nobody thinks to check it until the airline counter, and by then it’s a crisis instead of a checkbox.
  • Dinner reservation Saturday → “Confirm the reservation,” “Check the dress code,” “Arrange a ride.” Light prep for a light event — the checklist scales its ambition to the occasion.
  • Parent-teacher conference → “Write down questions to ask,” “Review the latest report card,” “Note any concerns from home.” The kind of prep that turns fifteen rushed minutes into a useful conversation.

Readiness score explained

The readiness score is a single 0-100% number that summarizes how much of an event’s prep you’ve completed. Check off half of an event’s tasks and the score climbs to match. It exists so that the question “am I actually ready for this” has a glanceable answer, which is the specific cure for the double-checking trust failure from chapter 3.1 — the habit of opening the app over and over to reassure yourself.

The score also quietly drives the reminder system, which is why it belongs in this section rather than as a cosmetic detail. A high readiness score tells Composed you’ve got this handled, so it suppresses the gentle action-layer nudges it would otherwise send; a low one tells it you might need a prompt. That coupling is covered in the next chapter on graduated reminders. For now the thing to hold is that the score isn’t a grade or a guilt meter — there are no streaks, no badges, no red. It’s an instrument reading, and instruments don’t judge you.

Tips vs tasks

The checklist contains two different kinds of items, and the distinction is built into how they behave. Tasks have checkboxes because they’re things you do — “Bring insurance card” is done or not done. Tips are read-only because they’re things you should know — “Most dental offices ask you to arrive 10 minutes early for paperwork” isn’t something you check off, it’s context that helps you prepare well.

Keeping them visually distinct matters more than it sounds. A list where everything is a checkbox pressures you to “complete” things that were never actions, which is how to-do lists turn into low-grade guilt machines. By separating the doing from the knowing, the prep checklist stays a tool for getting ready rather than another surface that makes you feel incomplete. The glossary on prep tasks goes deeper on the data model if you want it.

What the AI doesn’t do

The AI is deliberately narrow, and knowing its limits is part of trusting it. It generates the checklist once, at event creation — it does not learn from your past behavior, it does not generate subtasks inside tasks, and it does not let you ask it for more steps on demand. If you add “Dentist Thursday,” you get a dentist list; it won’t notice over six months that you always forget your retainer and start adding it.

This restraint is a feature, not a shortfall. An AI that quietly learned and adapted would be one you could no longer predict — and an unpredictable system is, by the trust equation in chapter 3.1, an untrustworthy one. By doing exactly one thing the same way every time, the prep checklist stays legible: you always know what it did and why. The pieces it doesn’t handle, you handle, and the boundary never moves under you.

What this replaces

What the prep checklist replaces is the mental note that fell out of your head. Before, the preparation existed only as a vague intention — “I should remember to bring the form” — held in the same overworked attention that’s juggling everything else. Most of the time, that intention quietly evaporated, and you found out at the worst possible moment that you’d forgotten.

The checklist moves that intention out of your head and onto a surface that doesn’t forget, the same way capture moved your events. The difference, explored in what being prepared actually looks like, is between hoping you’ll remember the prep and knowing the prep is written down somewhere you’ll see it in time. For a fuller case on why every event deserves one, see why your planner needs a prep task.

The practice this week: add one event you’d normally just drop on the calendar, and actually read the checklist Composed generates. Notice the one step you wouldn’t have thought of. That step is the whole feature.

Next: Graduated reminders, explained — the three-layer model and why quiet hours matter.