Short answer: turn every promise into a next action with an owner and a date at the moment it is made, and track what clients owe you separately from what you owe them. Review both once a day.Some of the riskiest items in a client business never appear on 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 come back to you."

"Send me the document and I'll approve it."

None of these feels big enough to become a ticket. But forgetting one can damage trust faster than a missed deadline on a large task, because the client noticed and you didn't. Promises need a different system from normal project work.

Why promises get forgotten

Project work has structure: a feature has a ticket, a design has a deadline. A promise usually starts as one sentence on a call. The meeting ends, everyone returns to their work, and the commitment ends up in meeting notes, an email thread or someone's memory.The problem isn't productivity. The commitment never became a next action.

Catch the promise when it's spoken

Train yourself to notice the phrases that signal a commitment, from either side:

"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, say it back and agree a date: "So I'll send the revised estimate Friday. Does that work?" A stated date is far easier to keep, and to follow up on, than a vague "soon."

Convert it into a next action straight away

The note "send revised estimate" is not enough. Turn it into:

Next action: Send revised estimate to Northwind
Due: Friday
Reason: Promised during Wednesday's call

Now the commitment comes back to you without relying on your memory. Do this within a few minutes of the call, while you remember exactly what was said.

Track both sides

Client relationships contain two kinds 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 should behave differently. When you owe something, you need a reminder before the date. When the client owes something, you need to know how long you've been waiting and when a nudge is reasonable.

"Waiting" should never mean forgotten

You request approval on Monday. The client says they'll take a look. You mark your task complete because your part is done.This is exactly how approvals vanish. Instead, record:

Waiting for: homepage approval
Since: Monday
Next check: Thursday

You've finished your action, but the loop is still open, and the system should say so.

Don't turn every promise into a project task

A common response is to put everything into ClickUp, Asana or Jira. That can work, but it fills your delivery board with relationship admin: "follow up with Sarah," "ask John for approval," "check whether Mike replied." Those are communication actions around the work, not deliverables.For many small agencies it helps to keep them apart. Your project tool answers "what work needs to be completed?" Your relationship system answers "what does this client need from us next?"

Use the history when you follow up

A reminder that says "contact Sarah" is better than nothing, but you still have to work out what to say. A reminder that keeps the reason is far more useful:

Waiting six days for approval of homepage version 3.

Now the message nearly writes itself:

Hi Sarah, just checking whether you've had a chance to review the latest homepage version. If it looks good, we can move into implementation. Happy to clarify anything before you approve.

When you're the one who's late

You will miss a promise at some point. How you handle it matters more than the miss. Say so early, give a new date, and keep it short:

Hi Alex, I owe you the revised estimate and it's going to land Monday rather than today. I wanted to tell you now so you aren't left waiting. I'll send it by noon Monday.

An early, specific message almost always lands better than silence followed by an apology.

A five-minute daily review

You don't need a heavy weekly process. Each morning, scan for:

Promises you made that are overdue or due today
Client requests waiting for your reply
Approvals and inputs you are still waiting on, and for how long
Anything you've been waiting on long enough that it needs a nudge

Five minutes here can prevent a relationship from going quiet for five days.

A quick test

Look at your current clients. Can you immediately answer:

What did you most recently promise each one?
What are you waiting for from them?
When will you contact them next?
Which relationship is overdue right now?

If the answers live partly in your inbox, partly in your head and partly on a project board, you have a follow-through problem, not a project-management problem.

Common questions

Should I log promises in my project management tool?

Log deliverables there. Log the communication around them (reminders, check-ins, approvals) in a place built for relationship follow-ups, so your delivery board stays about the work.

How detailed should a promise record be?

Short. Who, what, when, and where it came from. If writing it takes more than a minute, you'll skip it.

What about promises made in Slack or by email?

Same rule: when you read the commitment, create the next action right then. Don't leave it for later in the thread.

How AwiFin handles this

AwiFin treats promises, approvals and follow-ups as part of the client relationship. You record what happened and keep one clear next action. A client can move from proposal to follow-up to active client to approval to update without losing the history.The goal isn't to document everything. It's to make sure the right thing comes back to you at the right time.

How to Stop Client Promises From Falling Through the Cracks