Deadlines are normal in any job. So are delays.
The real problem is not the delay itself. The problem is silence. When you wait until the last moment, the other person has no time to adjust plans, shift priorities, or communicate to stakeholders.
If you want to sound professional, use a simple structure.
Flag it early.
Give a brief reason.
Offer a new plan.
Give options if needed.
1) Flag it early
Just a heads up, I’m seeing some risk to the timeline.
I want to flag this early so we can plan around it.
This is taking a bit longer than expected, and I want to make sure it’s done properly.
2) Give a brief reason
I ran into an issue with (X), and it’s taking longer than expected.
I found a dependency I didn’t account for.
I’m waiting on (team or person) before I can finish.
3) Offer a new plan
I’m running a bit behind because of (reason), but I have a clear plan to finish by (new date).
I’ll have a first draft by (time) and the final version by (time).
I can deliver (part A) by (date), and (part B) by (date).
4) Give options when priorities matter
We have two options: extend the deadline or reduce the scope.
If the deadline can’t be moved, we can ship a smaller version and improve it in the next sprint.
Which is the priority here: speed, quality, or completeness?
Two copy and paste templates
Just a heads up, I ran into (issue). I’m running a bit behind, but I can finish by (new date). Does that work?
I’m hitting obstacles with (task). Can we extend the deadline to (date)? If not, I can reduce the scope by (X). Which do you prefer?
When you communicate early and offer a plan, you do not just protect the project. You protect your reputation, too.