How to Stop Client Promises From Falling Through the Cracks

A practical way to track promises, client requests and commitments so important follow-ups don't disappear inside email and meeting notes.
May 21, 20267 min read
Short answer: the moment a promise is made, turn it into a next action with an owner and a date. Track what clients owe you separately from what you owe them, and look at both once a day.Some of the riskiest things in a client business never make it onto a project board. They sound like this:
"I'll send that over tomorrow."
"We'll revise the proposal."
"Let me check with the developer and get back to you."
"Send me the document and I'll approve it."
None of these feels big enough for a ticket. But forget one and the client notices, often before you do. A missed small promise can hurt trust more than a late big task, because it feels personal. "They said tomorrow. It's been a week."

Why promises slip

Project work comes with structure. Features get tickets, designs get deadlines. A promise is usually one sentence at the end of a call. Everyone hangs up, goes back to work, and the commitment ends up in meeting notes, an email thread, or nowhere.It's not a discipline problem. The promise just never became a next action.

Listen for the trigger phrases

Once you start noticing them, you'll hear them everywhere, from both sides of the call:
  • "I'll send..." / "We'll get back to you..."
  • "Let me check and..." / "I'll look into..."
  • "Once you send..., we can..."
  • "Can you share... by Friday?"
  • "We'll decide by..."
  • "I'll introduce you to..."
When you hear one, repeat it back with a date: "So I'll send the revised estimate on Friday, does that work?" It takes three seconds and turns a vague "soon" into something you can actually keep.

Write it down before the next call starts

A note that says "send revised estimate" isn't enough. Make it:
  • Next action: Send revised estimate to Northwind
  • Due: Friday
  • Reason: Promised on Wednesday's call
Do it within a few minutes of hanging up. An hour later, after two more calls, you'll remember it as "something about an estimate." The full after-call routine is in client meeting follow-up.

Promises go both ways

Every client relationship has two lists of commitments.
You owe the clientThe client owes you
Proposal or estimateApproval of design or scope
Progress updateCredentials and access
Answer to a questionFeedback on a draft
Document or fileAssets and content
Meeting scheduledPayment of an invoice
They need different handling. When you owe something, you want a reminder before the date. When they owe you, you want to know how long you've been waiting and when it's fair to nudge.

Waiting isn't the same as forgotten

Monday: you ask for approval. The client says "I'll take a look." You tick off your task, because your part is done.That's exactly how approvals vanish for three weeks. Instead, write:
  • Waiting for: homepage approval
  • Since: Monday
  • Next check: Thursday
Your action is finished, but the loop isn't. Your system should still show it. For approvals specifically, see how to track client approvals.

Not every promise belongs in the project tool

The natural reflex is to dump everything into ClickUp, Asana or Jira. It works for a while. Then your delivery board fills up with "follow up with Sarah," "ask John for approval," "check if Mike replied," and the real work gets harder to see.Those aren't deliverables. They're the conversation around the work. Many small agencies find it easier to keep them apart: the project tool answers "what do we need to build?", and something else answers "what does this client need from us next?" More on that split in CRM vs project management for agencies.

Keep the reason with the reminder

"Contact Sarah" is better than nothing. But you still have to work out why. Compare:
Waiting six days for approval of homepage version 3.
Now the email almost writes itself:
Hi Sarah, just checking whether you've had a chance to look at the latest homepage. If it works for you, we can start building next week. Happy to talk through anything first.

When you're the one running late

It will happen. What matters is how you handle it. Tell them early, give a new date, keep it short:
Hi Alex, the revised estimate is going to land Monday instead of today. Wanted to let you know now rather than leave you waiting. You'll have it by noon Monday.
People are much more forgiving of a heads-up than of silence followed by "sorry, this slipped."

The promises you didn't know you made

The dangerous ones aren't "I'll send it Friday." They're the half-sentences the client heard as a commitment:
  • "I'll look into it." The client hears: you'll come back with an answer.
  • "That should be possible." The client hears: it's included.
  • "Let's revisit that later." The client hears: you'll bring it up again.
  • "We can probably do that next sprint." The client hears: next sprint.
None of these have a date, so they never reach your list. But every one of them sets an expectation. Two habits fix most of it:
  1. Translate on the spot. "I'll look into it" becomes "I'll check with the developer and tell you by Thursday whether it's possible." If you can't give a date, say so: "I don't know yet, I'll tell you by Thursday when I'll know."
  2. Close the ones you won't keep. If you said "let's revisit that later" and you're not going to, retract it explicitly: "On the dark mode idea we talked about: we're not going to include it in this phase. If it's important, let's scope it separately." Retracting a soft promise costs one awkward line. Letting it rot costs trust when the client brings it up in month three.

Pad the date, not the scope

When you name a date, pick the one you'd hit on a bad week, not a good one. Our instinct is reliably optimistic. In a well-known study of the "planning fallacy," students estimated how long their thesis would take: on average 34 days, and 49 days if "everything went as poorly as it possibly could." The average actual time was about 55 days, longer than even their worst case (Buehler, Griffin and Ross, 1994). Your "I'll send it tomorrow" is subject to the same bias. "Thursday" when Wednesday is realistic. Clients remember whether you hit the date far more than they remember how early it was. And when a promise is big, split it: "I'll send the first two sections Tuesday and the rest Friday" gives you two small promises you can keep instead of one large one you might miss.

Five minutes each morning

No need for a big weekly review. Just scan:
  • Promises you made that are due today or already late
  • Client questions still waiting for your reply
  • Things you're waiting on, and for how long
  • Anything that's been waiting long enough to deserve a nudge
Five minutes here saves you from a relationship going quiet for five days.

Try this now

Look at your current clients and answer, without opening anything:
  1. What did you last promise each of them?
  2. What are you waiting for from them?
  3. When will you talk to them next?
  4. Which one is overdue right now?
If the answers are scattered between your inbox, your head and a project board, the issue isn't project management. It's follow-through.

Common questions

Should I log promises in my project management tool?

Put the deliverables there. The reminders, check-ins and approvals around them work better somewhere built for client follow-ups, so your board stays about the work.

How detailed should a promise record be?

One line. Who, what, when, and where it came from. If it takes more than a minute to write, you'll skip it.

What about promises made in Slack or email?

Same rule. When you read the commitment, create the next action right then. "I'll do it later" is how it got lost the first time.

Where promises live in AwiFin

AwiFin Today view with demo data: an overdue promised progress update sits at the top, with the reason and the next action next to it
AwiFin Today view with demo data: an overdue promised progress update sits at the top, with the reason and the next action next to it
AwiFin treats promises, approvals and follow-ups as part of the client relationship, not as separate tasks. You note what happened and set one clear next action. The same record carries the client from proposal to follow-up to active project to approvals, so the history never resets.You don't have to document everything. You just need the right thing to come back to you at the right time.

Sources

Was this article helpful?One click, no sign-up needed.
Turn next actions into progressTrack every follow-up. Prepare your next message.
TagsClient managementClient communicationAgency workflow
DM
Written by Dariusz M.AwiFin founder writing practical workflows for small agencies.
More articles →