Most people start looking for tools for managing virtual assistants on a day like this. The task is in a message. The latest draft is in an email. The approval was given on a call.

Your assistant asks which version to use.

So you open a new app to get organised, and now the same task exists in two places.

More tools often create more places where work looks finished without actually being accepted. The most useful tools for managing virtual assistants aren't the fanciest. They're the ones that answer three questions without anyone needing to search:

  1. Where does each task live?
  2. Where are the current instructions?
  3. Where are the finished, approved files?

This guide shows you how to build that with a shared folder, a few documents and a spreadsheet, plus how to tell when you've genuinely outgrown it.

We'll use Google Drive, Docs and Sheets as an example, simply because they're common and free to start with. That's not a claim they're the best tools for everyone.

Here, a virtual assistant (VA) is an independent freelancer or agency. Your system should make requests and decisions clear, not monitor every minute of their day.

Editorial scene showing reviewing the owner decision at a worktable for this guide.

Decide where a request becomes a real commitment

Choose one place where committed work is recorded. For a small service, a spreadsheet works fine.

A message can alert your VA to a request. But it only becomes a commitment when its scope, timing and owner are clear in that one place.

That stops casual ideas becoming invisible obligations. "Could we also update the presentation?" might be a question, not permission to drop today's agreed work. Keep proposed requests separate from committed work.

Write a short working agreement:

"Accepted tasks live in this tracker. Current procedures live in this folder. Finished work is linked from its task. Decisions that affect work are recorded beside it. Chat is for alerts and discussion, not the only record of approval."

Use the tools you already have, if they can do this safely. Switching to a new app costs setup time, access and learning. Change because your current setup genuinely can't meet a need, not because a list of "VA tools" makes a bigger stack look more professional.

Editorial scene showing checking a remote handover with another person for this guide.

Build a work folder with a clear privacy boundary

Create one folder for the service, owned by your business. Inside it:

  • Current instructions
  • Working files
  • Accepted (finished) files

Keep it shallow. A newcomer should be able to explain what goes where in one sentence.

Don't share your whole business drive. Google Drive's sharing guidance explains the difference between viewer, commenter and editor access, and that access given to a folder flows down to everything inside it. One convenient parent folder can expose far more than the task needs.

So:

  • Invite your VA's named account with the right access level.
  • Keep contracts, bank details and unrelated customer records elsewhere.
  • If a task needs a restricted source, share just that part, not the whole folder it lives in.

Create important files under your business's ownership. A link to a document owned by your VA's personal account might work today and cause problems later. Our offboarding guide explains why.

Add a "Start here" document with the tracker link, the instructions folder, submission rules and contacts. Test every link from your VA's account before relying on it.

Editorial scene showing comparing the workload against a simple calendar for this guide.

Build a tracker around decisions, not decoration

Create a spreadsheet with one row per task. Columns:

Column Why it matters
Reference A stable ID to connect files and messages
Task A recognisable result, not "email"
Requester Who asked
Current owner Who has to act next
Due date (with time zone) When it's needed
Status Where it stands
Input link What it's built from
Output link What was produced
Next decision What's blocking it
Last updated Spots stale work

"Current owner" is the most useful column most trackers forget. It shows whether the VA is preparing a draft or you are holding up an answer. Otherwise a task can say "with VA" for days while it's really waiting for you.

Write tasks as results: "Prepare approved workshop email draft" beats "email." Keep long instructions in a linked document so the tracker stays readable.

Skip "% complete" columns unless they mean something you can check. A draft that's "90% done" might still be blocked on its key fact. A clear next action tells you far more than an optimistic number.

Editorial scene showing reviewing the evidence before approving the next step for this guide.

Six statuses, each with a written meaning

Start small. Here's a set that works for most VA services:

Status Means
Proposed Request made, not yet committed
Ready Scope agreed, inputs available
In progress VA has started
Waiting for decision Blocked on a named person and question
Ready for review Output accessible, checks done
Accepted Authorised reviewer has accepted it

Write one sentence explaining when each applies.

"Accepted" doesn't mean "sent." If sending or publishing is a separate step, accepting the draft doesn't mean it's gone out.

Lock the labels with a dropdown. In Google Sheets on a computer:

  1. Select the status cells.
  2. Go to Insert, then Dropdown.
  3. Enter each label, using Add another item for each.
  4. Leave multiple selections off (a task has one status).
  5. Set it to reject invalid entries, not just warn.
  6. Click Done.

Test it by typing an unlisted value in a dummy row. Remember: this controls the labels. It doesn't make a status truthful.

Every "Waiting" needs three things: the question, the person who must answer, and what happens if it's late. Otherwise "Waiting" becomes a place difficult work goes to be forgotten.

Editorial scene showing checking access and responsibility before the work continues for this guide.

Give every draft one route to approval

Decide:

  • where your VA submits work,
  • where you record "accepted" or "needs changes."

The tracker links to the document, and comments hold detailed feedback. But the tracker should always show the current status and any decision needed.

Be explicit when reviewing:

  • "Accepted."
  • "Needs these changes."
  • "Waiting for this specific fact."

"Looks good, but check the price" isn't clear approval if the price is going to a customer.

Don't approve one version in chat while editing another in the document. If a call produces a decision, record it in the task, and point your VA to that record.

Use a simple versioning habit. In a live document, mark the accepted version, and don't treat later edits as automatically approved. For exported files, avoid five equally believable files called "FINAL."

Google's version history lets you see changes and name versions, but browsing history requires edit access. If a reviewer only has view access, send them a dated copy rather than widening access just for this.

Version history helps trace changes. It isn't an approval process by itself.

Keep current rules separate from one-off decisions

Keep a short decision log for anything that changes how future tasks work:

  • the decision,
  • its scope,
  • who approved it,
  • effective date,
  • which procedure it affects.

Link it from the task that triggered it.

Don't turn every comment into policy. A special arrangement for one customer might stay a one-off. Label it as such, or it'll quietly spread.

For example, you might approve a different greeting for one sensitive customer. That doesn't change your standard email style. Record it on the case, not in the main procedure.

But when something should apply to all future work, update the actual procedure deliberately, and tell your VA what changed. Your VA shouldn't need to read every past decision to do a routine task.

Our SOP guide covers writing those procedures.

Keep private information out of the convenient places

Trackers often get shared more widely than the source systems. So:

  • Use references and links, not copied customer addresses, messages or bank details.
  • Never store passwords in the "Start here" document. Use a password manager. The tracker can say which account is needed and who grants access, without the secret itself.

Hiding a tab isn't security. Google's guidance on hidden sheets explains that editors can unhide them, and viewers may still access the contents, including through copies. Hiding is a layout choice, not a lock.

Agree which extra tools are allowed. Can your VA use browser extensions or AI tools with your work? A harmless-looking document can still contain confidential information. Convenience isn't permission to send it elsewhere.

Our secure access guide helps you set this up properly.

A worked example: one research brief through the whole system

Here's a hypothetical example.

A consultancy buys a weekly supplier research service. The owner sets up:

  • a service folder with current criteria, a research template and accepted reports,
  • a tracker row for next week's report, linked to the criteria, with a due date.

Ready. Scope agreed, inputs available.

In progress. The VA starts and creates the working report in the folder, using the task reference in the file name.

Waiting for decision. A supplier looks like a fit but its delivery coverage is unclear. The VA records the source and asks: include as unconfirmed, or exclude? The owner is now the current owner. Meanwhile, the VA keeps preparing other verified entries.

Decision recorded. The owner says unconfirmed coverage gets excluded from the main shortlist and noted separately, and that this applies to future reports too. The criteria document gets updated, so the question doesn't come back every week.

Ready for review. The VA finishes, checks the evidence and links the output.

Correction. The owner requests one factual fix, recorded on the same task. Status goes back to In progress, then Ready for review again.

Accepted. The tracker links to the accepted report, not a discarded draft.

A new request. A chat message asks for research on a different market. The VA logs it as Proposed, not as an invisible addition to this week's report. Now the owner can agree its scope and timing without losing track of what's already owed.

Rehearse the awkward situations before automating anything

Create some harmless test tasks:

  • missing input,
  • rejected draft,
  • changed deadline,
  • completed work.

Ask your VA to move each through the system and say who needs to act next. You're testing the agreement, not their ability to guess your favourite labels.

Check:

  • Do notifications reach the right person without creating noise?
  • When a task is reopened, is the accepted file still identifiable? Is it a correction or new work?
  • Do links work from your VA's account? Fix the specific sharing issue, rather than making the folder public.

Try a deliberately broken handover. Mark a test task "Ready for review" but leave the output link blank. Ask the reviewer to spot what's missing and move it back. That checks whether your team treats a status as a claim to verify, not proof the work exists.

Only automate a step once the manual rule is clear. If nobody agrees what "Accepted" means, an automation will just spread confusion faster.

Add another tool only when a specific limit is hurting you

A spreadsheet can become unsuitable when you have:

  • many people owning tasks at once,
  • complex permissions,
  • recurring dependencies between tasks,
  • a support queue needing its own audit trail.

Those are good reasons to look at specialist tools. Common categories include:

  • Project management tools (such as Trello, Asana or ClickUp) for boards, owners and dependencies.
  • Helpdesk tools for customer support queues.
  • Password managers for secure credential sharing.
  • Shared inboxes for team email.

Write down the limitation first. "We can't see which reviewer owns each blocked task" is a requirement. "We need a more advanced workspace" isn't. Check whether a simpler column or rule would fix it.

Check current official pricing and features for the exact plan you'd use. A feature in a comparison article might not be in the free tier or your region. We haven't tested paid products or compared live prices here.

Plan the migration around active work. Decide which tasks move, which system becomes the official one, and how old links are handled. Running two live trackers indefinitely recreates exactly the confusion you were trying to fix.

Keep exports and ownership under your control. Tools can be replaced. Your accepted work and decision history shouldn't vanish when a subscription changes or your VA leaves.

Review the system by trying to find one unfinished decision

At the end of the first cycle, pick an unfinished task. Can you see:

  • the expected result,
  • the current owner,
  • the missing decision,
  • the relevant file,

...without searching chat? If not, fix that specific gap.

Then pick an accepted task. Could someone else open the accepted output and see what was approved? If several versions compete, clarify the record before adding more work.

Ask your VA which updates feel duplicated. If they're updating the tracker, writing a detailed email and posting the same thing in chat, cut the repetition. The system should reduce coordination, not become another job.

Your setup checklist

VA WORKING SYSTEM SETUP

Folder (business-owned):
  /Current instructions
  /Working files
  /Accepted files
  Start here doc (links, rules, contacts, NO passwords)

Sharing:
  VA named account access level:
  Inherited access checked? (Y/N)
  Sensitive files kept elsewhere? (Y/N)

Tracker columns:
  Ref / Task / Requester / Current owner / Due (time zone) /
  Status / Input link / Output link / Next decision / Last updated

Statuses (with definitions):
  Proposed / Ready / In progress / Waiting for decision /
  Ready for review / Accepted
Dropdown set to reject invalid entries? (Y/N)

Approval route:
Decision log location:
Allowed extra tools / AI tools:
Rehearsal cases run and results:
Date to review the system:

You have a working system when a request can become an agreed task, reach a decision and end up as an accessible, accepted result.

The number of apps matters far less than whether both of you can follow that chain without digging through scattered messages.

Related: how to manage a virtual assistant and the VA onboarding checklist.

Frequently asked questions

What is the best tool for managing a virtual assistant?

The best tool gives every task one home, clear statuses and a visible approval route. For many small services, a shared folder plus a spreadsheet tracker is enough. Move to a specialist tool when you hit a specific limit.

Should I use Trello, Asana or a spreadsheet?

Write down the specific problem first. A spreadsheet often works for one VA and modest volume. Dedicated project tools help with many owners, dependencies or audit trails. Check current pricing and features for the exact plan.

What statuses should a VA task tracker have?

A small set like Proposed, Ready, In progress, Waiting for decision, Ready for review and Accepted, each with a written definition.

Is hiding a sheet in Google Sheets secure?

No. Google notes that editors can unhide sheets and viewers may still access their contents, including through copies. Keep confidential information out of shared trackers entirely.

Should approvals happen in chat?

Chat is fine for alerting someone, but record the actual decision in the task or a linked decision note, so it doesn't disappear into a scrolling conversation.