How to structure your meeting checklists so nothing slips

Most meeting checklists fail in the same way. They are written as a record of what was talked about, not a list of what happens next. “Pricing page” is a topic. “Jack rewrites the pricing page headline by Thursday” is something somebody can tick.

A checklist that works has a shape, and the shape is the same every time. Here is the one we recommend.

One line, one action, one verb

Start every item with a verb: send, fix, book, decide, draft, check. If you can’t find the verb, the line is a note, not a task, and it belongs in the notes above.

Keep each item to one action. “Update the deck and send it to Northwind” is two tasks with two moments where it can stall. Split it, and the second can wait on the first without anyone losing track.

Aim for a line someone could read cold, a week later, and still know what to do. “Follow up with them” fails that test. “Send Northwind the revised quote” passes.

Put the name first, or at least in the line

Every item has one owner, named in the line itself: Emma fixes the two crash reports. Not “we”, not “design”, not “someone”. If two people are needed, one still owns it.

In trepil, a name from the meeting inside a checklist item turns into a chip. In a team workspace, you click it to give that to-do to them, so it lands in their own list. More on that in how to assign tasks to people after a meeting.

Give it a time, with @

A task with no date is a wish. Add a time with an @ at the end of the line:

• Send the deck @fri
• Book the follow-up call @tomorrow 10am
• Check the numbers with finance @oct 30
• Chase the contract @in 2h

trepil reads the phrase as you type, shows what it understood, and turns it into a reminder chip when you press Return. A day with no time means 9am. When the moment comes, you get a reminder, and the chip turns red if it passes unticked.

You don’t need a date on everything. Use one when someone said one out loud, or when the task blocks something else.

Group by what matters to the reader

A flat list works up to about seven items. Past that, group it. Pick one grouping and use it every week, so people know where to look:

• By person, for a team meeting where everyone wants to find their own lines fast.
• By project or customer, for a pipeline review or a client meeting.
• By when, such as This week and Later, for a planning session.

Nest small steps under the item they belong to, rather than listing them alongside it. The parent is the outcome; the children are how you get there. Tick the parent only when the outcome is real.

Keep decisions out of the checklist

Decisions go above the checklist, in their own short list. “We ship on the 28th” has no owner and nothing to tick. Mix it into the to-dos and it either gets ticked off by accident or re-argued next week. Our earlier guide on ending every meeting with a checklist covers that split in more detail.

Make the shape a template

Once you have a shape that works, stop rebuilding it by hand. In trepil, open Settings, then Meetings, and create one under Templates. A template is a list of headings, in order, each with a line on what belongs under it. For a weekly product review that might be:

1. What shipped: the releases since last week, one line each.
2. Decisions: what was agreed, with who agreed it.
3. Risks: anything that could move a date.
4. Checklist: every action, with an owner and a date where one was said.

Pick the template when the meeting starts and trepil writes the notes under those headings. You can also rewrite an old note with it afterwards. Notes already written stay as they were until you do.

A few templates worth having:

• One to one: wins, blockers, feedback both ways, then the checklist.
• Client call: what they asked for, what we promised, the checklist, next meeting.
• Stand-up: grouped by person, each with done, doing and blocked.

Read it back before everyone leaves

The last two minutes of the meeting are for the checklist. Read each line aloud, with its name and date. People correct the owner of a task far more readily when they hear it than when they read it later.

If a line has no owner by the end, either someone takes it or it comes off the list. An unowned task on a shared checklist is worse than none, because everyone assumes someone else has it.

A checklist you can trust

When trepil writes the note, the checklist is already there: each action with its owner and a date if someone said one, and each linked to the moment in the transcript it came from. Your job is the last mile. Fix a name, add an @ time, split a line that is really two, and give each item to its person.

Do that every meeting and the list stops being a record of the call. It becomes the plan for the week.