In this guide
A clear executive virtual assistant task list, with delegation priorities, quality checks, escalation rules, and a simple way to build the role.
What matters most
- Executive Virtual Assistant work should be defined around a visible workflow, a source of truth, and a clear definition of done.
- Screen candidates with a real scenario: Give the candidate a calendar with a client escalation, an internal one-on-one, a travel conflict, and a meeting with no agenda. Ask what they would change first and what they would confirm before moving anything.
- Manage the role using calendar error rate, follow-up completion, meeting readiness, and how often the executive has to re-triage the same work, not generic activity counts.
- For a Philippines-based hire, write the schedule in Philippine Time and the client time zone and settle holiday and escalation rules before day one.
Build the role around the executive's recurring decisions
Task delegation should begin with the actual workflow. For an Executive Virtual Assistant, document the source of truth, the completion standard, and the decisions that still belong to the accountable owner before adding more scope.
The strongest executive support task list is a connected workflow, not a dump of unrelated admin. Start with calendar, inbox, meeting preparation, follow-up, and executive coordination, define the source of truth and completion standard, and keep executive judgment, sensitive commitments, compensation, and decisions only the leader can make outside the first handoff.
Daily work that protects the calendar and inbox
When stakeholder follow-up enters the weekly queue, daily responsibilities should be the work that loses value when it waits. If the first handoff is document preparation, choose items where the Virtual Assistant can see the queue, act within a defined rule, and close the loop without needing a manager for every step.
- Complex calendar management: decide the response window, source of truth, and what counts as completed.
- Inbox triage: decide the response window, source of truth, and what counts as completed.
- Meeting preparation: decide the response window, source of truth, and what counts as completed.
- Travel research: decide the response window, source of truth, and what counts as completed.
Meeting preparation should end with decisions and owners
Task delegation should use evidence from a real workflow. Ask the candidate what source they would check first, what they would record, what they can decide alone, and what would make them stop and escalate. Then use this scenario: Give the candidate a calendar with a client escalation, an internal one-on-one, a travel conflict, and a meeting with no agenda. Ask what they would change first and what they would confirm before moving anything.
Keep sensitive commitments and people decisions with the executive
For the executive task handoff, keep executive commitments, sensitive people decisions, compensation, legal or investor matters, and anything the leader has not explicitly delegated with the person who has authority to make that decision. Give the VA enough authority to complete routine work, but do not turn access or convenience into an undefined decision right.
Also hold back tasks that are poorly defined. If your team still disagrees about the process for priority tracking, adding a remote hire will not resolve the ambiguity. Document the decision first, then delegate the stable part.
Turn follow-up into one visible action system
Task delegation lens: A good week means the executive walks into meetings prepared, does not rediscover the same follow-up twice, and can trust that calendar and inbox rules were applied consistently. Fewer preventable interruptions are a better signal than the number of emails processed.
For this delegation article, review calendar errors, follow-up completion, meeting readiness, and repeated re-triage. Those signals show whether the workflow is becoming easier to trust, not merely busier.
Hand over one executive workflow at a time
For executive work, start with real examples from executive research, inbox triage, and priority tracking. In that executive workflow, show what a finished item looks like, which fields or records must be updated, and what counts as an exception. If the role uses Calendly or Slack, demonstrate the exact workflow instead of assuming familiarity with the tool name means the candidate knows your process.
For priority tracking, do the first example together, let the Virtual Assistant do the second while you observe, then review the third from the finished output. This keeps training tied to actual work. It also shows where your documentation is missing context.
Define what happens outside the Philippine coverage window
Set the coverage model before live work is handed over. Define the live overlap in Philippine Time and the executive's local time, especially if mornings, board meetings, or travel days matter. State whether after-hours messages are informational or require action, which holiday calendar applies, and how the assistant should hand off anything that arrives outside the agreed coverage window.
For task delegation, keep executive commitments, sensitive people decisions, compensation, legal or investor matters, and anything the leader has not delegated with the person who has authority to make that decision. Write the escalation path before the first live handoff so exceptions do not depend on guesswork.
Add authority only after the assistant earns trust
If the first handoff is meeting preparation, add responsibility when the existing queue is stable and the Virtual Assistant has shown good judgment with exceptions. Expand one workflow at a time. If you add document preparation plus several unrelated responsibilities at once, you will not know which training gap caused a problem.
When stakeholder follow-up enters the weekly queue, the aim is not to make the task list as long as possible. For document preparation, it is to build a role where one person can own a meaningful set of related outcomes.
Check that the task list supports one executive operating rhythm
Delegation review: Review one busy day from the executive's calendar and inbox. You should be able to identify what the VA resolved, what was held for the executive, what changed, and why.
If the executive support review exposes missing ownership, weak evidence, or repeated rework, fix that workflow before adding more delegated scope.
Frequently asked questions
Which executive tasks should I delegate first?
For stakeholder follow-up, start with tasks that repeat, are easy to verify, and do not require a manager to make a fresh judgment every time. For this executive Virtual Assistant role, complex calendar management, inbox triage, and meeting preparation are sensible examples when they match your workflow. For executive research, give the Virtual Assistant a completed example, a deadline, and an exception rule before adding more responsibilities.
Should I separate daily, weekly, and monthly tasks?
Yes. Frequency changes the way the role should be managed. Daily work may need live visibility and tighter response windows. Weekly work can often be batched. For priority tracking, monthly work needs a calendar trigger so it is not forgotten. When stakeholder follow-up enters the weekly queue, sorting the task list by frequency also reveals whether you have enough coherent work for the hours you plan to hire.
How do I write an SOP for executive tasks?
Keep the first version short. Before handing off executive research, write the trigger, input, expected output, deadline, source of truth, and exception rule. Add one good example and one common edge case. When inbox triage enters the weekly queue, after the Virtual Assistant performs the task a few times, update the SOP with the questions that actually came up. If the first handoff is meeting preparation, a working checklist that gets revised is more useful than a long manual written before the role begins.
What KPIs should I use for delegated tasks?
When travel research and stakeholder follow-up share the same handoff, measure the result of the workflow: completion rate, accuracy, rework, turnaround, backlog, response time, or the quality of documentation. Choose only metrics the Virtual Assistant can influence. When stakeholder follow-up enters the weekly queue, avoid using keyboard activity or online status as a substitute for output when the job is primarily asynchronous.
How do I verify that an Executive Virtual Assistant candidate can actually do the work?
Use a short, job-related scenario instead of relying on tool names or self-ratings. Give the candidate a calendar with a client escalation, an internal one-on-one, a travel conflict, and a meeting with no agenda. Ask what they would change first and what they would confirm before moving anything. Ask the candidate to explain the source they would check, the steps they would take, the evidence they would leave behind, and the point where they would escalate.
How should I set the schedule for these delegated tasks?
For task delegation, confirm the first-month responsibilities, systems, weekly hours, and required live overlap in Philippine Time and the client's time zone. Decide which holiday calendar applies, what requires real-time coverage, and how work is handed off at the end of the shift. Also document which decisions the Executive Virtual Assistant can make independently and which must be escalated.