This article is AI-generated.
Meeting notes often end with a few lines like "maintenance to look at it", "follow up with the carrier", "someone to update the checklist". A week later nobody can say which of those happened. The notes weren't wrong. They just didn't say who, by when, or what finished looks like.
This article gives you a tracker layout to replace the to-do section of your meeting notes: the columns, a worked before and after, and how to open the next meeting by walking through overdue items first. How to nudge and escalate between meetings, and how to track personal tasks outside of meetings, are separate topics. Names and items below are illustrative.
The columns
| Column | What goes in it | What not to write |
|---|---|---|
| A ID | A running number that is never reused, e.g. WH-118 | |
| B Raised | Which meeting it came from | |
| C Action | One action, starting with a verb | "Packaging issue" |
| D Owner | One person's name | "Procurement", "Person A and Person B" |
| E Due date | A real date | "ASAP", "next week" |
| F Done when | The visible result that closes it | "follow up", "look into" |
| G Status | Open, In progress, Blocked, Done | |
| H Last update | Date of the latest note | |
| I Notes | One line: what's blocking it, or the new date | |
| J Days overdue | Formula | |
| K Sort order | Formula |
One owner per row. Two names means each person assumes the other is doing it. If several people are involved, name one owner and list the others as "with" in the notes.
"Done when" is the column people skip. "Follow up with the customer" can stay open for a month. "Send the complaint analysis to Person A" is either sent or it isn't.
Two formulas
Days overdue, J2:
=IF(OR(G2="Done",E2=""),"",IF(E2<TODAY(),TODAY()-E2,""))
Sort order, K2, so overdue rows float to the top and rows with no due date don't hide at the bottom:
=IF(G2="Done",4,IF(E2="",1,IF(E2<TODAY(),2,3)))
1 is "missing a due date", 2 is "overdue", 3 is "on time", 4 is "done". Sort the sheet by column K, then by due date. Rows with no owner or no due date are the ones to fix before you even look at overdue items, because they will never become overdue on their own.
With illustrative data, assuming today is 2026-10-09:
| ID | Raised | Owner | Due | Status | Days overdue | Order |
|---|---|---|---|---|---|---|
| WH-101 | 2026-09-25 | Person A | 2026-10-02 | Open | 7 | 2 |
| WH-102 | 2026-09-25 | Person B | 2026-10-16 | In progress | 3 | |
| WH-103 | 2026-09-25 | Person C | 2026-10-05 | Done | 4 | |
| WH-110 | 2026-10-02 | Person B | 2026-10-07 | Blocked | 2 | 2 |
| WH-111 | 2026-10-02 | Person D | (blank) | Open | 1 |
(illustrative data; formulas tested on this sheet in LibreOffice; the syntax is the same in Excel, but I haven't run each one in Excel itself)
WH-111 sorts above the overdue rows on purpose: until it has a due date, it can't be tracked at all.
Before and after
Before (illustrative), from a weekly warehouse meeting:
Action items: Dock door 4 keeps jamming, maintenance to look at it. Late carrier pickups again this week, follow up. Returns checklist is out of date, someone to update. Label printer on packing line 2, ASAP. Person A and Person B to sort out the cycle count backlog.
After (illustrative):
| ID | Action | Owner | Due | Done when |
|---|---|---|---|---|
| WH-118 | Book a repair for dock door 4 | Person C | 2026-10-12 | Repair date confirmed in the maintenance log |
| WH-119 | Send the carrier a list of this week's late pickups | Person A | 2026-10-10 | List sent, reply requested by 2026-10-14 |
| WH-120 | Update the returns checklist to the current process | Person D | 2026-10-16 | New version saved in "warehouse/checklists", old one moved to "retired" |
| WH-121 | Get the packing line 2 label printer fixed or swapped | Person B | 2026-10-10 | Line 2 printing labels again |
| WH-122 | Clear the cycle count backlog for aisles 1–6 | Person A (with: Person B) | 2026-10-20 | Counts entered for aisles 1–6 |
(illustrative)
Every "before" line was a real concern. What was missing: "maintenance" and "someone" aren't people, "ASAP" isn't a date, "follow up" has no end, and two names on one line meant nobody owned it. The "after" version fixes those four things and nothing else.
Anything with no action and no owner, such as "everyone please keep aisles clear", stays in the notes as a reminder and stays out of the tracker.
How to run the tracker at the next meeting
- Before the meeting, the person who writes the minutes sorts the tracker by column K and filters out Done.
- Open the meeting with the tracker, in this order: rows with no owner or no due date, then overdue, then due before the next meeting.
- Overdue rows get a new date in the notes, not in the due date column. Keep the original due date so the days-overdue column stays honest.
- A row is only Done when its "done when" is met. "Mostly done" stays In progress with a note.
- New actions from this meeting get added before you leave the room, or within the same day. A tracker updated three days later has already lost the details.
Keep this part short. If reviewing the tracker takes the whole meeting, the tracker has too many open rows, which is itself useful information.
A few rules that keep it usable
- One tracker for the meeting series, not a fresh list inside each set of minutes. Minutes link to the tracker by ID: "see WH-120".
- IDs never get reused. When an action is split, the original stays and the new part gets a new ID.
- Blocked needs a name. A Blocked row should say in the notes who it's waiting on, otherwise it sits there indefinitely.
-
File name and location, not "see attachment". If an action produces a document, the notes say where it is, for example
warehouse/checklists/returns-checklist_v4(illustrative).
Top comments (1)
tr.ee/dev-to
Some comments have been hidden by the post's author - find out more