Who this module is for
Practice this before offering the skill.
Best for every aspiring VA because communication is one of the first things clients notice.
Tools to open while practicing
- Slack
- ClickUp comments
- Notion
- Google Docs
Full VA training module
Client Updates Full Module
Learn how to send clear updates that build trust, report blockers, ask better questions, and reduce client follow-ups.
Mock client brief
Use this messy input as your training scenario.
Imagine a client sends you the items below and asks you to handle it. Your job is to turn the mess into organized work, clear decisions, and proof you can explain.
- Finished cleaning the tracker and found 3 duplicate leads.
- Drafted 2 email replies but need approval before sending.
- Could not access the shared Drive folder.
- Scheduled the Tuesday call and added the Zoom link.
- Still working on the SOP and expect to finish tomorrow morning.
- Need the client's preferred tone before replying to a complaint.
Module workbook
Learn the skill, then prove it with finished work.
This page is meant to be worked through, not skimmed. Read the lesson, complete the action steps, then build the final project at the bottom.
Learning objectives
- Write updates that are short, structured, and easy for busy clients to scan.
- Report blockers with a specific ask instead of vague confusion.
- Ask for approvals clearly and professionally.
- Build trust by communicating before the client has to follow up.
Key terms to know
- Done
- Work that is completed and can be checked, sent, saved, or reviewed.
- Blocked
- Work that cannot continue until a specific file, access, approval, or decision is provided.
- Approval request
- A message asking the client to review and confirm something before it is sent or finalized.
- Next priority
- The next most important task you will handle after the current update.
Guided lessons
Work through each part in order.
Each lesson has a concept, a VA action, and a small proof task. Do all three before going to the final assignment.
1
Part 1
Use a repeatable structure
A structured update helps the client scan quickly and trust that nothing is hidden.
Action 1
Use Done, Doing, Blocked, Needs Approval, and Next.
Action 2
Put the most important item first.
Action 3
Keep each bullet tied to a result, not just activity.
Proof task
Apply this part to the mock client brief above and save one clear example you could show in a portfolio or explain in an interview.
2
Part 2
Report blockers professionally
A blocker is not a failure. It becomes a problem when the VA disappears or asks vague questions.
Action 1
Name the blocked task.
Action 2
Explain what you already checked or tried.
Action 3
Ask for the exact missing decision, file, access, or approval.
Proof task
Apply this part to the mock client brief above and save one clear example you could show in a portfolio or explain in an interview.
3
Part 3
Sound calm and useful
Clients do not need panic. They need visibility and options.
Action 1
Avoid over-apologizing when a clear action is better.
Action 2
Avoid long paragraphs when bullets would help.
Action 3
End with what you will do next and when.
Proof task
Apply this part to the mock client brief above and save one clear example you could show in a portfolio or explain in an interview.
Walkthrough
Follow this process from messy input to finished output.
This is the exact practice flow learners should complete before marking the module done.
- 1Group each raw material under Done, Doing, Blocked, Needs Approval, or Next.
- 2Turn every blocker into a specific question or request.
- 3Remove extra explanations that do not help the client decide or understand progress.
- 4Write one daily update, one blocker update, and one approval request.
- 5Read each update out loud and make it shorter without losing meaning.
Copy-ready resource
End-of-day update template
This is not filler. Use it as the learner's working template, then customize it for the client, task, and tone.
Hi [Client Name], quick end-of-day update:
Done:
- [Completed task + result]
- [Completed task + result]
Doing:
- [Current task + expected completion]
Blocked / needs input:
- [Task] - I need [specific info/approval] so I can [next action]
Next:
- [Priority for tomorrow]
- [Priority for tomorrow]Hands-on practice lab
Write three client updates
You completed 4 tasks, have 1 blocker, need approval for 1 item, and have 2 priorities tomorrow.
Practice tasks
Final project requirements
Submit these outputs to yourself as proof. If a learner cannot explain these, they are not done with the module yet.
- One end-of-day update.
- One blocker update with a specific ask.
- One approval request.
- One rewritten version of a vague update into a clear update.
Checkpoint quiz with answers
What is wrong with saying I am confused?
It does not tell the client what you need. A better update names the blocker and asks a specific question.
Why use headings like Done, Doing, Blocked, and Next?
They make the update easy to scan and reduce follow-up questions.
When should you send a blocker update?
As soon as the blocker affects progress, not only when the client asks for a status update.
Avoid these mistakes
- Saying I am confused without a specific question.
- Writing a long story instead of a clear update.
- Hiding delays until the client asks.
- Only saying working on it with no timeline or next action.
Quality rubric
- The update is easy to scan.
- The client knows what is done and what is next.
- Blockers include a specific ask.
- Tone is calm, clear, and professional.
Portfolio proof
- Daily update sample
- Blocker update sample
- Approval request sample
Resume bullets after practice
- Prepared clear daily client updates covering completed work, blockers, approvals needed, and next priorities.
- Improved task visibility by communicating status, risks, and specific next actions through concise written updates.