Prep a Meeting in 10 Minutes From Last Time's Decisions

A Tuesday standup that starts from zero

Say you run a 12-person marketing team and the Tuesday standup opens the same way it always does: "So, where did we land last week?" Someone scrolls a chat thread, someone else digs through email, and ten minutes are gone before anyone talks about today's work. Multiply that by every recurring meeting on the calendar — team syncs, project reviews, vendor check-ins — and you've built a quiet tax on everyone's time, paid weekly, forever.

The fix isn't a better note-taking app. It's a different starting point for the agenda itself.

How should you prepare for a recurring meeting?

Pull forward what was decided last time and what's still open, put both at the top of the agenda, and add new discussion items underneath. A short agenda built from the prior meeting's decisions and open action items turns prep into a ten-minute task instead of a ground-up rebuild, because the meeting picks up exactly where the last one ended instead of relitigating it.

That's the short version. The rest of this is about building a repeatable habit around it so it doesn't depend on whoever happens to remember to check last week's notes.

Why meetings keep restarting from zero

Most recurring meetings lose their thread for the same three reasons:

• The notes from last time live in a document nobody reopens until someone asks "wait, what did we agree on?"
• Action items get mentioned verbally, written down somewhere informal, and then never checked before the next meeting.
• The agenda for this week is built fresh, from memory, instead of from a record of what's still outstanding.

None of these are failures of effort. They're failures of where the information lives relative to where the next agenda gets drafted. If decisions and open actions sit in one place and agendas get built in another, somebody has to do the manual translation every single time — and that translation step is exactly what eats the first ten minutes.

The ten-minute prep checklist

Before you open a blank agenda for a recurring meeting, work through this instead:

| Step | What you're doing | Time | |---|---|---| | Pull last meeting's decisions | Copy the 2-4 decisions made last time to the top of the new agenda | 2 min | | Check open actions | List who owns what's still outstanding and its current status | 3 min | | Flag anything overdue | Mark items past their due date so they get addressed, not skipped | 1 min | | Add new items | Only now add fresh discussion topics underneath the carry-forward items | 3 min | | Set rough timing | Give each item a time box so the meeting doesn't run long on old business | 1 min |

That's it — ten minutes, most of it copy-and-check rather than compose-from-scratch. The agenda ends up doing double duty: it's a planning document and an accountability record in one.

Where the decisions and actions actually live

This checklist only works if decisions and open items are somewhere you can actually find them quickly. If your meetings run through Microsoft 365, Teams minutes can capture what got agreed on without someone typing notes by hand during the discussion. From there, the practical move is turning agreement into a tracked item rather than a sentence in a transcript — that's what action tracking in Loop is for, and items that need ongoing work can move onto a kanban task board instead of sitting in a static list.

For the agenda itself, building it by hand every week from scratch is the thing that eats time. A timed, structured starting point — like the one you can put together with Kahrbon's meeting planner — gives you a template where carry-forward decisions and open actions have an obvious place to sit, instead of competing for space with whatever's top of mind that morning.

If you're running several recurring meetings — a weekly ops sync, a monthly vendor review, a quarterly planning session — the same discipline applies at every cadence, just with longer gaps between runs. The longer the gap, the more valuable it is to have last time's decisions written down somewhere specific rather than relying on memory.

Making the carry-forward habit stick

A few things make this easier to sustain past the first few weeks:

• Put "review open actions" as the literal first agenda line, every time, so it's not optional.
• Assign an owner and a due date to every action the moment it's agreed — not after the meeting, during it.
• Review your meeting history and time spent occasionally to see which recurring meetings are actually producing closed actions and which ones are just producing more meetings.
• If your organization runs meetings across Teams and a shared directory, keep the agenda and the minutes in the same system so nobody has to hunt across tools to find last week's decisions.

None of this requires new discipline from every attendee — it requires one person (usually whoever owns the agenda) to spend ten minutes before the meeting pulling the right things forward. Everyone else just shows up to a meeting that already knows what happened last time.

Frequently Asked Questions

How long should meeting preparation actually take?

For most recurring meetings, ten minutes is realistic if you're pulling from an existing record of decisions and open actions rather than reconstructing the history from memory or scattered notes. The time goes up sharply if someone has to search chat logs or email threads first — which is the problem this checklist is built to avoid.

What's the difference between meeting notes and an action tracker?

Notes are a record of what was discussed; an action tracker is a record of what someone committed to do and by when. Notes are useful for context, but if action items only live inside a notes document, they tend to get mentioned once and forgotten. Moving commitments onto a dedicated tracker, like Loop, keeps them visible until they're closed.

Should every recurring meeting start with a review of past decisions?

For meetings that build on prior work — status updates, project syncs, committee check-ins — yes, a brief review keeps everyone aligned and prevents re-deciding the same thing twice. One-off meetings with no prior history obviously don't need this step, but most recurring meetings on a typical calendar do qualify.

Who should own updating the agenda between meetings?

Usually whoever chairs or organizes the meeting, since they're best placed to see which open items are overdue and which new topics need adding. For formal governance meetings, your organization's own bylaws or counsel should guide how agendas, minutes, and any formal votes are documented and retained.

Does this approach work for board or committee meetings too?

The same carry-forward principle applies — starting from open items rather than a blank page — though board and committee meetings often carry extra requirements around formal minutes, voting records, and disclosures that should follow your organization's governance policies rather than a general checklist.

If your team is rebuilding the same agenda from scratch every week, it's worth seeing what a system built around meeting preparation that carries decisions and actions forward actually looks like in practice. Get in touch or start a free signup to try it on your next recurring meeting.