You hired a VA to help move the work forward, but your day still fills with questions. Can this reply be sent? Which version should be used? Is it okay to move the meeting? The task list is delegated, yet the decisions are still waiting on you.
That does not automatically mean the VA needs to be replaced. The work may be missing a clear approval process. Before adding more tasks, look at which questions repeat and what information would let someone handle them confidently.
Find the decisions that keep returning
Keep a short record of questions for a normal working week. Group them by type: routine action, missing information, business judgment or exception to a rule.
If the same question appears several times, identify what is absent. A VA asking which logo to use may need a clear approved asset library. A VA asking whether to promise a delivery date may correctly be protecting a decision they cannot make.
The aim is to reduce avoidable questions while preserving useful judgment. Do not respond to every interruption by telling someone to use their initiative.
Use three clear levels of authority
For each repeated task, agree one of these arrangements:
Act within the rule: complete routine work that meets the documented conditions.
Prepare a recommendation: gather the facts and propose an option for the owner to choose.
Get approval first: wait before making a commitment, publishing sensitive material or changing an agreed scope.
These are practical categories for your own process. Match them to the person's training, access and agreed role. Do not assume a job title defines authority.
Write boundaries using real situations
An illustrative inbox rule might allow a VA to send approved answers about where a resource is located. A request for a discount or an exception to the service terms goes to the owner.
An illustrative calendar rule might allow routine bookings in designated hours but require approval before moving a protected workshop preparation block.
Include a few examples of situations outside the rule. “Ask if unsure” is still useful, but it works better when the person has a clear starting point. See our inbox handover and calendar management guide for more detailed examples.
Give decision requests a useful format
Ask for the context, the decision needed, relevant options and the impact of waiting. If the VA has enough information to make a recommendation, include it.
An illustrative request could say: “The client supplied a new image after the newsletter was approved. We can keep the approved image or replace it and send a new proof. I recommend a new proof because the caption refers to the old image. Please choose by 2 pm so the scheduled send can stay on track.”
This gives the owner a decision to make. It avoids a message that simply says “What should I do?” and leaves all the investigation for later.
Set a review rhythm the owner can maintain
Batch routine approvals into an agreed review time where possible. Use a separate route for issues that genuinely cannot wait, and define what qualifies as urgent.
The owner needs to hold up their side of the process. If approval requests sit unanswered, agree whether the work pauses, moves to a later date or proceeds under a previously approved rule. Do not leave the VA to assume silence is permission.
A regular operations review can resolve broader priorities, while the daily approval queue handles specific assets or replies.
Approve the actual result
Make it clear what is being approved: the final email proof, the proposed reply, the page link or a particular version of a document. A discussion about an idea is not necessarily approval of the final asset.
Record the approval where the work is managed. If the content changes materially afterwards, identify what needs another review. This keeps the person executing the task from guessing which conversation was the final instruction.
Use simple statuses that distinguish prepared, approved, scheduled and completed. Those stages help everyone see what remains to happen.
Expand authority using evidence
After several successful examples, review whether a task can move from approval first to action within a rule. Check the person's understanding, the exception rate and the consequences of a mistake.
Start with a manageable scope. Let the VA handle a defined group of routine requests before expanding to a more complex workflow. Update the SOP when the rules change.
Retain decisions that require the owner's authority. Effective delegation does not mean removing every review; it means applying review where it helps.
Use the next question to improve the system
When a question returns, ask whether the rule, source material or authority needs clarification. A good question can reveal a gap before it causes a problem.
If you are beginning the relationship, our VA onboarding checklist can help establish these expectations from the start.
VAmazing supports practical coordination, documentation and business systems. Get in touch if your delegation needs clearer decision boundaries so the work can move with fewer interruptions.