Every freelancer will have a project that runs late. The ones who handle it professionally preserve the client relationship. The ones who handle it badly create disputes that outlast the project.
The professional handling of a late project has three rules.
Rule 1: Tell the client before they ask
The moment you know you will not hit a deadline, tell the client. Not when the deadline passes. When you know.
This sounds simple. It requires overcoming the instinct to hope the situation improves before you have to raise it.
The hope almost never materializes. The client who finds out on the deadline day that the delivery is not coming has a more intense reaction than the client who found out three days earlier.
The earlier communication is always the right move.
Rule 2: Be specific about the new timeline
"I need a few more days" is not a timeline. "Delivery will be [specific date]" is a timeline.
Vague timelines require follow-up conversations. Specific timelines allow the client to plan. Give them the specific date.
If you are not sure of the specific date, say so: "I am currently estimating [date] but I want to confirm that before committing. I will have a definitive date for you by [earlier date]."
Rule 3: Explain without making excuses
One sentence about why the delay happened. Not a paragraph of context-setting. One sentence.
"The integration with the client's legacy system was significantly more complex than the documentation suggested. I should have flagged the risk earlier and I did not."
That sentence acknowledges the situation honestly. It does not transfer blame. It does not minimize the impact. It is the right sentence.
The Solopreneur AI Toolkit includes prompts for writing difficult client communications including late delivery notices. EUR 12.
Top comments (0)