What to Do When an Employee Repeatedly Misses Deadlines
Start with the last three examples
A missed deadline is frustrating, especially when customers or colleagues are waiting. But saying that someone is “always late” rarely explains why. Review the last three commitments: what was due, when it was agreed, what was delivered and what happened between those points. Separate the dates that were genuinely missed from dates that changed because priorities or requirements changed.
A useful opening is: “We agreed Friday for the report, and it arrived Tuesday. This has happened on two other projects. Can we look at what got in the way?” This identifies a pattern without assuming carelessness. Give the employee space to explain, but compare the explanation with the actual workflow.
Test whether the deadline was realistic
Ask how the estimate was made. Did the employee know the full scope? Were they carrying urgent work for another manager? Was the task dependent on data, approvals or decisions from someone else? A deadline set without considering those constraints may be a planning failure rather than an individual one.
For example, a colleague may need sales figures by Wednesday to produce a Friday report. If the figures routinely arrive on Friday afternoon, reminding the colleague to work faster will not solve the problem. The handover and dependency need attention.
Identify where work starts slipping
Look for the earliest predictable warning sign. Some people delay starting because the task is unclear; others underestimate how long review and corrections will take. A few complete most of the work on time but wait too long to ask for a decision. Each pattern calls for a different response.
Ask the employee to describe the stages of a typical task. Compare the plan with the actual sequence. If a project repeatedly takes eight days rather than five, use that evidence in the next estimate instead of demanding an optimistic date.
Agree a better working arrangement
For the next commitment, define the deliverable, deadline and dependencies in plain language. Add one or two meaningful checkpoints, not a daily meeting by default. A draft halfway through may reveal problems early; a dependency check before work begins may be enough for a simpler task.
Agree when the employee must raise a risk. “Tell me by Tuesday lunchtime if the customer data has not arrived” is more actionable than “keep me updated”. The manager must respond promptly when the warning arrives; otherwise the employee learns that escalation achieves nothing.
Where priorities conflict, decide explicitly what can move. If a new urgent assignment takes precedence, revise the existing commitment and notify those affected. Do not hold someone accountable for two incompatible deadlines without choosing between them.
Review the result, not just the explanation
After the next deadline, ask whether the changes worked. Did the task arrive on time? Was quality maintained? Did the new checkpoint reveal issues early enough to act? If the process improved, retain the useful parts and remove unnecessary reporting.
If missed deadlines continue despite achievable commitments, adequate resources and clear support, address the individual performance concern through the organisation's normal process. Keep records factual, offer appropriate support and involve HR when needed. Avoid making promises about consequences that are outside your authority.
Reliable delivery comes from realistic planning, early warnings and clear ownership. A manager who fixes the system as well as holding people accountable is more likely to see lasting improvement.
Further reading: Browse the free management guides for related background. Where relevant, explore the management books.