Nobody likes the person who sends follow-up messages every day asking “any updates?” But deadline tracking is a legitimate responsibility, and projects with weak tracking systems routinely miss dates.
The difference between being seen as a nag and being seen as organized comes down to system and tone.
The Core Principle
Track the deliverable, not the person. The goal is to know when something is at risk — not to make the other person feel surveilled.
Set Expectations at Kickoff
The best time to set up a tracking system is at project start, not when you are already behind.
At kickoff, agree on:
- What counts as “done” — Is it sent, or is it approved? Make the definition clear upfront.
- When deliverables are due — Not just the date, but the time (end of day vs. morning, for example)
- How you will communicate delays — “If this slips, I need 48 hours notice so we can find a solution”
- The tracking channel — Where will you share status? Slack thread, project board, email?
Write this into the project brief or scope document so it is documented, not just agreed to verbally.
If project ownership changes, a structured project handoff helps preserve those deadlines, responsibilities, decisions, and context.
The Status Check System
Instead of “any update?” use a structured check:
At 50% of time elapsed:
“Hi [name] — checking in on the [deliverable] due [date]. Where are we? Anything I can help unblock?”
At 75% of time elapsed:
“[Name], just a heads-up — we are at 75% of the timeline for [deliverable]. What is the current estimate?”
At 100%:
“Reminder: [deliverable] is due today. Please send by [time] so we have buffer for review.”
This keeps you informed without pestering. And it creates a documented pattern that shows you are tracking, not just reacting.
How to Handle Late Deliverables
When something is late:
- Do not escalate immediately. Send one message first: “The [deliverable] was due today and we do not have it. What is the revised estimate and how does this affect [downstream dependency]?”
- Assess impact. Is this a one-day slip with no downstream effect, or does it push a client deadline?
- Escalate to your manager only if: the revised estimate threatens a deadline, the person has a pattern of missed deliverables, or you have tried twice with no response.
The Tools That Help
- Shared project board (Asana, Monday, Notion) with task owners and due dates visible to all
- Automated reminders from the tool before the due date
- Weekly status reports that surface who is tracking and who is not
- A clear escalation path documented at project start
What NOT to Do
- Do not send “just checking in” messages without context or a specific ask
- Do not track by memory — if you have to remember it, you do not have a system
- Do not wait until the day something is due to discover it is late
The Real Rule
If you are frequently the person chasing deliverables, one of two things is true: either the tracking system is weak (fix it at kickoff next time), or the people you are chasing have a pattern of missing deadlines (escalate that, do not just chase it).
Office Email Templates Bundle — templates for time-sensitive follow-ups, status updates, and escalation emails.