Measuring Your VA's Performance Without Micromanaging

The anxiety is understandable: you are paying for hours you cannot see. Some owners respond with surveillance — screenshot software, activity trackers, constant check-ins — and reliably end up with a resentful assistant and no better results. The alternative is simpler and works: define outcomes, make work visible, and review a handful of numbers on a rhythm.

Measure outcomes, not activity

Activity metrics — hours logged, messages sent, keystrokes recorded — tell you whether someone was busy, not whether the business moved. Outcome measures tell you what actually matters:

• Invoices sent within a day of job completion
• Enquiries receiving a first response within the agreed window
• Quotes followed up on schedule
• The task board clear of overdue items
• Newsletter out on its planned date

Notice these are measures of the system your VA runs, not of the person. That is the point: you are buying reliable operation of defined processes, and that is what should be measured.

Pick three to five numbers, not fifteen

For most engagements, a handful of numbers reviewed weekly covers everything worth knowing. A simple weekly snapshot — assembled by the VA themselves as part of the role — might read: 14 invoices sent, average response time 3 hours, 6 quotes followed up with 2 responses, zero overdue tasks. Two minutes to compile, ten seconds to read, and drift becomes visible within a week rather than a quarter.

Self-reporting is not naive: the numbers are verifiable in your systems whenever you care to look, and asking the person who runs the process to report on it reinforces ownership rather than undermining it.

Quality: sample, do not audit everything

Checking every output forever is micromanagement with a schedule. Instead, review everything early — the first fortnight of a new task — then step down to sampling: read a few sent emails a week, skim this month's reconciliations, spot-check one procedure. Increase sampling only when something slips. This mirrors how quality control works everywhere: intensity proportional to risk and track record.

The review rhythm

• Weekly: the snapshot numbers plus a fifteen-minute call — anything blocked, anything unclear, priorities for the week ahead.
• Quarterly: a longer conversation about the engagement itself. What should we stop, start, continue? Is the hour allocation right? What could you take on that you are not doing today? Quarterly reviews are where good engagements compound into great ones, because capable assistants are chronically under-asked.

When the numbers slip

Raise it early, specifically and without ambush: response times drifted from three hours to two days these past two weeks — what is going on? Sometimes the cause is workload, sometimes unclear priorities, sometimes life. One honest conversation solves most slippages. A pattern of slippage after honest conversations is itself an answer, and the offboarding steps in your services agreement and access register exist for exactly that case.

Why not just use monitoring software?

Screenshot and activity-tracking tools promise certainty and deliver theatre. They measure presence, not quality; they punish thinking time; they signal distrust to precisely the conscientious people you most want to keep; and they create privacy questions you do not need. If you feel you need surveillance to trust your assistant, the relationship already has a problem that software will not fix. Clear outcomes, visible work and honest reviews give you real control — the kind that improves the work rather than merely watching it.

FAQ

How soon should a new VA be at full speed?

Expect noticeably useful output in the first week on a well-briefed task, and steady-state speed on recurring work within a few weeks. Complex or specialised processes take longer — the investment is front-loaded.

Should underperformance affect payment?

Not retrospectively — pay for work delivered under the agreement you made. Persistent quality problems are a conversation about the engagement, and ultimately a termination decision, not an invoicing dispute.

What if I only have vague tasks and cannot define outcomes?

That is a briefing problem rather than a measurement problem. Tighten the briefs first — our task brief guide shows the structure — and measurable outcomes fall out naturally.