Chasing commitments without becoming the person who nags

Every team has someone who is good at this and someone who is not, and the difference is almost never assertiveness. The people who are good at chasing have a system. The people who are bad at it have a mood — they wait, get annoyed, wait longer, then send something with an edge on it.

The system is learnable and mostly mechanical.

Why it feels awkward

Following up feels like an accusation because it usually arrives late. By the time most people chase, the thing is properly overdue, they are already irritated, and the message carries that. The recipient hears a complaint, gets defensive, and the exchange costs both of you more than the task was worth.

Chase earlier and none of that happens. A note sent the day something is due reads as administration. The same note sent nine days later reads as a grievance, no matter how carefully you word it.

Get the commitment right in the room

Most failed follow-ups were doomed at the moment the promise was made, because the promise was not specific enough to chase.

• One name. "The team will look at it" cannot be chased. Somebody has to own it, and that has to be said out loud while everyone is still in the meeting.
• A real date. "Soon", "next sprint" and "before the launch" are not dates. If the person cannot give one, that is useful information now rather than a surprise later.
• A stated deliverable. "Look into the pricing" is not checkable. "Send the revised quote" is. If you cannot tell from the wording whether it is done, you will not be able to tell in three weeks either.

Write it down where you will see it again — not in the notes document, which nobody reopens, but somewhere that will surface it on the date.

The first follow-up

Send it on the day, not after. Keep it short, factual, and free of any suggestion that you are disappointed:

Hi — checking in on the revised quote we agreed for today. Is it still on track, or has something moved?

Three things are doing work there. It names the specific thing. It gives the date as a fact rather than an accusation. And it offers an exit — has something moved — which lets the person tell you the truth instead of defending themselves. Half the time the answer is genuinely "yes, sorry, Thursday", and that is a fine outcome that cost nobody anything.

Do not apologise for asking. "Sorry to chase" teaches everyone, including you, that asking is an imposition. It is not; it is the job.

The second one, and the one after that

If the first is ignored, change something. Sending the same message again, more tersely, is the behaviour that earns the reputation you are trying to avoid.

• Second follow-up: change the channel. If the first was email, say it in the next meeting or on a call. A thing that is easy to leave unanswered in writing is hard to leave unanswered in person.
• Third: change the ask. Stop asking for the deliverable and start asking for a decision. "Do you still want to own this, or should it move?" is not a threat — it is an offer, and it is usually answered honestly.
• After that, escalate — visibly. Escalating without telling the person is the actual betrayal. "I'm going to raise this with Priya on Friday if we're still stuck" gives them a chance to fix it and makes the escalation a stated process rather than a knife.

Do it on a schedule, not on a feeling

This is the whole trick. If you chase when you are annoyed, your follow-ups will carry that, and they will be irregular — some things chased three times, others never. If you chase because it is Friday and Friday is when you look at what is outstanding, the messages come out even-tempered and nothing gets forgotten.

A schedule also protects the relationship. Being chased by a process is impersonal in the way you want: it is not that you do not trust them, it is that everything gets checked. Say that out loud once — "I go through outstanding items every Friday, so you'll hear from me" — and the follow-ups stop registering as personal entirely.

Where DayMarshal fits — honestly

DayMarshal extracts commitments from meetings with an owner and a date, and tells you when one goes past it — once, inside working hours, to the person the promise was made to rather than to everyone who could see the meeting. A broken promise becomes a nudge you can act on rather than a team-wide alert, and a promise already marked kept is never chased, because chasing somebody about something they delivered is the fastest way to get an assistant switched off.

It will not write the message. Wording is judgement, and judgement is yours.

For the review rhythm that makes this routine, see a weekly review that takes fifteen minutes. For getting the commitment recorded properly in the first place, see turning meeting notes into assigned action items.