How to Show a Client Progress When the Final Deliverable Is Not Ready Yet
Stop sending vague “still working on it” updates. Show your client useful progress, clear evidence, risks, and the next decision.
The client asks, “How is the project going?” You have done research, tested ideas, and ruled out a bad approach. But the final design, report, or website is not ready to show.
“Still working on it” makes real effort sound like no progress. A list of hours may not help either; the client wants to know what the work means for their project.
A useful progress report shows what changed, what evidence exists, what remains, and what you need next. It can build confidence without pretending unfinished work is complete.
Report against the promise, not your entire activity log
Start with the result or milestone you agreed with the client. Then explain where you are relative to it. Drag to compare.
Keep the detailed time record available if it is relevant to your agreement. The progress note should explain the work, not overwhelm the client with every action.
Show an artifact or a decision
Progress does not always mean a finished file. It might be a tested idea, a narrowed set of options, a draft structure, or a risk you discovered early. Label a rough draft as a rough draft so the client does not mistake it for a final design.
Do not use a busy-looking activity list to disguise a lack of movement. If the work is blocked, say so and name the decision needed.
Use this client progress report template
- Project and reporting period
- Agreed next milestone
- Current positionWhat is complete, in progress, or at risk?
- What changed since the last updateTwo or three meaningful points
- EvidenceLink to the current draft, test, or decision note
- What remainsThe work needed to reach the milestone
- Input or decision neededWho needs to do what, by when?
- Next updateWhen the client will hear from you again
For a small project, this can fit in a short email. A complex project may need a linked report, but the summary should still make the current position clear.
A filled-in example
- MilestoneFirst complete page draft by Thursday.
- Current positionOn track if the confirmed price arrives by Tuesday afternoon.
- CompletedAgreed the page structure and drafted the main message. Tested the registration form with sample entries.
- EvidenceLink to the draft page. The images are placeholders and are labeled.
- RemainingAdd the final price, replace the images, and check the mobile layout.
- Decision neededPlease confirm whether the ticket includes the recording by Tuesday at 2 p.m.
- If that input is lateI will send the page with the offer section marked for confirmation, and we will agree the final release time.
- Next updateThursday morning with the review-ready version.
The condition on the deadline is visible before it becomes a missed promise.
Explain hours when hours are part of the agreement
Give the client the information needed for the decision at hand.
Do not assume every logged hour is billable. Distinguish client work from internal admin or corrections you have agreed not to charge for.
Raise risks before the client asks
Raise risks before the client asks.
If the work has expanded, show the difference between the original scope and the new request. Do not silently absorb it and then surprise the client with a delay or bill.
Agree a predictable update rhythm and keep current links in one place. Ask for feedback on the part that is ready to decide: “Please confirm the structure; we are not reviewing colors yet” can prevent avoidable revision loops.
Write the update from the record, not from memory
M-Tracker helps you keep task outcomes and recorded work sessions together, so a progress note is based on what actually happened this week.
If you request a work quality review before sending a draft, treat the feedback as preparation, not client acceptance. The client doesn’t need your internal records; they need the result, the remaining work, and any decision you need from them.
Get started for freeNo credit card required. No employee surveillance.
Common reporting questions
How often should I send an update?
Agree a rhythm that fits the project. A short, fast-moving job may need more frequent updates than a long research phase. Always raise a meaningful risk when it appears rather than waiting for the scheduled report.
What if I have nothing polished to show?
Show a clearly labeled working artifact or explain the decision the work has enabled. If there is genuinely no progress, be honest about why and what changes next.
Should I share every problem?
Share issues that affect the client’s choices, scope, timing, or confidence. You can handle routine working details without turning the report into a diary.
Work you can trust, without redoing it.
Your team gets feedback before work reaches you, or your client.
Copyright © 2020 – 2026 M-Tracker. All Rights Reserved. Privacy Policy