The Goldilocks Problem of VA Communication
Business owners tend to fall into one of two communication failure modes with their virtual assistants. The first is under-communication: send a task list on Monday, check results on Friday, and wonder why the output missed the mark. The second is over-communication: constant check-ins, real-time Slack pings, and task-by-task approval requests that make the VA's role feel more like supervised clerical work than professional assistance.
A 2023 Microsoft Work Trend Index report found that over-communication in remote teams accounts for up to 57% of notification-driven interruptions, with the average remote worker experiencing 250+ interruptions per day. For VAs who need focused time to complete research, writing, or data tasks, constant contact is a productivity tax.
The goal is a communication structure that provides enough visibility to maintain quality while giving your VA the autonomy to do their best work.
Match Communication Frequency to Task Type
Not all VA work requires the same check-in cadence. A useful framework:
High-stakes, low-repeatability tasks (first-time projects, client-facing deliverables, complex research): Check in at brief, midpoint, and delivery. Three touchpoints keeps you informed without micromanaging.
Recurring, well-defined tasks (weekly reports, inbox management, social scheduling): One brief at setup, then delivery confirmation. After the VA demonstrates mastery, a simple async confirmation ("done, here's the link") is sufficient.
Exploratory tasks (brainstorming, market research, vendor sourcing): One brief, then a midpoint check-in to course-correct direction before effort is wasted on the wrong track.
The Non-Negotiables: What Must Happen Regularly
Regardless of task type, three communication practices are non-negotiable for a healthy VA relationship:
1. A weekly written status note. Either you send one to your VA at the start of the week, or your VA sends one to you at the end of the week. This note covers: what was completed, what is in progress, what is blocked, and what is queued. This prevents invisible bottlenecks from compounding.
2. A monthly 20-minute check-in call. Even the most efficient async relationship benefits from a periodic human conversation. Use this for: big-picture direction updates, workload calibration, feedback that does not fit in a written comment, and relationship maintenance.
3. A clear response-time agreement. Define expected response times for different communication types. Example: Slack messages within 4 hours during working hours. Email briefs within 24 hours. Emergency tasks (flagged as URGENT) within 2 hours. Without a defined SLA, both parties develop different expectations and both feel let down.
Async-First, Sync When Necessary
The default communication mode for VA relationships should be asynchronous. Async communication respects timezone differences, allows non-native speakers to process and respond thoughtfully, and creates a written record that both parties can reference.
According to GitLab's 2022 "Remote Work Report," teams that adopt async-first communication norms are 25% more productive per capita than those that default to synchronous communication.
Move to synchronous only when: the issue is too complex to resolve in writing within one exchange, there is a misunderstanding that needs real-time clarification, or a sensitive conversation requires a human tone that text cannot carry.
When Communication Frequency Reveals a Process Problem
If you find yourself checking in more than planned — because outputs are wrong, tasks are missed, or you are unsure of progress — the problem is usually not your VA's communication. It is an unclear process.
Signs that frequency increases are a process symptom:
- You are checking in mid-task to "see how it is going" because the brief was vague
- Your VA is asking the same clarifying questions repeatedly
- You are uncomfortable letting a task run to completion without confirmation
In these cases, step back and fix the brief, the workflow documentation, or the task scope rather than adding more touchpoints.
Building the Communication Agreement
During onboarding, formalize your communication preferences in writing. A one-page document covering: preferred channels, expected response times, check-in cadence, and escalation path for blockers. Share it on Day 1 and revisit it at the 90-day mark.
This agreement saves both parties from guessing what the other expects and eliminates one of the most common sources of VA friction before it starts.
For business owners who want a VA experienced in async-first, structured communication from day one, Stealth Agents provides pre-vetted candidates trained in professional remote communication standards.
Sources
- Microsoft, "Work Trend Index Annual Report 2023," microsoft.com/en-us/worklab
- GitLab, "Remote Work Report 2022," about.gitlab.com/remote-work-report
- Asana, "Anatomy of Work Global Index 2023," asana.com
- Society for Human Resource Management, "Managing Remote Workers: Communication Best Practices" (2022), shrm.org