How to Remember What You Promised—and to Whom

Promises hide inside ordinary sentences

‘I’ll check and get back to you.’ ‘Send me that after the holidays.’ ‘Let’s revisit this in March.’ None of these sound like tasks when spoken, and none of them will reach a task manager by themselves.

The realistic habit is a quick note or voice memo right after the conversation, in your own words, without formatting.

Let detection turn commitments into tasks

A memory system can recognize that a sentence contains an intended action, a likely owner, and sometimes a date—and propose a task. The proposal matters more than the automation: you confirm or dismiss, so the list stays honest.

• The detected task must link back to the note that created it.
• Dates are kept only when the note actually supports them.
• A promise made to you is tracked differently from a promise you made.

Keep the ‘to whom’ attached

A commitment without a person is just a vague intention. Because the task points to its source note, the who, the why, and the exact wording stay one tap away—useful when you finally act on it three weeks later, or when someone remembers the agreement differently.

Review open promises, not your whole list

Once commitments are captured with people attached, one small weekly question becomes possible: what have I promised that is still open, and what is still owed to me? That is a five-minute review with an outsized effect on trust.

The four places promises are made and lost

Almost none of them are places you would think to open a task manager, which is the whole problem:

• The end of a call, in the last thirty seconds, after the notes have stopped.
• A hallway or doorway conversation—no screen present, no record created.
• A chat thread, where the promise is one message inside forty and scrolls out of view within a day.
• Your own head: ‘I should get back to them about that’, which is a promise you made to someone who now expects it.

Why this fails even for organized people

The failure is not memory and it is not discipline. It is that the moment of promising and the moment of recording are separated by a context switch, and the context switch is where the promise dies. You finish the call, the next thing starts, and by the evening the commitment has been replaced in working memory by four newer ones.

This also explains why more elaborate systems do not help. A task manager with projects, priorities, and contexts still requires you to arrive at it deliberately, and arriving deliberately is exactly the step that did not happen. Capturing where the promise was made—one sentence of voice while walking back to your desk—removes the switch instead of adding structure around it.

There is a limit worth stating: nothing catches the promise you never registered as one. Detection works on what you captured, and some commitments are recognizable only to the other person. A weekly ‘what is owed in both directions’ question is the practical backstop, because it prompts recall instead of waiting for a note to exist.