The First 30 Days With a VA, Week by Week
There are two ways to spend a VA's first thirty days.
In the first, you hand over tasks as they come up, answer questions when they arrive, and hope the shape of the job emerges from repetition. It feels efficient because nothing gets scheduled and no time gets blocked. Thirty days later you have someone who can do a handful of things under supervision and a nagging sense that this is costing more attention than it's returning.
In the second, you spend the month building an operator. It costs more up front — real hours, on your calendar, in weeks one and two. By day thirty you have a person who owns a defined piece of your operation and runs it without you.
Same thirty days. The difference is entirely in the sequence.
Below is the sequence. It's built for a new VA, and it works just as well as a reset for a relationship that started badly — plenty of executives run this as a month two after a month one that didn't go anywhere.
Before day one
Two to three hours of preparation saves considerably more than that later. Do it before they start, not during week one.
Filter the list. Write out everything you're planning to hand over, then run each line through five moves in order: own, delete, batch, automate, delegate. Delegate is last for a reason. A surprising share of any executive's task list should be deleted outright or handled by a tool, and passing that work to a person makes their first month an exercise in doing things that shouldn't exist.
Whatever survives to delegate is the real job.
Pick the starting five. From what's left, choose three to five recurring tasks for week two. Recurring matters — a task that happens weekly generates five learning cycles in a month, where a one-off generates one.
Set up access, staged. Company email, communication tool, and read access to what they'll need in week one. Not everything, and not on day one. Access expands as the relationship earns it, which is both good security practice and a structure your VA can feel.
Find one example of good. For each of your starting tasks, dig out a real piece of work you approved without edits. This is the single highest-leverage thing on the list, and the one most executives skip because it takes twenty minutes of searching.
Week 1 — Context, not tasks
The instinct is to get them productive immediately. Resist it for four days. A VA who understands the business in week one is worth more in week three than one who started doing tasks on day two.
Day 1: the business, not the role. A real conversation about what the company does, who the customers are, what you're trying to grow this quarter, and where the pressure is. Most VAs are never told any of this, which is why so many of them execute competently in the wrong direction.
Day 2: the people and the patterns. Who's who, who they'll interact with, which relationships are delicate. Then the judgment layer — which client wants bad news by phone, what "urgent" means from each of the people who say it, which invoices always need a nudge. This is the material that stays trapped in an executive's head and causes more failed VA relationships than any skills gap.
Day 3: two small tasks, start to finish. Something completable in an hour with a clear right answer. The purpose isn't output, it's a first pass through your feedback style with low stakes on both sides.
Day 4: shadow something real. Sit them in on a meeting, forward a live thread with commentary, walk them through a decision as you make it. Watching how you think transfers more than any document.
Day 5: their questions, uninterrupted. Block thirty minutes and let them run it. What they ask tells you exactly what didn't land, and it's the cheapest diagnostic you'll get all month.
Time cost this week: one to two hours a day. It's the heaviest week and it front-loads on purpose.
Week 2 — Ownership on a narrow surface
Now hand over the starting five. Not "help me with" — hand them over.
Ownership means the task is theirs, including remembering it exists. If you're still initiating it, they don't own it. Say that explicitly, because a lot of VAs have been trained by previous clients to wait for a prompt.
Define done for each one. What a finished output includes, what standard it has to clear, and the example you dug out before day one. Three parts, and the third does most of the work.
Draw the decision line. For each task, what they decide alone and what comes to you first. Ambiguity here is what produces both of the classic complaints — someone who asks about everything and someone who goes too far — and it's one conversation to prevent.
Same-day feedback, all week. Fast and specific, on the day. A correction that arrives Friday on a task performed daily has already been practised four more times the wrong way. Move the feedback and the learning curve steepens sharply.
Time cost this week: thirty to sixty minutes a day, mostly feedback.
Week 3 — Widen, and build the reporting
By now the starting five should be steadying. Expect rough edges; don't expect polish.
Add two or three tasks, chosen to sit adjacent to what they already own. Adjacent work compounds — someone who owns your calendar can take meeting prep with almost no additional context, where an unrelated task starts the learning curve over.
Start the written update. This is the week the reporting rhythm begins, and it's the thing that changes how the relationship feels for you more than anything else in the month. Have them send a weekly update built around what an executive needs to read:
- A thirty-second snapshot — what moved, what mattered, what you need from them
- What got done, and what it produced
- The numbers, week over week
- What's in motion but not finished
- What needs a decision only you can make
- Where they're focused next
Once that lands every Friday, the question "what did they even do this week" stops being a feeling and becomes a document. Executives consistently underrate this until they have it.
Have them start writing things down. As corrections come in, your VA records them — a running notes file per recurring task. The person receiving the feedback should be the one documenting it, partly because writing it is how it sticks, and partly because you'll never keep it up yourself.
Time cost this week: two to three hours total, across the week.
Week 4 — Rhythm, then review
Lock the operating cadence. A standing weekly check-in on the calendar, twenty minutes, same slot, that happens whether or not there's a problem. Problem-triggered communication trains everyone to associate contact with something being wrong, and it disappears in exactly the busy weeks where it matters most.
Run a real thirty-day review. Not a vibe check. Go through each owned task: what's solid, what's inconsistent, what still needs you. Ask what's unclear, what they're waiting on you for, and what they think they could take on next. That last question is where you find out whether you hired a task-doer or a partner — and the answer often depends more on how the month was structured than on the person.
Expand access in line with what's been earned, and say that's what you're doing. It reads as trust, because it is.
Time cost this week: an hour or two total, plus the review.
What day thirty should look like
Concrete markers, so you're not guessing:
- Your VA independently owns three to five recurring responsibilities, including remembering to do them
- A weekly written update arrives without being requested
- There's at least one documented process in their words, not yours
- Questions have shifted from how do I do this to should we do it this way
- You're spending under an hour a week on supervision
- You could take a week off and the owned work would keep moving
Hit most of those and you have an operator, and the next thirty days are about widening scope rather than establishing basics.
Miss most of them and the thing to examine is the month, not the person. The commonest cause by a distance is a week one that got skipped in the interest of getting productive faster — which is also why the second month of a bad start usually works, once someone goes back and does the context transfer that never happened.
The uncomfortable part
This month costs you roughly fifteen to twenty hours, most of it in the first fortnight, at a point where you hired someone specifically because you don't have fifteen to twenty hours.
That's the actual reason it gets skipped, and it's worth naming rather than pretending otherwise. The trade is real: a month of concentrated attention in exchange for a year of a person who doesn't need it. Executives who won't make that trade tend to spend the same hours anyway, distributed across twelve months of corrections, re-explanations, and eventually another search.
The 30 days, run for you
Vamped installs this as a five-day intensive — the filtered scope, the context transfer, the definitions, the reporting cadence — and then coaches the relationship while it beds in. Same structure as above, without the fifteen hours of your calendar and without discovering the gaps by hitting them.
Not starting fresh? If your VA is already in place and struggling, run the VA Scorecard first — it'll tell you which parts of the above are missing before you rebuild all of it.