Writing a virtual assistant job description usually goes like this. Your draft starts with email and scheduling. Then you remember social media. And invoices. And research, customer support, the website...
By the last line, you're advertising for someone who can run most of your business, accept an unlimited workload, and somehow know which bit matters first.
That's the trap with a virtual assistant job description. You can copy a template that makes the list look tidy. It just won't make the job workable.
A good description doesn't attract everyone. It attracts the right people, and gives the wrong people an easy reason to scroll past.
This guide shows you how to write one that does exactly that, with a full example at the end you can adapt.
On this site, a virtual assistant (VA) means an independent freelancer or agency you buy a service from. "Job description" is the phrase everyone searches for, but what you're really writing is a brief for a service, not a job advert for an employee.
Open with what will be different when it works
Start with the problem that made you look for help. Be concrete:
- Client files are incomplete before meetings.
- Supplier updates get lost in email.
- Approved content sits for weeks waiting for someone to publish it.
Then describe what "fixed" looks like:
"Every confirmed consultation has a complete preparation file before the appointment."
That gives an applicant something real to picture. Compare it with:
"Support our growing business with various tasks."
That tells them nothing about the work or the standard.
Be careful not to promise outcomes nobody can control. A VA can run a follow-up process, but can't guarantee every customer replies. Write the responsibility as "keep the case current, complete agreed actions and flag decisions," not "make sure every customer responds."
If you can't describe the result, you probably have several unrelated needs mixed together. Our guide on which tasks to outsource first can help you separate them.
Group tasks that share the same information
Pick work that hangs together. Preparing a client file, requesting missing details and confirming it's ready for the appointment all use the same context. That's one coherent bundle.
Adding "advertising strategy" because they might have spare time is a different skill entirely.
For each responsibility, write three things:
- The trigger: what starts it. ("A signed proposal arrives.")
- The action: what they do. ("Collect required documents.")
- The evidence: how you'll know it's done. ("A checklist showing files received and gaps assigned to someone.")
That's far clearer than "excellent organisational skills."
Public templates are useful for jogging your memory. Upwork's VA job description template, for example, covers admin, scheduling, social media, finance support and research. Treat that as a menu to choose from, not a list one person must cover.
For occasional extra work, add one honest line:
"Additional research projects may be quoted separately."
That's better than "other duties as required," which tells applicants the job could become anything.
Separate what they need on day one from what you'll teach
List what someone genuinely must bring:
- careful comparison of records,
- clear written communication,
- the habit of keeping unresolved cases visible.
Then list what you'll explain:
- your file naming conventions,
- your specific booking rules,
- your product details.
Ask yourself whether named software is really essential. Someone who's used a similar customer database can learn yours quickly. Knowing a tool's logo doesn't prove they can spot conflicting information.
Ask for evidence, not adjectives:
- Weak: "Exceptional attention to detail."
- Strong: "Can explain how they checked document completeness in previous work."
Don't add degrees or years of experience just because a template has them. If the work genuinely needs a qualification, say so and check it. Otherwise, describe the skill that actually protects the result.
And say what you'll provide: current policies, examples, where to find inputs, and a named person for decisions. That helps experienced applicants judge how much setup is involved.
Say when the work happens, not just how many hours
Describe:
- when inputs arrive,
- when results are needed,
- which parts need someone available live.
If work can be done flexibly before a deadline, say so. If customers need replies within certain windows, name those windows and their time zone.
Keep "hours of work" separate from "hours available." Ten hours of tasks a week doesn't automatically mean someone sitting by their inbox through all your opening hours. Ask applicants what availability they can offer. Our part-time vs full-time guide explains why this matters so much.
State the fee basis and currency. You can:
- give a budget for a defined trial,
- ask applicants to quote against the scope, or
- give a considered range with the assumptions behind it.
And explain how extra work gets approved, so nobody's guessing whether to stop at a limit.
One more thing. Don't fill the description with employee-style control ("must be online 9 to 5 in our time zone, no other clients") and then stick "contractor" at the top. The UK government's self-employment guidance explains that the real relationship matters, not the label. Our contractor or employee guide covers this.
Show exactly where their authority stops
This section separates good descriptions from great ones, and almost nobody includes it.
A VA can prepare a reply without permission to send it. They can find an invoice without approving payment. They can suggest a meeting change without moving an important meeting.
So say which version you want:
- What they can decide alone: "Request missing information and offer released dates."
- What stays with you: "Price changes, contract terms, sensitive complaints."
- How they flag it: "Record it in the exception list with the relevant details and the decision needed."
"Escalate as necessary" doesn't tell anyone where a stuck case goes.
When good applicants see this section, they recognise someone who's thought the job through. That makes them more likely to apply.
Keep sensitive details out of the public post, though. You can say "work uses named accounts and limited permissions" without describing your security setup.
A complete example you can adapt
Here's a full brief for a made-up workshop business whose confirmed bookings often lack attendee details and preparation materials. Swap in your own details. It's a service brief, not a legal contract.
INDEPENDENT VIRTUAL ASSISTANT SERVICE:
WORKSHOP BOOKING COORDINATION
About us
We run professional workshops for business customers. After a booking
is accepted, several admin steps need doing before the trainer can
prepare. We're looking for an independent provider to coordinate those
steps and keep incomplete bookings visible.
The result we need
Every confirmed workshop has the agreed date, a confirmed client
contact, the required attendee information and the correct preparation
materials. Anything missing has a named owner and a next action before
the preparation deadline.
What you'll do
Work starts when we mark a proposal as accepted in the shared booking
record. You'll:
- check the signed agreement and client contact are present
- request missing attendee details using our approved message
- offer dates from our released availability
- prepare the invitation
- put the right materials in the client folder
- keep the booking status current
- flag anything that needs a business decision
Not included
Sales calls, price negotiation, workshop design, payment approval,
advertising, or personal errands. Separate projects may be quoted
later; they're not assumed to be part of this service.
What you can and can't decide
You can request routine information and offer released dates.
You can't promise an unavailable trainer, change contract terms or
agree extra workshop content. Put those in the exception list with the
relevant proposal wording and the decision you need from us.
Volume and availability
Assume around six new bookings a week, with up to twelve open bookings
waiting for information at once. No historical backlog.
This is scheduled work, not live support. Please propose an
arrangement that reviews complete requests by the next business day,
stating your time zone and availability. Urgent issues outside your
hours stay with our business contact.
Skills we need
Experience coordinating documents, appointments or client preparation.
Clear writing, accurate records, and a sensible way of spotting missing
or conflicting information. Experience with our exact software is
helpful but not essential.
What we provide
Current checklist, approved messages, materials index, released
availability, examples of finished bookings, and a named contact for
questions during agreed review times. Access limited to what the work
needs.
Fees and selection
Please quote in your currency and explain your pricing basis (hourly,
retainer or other), assumptions, minimum commitments and extra-work
charges. Shortlisted applicants get a short PAID assessment using
invented bookings. Fee, time limit, deadline and allowed tools are
agreed before it starts. Payment doesn't depend on being hired.
How to apply
Briefly describe one comparable job, your part in it, and how you
checked the result. Share a sample only if you have permission and it
contains no confidential client information. If you can't share past
work, explain your method instead.
Include your availability, fee basis, earliest start and any question
that would affect your quote.
Also answer this:
A client confirms a workshop but sends attendee names with no email
addresses, two days before materials are due. What would you do?
After selection
Start is subject to agreeing scope, fees, confidentiality, data
handling and the service arrangement. We'll confirm the first
responsibility and review date in writing before any live access.
Notice what this does. A strategist reads "coordination" and moves on. Someone wanting flexible hours can judge the response requirement. Someone with relevant experience can explain it, even if they've never used your software.
That final question is a gem. Three sentences of someone's reasoning tell you more than a whole CV.
Ask for evidence without turning applying into free work
Keep the first response short. You need enough to decide whether to talk, not a finished project from every applicant.
If you want new work produced, make it a paid assessment for your shortlist. Upwork's rules explicitly prohibit asking freelancers for free work, including work submitted to win a job. Other platforms have their own rules too.
A few more tips:
- Skip hidden "trick" instructions like "write BANANA in your reply to prove you read this." Missing a gimmick at the bottom of a long post doesn't tell you how someone handles a real customer record.
- Say whether AI tools are allowed in any assessment, and what information must not be uploaded.
- Ask for the same evidence from everyone, so you can compare fairly.
Our applicant screening guide shows how to compare the responses you get.
Six mistakes that quietly ruin a VA job post
Here are the most common problems, and the quick fix for each.
1. The everything list. Email, scheduling, social, bookkeeping, research, website. Fix: pick one coherent area and quote extras separately.
2. Personality instead of work. "Proactive, detail-oriented, positive attitude." Fix: describe the outcome and ask for evidence of similar work.
3. Hidden availability. Saying "flexible" while expecting instant replies all day. Fix: state the real response windows with a time zone.
4. No authority section. Applicants can't tell if they'll be trusted to decide anything. Fix: list what they can decide and what stays with you.
5. No pay information. Good providers skip posts where they can't judge if it's worth their time. Fix: give a budget, a range with assumptions, or ask for a quote against a clear scope.
6. A free "test" in the application. Fix: keep applying simple and pay shortlisted people for any real work.
Fixing just two or three of these usually changes the quality of applications noticeably, because the right people can finally recognise themselves in what you've written.
Read it as an applicant before you post it
Before publishing, read the title, result, skills and fee together. Look for contradictions:
- Does an "admin" role secretly need advanced marketing strategy?
- Does "flexible hours" sit next to an expectation of instant replies all day?
- Does a modest scope end with "and anything else that comes up"?
Test it with a realistic exception. In the workshop example, a client asks for a different date and a discount. The date falls within the VA's authority. The discount doesn't. If your description can't separate those two, fix the authority section.
Ask whether a capable provider could estimate the work from what you've written. If you don't have good volume data yet, say so: "The first paid assignment will help us measure the workload."
Check the tone too. Words like "rockstar," "ninja," "join our family" or "whatever it takes" don't describe the work. You're buying a professional service.
And remove anything private: real customer names, internal records, or security details.
Turn the winning proposal into a clear start
A great application can still lead to a messy start if the final conversation quietly changes the scope.
Before work begins, confirm in writing:
- the result and first responsibilities,
- fee basis, currency, invoicing dates and spending cap,
- agreed availability and what happens outside it,
- who can approve extra work.
Confirm the first paid task separately from the ongoing service.
In the workshop example, the first live responsibility might be preparing drafts only, until a review shows accurate handling. Write that down so the description doesn't accidentally grant every future permission on day one.
Keep it current as the work changes
Once work begins, compare the description with what you're actually asking for.
- If new kinds of tasks keep appearing, discuss whether they fit the VA's skills, capacity and fee.
- If you give them more authority because they've proven themselves, update the description and permissions.
- Keep dated versions, so you both have a neutral reference if things drift.
And if applications are poor, look at the description before blaming the platform. You might be attracting generalists to specialist work, hiding essential availability requirements, or asking for too much before any paid commitment.
A good VA description lets the right provider say, with confidence: "I can deliver this, under these conditions." That's the response you want, far more than enthusiasm about a role nobody can define.
Next: screen your applicants, prepare your interview questions, and see the full process in how to hire a virtual assistant.
Frequently asked questions
What should a virtual assistant job description include?
The result you need, the starting scope and exclusions, what the assistant can decide alone, volume and availability, skills needed on day one versus what you'll teach, what you'll provide, the fee basis and how to apply.
Should I list every task I might want help with?
No. A long list attracts generalists and makes quotes impossible to compare. Describe one coherent area of work and say extra projects can be quoted separately.
Should I include the pay rate in a VA job post?
It helps. You can give a budget for a defined trial, a range with its assumptions, or ask applicants to quote. Avoid a placeholder price that isn't real.
How do I stop getting hundreds of irrelevant applications?
Be specific. Describe the actual work, required availability and exclusions, and ask applicants one question drawn from the real job. Specific posts make unsuitable people rule themselves out.
Can I ask applicants to complete a test as part of applying?
Keep the application light. If you want new work produced, make it a paid assessment for shortlisted people. Some platforms prohibit asking freelancers for free work.