Freelance Project Update Emails: Three Templates for Check-Ins, Delays, and Handoffs

A client who does not hear from you assumes the worst. Not because they distrust you — because silence about something they are invested in gets filled with worry. A well-timed project update takes five minutes and prevents the anxious check-in email that costs you two hours of context-switching to handle.

Most freelancers default to one of two modes: radio silence until the work is done, or over-communicating to the point that updates become noise. Neither works. The rule is simpler: update when something changes, when you are about to hit a milestone, or when a deadline is approaching and the client should know where things stand.

• Before a scheduled delivery: A short heads-up 24 to 48 hours in advance sets the right expectation and gives the client time to clear space for feedback.
• When something changes: A delay, a decision you need from them, or a scope question that surfaced mid-project. The sooner you send this, the easier the conversation.
• When you do not need to send one: Do not manufacture updates. An email that says nothing useful trains clients to ignore your updates when they actually matter.

The mid-project check-in

Keep it under 100 words. Cover what is done, what is next, and whether you need anything from the client. That is it — no explanation of your creative process, no lengthy reassurance, no preamble about how exciting the project is.

• Subject: [Project name] — update + what I need from you
• Hi [Name], Quick update on [project name]: [one sentence on what you have completed]. I am now working on [next phase] and expect to have [deliverable] ready by [date]. Before I get there, I need [specific thing from the client — an asset, a decision, content, or an approval]. Can you send that by [date] so I can stay on track? Let me know if you have questions.

The delay notice

Delays are uncomfortable to send. Send them anyway — early and specifically. A delay notice sent four days before a deadline is a professional heads-up. The same information sent after the deadline is a broken promise. The difference between the two is not the circumstance; it is when you chose to say something.

• Subject: [Project name] — timeline update
• Hi [Name], I want to let you know that [deliverable] will be ready on [new date] rather than [original date]. [One sentence on the reason, without over-explaining.] I have already adjusted my schedule to prioritize this and am confident in the new date. I will keep you updated if anything changes. Apologies for the shift — I wanted to tell you as soon as I knew.

The project completion and handoff

The final delivery email is underused as a relationship asset. Most freelancers attach the files and say here it is. A better version confirms what was delivered, explains what happens next, and leaves a door open for future work.

• Subject: [Project name] — final files and next steps
• Hi [Name], [Project name] is complete. Attached you will find [specific list of deliverables — file names, formats, any logins or access details]. A few notes: [brief explanation of any decisions made or anything the client needs to know to use what you delivered]. Your invoice for the remaining balance is attached as well — payment terms are [net 15 or net 30]. It has been great working on this. If you have questions once you have had a chance to review, I am happy to jump on a call. I would love to work together again — if anything comes up, do not hesitate to reach out.

The rule that prevents most unsolicited check-in emails

The unprompted check-in from a client almost always happens when they do not know what to expect next. The fix is not to respond faster — it is to set the expectation at the start of every project: here is when you will hear from me, and here is what you will hear. Clients who know what to expect do not fill the silence with anxiety. They wait.

If you track your hours by project, sharing a brief summary of where the time has gone alongside a mid-project update — even just a line or two — tends to cut the budget anxiety that generates a second wave of check-ins. Transparency is faster than reassurance.