Most VA hires fail at the handoff, not the hire. The 30-day ramp, the order to give tasks in, and what to write down before day one.
The pattern repeats across DTC brands with unnerving consistency. You hire a Shopify VA, spend two weeks answering questions you thought you had already answered, redo half their work yourself, and quietly conclude that virtual assistants do not work for your store.
The hire was almost certainly fine. What went wrong is the handoff: you gave a competent stranger a set of tasks that only exist properly in your head, and no amount of competence compensates for that. This is a documentation problem wearing a hiring problem's clothes.
Here is the version that works: what to write down before they start, the order to hand tasks over in, a 30-day ramp, and the month-three failure that catches almost everyone.
Run one test on any task you are about to delegate. Could a competent person who has never seen your store do it correctly from what is currently written down? If the answer is no, you have not delegated the task. You have created a dependency on yourself that now also costs you a salary.
Three things make this worse in a DTC context specifically:
That last one is where most training material stops, which is why most training material fails.
Not your whole operation. Three tasks, the ones you plan to hand over first. Each one needs four parts, and the third is the one everybody skips.
What starts this task, stated precisely enough to be noticed. Not 'handle refund requests' but 'a Gorgias ticket is tagged refund-request, or a customer email contains the word refund and has an order attached.' A VA cannot act on a trigger they cannot recognize.
Click by click, in the tools you actually use, with a screenshot of each screen. Written steps alone assume the reader already knows where things are. They do not, and asking them to find out is how a 20-minute task becomes a 20-minute task plus four questions.
This is the part that separates a document someone can work from and a document that generates questions. Every judgment you make without thinking has to become an explicit rule with a number in it.
Without rules like these, a VA does one of two things: asks you about everything, which is not delegation, or guesses, which is worse. Give the thresholds and you get consistent decisions from someone who has never met your customers.
One sentence naming who to ask, on which channel, and how long to wait before proceeding. 'If unsure, message me on Slack and wait' is incomplete without the last part. Say what happens if you are asleep, because for most offshore arrangements you will be.
Rate the tasks your store runs weekly and see which ones nobody else could pick up. That list is the documentation order for the handoff.
The instinct is to delegate the task you hate most. Resist it, because the task you hate most is usually the one with the most judgment in it, and judgment is the last thing to hand over, not the first.
Hand tasks over in this order:
A brand doing 300 orders a week can usually move through the first two tiers inside a month. The third takes a quarter, and some brands never hand it over, which is a legitimate choice rather than a failure.
Record yourself doing each of the three tasks end to end, narrating the decisions as you go, and send the recordings before their first shift. Then they do the same tasks and you review every single one. Expect corrections. The point of week one is not output, it is finding the gaps in your own documentation, which will be more numerous than you expect.
Keep a running list of every question they ask. That list is the missing content in your SOPs, and it is the most valuable artifact of the first week.
Stop reviewing everything and start sampling around one in five. Add a fourth task from tier one or two. If week one produced fifteen questions and week two produces two, the documentation is working. If week two produces fifteen again, stop adding tasks and fix the documents.
Hand over one tier-three task in draft-and-approve mode. You are reading their reasoning, not just their output. When you disagree with a call, explain the reasoning rather than correcting the text, and add the rule you just articulated to the document. Most of your decision rules get written in week three, not week zero.
No review on the first tasks, weekly sampling instead. Judgment work stays in draft mode. By the end of the month you should be able to name exactly which tasks you no longer think about, and that number, not hours worked, is what you bought.
Handing over ten tasks in week one because the VA seems capable. They are, individually. But ten undocumented tasks at once means ten sets of questions arriving in parallel, which is more management overhead than doing the work yourself, which is how brands conclude that VAs do not work.
Time tracking and activity screenshots measure the wrong thing and poison the relationship. What you want is a small number of outcome checks per task.
The recording point generalizes. When the way a task gets done drifts from the way it was documented, watching a real run beats rereading the document, and it doubles as the raw material for the update.
The failure almost nobody plans for arrives around week ten, and it does not look like a training problem. It looks like a VA who was doing fine and has started making mistakes.
What actually happened is that the store moved and the documentation did not. Klaviyo redesigned the flow builder, so the screenshots are wrong. You changed the refund window in Slack and never updated the SOP. You switched 3PLs and the receiving steps are different now. The VA is following the document exactly, which is what you asked for, and getting it wrong, which is not their fault.
That gap is drift, and remote teams feel it before anyone else does, because a person in the room notices the button moved while a person following a document does not. Two habits contain it: when the VA hits something the document does not cover, they log it rather than improvising silently, and once a quarter they re-record a task end to end so the two of you can compare the current run against what the SOP claims.
The six signals that a procedure has stopped matching reality, and the 20-minute monthly check that catches them before your VA does.
This is the problem ReccordSOP is built for: record the task once and it becomes a step-by-step SOP with screenshots your VA can follow, and when the process changes, re-recording it shows exactly which steps moved. For a remote handoff that is the difference between documentation that ages well and documentation that quietly turns into misinformation.
Ready-made procedures for Klaviyo, Gorgias, Recharge, ShipBob and the rest, plus the cross-tool ones. Copy them as a starting point for the handoff pack.
Documentation fixes most VA problems, not all of them. Three signals point at the person rather than the process, and it is worth naming them honestly so you do not spend a quarter rewriting documents for someone who will not follow them:
Everything else is almost always fixable by writing the thing down properly. Before you conclude that a VA cannot do the job, reread what you gave them and ask whether you could do the task from that document alone, in a different timezone, without being able to ask a question.
Once the first three procedures exist, this is how the rest of the library gets built without stalling in week two.
Start with only the three tasks you plan to hand over first, not your whole operation. For each one, document four things: the trigger that starts it, the click-by-click steps with a screenshot of every screen, the decision rules with actual numbers in them (refunds under $75 go through, over $75 get drafted for approval), and who to ask when something is unclear. Screen recording each task while narrating your decisions is the fastest way to produce this, because it captures the judgment calls you would forget to write down.
Roughly 30 days to full independence on routine work, and about a quarter before handing over judgment work like escalations and policy exceptions. The realistic week-one experience is that you spend more time than the task would have taken you, because week one is really about finding the gaps in your documentation. That investment is what buys the following eleven months.
High frequency, low stakes, and reversible: order tagging, tracking-number replies, review requests, inventory note updates. Then move to medium-stakes work that has a clear rule attached, such as standard refunds under a set threshold. Save escalations, angry customers, and policy exceptions for last. The common mistake is delegating the task you hate most first, which is usually the one requiring the most judgment.
In stages, and the last stage is not documentation, it is decision authority. Written procedures get someone to competent execution. Running the store without you also requires explicit spending and policy limits (what they can approve alone, what needs you), a named escalation path for the situations no procedure covers, and a review cadence where you check outcomes rather than activity. Most brands reach independent routine operations and deliberately keep judgment work, which is a reasonable end state rather than a failure.
Usually the store changed and the documentation did not. A tool shipped a redesign so the screenshots no longer match, a policy shifted in a Slack thread that never reached the SOP, or you switched fulfillment partners. The VA is following the document exactly and getting it wrong. Remote workers hit this before in-house staff do, because someone in the room notices the button moved and someone following a document does not. Re-record the task and compare it against what the procedure claims.
I built ReccordSOP after watching too many DTC ops teams lose months to undocumented workflows. These SOPs are battle-tested with Shopify operators running $1M to $50M brands.
Last reviewed August 8, 2026
A new agent's first month sets their ceiling. A documented onboarding is how you raise it.
Most SOP projects don't fail because the docs are bad. They fail because nobody follows them and nobody updates them.
Most SOPs are wrong within 90 days of publishing. Here's how to detect it before it costs you a customer.
We use essential cookies for sign-in and a small amount of analytics to improve the product. Privacy policy.