Virtual assistant performance metrics: a simple scorecard for founders
A practical VA performance scorecard with weekly metrics, review rules, source-backed guardrails, and update templates.
Operator sections with practical steps.
Decision points before handoff.
Visible citations and source notes.
Key takeaways
- Use 5 to 7 metrics, not 20. A small scorecard is easier to fill in every Friday and easier to coach from.
- Separate volume, speed, quality, judgment, and access safety so one good number does not hide a risky habit.
- Review 100% of high-risk work at first, then choose a manager-set completed sample for low-risk work once the assistant is steady.
- Ask for a weekly note with completed work, errors found, stuck items, SOP fixes, and owner decisions needed.
- The scorecard should decide one next step each week: keep the lane, tighten the rule, or add the next safe task.
A virtual assistant can look busy while the founder still feels stuck. Messages move, calendars change, and tasks close, but nobody knows if the work is getting safer or easier to manage.
A simple performance scorecard fixes that. It turns the first 30 days into a small set of numbers, notes, and coaching decisions instead of a vague feeling that the VA is doing well or falling behind.
Weekly VA scorecard
Start with these rows for the first month. Keep the scorecard short enough to finish in 10 minutes.
| Check | Working guidance | Why it matters |
|---|---|---|
| Work completed | Count by task lane | For example: 42 CRM updates, 18 follow-ups drafted, 9 meetings scheduled. |
| On-time rate | Target 90%+ after training | Track due dates missed and why they slipped. |
| Error sample | Manager-set completed sample | Set it from volume and risk; check accuracy, tone, missing links, and rule breaks. |
| Stuck items | 0 silent blockers | Every blocker needs a note, owner question, or proposed next step. |
| SOP fixes | 1 to 3 updates weekly | Turn repeated questions into new examples or clearer rules. |
Keep each metric tied to reviewable evidence
A count is useful only when the reviewer can see what it represents. Keep the evidence link, sample result, and owner decision beside the number instead of relying on a status update alone.
| Check | Working guidance | Why it matters |
|---|---|---|
| Completed work | Task links or record IDs | A reviewer can open the finished batch rather than trusting a total. |
| Quality | Completed sample plus error pattern | Name the missed rule and whether the SOP needs an example. |
| Blockers | Paused item and named owner | A question is not resolved until the authorized owner decides it. |
| Access safety | Named-account and MFA check | Use approved accounts and folders; do not put shared passwords in a weekly note. |
Two review notes to copy
- Weekly update: "Completed: [numbers]. Missed or delayed: [items + reason]. Errors found: [count + pattern]. SOP updates needed: [changes]. Owner decisions: [questions]."
- Coaching note: "Keep doing [specific habit]. Tighten [one rule]. Next week, do not expand the role until [metric or example] is steady."
Friday decision note
Choose one next move. Use the record to prepare the monthly review; the named owner still approves exceptions, access changes, customer commitments, and any expansion of the role.
- Keep: [lane] is steady. Tighten: give [rule] an example. Expand: add [adjacent task] after a clean sample.
Five-minute Friday review sequence
Use the completed-work evidence and the sample before deciding what changes next week. The owner still approves exceptions, access changes, customer commitments, and any expansion of the role.
- Minute 1: compare the completed count with the assigned task lane; do not count work that has no finished evidence.
- Minutes 2–3: review the planned sample, note the error pattern, and separate a missed rule from a missing SOP example.
- Minute 4: list every blocker or exception that needs an owner decision; do not convert a pause into permission.
- Minute 5: choose keep, tighten, or one adjacent expansion, then name the next sample and review date.
Measure the role, not the person in general
Match the scorecard to the work the VA actually handles. Inbox work needs drafts, labels, escalations, and missed follow-ups; CRM work needs record updates, duplicate fixes, missing fields, and source links; reporting needs on-time reports, source checks, and owner questions before the deadline.
The U.S. Bureau of Labor Statistics includes scheduling, records, correspondence, and office support in administrative-assistant work. Early VA tasks are usually visible enough to count, sample, and improve without treating the assistant as owner of the whole process.
Use 5 to 7 metrics; more makes the review another job. Each Friday, decide whether the current work is ready for more trust or needs a tighter rule.
Use five metric buckets in the first 30 days
The first bucket is volume: tasks finished by lane. Count items like 35 emails labeled, 12 follow-ups drafted, 8 calendar conflicts solved, or 60 CRM records cleaned. Volume matters because it shows whether the role is taking real work off the founder's desk.
The second bucket is speed: due dates hit, turnaround time, and aging tasks. The third is quality: error patterns found in review.
The fourth is judgment: how often the assistant paused, escalated, or asked before a risky decision. The fifth is access safety: whether they used approved accounts, source links, and red-line rules.
Do not reward speed by itself. A VA who clears 100 records with 18 missing source links creates cleanup work. A better Friday note says: "60 records updated, 5 missing-source errors found in a 20-record sample, SOP step added for source links, and 4 records paused for owner review."
Set review rules before the work expands
For the first 2 weeks, review high-risk work before it leaves the business. That includes refunds, payments, contract wording, sensitive customer replies, payroll changes, legal wording, and anything involving private data. Low-risk work can move faster, but it still needs sampling.
NIST's Digital Identity Guidelines treat authentication and account recovery as security controls. In plain terms, the VA scorecard should include access habits: named accounts, MFA, approved folders, no shared passwords in chat, and no owner-only decisions made alone.
Review every risky draft before it leaves. For repeat low-risk work, use the quality sampling schedule planner to set a routine around volume, risk, and the manager time you have. If 3 of 10 sampled CRM updates miss source links, fix the SOP before adding another task lane.
Use a mini-scenario before you add more tasks
Picture a founder who gives a VA 12 hours a week to handle inbox labels and calendar cleanup. In the first week, the VA labels 80 emails, drafts 10 follow-ups, schedules 7 meetings, and flags 3 customer questions.
At Friday review, the founder samples 25 emails and finds 2 wrong labels plus 1 follow-up that needs a softer tone. Rather than adding bookkeeping, research, and support tickets in week 2, the founder keeps the task group narrow and adds 6 examples to the SOP.
If a customer asks for a refund, the VA pauses: "I drafted two options, but I need approval before sending." By week 4, routine scheduling and straightforward follow-ups may move to spot checks, while exceptions still go to the owner.
Use the scorecard to decide the next step. Add work only when the current task group is accurate, documented, and safe.
Connect metrics to a keep, tighten, or expand decision
End each weekly review with one decision. Keep means the same work lane continues for another week.
Tighten means the SOP, access, examples, or review rule changes. Expand means one adjacent task is added after the current lane is steady.
Atlassian's roles and responsibilities play is built around clarity on who owns what and how decisions get made. The VA version is simple: write what the assistant owns, what they draft only, what they may never approve, and who answers exceptions.
If the scorecard shows on-time work, fewer repeat errors, no silent blockers, and clean access habits across a manager-set completed sample, add the next safe task. If not, keep the lane small and improve the system first.
How to use this playbook
Read this article like a work guide. Pick one task, one role, or one quality rule and turn it into a short checklist before you give it to an assistant. Small changes are easier to train and easier to check.
The next step is simple: connect the idea to a role scorecard, SOP, onboarding plan, or weekly scorecard. That turns the article into a tool you can use.
Where this fits
Virtual assistant performance metrics: a simple scorecard for founders fits the same basic path used across OutsourcedU: choose the work, write the rule, train the person, check the result, and add more only when the work is steady. Skipping steps usually creates cleanup work.
If this topic is active in your business, the next supporting page is Remote team management systems. Use that page to connect the article to a broader setup plan, including outcomes, rhythm, quality checks, and management expectations.
FAQ
What metrics should I use for a virtual assistant?
Start with work completed by lane, on-time rate, error patterns, stuck items, SOP updates, escalation quality, and access-safety habits. Keep it to 5 to 7 metrics.
How often should I review VA performance?
Use a short weekly review during the first 30 days. Review high-risk work before it goes out; for low-risk work, set a completed sample that fits the volume, risk, and manager review time.
What is a good VA scorecard for a founder?
A good founder scorecard is simple: tasks finished, deadlines hit, errors found, owner decisions needed, SOP fixes, and one next step: keep, tighten, or expand.
When can I give a VA more responsibility?
Add one adjacent task after the current lane is accurate, documented, and safe for 2 straight weeks. Do not expand just because the assistant has spare hours.
Sources
- U.S. Bureau of Labor Statistics, Secretaries and Administrative Assistants — Administrative task scope.
- NIST SP 800-63B-4 Digital Identity Guidelines — Current authentication and account-recovery guidance.
- Gallup, State of the Global Workplace 2026 — Manager clarity.
- Atlassian Team Playbook, Roles and Responsibilities — Ownership rules.
Related articles
These guides cover adjacent planning work. Pick the one that fits the next decision instead of treating them as a required sequence.
Remote team management system: the weekly operating rhythm
A practical remote team management system for founders with offshore assistants, SOPs, scorecards, and weekly reviews.
Read the guideOffshore performance review system for remote teams
A review system for offshore assistants, with scorecards, examples, and a 30-day coaching rhythm.
Read the guideOutsourcing role scorecard: the one-page tool that prevents vague hiring
Use an outsourcing role scorecard to define outcomes, responsibilities, metrics, access, and the first 30 days before hiring support.
Read the guideFirst virtual assistant checklist before you hire
Use this first virtual assistant checklist to define tasks, SOPs, access, success measures, and a 30-day review plan before you interview or hire.
Read the guide