Updated May 23, 2026
Key Takeaways
- Expectations that exist only in your head are not expectations - they need to be written down and confirmed by the VA before work begins.
- The four areas that cause the most friction if undefined: turnaround times, quality standards, communication norms, and scope of authority.
- A written expectations document reviewed and signed off in Week 1 prevents the majority of performance disputes in the following months.
- Expectations should be revisited every 90 days as the role evolves - static expectations on a growing role create silent gaps.
- Stealth Agents full-time dedicated VAs start at $10/hr - they operate professionally, but your specific standards still need to be made explicit.
Most VA relationships that underperform do not fail because the VA lacks skill. They fail because the business owner expected something specific that was never communicated, and the VA delivered something reasonable but different.
Expectations that live in your head are not set. Setting expectations means writing them down, communicating them clearly, and confirming the VA understands them before the work begins.
Here is how to do it systematically.
The Four Areas That Always Need Explicit Expectations
1. Turnaround Times
Define how quickly you expect different categories of tasks to be completed. Not everything is urgent, and treating everything as urgent burns out VAs and trains them to rush at the expense of quality.
A simple framework:
- Same-day (within 4 hours): Time-sensitive client communications, urgent meeting bookings, anything with an external deadline today
- Next-day: Most recurring tasks, email drafts for review, research summaries, reports
- This week: Projects, batch tasks, anything without an external deadline
Write these down and share them. Ask the VA to confirm they understand. Revisit if you find the same-day category becoming a catch-all.
2. Quality Standards
Define what "done correctly" looks like for each major task type. This is harder than turnaround times because quality is context-dependent, but it is more important.
For written output (emails, reports, summaries): Specify the expected length, tone, and format. Share examples of past work that represents the standard. Explicitly note what you do not want - overly formal language, bullet points where paragraphs belong, vague summaries that do not include specific data.
For recurring operational tasks (data entry, CRM updates, scheduling): Define the accuracy standard and the checking process. If a CRM entry has three wrong fields, is that acceptable or a redo? State this clearly.
For research tasks: Define what a usable output looks like. A one-page summary with source links? A spreadsheet of competitors with five data points each? "Research X topic" without a format spec produces a wide range of outputs, only some of which are useful.
3. Communication Norms
Define how and when the VA should communicate with you, and when you will communicate with them:
- Primary channel: Where does task-related communication live? (Slack, WhatsApp, email, project management tool)
- Response time expectation during work hours: If you send a message at 10 AM, when do you expect a reply?
- End-of-day update: Do you want a daily summary of what was completed and what is pending?
- When to escalate vs. use judgment: What types of decisions can the VA make independently? What requires your sign-off?
The escalation question is often skipped and always important. A VA who escalates everything slows you down. A VA who exercises judgment on things outside their authority creates problems. Define the line.
4. Scope and Boundaries
What is in scope for the role and what is not? This matters more than people expect. If a VA is hired for executive support but starts getting pulled into customer service, the quality of the original role suffers without anyone making a deliberate decision about it.
State clearly:
- The primary task set the VA is accountable for
- Tasks that are explicitly out of scope
- The process for expanding scope (does it require a conversation first, or can you just assign it?)
How to Document and Communicate Expectations
Write a one-to-two page expectations document before the VA's first day. It should cover:
- Role summary (what the VA owns and why it matters)
- Core tasks and their turnaround tiers
- Quality standards with examples
- Communication norms
- Scope and authority
- How performance will be evaluated
Share this document on Day 1. Walk through it together in a short call or video. Ask the VA if anything is unclear. Have them confirm in writing (a reply email or a message saying "understood") that they have read and understood the document.
This is not bureaucracy - it is the foundation of a productive working relationship. Every misalignment you prevent in Week 1 is a correction conversation you avoid in Week 6.
Revisiting Expectations Over Time
Expectations set on Day 1 become stale as the role evolves. A VA hired initially for calendar support may be handling research, vendor coordination, and draft writing six months later. If the expectations document has not been updated, the VA is operating on partial or outdated guidance.
Review and refresh expectations every 90 days. This does not require a long meeting - a short conversation covering "here is what is still accurate, here is what has changed" is enough.
Common signs that expectations need to be updated:
- The VA is consistently doing work that was not in the original scope (either too much or in a different direction)
- Quality issues are appearing on tasks that were previously solid - often a sign that new task types were added without corresponding standards
- The VA is making decisions independently that you would prefer to be involved in (or vice versa)
FAQ
Q: What if my expectations are not fully formed when I hire?
A: That is common, especially for first-time VA hires. Start with what you know - the three to five tasks you most want off your plate - and build expectations around those. Leave room for the expectations document to evolve as you learn what the role actually involves in practice.
Q: Should expectations be in writing or is a verbal conversation enough?
A: In writing. Verbal conversations are interpreted differently by different people, and memories diverge over time. Written expectations are referenceable. When a dispute arises about what was agreed to, "here is the document we reviewed on Day 1" resolves it quickly. Verbal conversations can supplement the written document, but do not replace it.
Q: What if the VA pushes back on an expectation?
A: Listen to the pushback. Sometimes it surfaces a misalignment - for example, if a turnaround expectation is not realistic given the task complexity, it is better to discover that in conversation than after a series of missed deadlines. Adjust where the pushback is reasonable; hold the line where it is not.
Q: How do I handle expectations around availability and time zones?
A: Explicit is better than assumed. State the hours during which you expect the VA to be reachable and responsive. If you need overlap with a specific time zone, state that clearly in the hiring brief and confirm it again in the expectations document. Time zone misalignment is one of the most common sources of frustration in offshore VA relationships.
Setting expectations is not a one-time event - it is the ongoing governance layer of a productive VA relationship. Stealth Agents places dedicated full-time VAs starting at $10/hr. They bring professional habits to the table; your job is to make sure your specific standards are written, shared, and revisited as the role evolves.