Why a new list every meeting loses the work

Recurring forums, standups, and project reviews often file notes and start blank next time. The open work is still open. The team pays for the meeting again to remember it. A rolling action log is the opposite: the next agenda starts from what is not Done.

If you already track a single meeting well, this is the next step. The single-meeting habit is covered in how to track action items. The rolling log is that list kept across dates.

The ten-minute carry-over

Open the same log at the start. Read every row that is not Done. The owner says done, still open, or blocked. Change dates in the meeting, not in a side channel later. Then move on to new topics. Put new actions at the bottom with the date they were raised.

Build the agenda so this pass has time. A meeting agenda maker can draft the timed blocks; the first block should be this review, not introductions.

What “carried over” is allowed to mean

Carry-over is not failure. A multi-week item should show First raised and Last reviewed so the room can see age. An item that has been blocked for three meetings needs a decision: change the owner, change the scope, or drop it on purpose.

Dropping an item is a decision. Write it down. Silent deletion is how people disagree later about whether the work was still owed.

When the log should leave the document

A shared doc works until people stop opening it. The signal is a meeting that starts with “what did we say last time?” even though the log exists. MinutesLoop is the same list as Open Actions: it survives between meetings, and each owner sees their rows on a Desk.

You can still paste notes into the free tools to draft minutes and actions. Confirm them once, and the board is the rolling log.