How to Track Client Commitments in a Consulting Engagement

Why commitments slip in consulting engagements

Commitments are made everywhere: in steering committees, in side conversations after a workshop, in the last line of a long email. Few of them end up in the project plan, because the plan tracks work packages, not promises.

Client deliverables are the hardest part. You can't assign tasks to the client's team, but your timeline depends on their data, decisions and availability. If you don't track what you are waiting for, you notice the gap only when the milestone is already at risk.

Seven rules for tracking commitments

These rules work in a spreadsheet, a notebook or a dedicated tool. What matters is that you apply them the same way in every engagement.

1. Write it down the same day

Every commitment from a meeting goes into your list before the end of the day, ideally while you write the recap. A commitment you write down a week later is already a guess.

2. Track both sides

List what you owe and what the client owes in the same place. Client deliverables are often the reason a milestone slips, and they are the ones teams forget to track.

3. Owner, item, date, source

Each line needs four things: who delivers, what exactly, by when, and where it was agreed (the email or meeting). Without a source, every discussion about a commitment turns into memory against memory.

4. Keep “waiting for” separate

Your own tasks and the things you are waiting for need different handling. Tasks you do; waiting-for items you follow up on. A separate view shows at a glance which follow-ups are due.

5. Review weekly

Once a week, go through the open items of each engagement: what is done, what is overdue, what is due next week. Ten minutes per engagement is usually enough.

6. Make commitments part of the status call

Go through open commitments in every status call, oldest first. When the client hears their own open items read out with dates, they tend to move.

7. Escalate early, with dates

If a client deliverable threatens a milestone, say so two weeks before, not two days before. Name the dependency and the consequence: “Without the data by the 31st, the workshop on the 14th moves.”

A 10-minute weekly review per engagement

Minutes 1–3: Scan the emails and meeting notes since last week and add new commitments.
Minutes 4–6: Mark what was delivered. Check overdue items on both sides.
Minutes 7–10: Draft the follow-ups for overdue client items and update the dates of your own deliverables if needed.

The first three minutes take the longest when you run several engagements, because the commitments are scattered across email threads and calendar entries.

Template: a commitment log

One entry per commitment. Copy these fields into a spreadsheet or your notes; here is a filled-in example:

Engagement: Operations review
Owner: Client (M. Roth, COO)
Commitment: Warehouse data export for all three sites
Due: October 16
Agreed in: email from October 9
Depends on it: site manager workshop on November 14
Status: open, reminder sent October 20

Beyond commitments: a light RAID log

Many consulting teams track commitments as part of a RAID log. For small engagements, a light version is enough:
Risks: what could delay the next milestone, and the earliest date you would know.
Assumptions: what your plan takes for granted, such as data quality or the availability of key people.
Issues: what is already causing a delay and who is resolving it.
Dependencies: the client deliverables and decisions your work depends on. This is where your waiting-for items live.

Common mistakes

Tracking only your own tasks. The client's open items are the ones that surprise you.
No dates. “Client to send data” without a date is a wish, not a commitment.
No source. When someone remembers the agreement differently, the email it came from settles it in a minute.
A log nobody looks at. If the list doesn't come up in the status call, it is out of date within two weeks.

How to raise an overdue client deliverable

Stay factual and connect the open item to its consequence. The client usually has good reasons for the delay; your job is to make the trade-off visible, not to assign blame. More wording ideas are in our seven follow-up templates for consultants.

An example for a deliverable that is a few days overdue:

Hi Megan,

The warehouse data export we discussed on October 9 hasn't come through yet. The site manager workshop on November 14 depends on it: we need about two weeks for the analysis.

If the export arrives by October 31, the workshop date holds. If that's difficult, we could start with the two larger sites and add the third later. Which works better for you?

Best,
Daniel

Let aenuma build the list for you

A spreadsheet works, but someone has to fill it after every meeting and every email. In practice, that is where most commitment logs die.

aenuma builds the list from your Outlook emails: you assign them to an engagement, and who owes what shows your commitments, the client's deliverables and what you are waiting for, each linked to the email it came from. The engagement briefing puts them in context before your next status call.

By Joshua Schütt, founder of aenuma. Last updated: October 2026. Examples are fictional.

How to track client commitments and deliverables in a consulting engagement.