Separate progress, completion timing and the next update
Write down three different facts before replying. First, state the last meaningful step completed. Second, describe what remains and whether the team can estimate it. Third, choose when you will review the status and contact the client again. A next update date is within your control even when the work depends on another person or an uncertain queue.
Do not let a follow-up date sound like a promised finish date. If you cannot yet estimate the remaining work, say so plainly and explain which condition would make a better estimate possible. A clear boundary is more useful than a calendar date that has no dependable basis.
Describe the dependency without blame
Name the specific input, approval, resource, or decision that is outstanding, along with the stage it affects. Avoid saying that the client is holding everything up when other work continues or the team has not yet made its own next move. Where several conditions remain, identify the one that currently controls planning and distinguish it from work that can proceed now.
If the uncertainty comes from your own workload or queue, say that the request is in a queue and explain what you can confirm today. Keep other clients' information private and avoid implying that a place in line guarantees a date.
Use a short update with a real next check-in
A practical message can follow this pattern: “The draft review is complete. We are waiting for the final product photos before we can confirm the remaining build sequence. I cannot give you a reliable completion date today because that sequence depends on those files. I will send you another update by October 21, even if the files have not arrived.” Replace every sentence with facts that apply to the project.
Choose a date you can keep and assign someone to send the update. If the client needs to make a decision or provide an item, explain exactly what would help and how the team will proceed after it arrives. Do not treat silence as approval.
Correct the message when the facts change
If the dependency arrives early, review it and update the client with the next known step instead of waiting for the scheduled check-in. If a new obstacle appears, explain that the earlier estimate or assumption no longer holds and give the next update date you can support. Keep the old message or status in your normal project record so the team can see what changed.
A next-update commitment is useful only if somebody owns it. Record the sender and date in the project record, then check that the message went out. The template does not establish an entitlement, a contractual notice period, or a required client communication policy.
Worked example
In the fictional example, Cedar & Coast Studio has completed a homepage wireframe and its internal copy review. The client has not yet supplied final product photographs, so the studio cannot confirm when the build will finish. The account lead sends the update below and records October 21 as the next check-in, not as the delivery date.
“Hi Dana, we have completed the homepage wireframe and reviewed the copy. The build sequence still depends on the final product photographs, so I cannot give you a reliable completion date today. Once we receive and check those files, I can confirm the remaining work and give you a clearer schedule. I will update you again by October 21, even if the files have not arrived.”
Using Areinum
Give Areinum Assistant the current project notes and ask for a draft update that separates completed work, the outstanding dependency and the next check-in. The person responsible reviews the wording and sends it through the agreed channel.
See the example
Client status update worksheet
The client names, project details, dependency, dates, and message in this guide are fictional.
| Project ID | Current stage | Completed since last update | Open dependency | Effect on completion estimate | Next update date | Internal sender | Client update sent |
|---|---|---|---|---|---|---|---|
| CED-014 | Homepage wireframe complete | Internal copy review finished | Final product photographs | Remaining build sequence cannot yet be estimated | 2026-10-21 | Taylor Brooks | Yes, fictional example |
| CED-015 | Campaign concept review | First concept shared | Client choice between two concepts | Production timing depends on the selected concept | 2026-10-22 | Morgan Lee | No, draft the update |
| CED-016 | Data import review | Sample file checked | Internal decision on two unmatched fields | Completion date depends on the team's mapping decision | 2026-10-20 | Riley Chen | No, draft the update |
- Use one row per client project and describe the current stage in terms the client can understand.
- Separate completed work from the open dependency. Explain the effect on timing without turning an uncertain estimate into a promise.
- Choose a next update date that the named internal sender can meet. It is a communication commitment, not the project completion date.
- Mark an update as sent only after it has actually been sent. Replace all fictional examples before using the worksheet.
Limits of this method
- The source is one practitioner's account and does not establish market demand or a general service timeline.
- Use dates and commitments that fit your actual agreement and operating process. This template is not legal or tax advice.
Questions you may have
What date can I give if I cannot estimate completion?
Choose a date when you can genuinely review the status and update the client. State clearly that it is a check-in, not the finish date.
How should I explain a delay caused by my own queue?
Say what is in the queue and what you can confirm now. Avoid disclosing another client's information or implying a queue position guarantees timing.
What if the dependency changes before the next check-in?
Update the client earlier, explain the new fact and say whether you can now make a reliable estimate.
Will Areinum send the client update for me?
This guide describes preparing a draft for review. The person responsible checks the facts and handles the actual client update.
Sources and further reading
- Best Practices for managing post-extension client expectations?
A solo tax-practice poster describes client questions about work in an uncertain queue and asks how to communicate realistic timing.
One self-reported practitioner discussion does not establish prevalence, identity, or a generally suitable timeline. This guide offers a communication method, not tax advice.
2026-10-18
The demo uses sample company data. Access may need to be arranged.
Explore the demo