The right KPIs for a virtual assistant measure outcomes you care about, such as response time, accuracy and tasks completed on schedule, rather than hours logged or mouse activity. Pick three to five per role, write down the target and how it is measured, review them monthly and change any measure that encourages the wrong behavior.
KPIs get a bad reputation because they are often used badly. Someone sets a target for the number of emails answered, and suddenly emails get answered fast and poorly. Or a dashboard tracks twenty numbers and nobody looks at any of them.
Used well, a handful of measures does something simple. It gives you and your assistant a shared picture of what good looks like, so you can stop guessing and stop hovering. Our guide on how to manage remote staff explains how KPIs fit into a weekly rhythm.
What makes a good KPI
It ties to a result you care about
Ask what would change in your business if this number got better. If the answer is nothing much, drop it.
The assistant can influence it
Holding an assistant to revenue targets when they do not control pricing or sales calls breeds frustration. Measure what is within their reach.
It is easy to collect
If gathering the number takes an hour, it will stop being gathered. The best KPIs come straight out of tools you already use.
It comes in pairs
Speed measures should be paired with quality measures. Volume should be paired with accuracy. A single number alone invites gaming.
Measures to avoid
Hours online, keystrokes and screenshots tell you someone was present. They say nothing about whether the right work got done. Tasks closed can work, but only if tasks are roughly similar in size. Otherwise people pick off the easy ones.
Number of messages sent is another trap. More messages often means less clarity.
Example KPIs by role
These are starting points. Pick the few that match what you actually hired for.
Executive assistant
- Inbox triaged by an agreed time each day
- Meeting requests answered within a set number of business hours
- Scheduling errors per month, aiming for zero double bookings
- Your own hours spent on admin each week, tracked roughly by you
Customer support
- First response time during working hours
- Resolution rate without escalation
- Customer satisfaction score from a one question survey, if your helpdesk supports it
- Reopened tickets as a quality check
Our customer support virtual assistant guide goes deeper on support metrics.
Bookkeeping
- Bank accounts reconciled by a set day each month
- Uncategorized transactions at month end
- Invoices sent within one business day of the trigger
- Errors found by your accountant at review
Lead generation and appointment setting
- New leads contacted within the target window
- Meetings booked per week
- Show rate for booked meetings
- Lead records with all required fields complete
Data entry
- Records processed per day, paired with
- Error rate from a weekly spot check of a random sample
Setting targets
Do not set targets on day one. Spend the first month measuring without judgment. That shows you what a normal week looks like and what is realistic. Then set targets a little above the steady level you saw, and agree on them together.
Write each KPI down in one line. Name the measure, the target and the source. For example, "First response time under two business hours, measured from the helpdesk report." If the role is new to you, our virtual assistant job description guide helps you define the responsibilities that the KPIs will follow.
A simple monthly scorecard
Keep it on one page. Each month, fill in four columns for every measure.
- The measure and target
- This month's result
- A green, yellow or red mark
- One sentence of context
Context matters. A slow response month might trace back to a product launch that tripled volume. The note keeps the number honest.
Review the scorecard at a monthly call. Spend most of the time on yellows and reds and what would help. Celebrate greens briefly and specifically.
A worked example
Imagine a part time assistant handling customer email for an online store. After a month of measuring, you see a typical first response time of about three hours, a resolution rate of around seventy percent and a handful of reopened tickets each week.
You agree on targets of under two hours for first response and eighty percent resolution. In the review, you notice that most escalations are refund questions. The fix turns out to be a clearer refund policy SOP, which raises the resolution rate the following month without the assistant working any harder.
That is the real value of KPIs. They point you at the process problem behind the number.
When KPIs go wrong
The number improves and the work gets worse
This usually means a single measure without a quality pair. Add one.
The assistant feels watched
Explain why each measure exists and how it will be used. Share the scorecard openly and let them suggest changes.
Nobody looks at it
Cut the list. Three measures reviewed monthly beat ten that sit in a spreadsheet.
The target was wrong
It happens. Adjust it openly and note why. Moving targets quietly destroys trust.
KPIs and pay
Tying small bonuses to KPIs can work, but it raises the stakes on gaming. If you do it, use measures that are hard to fake, such as accuracy from spot checks, and keep the bonus modest. Many small businesses get more from simply recognizing good results and adding responsibility.
Leading and lagging measures
Some numbers tell you what already happened, such as customer satisfaction last month or errors found at the accountant's review. Others warn you early, such as the number of tickets waiting more than a day or invoices not yet sent by Wednesday. Owners tend to pick only the first kind because they feel more important.
A healthy scorecard mixes both. The early warning numbers let your assistant fix things before they show up in the monthly result. A good habit is to put one early measure in the daily update. For a support role that could be the count of tickets older than twenty four hours at the end of the shift. For bookkeeping it could be uncategorized transactions as of today.
Letting the assistant own the scorecard
The most effective setups we see hand the scorecard to the assistant. They gather the numbers, fill in the context column and propose fixes for anything yellow or red before the monthly call. You review and decide.
This does three useful things. It saves you time. It gives the assistant a reason to understand why each measure exists. And it shows you how they think about problems, which helps when you decide what to hand over next.
A simple prompt for the monthly call works well. Ask them to bring the scorecard, one thing that went better than expected, one thing that went worse and one change they would like to try next month.
Reviewing KPIs as the role grows
The measures that fit month one rarely fit month twelve. As an assistant takes on more, retire the measures for tasks that now run smoothly and add measures for the new work. A scorecard that never changes usually means nobody is looking at it closely.
Getting started
Pick the role, choose three measures from the lists above, measure for a month and then set targets together. That is enough to replace most of the uncertainty that leads to micromanagement.
If you are still deciding whether to hire, our pricing page shows plans. An Assistant starts at $1,500 a month full time or $900 part time, and a Specialist starts at $2,200 a month.
KPI questions
How many KPIs should a virtual assistant have?
Three to five per role is usually right. More than that gets ignored.
Should I track hours worked?
Track hours if you need them for billing or the plan itself. For performance, focus on outcomes.
When should I set KPI targets?
After a month of measuring without targets, so you know what a normal week looks like.
How often should KPIs be reviewed?
Monthly for the full scorecard, with a quick look at any urgent measure during your weekly call.