A virtual assistant supports a person’s work, not just their inbox
A client asks for a meeting, a document and a follow-up. The tasks look separate, but they share information: the purpose of the meeting, the correct time zone, the latest document and the person who must approve it. Good assistance makes those dependencies visible.
Administrative work can include scheduling, maintaining records, preparing documents and communicating with colleagues. O*NET’s administrative-assistant task descriptions provide occupational context, not a promise that every virtual assistant does the same work. A role supporting a creative business may differ from one supporting an operations team.
Give an executive a workable next hour.
An executive has a travel deadline, a busy inbox, a flexible social post and an invoice that needs approval. There are only 60 minutes to allocate.
Your role: Build a short plan, protect the fixed deadline and respect what the client has actually allowed you to do.
What you’ll learn: Balance time, priorities and approval before taking action for a client.
No account needed. Nothing is sent or saved. You can restart at any point.
Read the full guided story without the interactive controls
You can follow the same lesson here without JavaScript.
Read the brief before filling the calendar
Inspect the tasks, their time estimates and the invoice’s approval requirement.
What happens and why: Travel needs 30 minutes and has a fixed deadline today. Inbox triage takes 15, social scheduling 30 and invoice handling 20. These are fictional planning estimates.
Build a plan that fits
Select tasks for the next 60 minutes. Include the urgent travel task and examine the time left.
What happens and why: Travel plus inbox uses 45 minutes and leaves 15. Adding every task overbooks the hour. A workable plan may require deferring flexible work and communicating the trade-off.
Check what you are authorised to do
The invoice has not been approved. Prepare an approval request instead of treating calendar space as permission to pay.
What happens and why: Capacity is not authority. Ask the client for explicit approval; do not mark the invoice paid or assume permission from silence.
Hand over a clear plan
Create a note showing the selected work, remaining time, deferred items and invoice status.
What happens and why: A useful handover makes priorities and constraints visible. No payment, calendar event or client message is sent by this model.
Takeaway: A useful assistant manages constraints as well as tasks: protect deadlines, avoid overbooking and get approval for actions outside delegated authority.
Where this is useful: Useful in executive assistance, team coordination and client administration.
A fictional educational example, not a confirmed TWA assignment, assessment or learner outcome. Simplified to explore one idea; real situations need context and authorised procedures.
Optional deeper exploration: open the original technical workspace
Want to explore the technical model?
The guided story above introduces the idea. This original workspace lets you try actions in different orders. It has its own reset and does not inherit your story choices.
- Capacity
- The amount of time available for planned work.
- Dependency
- Something that must happen before another action, such as approval before payment.
- Delegated authority
- Actions a client has explicitly permitted you to take.
- Handover
- A clear explanation of the plan and what still needs attention.
Plan the day before filling it.
Learning objective: Respect capacity, dependencies and delegated authority.
You have 60 minutes. A fictional client has an imminent travel deadline; paying an invoice requires approval.
Evidence desk
- Travel booking
- 30 min · deadline today
- Invoice
- 20 min · client approval not yet granted
- Inbox triage
- 15 min · routine
- Social scheduling
- 30 min · flexible
Your workspace
Worked explanation & takeaway — available without JavaScript
Travel plus inbox triage fits in 45 minutes and protects the fixed deadline. Ask for invoice approval rather than making an unauthorised payment. A schedule over 60 minutes needs negotiation; priorities depend on the real client brief.
Fictional educational model. No live system, personal assessment or confirmed TWA assignment. All actions run locally in your browser.
Triage a client request
No email is sent and no calendar is accessed. Compare the next action for each fictional request.
- Clarify
Identify the purpose, deadline and missing information.
- Prepare
Organise the draft, options or document.
- Confirm
Seek approval for commitments and sensitive changes.
- Follow up
Record the decision and the next owner.
Ask for the meeting purpose, attendees, time zones and constraints. Offer options before representing anything as booked.
Read both scenarios and explanations
“Book something next week”
Ask for the meeting purpose, attendees, time zones and constraints. Offer options before representing anything as booked.
“Send the latest proposal”
Check which version is approved and who may receive it. Prepare a draft rather than sending an uncertain document.
An educational illustration using fictional situations. It is not a confirmed TWA assignment, live system, assessment or promise of a particular tool.
Organise the work before choosing a productivity tool
Begin with clear file names, accurate records, a task list and messages that distinguish a request from a decision. Confirm deadlines and time zones instead of guessing. If an instruction is incomplete, ask a focused question: which version should be sent, who should attend or which commitment has actually been approved?
TWA’s existing direction includes email/calendar organisation, research, documents, data entry, Google Workspace, spreadsheets, collaboration, task tracking and AI-assisted productivity. Those areas support a learning conversation; the exact tool access and activities need confirmation. You do not need to invent a previous client to practise with a fictional brief.
Permissions are part of professional support
A calendar can reveal more than availability. Google Calendar distinguishes free/busy visibility from permissions to edit details or manage sharing. Match access to the task and the client’s instructions rather than asking for full account control by default.
In a sample workflow, an assistant can prepare two meeting options without confirming a booking. Draft a client message for review, keep confidential information out of unrelated AI tools and record what still needs a decision. A useful handover explains what is complete, what is waiting and who owns the next step. Quietly assuming approval can create a more serious problem than a delayed reply.
A fictional client onboarding and weekly handover
Organise a sample client’s meeting request, document draft and follow-up actions without contacting anyone or using private records.
What you could document
- A short client brief with scope and approval boundaries
- A calendar proposal showing time zones and unconfirmed holds
- A task tracker with owners, deadlines and status
- A concise handover and a professional clarification message
What makes the explanation useful?
Check consistency between the brief, calendar and tracker. A reviewer should see which commitments are confirmed and which still need permission.
The learning plan determines actual activities and assessment. These deliverables are examples, not contractual curriculum outcomes.
Develop a service around a clear scope
A foundation route can build digital organisation and communication habits. More focused work might deepen document quality, spreadsheet tracking, research methods or administrative operations. Specialising in a business context requires understanding its processes, not simply listing more apps.
For readiness, bring an example of a routine task you can explain. Discuss how you check accuracy and what you do when instructions conflict. Neither remote work nor training guarantees a client, an income or a particular working arrangement; the goal is to make your practice and reasoning visible.