# Lists, checkboxes, and meeting notes

Use lists for parallel items and numbered steps when order matters. Checkbox notation records task status as ordinary Markdown text.

## Make a useful list

```markdown
## Materials
- Revised draft
- Delivery schedule

## Review sequence
1. Read the draft.
2. Check the dates.
3. Save the review notes.
```

Start each item on its own line. Use a blank line before a list so its boundary is clear in the saved text and in other readers.

## Track a few actions

```markdown
## Actions
- [ ] Ask Morgan for the date.
- [x] Review the first draft.
```

Change `[ ]` to `[x]` in the text when an action is complete. Do not rely on a clickable task widget, notifications or a separate task database: the saved note is the record.

For meeting notes, include an owner and an agreed deadline in each item when known. Keep unanswered questions in a separate section so they do not look like assigned work.

## Check the saved result

Press Command S and reveal the Markdown file. Confirm the list text and task markers are present. If your next destination renders task lists differently, the source markers still preserve the status.

See [meeting follow-ups](/docs/everyday-use/meeting-follow-ups) for a complete capture and review workflow.