Who this module is for
Practice this before offering the skill.
Best for aspiring VAs supporting busy clients, project teams, content teams, agencies, or online businesses.
Tools to open while practicing
- Trello
- Asana
- ClickUp
- Notion
- Google Sheets
Full VA training module
Task Tracking Full Module
Learn how to turn messy client requests into clear tasks with status, owner, due date, priority, and next action.
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.
- Can you handle invoices?
- Please check the calendar for next week.
- Marketing stuff needs to go out soon.
- Ask Maria about the graphics.
- The client list needs cleaning before Friday.
- We still need captions for the launch post.
- Can someone follow up with the lead from yesterday?
- I cannot find the Zoom recording.
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
- Capture requests from scattered messages into one task system.
- Rewrite vague requests into clear action-based task cards.
- Track owner, due date, priority, source, blocker, and next action.
- Send a task update that gives the client visibility without extra follow-up.
Key terms to know
- Owner
- The person responsible for completing or moving the task forward.
- Status
- Where the task currently stands, such as New, Doing, Waiting, For Review, or Done.
- Source link
- The original message, email, file, or document where the request came from.
- Blocker
- The missing access, file, decision, approval, or information stopping progress.
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
Capture requests in one trusted place
Tasks get lost when they live in email, chat, notes, and memory at the same time.
Action 1
Pick one task home for the client.
Action 2
Copy requests from messages into the task board.
Action 3
Link back to the source message or document when possible.
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
Rewrite vague requests into action tasks
A good task tells the worker exactly what needs to happen next.
Action 1
Start with a verb: draft, schedule, update, research, organize, follow up, review, send.
Action 2
Add the object of the work: three captions, invoice tracker, client folder, meeting invite.
Action 3
Add due date, owner, priority, source, and next action.
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
Send daily task visibility
Clients trust assistants who show progress before being asked.
Action 1
Review New, Doing, Waiting, For Review, and Done daily.
Action 2
Move cards based on reality, not optimism.
Action 3
Send completed tasks, blockers, and next priorities.
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.
- 1Rewrite every vague request into an action task that starts with a verb.
- 2Add owner, due date, priority, status, source, and next action to each task.
- 3Separate tasks that need client approval from tasks you can complete independently.
- 4Move tasks into New, Doing, Waiting, For Review, and Done.
- 5Write a daily task update summarizing progress and blockers.
Copy-ready resource
Task card template
This is not filler. Use it as the learner's working template, then customize it for the client, task, and tone.
Task: [Action + object]
Owner: [Name]
Due: [Date/time]
Priority: [High/Medium/Low]
Status: [New/Doing/Waiting/For Review/Done]
Source: [Email/chat/doc link]
Next action: [The very next thing needed]
Notes: [Context, decisions, or blocker]Hands-on practice lab
Convert messy messages into a task board
Your client sends 10 requests across email and Slack, including vague messages like handle invoices, check calendar, and marketing stuff.
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.
- A task board with 10 realistic task cards.
- Each card includes owner, due date, priority, status, source, and next action.
- A Waiting column with clear blocker notes.
- A daily task update based on the board.
Checkpoint quiz with answers
Why should a task start with an action verb?
It makes the next step obvious and prevents vague task names like email, marketing, or invoices.
What belongs in a Waiting task?
The blocker, who needs to respond, what is needed, and when to follow up.
What does a daily task update help the client see?
Completed work, active priorities, blockers, approvals needed, and what happens next.
Avoid these mistakes
- Using vague task names like email or marketing.
- No due dates.
- No source links.
- Letting Waiting tasks sit with no follow-up plan.
Quality rubric
- Every task starts with an action verb.
- Every task has a next action.
- Waiting tasks explain what is blocking progress.
- Done tasks are truly completed or sent for review.
Portfolio proof
- Trello or Notion sample board
- 10 task card examples
- Daily task update
Resume bullets after practice
- Managed task boards by converting client requests into actionable tasks with owners, due dates, priorities, and next steps.
- Sent daily task updates summarizing completed work, blockers, approvals needed, and upcoming priorities.