Guides
How to manage virtual assistant agency client deliverables
Managing virtual assistant agency client deliverables needs one queue, five task states, a work-in-progress limit, and a written rule for what counts as urgent.
What to take away
- One intake channel per client, with a stated rule for what happens to work that arrives anywhere else. Without it, scope grows invisibly and nobody can be held to a turnaround.
- Five states cover every task. More states produce a board nobody updates.
- Limit work in progress per assistant. An assistant with twelve open items is delivering none of them today.
- Urgency has to be defined by you, in writing, or it will be defined by whoever writes in capital letters.
This page describes an operating system for the work. It states no turnaround times, because those belong in your own agreements.
One queue, one door
Every client gets one channel through which work is accepted. A shared mailbox, a board, a ticket address. Which one matters far less than that there is exactly one.
Then write the rule for everything else: a request that arrives by another route is moved to the channel, acknowledged from the channel, and answered there. Not refused. Moved.
Two things happen. The client learns the route within about a week. And you gain a complete record of what was actually asked for, which is the only evidence you will have when a scope conversation arrives. The terms that record is measured against belong in the agreement, and the shape of that document is in the sales and proposal guide.
Five states, and nothing else
| State | What it means | Who can move it |
|---|---|---|
| Received | Logged, not yet assessed | Anyone |
| Clarifying | Waiting on an answer from the client | Assistant |
| Ready | Understood, estimated, waiting for capacity | Assistant |
| In progress | Being worked on now | Assistant |
| Delivered | Sent, with a note of what was done | Assistant |
Two rules make this work. Nothing sits in Received longer than your acknowledgment standard. And Clarifying is visible to the client, so the wait is attributed correctly rather than read as slowness.
That second rule prevents more complaints than any other single practice in this trade.
Limit work in progress
An assistant with a dozen open items is switching context all day and finishing nothing. Set a maximum number of items in progress per person and hold it.
When the limit is reached, new work goes to Ready and the client is told when it will start. That message is not bad news. It is the difference between an agency and a person who has stopped replying.
The right limit is one you find by watching. Lower it until delivery becomes predictable, then leave it alone.
Define urgent before somebody else does
Write three lines into the working standard.
- What counts as urgent, described by consequence rather than by tone. Something a customer sees, something with a legal or financial deadline, something that blocks the client from working.
- What happens to an urgent item: it moves to the front, and one other item moves back. Say which one, or the assistant is asked to do both.
- Who may declare something urgent. Usually one named person on the client's side.
Without these, urgency is claimed by whoever is most anxious, and your capacity is allocated by volume of exclamation marks.
Deliver with a note
Every delivered item carries two lines: what was done, and anything the client should know. Not a report. Two lines.
This is the cheapest quality control you will ever run, because writing what you did surfaces the thing you skipped. It also builds the record that makes month-end reporting a compilation rather than a reconstruction.
The review step, where work leaves the building
Anything reaching a client's customers needs somebody other than the author to look at it. That is not a comment on your team. It is that the author cannot see what they assumed.
Where the work touches a client's public-facing material, some obligations belong to the client's business rather than to yours, and the right move is to name them rather than to decide. Accessibility is the usual one, and the Department of Justice's ADA guide for small businesses is a reasonable orientation to raise with them.
Where tasks involve asking a client's customers for reviews or testimonials, the FTC's guidance on soliciting and paying for online reviews governs how it can be done, including the rules against conditioning an incentive on a favorable review and against undisclosed material connections. Put that constraint in the working standard so an assistant is never asked to improvise it.
What the queue tells you at month end
Four counts, taken straight off the board, are worth more than a satisfaction survey.
- Items received, by client. Volume drift is scope drift.
- Time spent in Clarifying. A rising figure means the working standard is thin, or the client is sending vague requests.
- Items that reached Ready and waited. This is your capacity signal.
- Urgent declarations. A client whose every item is urgent has a planning problem you should raise before it becomes a renewal problem.
Read them per client, not in aggregate. The average hides the account that is about to become a complaint, and each of these counts is also an early indicator for the retention work described in the renewal and reporting playbook.
Scope drift, caught in the queue
The queue is where scope growth becomes visible before it becomes a loss.
Once a month, look at items that fell outside the agreed scope. Not to bill them retroactively, which is the fastest way to a dispute, but to decide: absorb it deliberately, reprice at renewal, or stop doing it and say so.
Doing nothing is the fourth option and it is the one most agencies choose by default. The cost of that choice, and how it works its way into margin, is set out in the pricing and profit guide.
Who directs the work
One thing belongs in writing at the start: who on the client's side gives day-to-day instructions, and who on your side assigns and supervises.
It matters for the queue, because an account taking direction from four people has no scope. It also bears on worker status, which the Labor Department's page on misclassification myths explains is decided by the economic reality of the relationship rather than by what an agreement calls it.
The wider onboarding process that establishes all of this is set out in the onboarding workflow for new clients, and the way a well-run queue becomes the thing clients tell other people about is what the marketing and growth guide means by delivery as a channel.
Common questions
Do I need project management software?
You need one place work is logged and five states. A shared board is enough at small scale, and switching tools rarely fixes a queue problem.
What if the client refuses to use the channel?
Keep moving their requests into it and answering from it. Almost everyone adapts. Where they genuinely will not, log the request yourself on receipt, so the record exists even if the habit does not.
How do I handle a client who sends everything as urgent?
Show them the queue at month end with the urgent count on it. The conversation is much easier with a number in front of both of you.
Should assistants estimate their own work?
Yes, and compare estimates to actuals monthly. The gap is the most useful training signal you will get.
