Why Didn't Your VA Stick, and What Was Missing?
Most often because the job arrived as a list of tasks while every judgment call stayed with you. When the first result came back messy, you redid it yourself, and the VA learned to wait for you instead of deciding. Fix the brief before you replace the person, because the next hire would walk into the same gap.
You hired a VA. You felt relief for about three weeks. Then you were back in the inbox, rewriting their emails, and telling yourself the hire was the wrong person.
I hear that story more than any other when owners talk about why help "didn't stick." The VA is usually not the failure. The handoff is. You gave them a task list with no outcome, no decisions they were allowed to make alone, and no review rhythm. The first time something came back messy, you took the work back. That taught both of you the same lesson: this role is temporary.
What was the handoff missing?
Most owners hand over activity. "Clear the inbox." "Update the CRM." "Book my calls." Those look like instructions. They are not ownership. Ownership needs three pieces that almost never show up in the first week.
- One outcome sentence.
- Three decisions they can make without asking you, with a dollar limit attached.
- A short, fixed review so the work does not live or die on your mood.
An owner of a roughly $2M service firm hired a VA to "free up my time." That was the whole brief. In month one she pulled about six hours a week off his plate: calendar, follow-ups, vendor chasing. In month two a client email went out with the wrong tone. He rewrote it himself at 9:40 that night, then started handling similar emails again "just until she gets it." By week six he was doing the six hours again, plus managing her. He let her go at week eight and told me she wasn't proactive enough.
She could not be proactive. He never told her what "free up my time" meant in numbers, what she could decide under $200, or when he would look at her work. He only looked when something broke.
The same pattern shows up with EAs, office managers, and "operations support" hires. The title changes. The missing pieces do not. If you assign tasks and keep every judgment call, you did not hire help. You hired a slower version of your own hands, with a weekly invoice attached.
How does a VA role fall apart?
Here is the sequence I keep seeing. Owner dumps a list. VA asks clarifying questions. Owner answers two of them and says "use your judgment" for the rest. VA uses judgment. Owner disagrees with one call. Owner redoes the work. VA learns to ask before every call. Owner experiences that as neediness. Role collapses.
The counterintuitive part: the VA who asks the most questions is often responding correctly to a vague handoff. The quiet one who guesses is the one who will eventually send the email that makes you reclaim everything.
If you redo their work, write down why. Not in your head. On a note you keep for the Friday review. "Wrong tone for this client" is useful. "I would have phrased it differently" is taste, and taste is not a firing offense.
I had an owner track redos for 21 days. He logged 19. Eleven were preference. Five were missing context he had never written down. Three were real standards. He had been treating all 19 like character flaws in the hire.
How do you hand off work to a VA so it sticks?
Write one outcome sentence before you assign anything. Make it measurable enough that both of you can tell if the week worked. If you cannot write the sentence, you are not ready to hire for the seat. You are still designing the seat.
A role scorecard is one way to finish designing that seat before you hire for it.
Examples that work in a 5+ person firm:
- Outcome: Keep my weekday calendar free of anything under 30 minutes that someone else can handle, and get me a written brief by 4pm the day before any meeting I must take.
- Outcome: Every inbound lead under $5,000 gets a same-day reply and a booked next step within 48 hours, without me touching the thread unless the lead asks for the owner.
- Outcome: Vendor and admin noise under $200 never reaches my phone. I see a Friday list of what you handled, not a stream of pings.
Then list three decisions they own alone. Put a dollar ceiling on money decisions. Under $200 is a starting point for most office work. Raise it once they have a clean month. Categories matter as much as the number. "Under $200" for supplies is not the same as "under $200" for software renewals or client credits.
- Decide alone: Reply to vendor requests under $200 using our standard payment terms.
- Decide alone: Move or decline calendar requests that conflict with my deep-work blocks.
- Decide alone: Escalate a client complaint to me only if it involves a refund over $200, a legal threat, or a named account over $50k a year.
Add the review. Fifteen minutes on Friday. Same time every week. They bring: what they owned, what they decided, what they redid or almost redid, and one question. You bring your redo notes. Skip the review and the role drifts within a month.
A decision map for the first messy email helps more than another pep talk:
- If the issue is preference, leave their version and add one line to the standards doc.
- If the issue is a missing standard, write the standard, then have them send the fix.
- If the issue is over the dollar or risk line you set, you take it, and you update the decision list so the next one does not land wrong.
That map keeps you from the default move, which is reclaiming the whole inbox because one message stung.
What went wrong when an owner tried this?
I worked with an owner through this exact setup. He wrote the outcome. He listed the three decisions. He put Friday at 3:30 on both calendars. Week one was clean. Week two a $180 software renewal hit. The VA approved it under the dollar rule. The owner had meant "under $200 for office supplies," not software. He never wrote that. He reversed the charge, chewed her out in Slack, and spent the weekend rebuilding his own filter rules.
We fixed it by rewriting the decision list with categories, not just a number: supplies and shipping under $200, software only after a one-line note to him, client credits never. The Friday review that week was awkward. He apologized for the Slack message. She admitted she had started waiting on every small call again. It took another three weeks before the six hours stayed off his plate for a full month.
The lesson was not "hire better." It was that a dollar limit without categories is still a trap, and a public redo in Slack teaches fear faster than a private Friday note teaches judgment.
Another owner tried the Friday review and turned it into a 45-minute status dump. She asked about every email, including the tone on a vendor reply the VA had already sent. The VA stopped deciding midweek and saved questions for Friday. We cut the meeting back to 15 minutes with a hard rule: if it can wait for Friday, it waits; if it cannot, send a one-line recommendation, not a question. Volume of pings dropped from roughly 12 a day to 3 within two weeks.
When should you skip a VA handoff?
Skip the VA handoff if the role is judgment-heavy and you cannot yet describe the outcome in one sentence. Define the role first. "Help with marketing" is not a role. "Own inbound lead response under $5k" is.
Skip it if you will not protect the Friday review for the next four weeks. A handoff with no review is how you get back to doing the work in silence and blaming the person.
If preference edits still eat your evenings, fix that habit before you post another job. One owner corrected "please find attached" to "attached" on three emails in a row, then wondered why the new hire stopped drafting. You will burn another person teaching them that their draft is only a draft for you.
If someone on your team already has the judgment and you have been using them as a task dump, try this handoff with them before you post a new job. You may already have the person. What you don't have is a real seat.
Do not use this model for a role that is mostly craft you sell as the expert. Hand off the admin around the craft. Keep the craft until you have a different problem to solve.
When the seat to hand off isn't admin, from operator to owner covers which one to pick first.
What can you change this week?
Pick one person who already touches your calendar or inbox.
- Write one outcome sentence.
- Write three decisions with a dollar limit and a category.
- Book a 15-minute Friday.
- For two weeks, if you redo their work, write why before you hit send.
If the notes say "preference" more than "standard," the problem is still the handoff. The person was never the whole story.
How early to start handing work over at all is the question behind when to delegate in your business.
Frequently asked questions
What should a VA own first?
Start with work that has a clear finish line and a low cost when it goes wrong, like calendar requests or vendor follow-up. Leave client-facing writing until the standards doc has a few real entries. Inbox ownership comes later, once your redo notes say standard more often than preference.
What if my VA keeps asking questions?
Group them by type at the Friday review, turn each repeated type into a decision rule or a line in the standards doc, and ask for a recommendation with every new question. The count should fall as the rules fill in.
Can a VA in a distant time zone own real decisions?
Yes, if the decisions are written down. A gap in working hours makes vague handoffs fail faster, because every question waits overnight. Write the decision rules before the first shift, keep the Friday review at a time that suits you both, and let them act inside the limits without waiting for your morning.
Which part of your inbox could someone else own?
If you want help turning that handoff into a role that sticks, start here: systemstoscalegroup.com/getstarted
