Freelance Weekly Status Update Email: Template and Prompts
Freelance weekly status update email template: done, in progress, blocked, next and decisions, plus AI prompts that never invent progress.
Part of Freelance client emails: every template from first call to rate increase, in one place.
Kickoff is done. The deposit cleared. Now the client wants to know what is happening without a 40-minute call every Friday. A short weekly status update email does that job: it shows progress, surfaces blockers early, and asks for decisions before they stall the timeline.
This guide gives you a reusable email template (done / in progress / blocked / next / decisions needed), a simple cadence that fits most freelance projects, and a light AI workflow: ChatGPT or Claude drafts the update from your notes or a meeting transcript. The model organizes. You verify every fact. Nothing gets invented.
If you still need the message that starts the paid work, use our freelance client kickoff email. This page is the mid-project rhythm that keeps trust high after that.
Why a weekly status email beats vague check-ins
Most client anxiety is not about quality. It is about silence. When they have not heard from you in ten days, they invent stories: the work is stuck, you forgot them, or the deadline is at risk.
A good weekly status email does five jobs:
- Prove progress. Concrete done items, not "making good headway".
- Show the pipeline. What is in progress and when you expect it next.
- Surface blockers early. Inputs you are waiting on, with owners and dates.
- Set next week's focus. So the client knows what "busy" means for you.
- Ask for decisions. Approvals, choices, and access that only they can give.
Skip the email and you spend Mondays answering "any update?" threads. Send a clear one and those threads shrink.
The five sections (and what belongs in each)
Keep the same headings every week so clients learn where to look. Fill only what is real. Empty sections are fine; fake progress is not.
| Section | Put here | Leave out |
|---|---|---|
| Done this week | Finished deliverables, sent drafts, closed tasks | Vague effort ("lots of research") |
| In progress | Active work with a next checkpoint date | Items you have not started |
| Blocked | What you need, who owns it, since when | Blame or long excuses |
| Next week | Top 2 to 4 planned outcomes | A full backlog dump |
| Decisions needed | Approvals, options, access, dates | Soft "let me know thoughts" |
If a blocker is really a scope change ("can you also redesign the homepage?"), do not bury it in status. Route it through your scope creep and change-order process so unpaid work does not hide inside a friendly update.
The weekly status email template
Copy this into your mail client. Aim for under 200 words when the project is calm. Busy weeks can run longer; still keep bullets short.
Subject: [Project name] · week of [Mon date] status
Hi [Name],
Quick status for [Project name].
Done this week:
- [Deliverable or task], sent [day] ([link or location if useful])
- [Deliverable or task]
In progress:
- [Item]: next checkpoint [weekday]. On track for [milestone date].
- [Item]: waiting on internal review; sending draft by [day]
Blocked / waiting on you:
- [Asset, access, or decision] · owner: [name] · needed by [date]
- [Item] · owner: [name] · needed by [date]
Next week:
- [Outcome 1]
- [Outcome 2]
- [Outcome 3]
Decisions needed (reply is enough):
1. [Choice A or B, or approve draft X]
2. [Confirm date / access / stakeholder]
Happy to jump on a 15-minute call if any of the above needs discussion.
Otherwise I'll keep moving and send the next update on [usual day].
Thanks,
[Your name]
Send it on the same weekday every week when you can (for example Friday morning in their timezone). Predictable cadence beats perfect prose.
Cadence, length, and when to skip
| Situation | What to do |
|---|---|
| Active build or design week | Full five-section email |
| Quiet week (waiting on client) | Short email: what is blocked, what you need, when you will resume |
| Same-day kickoff or handoff call | Skip that week's email; send a one-page call summary instead |
| Multiple clients | Same template, different subject lines; batch drafts then send |
| Retainer with a shared board | Email can point at the board, but still list decisions needed in the body |
If your kickoff set communication rules (channel, reply window, change notes), keep those rules visible in the footer of the first few status emails. That is part of the AI client onboarding workflow: status is how onboarding stays true in week three.
AI draft workflow: notes or transcript to email
AI is useful here for structure and clarity. It is dangerous when it invents "completed homepage wireframes" that never happened. Start from facts you already wrote down.
Step 1: Collect a fact pack
Before you open ChatGPT or Claude, paste only what you trust:
Project name:
Week of (dates):
Done (bullet list from my tracker / commits / sent emails):
In progress (with next dates):
Blocked (item, owner, since when, needed by):
Planned next week:
Decisions I actually need from the client:
Links I may include (only real ones):
Anything I must not claim:
If you recorded a check-in, add a transcript or notes from a meeting notes tool. Strip credentials and anything the client would not want pasted into a consumer chat.
Step 2: Draft prompt
Draft a freelance weekly client status email under 200 words.
Use only the facts below. Do not invent progress, dates, links,
owners, or deliverables. If something is unclear, put it under
"Decisions needed" or omit it. Tone: calm, clear, professional.
No guilt, no over-promising, no "just circling back" filler.
Use these headings: Done this week, In progress, Blocked / waiting
on you, Next week, Decisions needed.
Subject line: "[Project] · week of [date] status".
Facts:
"""
[paste fact pack]
"""
Step 3: Fact-check before send
Read every bullet against your tracker. Delete anything the model added. Fix dates. Confirm links open. If a "done" item is only half done, move it to in progress. You own the send.
A second useful prompt when the week was messy:
Tighten this status draft. Keep every factual claim.
Cut soft language. Turn vague blockers into owner + needed-by date.
Flag any sentence that sounds like new scope or a promise I did not
make in the facts.
Draft:
"""
[paste]
"""
What not to hand to AI
- Sending unreviewed. Status emails create a paper trail. Wrong "done" items damage trust.
- Inventing progress to sound busy. Clients would rather hear "blocked on brand files since Tuesday" than a fictional update.
- Pricing, late fees, or legal threats. Those belong in payment or contract threads (see late payment reminder emails), not weekly status.
- Secret credentials. Never paste passwords, full contract PDFs with unnecessary PII, or private financials into a chat UI.
Soft automation (optional)
Some freelancers schedule a Friday reminder or stub a draft from a project board. The stub should still need your eyes before it goes out. If you already automate lead-to-active handoffs, a weekly "create draft status" step can sit in the same stack. Make works well when you want a scheduled scenario that opens a draft without auto-sending to the client. Keep the send button human.
FAQ
How long should a freelance weekly status update email be? Under 200 words on a normal week. Use bullets. If you need more than a page, you are writing a report; link a doc and keep the email as the summary plus decisions.
What if I have nothing new to report? Still send a short note: what you are waiting on, the date you need it, and when work resumes. Silence is worse than a blocked update.
Should I copy the whole team? Copy decision-makers and the day-to-day contact named at kickoff. Blind-copying the whole company creates reply chaos. Ask once who should be on status emails.
Can AI write the update from a transcript alone? It can draft structure from a transcript, but you must verify every done and blocked item against reality. Transcripts miss side chats and overstate agreement.
What if the client asks for extra work in the reply? Thank them, confirm whether it is in the signed scope, and if not, send a short change note before you start. Do not absorb new scope inside the next status email.
Bottom line
A weekly status update email is not theater. It is the cheapest way to keep a mid-project client calm: real done items, honest blockers, clear next steps, and explicit decisions. Use the same five headings every week. Let ChatGPT or Claude draft from a fact pack or transcript, then delete anything the model invented before you hit send.
When blockers keep pointing at missing inputs or fuzzy deliverables, run the free 40-point scope checklist once more against the signed proposal so next week's status has fewer surprises.
Related guides
Freelance Request Assets Email: 5 Templates That Unblock Work
Ask clients for brand assets, logos, credentials and content: what to check first, five copy-ready emails, an asset checklist, and AI prompts that refuse invented details.
Freelance Milestone Approval Email: 5 Templates to Get Sign-Off Mid-Project
How to ask a client to approve a milestone before you continue: what to check first, five copy-ready emails (ready for review, gentle nudge, phase invoice, conditional next step, silent client), and AI prompts that keep your terms intact.
Out of Revision Rounds? 5 Freelance Email Templates to Set the Limit Kindly
How to tell a client the included revisions are used up: what to check first, five copy-ready emails (heads-up, last round, paid extra round, final sign-off, too many small changes), and AI prompts that keep your terms intact.