Key takeaways
· Measure outcomes per role - task turnaround for VAs, close dates for bookkeepers, response times for support - not activity theatre like hours online.
· Three to five KPIs per role is the ceiling; more and nothing is actually managed.
· The weekly scorecard ritual matters more than the metrics chosen.
"How do I know they're actually working?" is the wrong question - hours-online surveillance measures presence, not value, and burns trust. The right question: is the outcome the role exists for happening, visibly, every week? KPIs answer that in five lines.
KPI sets by role
Virtual assistant: task turnaround (% of routine tasks done within agreed SLA), inbox/queue age (nothing older than 24h), CRM currency (updates within one business day), error/rework rate, and one proactive improvement per week.
Bookkeeper: reconciliation currency (bank recs done daily/weekly), month-end close date (by the 3rd is elite), unreconciled item count, query-list size and age, payroll accuracy. See hire a bookkeeper for how these show up in the role.
Executive assistant: inbox triaged by 9am, zero double-bookings, meeting notes distributed same day, follow-up completion rate, travel booked without repeat questions.
Customer support rep: first response time, resolution time, CSAT, reopen rate, ticket backlog age. Weekly voice-of-customer digest as the qualitative layer.
The one-page weekly scorecard
Five rows (the KPIs), four columns: target, this week, last week, notes. The team member fills it Friday; you read it in two minutes; the Monday sync discusses any red cell. That is the whole system - the discipline of it does more than any dashboard. Numbers they self-report honestly beat numbers you extract - and the self-reporting habit is itself a signal.
Reviews that use the data
Monthly: scorecard trends, one thing to improve, one thing to hand over next (role growth is retention - see the retention playbook). Quarterly: reset the KPI targets as the role matures. In RemoteHirely placements, our HR check-ins run alongside - performance issues get caught from two directions.
Leading vs lagging: pair every KPI
Lagging KPIs (close date, CSAT, error rate) tell you what happened; pair each with its leading twin so problems surface mid-week, not month-end. Close-by-the-3rd pairs with daily unreconciled count; CSAT pairs with first-response time; error rate pairs with query-list usage (a bookkeeper who queries nothing is guessing). The scorecard carries both columns - lagging for accountability, leading for steering.
Setting targets that survive contact with reality
Baseline first: run two weeks with no targets, measure, then set targets at "current best week, consistently" - not aspiration theatre. Ratchet quarterly, and let the team member co-set the numbers: self-set targets get chased, imposed ones get explained. One warning from experience: never target raw activity (tickets touched, transactions coded) without a quality pair - you will get exactly what you measured and none of what you meant.
Frequently asked questions
Should I use time-tracking or screenshot software?
We advise outcomes over surveillance. Activity trackers are appropriate in some regulated or hourly-billing contexts, but a role with real KPIs makes them redundant - and trust compounds where surveillance corrodes.
What is a fair ramp before KPIs count?
Weeks one to four are onboarding (the 30-day plan); scorecard from week two, targets enforced from month two.
What if KPIs are consistently missed?
Diagnose in order: unclear brief, wrong tools, wrong volume assumptions, wrong person. A managed placement's free replacement covers the last case; the first three are fixable in a week.
Should KPI results affect pay?
Performance feeds the annual review cycle (which in our model aligns with remuneration reviews); weekly scorecards should stay a steering tool, not a piecework meter - the fastest way to kill honest self-reporting is to price it.
Want the scorecard template with your placement?