The Three-Field Rule That Fixes Why Your Meeting Notes Never Turn Into Finished Work

Most meeting notes are not action items. They are transcripts of good intentions.

You leave a meeting with three things to do. By Thursday you remember one of them, half finish it, and forget the other two until someone asks about them in the next meeting. If that pattern sounds familiar, the problem almost never turns out to be memory. It is that what got written down during the meeting was not actually a task.

Open your own meeting notes right now and look at the last few action items you captured. There is a good chance several of them look like this: "follow up with the vendor." "Look into the budget issue." "Talk to the client about timeline." Each one reads like a real commitment. None of them can actually be completed, because none of them define what finished looks like, who is responsible, or by when. They are not tasks. They are transcripts of a good intention that happened to get said out loud.

This is fixable with one small habit, applied consistently, and it takes about ten seconds longer per item than what most people already do.

Why the problem is not what you think

The usual explanation people reach for is forgetfulness, and the usual fix is a better app, a better reminder system, a better habit of "checking in more." All of that assumes the item was captured correctly in the first place and the failure happens later, when you forget to look at it. Sometimes that is true. But a huge share of dropped commitments never had a real chance, because the thing written down during the meeting was too vague to act on, even by the person who wrote it.

Here is the test that exposes this instantly: could a stranger, with no memory of the meeting, read your note and know exactly what "done" looks like? Take "follow up with the vendor." Follow up meaning what, an email, a phone call, a signed contract? A stranger cannot tell, and neither, three weeks later, can you. The note survives being written down and still fails, because there is nothing in it to trigger action and nothing in it to tell you when you have finished.

Compare that to "send the vendor a written extension request by Thursday, owner: you." Anyone can read this and know instantly whether it is done. The email either went out or it did not.

The three fields

The fix is not a new tool. It is a rule you apply the moment a commitment is spoken, before the conversation moves to the next topic and the precise wording starts to blur. Every action item gets exactly three fields, written in this order, every time:

What. A verb plus a concrete, checkable deliverable. Not "look into pricing," but "pull competitor pricing for the three companies discussed and put it in a one page comparison." If you cannot write the what as a specific artifact that will exist when the task is done, you have caught a vague commitment before it left the room, and the fix is one clarifying question, asked out loud, right then: "when you say look into it, do you mean a written recommendation, or just a gut check next time we talk?"

Who. One name. Not "the team," not "we," one person, even if it is you. Two names on one item functions like zero names, because each person quietly assumes the other one has it, and it takes an awkward moment after the fact to discover neither of you did.

By when. A specific date, not a relative one. "Next week" decays into ambiguity the moment the meeting is more than a day old. "Thursday the 14th" does not. If a date was not mentioned in the discussion, ask for one before the topic changes. Four words, "by when do you need this," and a floating intention becomes a task with an actual deadline.

That is the entire rule. What, who, by when, written within about ten seconds of the commitment being spoken, not reconstructed from memory after the meeting ends.

Where people undermine this without noticing

The most common way this fails in practice is not forgetting the rule entirely, it is applying it selectively. An item feels too small to bother with, "I'll send that link," so it gets skipped. An item feels too obvious to write down, "obviously I'm doing the thing from last time," so it also gets skipped. Both instincts are backwards. Small items are exactly the ones most likely to be forgotten, because nothing about them feels urgent enough to stick in memory without a written trigger. And "obvious" commitments get dropped constantly precisely because their obviousness gave everyone permission not to write them down.

For the first few weeks of using this rule, apply it to everything, no exceptions for items that feel minor. Once the habit is automatic, you will develop reasonable judgment about which two second favors genuinely do not need a written record. Until then, the discipline of writing everything is what makes the habit stick.

Try it on your next meeting

Pick one meeting you have this week. Every time something gets agreed to, write the what, the who, and the by when within ten seconds, out loud if you are the one running the meeting so the room can correct you in real time if you got any of the three fields wrong. That is the whole experiment. You will likely notice, within that single meeting, at least one commitment that sounded solid in the moment and fell apart the instant you tried to write a concrete "what" for it. Catching that in the room, rather than discovering it three weeks later when nothing happened, is most of what this rule is actually for.

Capturing items well is the first of five places a commitment can quietly die between being spoken and being done. Getting good at the other four, keeping every open item in one trusted place, reviewing it on a fixed weekly cadence, and responding calmly when something slips anyway, is the difference between a habit that works for a week and a system that holds up for a year. I wrote a full guide covering all five, with copy-paste templates for the review and the follow-up conversations: https://manggaleh.gumroad.com/l/yrnugd.

Disclosure: this article links to my paid ebook on the same system.