Track commitments in email two ways. Manually, review your sent mail once a week and list every promise with a date, then read the client's messages for questions you never answered. Structurally, use a tool that extracts commitments from the text itself, in both directions, so a promise made on Tuesday is on Friday's list without anyone logging it.
Somewhere in your team's sent folder right now is a sentence like I'll get you the revised numbers by Friday. It felt weightless when it was written, a courtesy at the end of a longer email about other things. The client read it as a contract. They have arranged their week around it, and nothing in your toolchain knows it exists.
Whether Friday happens now depends on one person's memory, working against forty other accounts and two hundred other emails. Sometimes memory wins, and the relationship is shaped by how often it does.
How do you track promises made over email?
There are two kinds of commitment in every thread, and a tracking method has to cover both. What you owe them: the revised numbers, the call you said you would set up, the fix you promised by month end. And what they owe you: the brief, the sign-off, the answer to the question you asked twice. A follow up tracker that only holds your side is half a tracker.
The method is the same for both. Read the message, pull the promise out as a sentence with an owner and a date, and put it somewhere the whole team sees. The manual and structural versions below differ only in who does the pulling.
Why do email commitments slip through?
Because commitments live in prose, and every tracking tool we have runs on fields. A promise does not arrive labeled. It is a clause in a paragraph, phrased a hundred different ways, made from a phone in a taxi. Task managers track what someone remembered to transfer, and the transfer is the step busy people skip.
Snoozes and reminders have the same flaw one layer down. They require you to notice, in the moment, that what you just wrote was a promise. The commitments that slip are the ones that never felt like commitments when they were made.
There is a second category: their questions to you. A client asks something in paragraph three of a message mostly about something else. You answer the something else. The thread shows as replied and satisfies every metric your inbox tool has, while the question in paragraph three ages.
The cost is trust, and it compounds
A single missed Friday is nothing, apologized for and forgiven. But follow-through is the only measure of reliability a client ever gets, and it moves slowly in one direction. Each kept small promise deposits a little trust. Each missed one withdraws more than it deposited.
Accounts are lost over accumulated small slippage far more often than over any single failure. The exit interview says something vague about communication, because no single incident was worth naming. You almost never lose on the merits. You lose on the Fridays.
The manual fix: a commitments review
Even with no tooling, one ritual helps. Once a week, each person spends fifteen minutes scanning their sent mail and writes down every promise they made, with dates, in a shared sheet. Add a second column for what the client owes you, pulled from their last message. It is crude and it leaks, and the volume it reveals is the argument for doing it.
A busy account manager makes far more small commitments in a week than they can recall. Seeing the real number convinces people the problem is structural, which is the first step to fixing it that way.
How to follow up with a client without being pushy
The follow-up that feels pushy is the one with nothing in it. Checking in on this is a request for the client to do your tracking. The follow-up that lands names the specific item, states what you have done since, and makes the next step small.
- Lead with the item, in their words. Following up on the brief for the Q2 campaign reads as organized; just checking in reads as noise.
- Give before you ask. Attach the draft, the numbers, or the answer to their last question, then ask for what you need.
- Set the next date yourself. If I have not heard back by Thursday I will proceed with option A. It closes the loop without demanding a reply.
- Space follow-ups by the stakes. A signature holding up a launch gets a nudge in two days. A nice-to-have waits a week.
Templates for the first, second and final follow-up, plus a Sheets tracker, are in how to follow up with a client. The QBR version, where you revisit a quarter of commitments at once, is in the QBR template and agenda.
The structural fix: extraction instead of discipline
The durable answer is to stop depending on humans noticing promises at all. We build Sektra to read the team's mail as it flows through Gmail and Outlook and extract commitments from the prose itself, in both directions. It captures what you owe them, what they owe you, and which of their questions are still waiting on an answer.
Everything accrues to the client's relationship record, visible to the whole team and queryable through the assistant. A promise made by someone now on vacation is still a promise the team knows about, and nothing depends on anyone logging anything.
The morning digest does the part memory cannot. It lists what is coming due and what has aged, with a Waiting on them section for threads where the client has owed a reply for three days or more. Friday arrives already knowing what it owes. The analytics then report commitments made, met and overdue per client, which is the follow-through number account management teams can put on a scoreboard. Queue tools such as Front track who replied and how fast, and keep no record of what was promised; the product page shows the difference.
