Module 5: Managing Async
You don't manage a VA by watching them — you manage by rhythm. This module sets up the async operating system: when you talk, what "done" means, and how to end it well when it's not working. Done right, managing your VA costs you ninety minutes a week. Done wrong, it costs you the whole point of hiring.
Communication rhythms
Async management runs on three channels and nothing else. Channel one is for tasks: a project board or a shared document where work is assigned, tracked, and marked done. Channel two is for quick questions: a messaging thread where either of you can ask something small and expect an answer within one business day. Channel three is one weekly fifteen-minute call — same day, same time — for anything that needs a real conversation. Everything else is async.
Set response-time expectations up front, in writing. "I reply within one business day; you reply within one business day; urgent means a call, and urgent is rare." Without this, both sides guess. The VA waits nervously on every message; you wonder why a simple question sat unanswered for two days. The fix is boring: say the number out loud on day one and put it in the operating agreement.
Here is the mindset shift: "no news is good news" fails in async work. Silence from your VA does not read as smooth progress — it reads as stuck. That is why the standup exists (next lesson), and why you reply to it every day even when there is nothing wrong. One short reply — "looks good, keep going" — costs you ten seconds and buys them confidence. Rhythm replaces watching. You do not need to see them work; you need to see the work move.
Hours spent managing per week
Build brief
What are your actual working hours, and what response time will you promise your VA?
Saved
The async standup
The async standup is three lines, posted at the start of your VA's workday. Line one: what I finished yesterday. Line two: what I am doing today. Line three: where I am stuck. It takes five minutes to write and replaces an hour of meetings a week — there is no scheduling, no small talk, no screen-sharing to watch someone type.
The format only works if the lines are specific. A good standup reads: "Finished: archived 40 newsletter emails, flagged 6 client emails, sent the invoice summary to the bookkeeper. Today: scheduling this week's social posts, researching three podcast guests. Stuck: the booking tool asks for your calendar password — can you approve the invite so I can proceed?" A useless standup reads: "Working on emails. Doing social stuff today. All good." The first one lets you manage in one reply; the second one tells you nothing and hides the stuck.
Your job is to reply once, every day. Confirm, redirect, or unblock — that is the whole menu. "Flagged emails look right, keep going. For the podcast guests: prioritize anyone with an audience over ten thousand. Calendar invite approved — check your vault." If a line is vague, ask for specifics that same day: vague lines compound into vague weeks. Five minutes from them, two minutes from you, and the whole week stays visible without a single extra meeting.
Specific beats vague
A standup that works vs. one that hides
| Line | Specific — you can manage it | Vague — it hides the stuck |
|---|---|---|
| Finished | Archived 40 newsletters, flagged 6 client emails | Working on emails |
| Doing | Scheduling social posts, researching 3 podcast guests | Doing social stuff today |
| Stuck | Booking tool needs your calendar password — approve the invite? | All good |
Build brief
Write your 3-line standup format — what exactly goes on each line for YOUR tasks?
Saved
When to let go
The thirty-day trial is a decision date, not a formality. State it on day one: "We work together for thirty days, then we both decide." At day thirty, score four things from one to five: reliability (do they do what they said, when they said it?), quality (is the work right the first time?), communication (do you hear from them before small things become big?), and initiative (do they solve problems or only follow instructions?).
Reliability is the foundation everything else stands on. A VA who scores two on reliability but four on quality is not a near-miss — they are a bad fit. Missed deadlines cost you the exact hours you hired to buy back, plus the management time spent chasing. If reliability is below three at day thirty, let go kindly and fast: one short call, thank them honestly, pay through the week, and revoke access the same day. Kindness is speed here. Dragging it out for another month is not compassion — it is avoidance that costs both of you.
You can end it without burning bridges. People remember how exits felt: pay promptly, speak specifically about what you appreciated, and keep the door open for a different role or a referral. And remember the math: keeping a bad fit costs more than rehiring. A second search takes two weeks; a bad VA drains you for six months. Set the trial terms in writing on day one so day thirty is a review of the agreement, not an awkward surprise.
Do the math
A bad fit costs more than rehiring
Build brief
What's your minimum reliability score at day 30 — and will you honor it if the person is likable?
Saved
Day 30 scorecard: reliability 2, quality 4, communication 3, initiative 2. Your VA is nice and tries hard. Keep or let go?
Your turn: Draft your operating agreement — channels, response times, standup format, weekly call time, and 30-day trial terms. Keep it to one page.
Saved.
Your next 24 hours
Set up your two channels (tasks and quick questions) and write your response-time expectations in one short document. Pick your weekly call day and time — put it on both calendars.
Steal this template
Module 5 cheat sheet
- Three channels only: task board, messaging for quick questions, one weekly 15-minute call.
- Set response-time expectations in writing on day one — one business day is the standard.
- The daily standup is three lines: finished yesterday, doing today, where I'm stuck.
- Reply to every standup once: confirm, redirect, or unblock — specific lines only.
- Day 30 is a decision date: score reliability, quality, communication, initiative 1–5.
- Below 3 on reliability: one short call, pay through the week, revoke access same day.