KPIs for remote teams: how to set, share and review them
Short answer Give each remote role one to three KPIs that count results a customer or the business can feel (jobs booked, invoices sent on time, reviews earned), not hours online. Write each one down with its formula and data source, keep them in one shared sheet, glance weekly and reset quarterly. Hourly employees' hours must still be recorded by law.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callKPIs for remote teams: the rule
A KPI (key performance indicator) is the one number that tells you whether a job is getting done. When you can't see someone work, the number has to stand in for what you would have noticed walking past their desk. So it must count a result, not effort.
- One to three KPIs per role. More than that and nobody knows which one wins when they clash.
- Each counts a result someone outside the role would notice. A booked job, a paid invoice, a five-star review. Not logins, messages sent or hours online.
- Pair any speed or volume number with a quality check, so it can't be hit by rushing.
- Write each down on a one-line card: formula, where the number comes from, who owns it, target, period.
- One shared sheet everyone can open, updated on a fixed day.
- Look weekly, talk monthly, reset quarterly.
What makes it less simple: hourly employees still need their hours recorded by law, and some places require written notice before you monitor anyone electronically. Both are covered below.
What KPIs should I set for each remote role?
Start from what the role exists to produce, then find where that number already lives. Most small service businesses can fill this table from tools they already pay for.
| Remote role | Result KPI | Quality pair | Instead of | Where the number lives |
|---|---|---|---|---|
| Call answering / booking | Calls booked as jobs ÷ calls answered | Booked jobs that actually happened | Calls taken | Phone system, booking calendar |
| Sales rep | Quotes won ÷ quotes sent; won value | Jobs cancelled within 30 days | Calls made | CRM or quote log |
| Bookkeeper | Books closed by day X of the month | Corrections found at review | Hours logged | Accounting software |
| Customer support | Issues solved on first reply | Issues reopened within 7 days | Tickets closed | Help desk or shared inbox |
| Marketer or writer | Leads from their channel | Leads that became paying customers | Posts published | Analytics, CRM |
| Virtual assistant | Agreed tasks done by due date | Tasks sent back for rework | Time active | Task board |
If you can't name a result for a role, the role itself is fuzzy. Fix the job description before you pick a number.
How do I write a KPI nobody argues about?
Write a card for each KPI before anyone is measured on it. Arguments in remote teams come from two people reading the same word two ways ("booked" when the call ends, or when the deposit clears?).
| Field | Example |
|---|---|
| Name | Booking rate |
| Formula | Jobs booked ÷ calls answered, Monday to Sunday |
| Counts as booked | Appointment in the calendar with an address |
| Data source | Phone system report + booking calendar |
| Owner | The person answering calls |
| Target | 40% (set from the last 8 weeks, not a guess) |
| Updated | Every Monday by 10 a.m. their time |
Set the first target from your own last two months, then raise it once it's being hit. Let the person who owns the number help write the card: they know where the data is wrong.
How do I share KPIs with people I never see?
Use one live sheet or dashboard, one tab per role, readable by the whole team. Everyone sees the same number at the same moment, so a weekly meeting isn't needed just to learn the score. A free Google Sheet works; Looker Studio can pull marketing numbers in automatically.
Pair the sheet with a short written update from each person on the same day each week, answered asynchronously (each person replies when their day starts, no call needed):
- My number this week, and the target.
- What moved it, up or down.
- What I'll try next week.
- Where I'm stuck.
Time zones stop mattering because nothing waits for a meeting. A written trail also shows you the pattern behind a bad month, which a call rarely does.
How often should a remote team review KPIs?
| When | Who | What happens | Length |
|---|---|---|---|
| Weekly | Each person, in writing | Number, cause, next step | 5 minutes to write |
| Monthly | Owner and each person, on video | Trend over 4 weeks, blockers, help needed | 20–30 minutes |
| Quarterly | Owner, with the team's input | Keep, change or drop each KPI; reset targets | 1 hour |
Drop or rewrite a KPI at the quarterly review when any of these is true: it has been hit every week without effort, people are hitting it while customers complain, or the business goal behind it changed (you stopped selling that service, or you're full and need margin, not volume).
Can I track hours, screen time or keystrokes?
You can, but activity data shows presence, not results, and the law adds duties. Know these before buying monitoring software.
Hourly (non-exempt) employees in the US: you must record their hours anyway. The FLSA requires records of "Hours worked each day" and "Total hours worked each workweek" for each non-exempt worker, and "Any timekeeping plan is acceptable as long as it is complete and accurate" (DOL Fact Sheet #21). For people working from home, the Department of Labor's February 2023 bulletin says:
"If the employer knows or has reason to believe that work is being performed, the time must be counted as hours worked regardless whether the employee works at the employer's location or teleworks from another location." (DOL Field Assistance Bulletin No. 2023-1)
The same bulletin says breaks of 20 minutes or less count as paid time at home too, and that a reasonable way to report unscheduled hours, with pay for all reported hours, satisfies the employer's duty. So the honest setup is a timesheet for pay, and KPIs for performance. Don't mix them.
New York: written notice before electronic monitoring. Employers that monitor employees' phone, email or internet use must give "prior written notice upon hiring," have it acknowledged in writing or electronically, and post it "in a conspicuous place." Maximum civil penalties are $500 for a first offense, $1,000 for a second and $3,000 for each later one (New York Civil Rights Law § 52-c*2). Other states have their own rules; check yours.
Ontario: a written monitoring policy at 25 or more employees. Employers with 25 or more employees in Ontario on January 1 must have a written policy before March 1 saying whether they monitor electronically and, if so, how and for what purposes. Part-time and casual staff each count as one. The rule doesn't ban monitoring; it requires transparency (Ontario ESA guide). Ontario employers must also record the hours employees work each day and week, with lighter rules for some salaried staff (Ontario ESA guide: Record keeping).
Canada more broadly. The federal privacy commissioner's guidance applies directly to federally regulated employers, but its test is a sensible bar anywhere:
"It is important that any employee monitoring be limited to purposes that are specific, targeted and appropriate in the circumstances." (Office of the Privacy Commissioner of Canada: Privacy in the Workplace)
It adds that employers must tell employees the purpose, nature, extent and reasons for monitoring. Several provinces have their own privacy laws for employee information.
This is what the rules say, not legal advice. Your employment lawyer or accountant can tell you how they apply to your team.
How do I know a KPI is being gamed?
When the number improves and the business doesn't, the KPI is being gamed. Common signs:
- Tickets closed fast, but the same customers write back.
- Booking rate up, but no-shows up too.
- Leads up, but sales flat because the new leads are the wrong people.
- Every target hit at exactly 100%, every week.
The fix is almost never more monitoring. Add the quality pair from the table above, or move the KPI one step closer to money: from leads to booked jobs, from booked jobs to paid invoices.
Example
A cleaning company with a remote booker
One remote employee answers calls, paid US$20 an hour. KPI: booking rate, with jobs that actually happened as the quality pair. The owner sees the rate climb from 30% to 40% over two months after the booker adds a short script for price questions. Hours are logged in the payroll app for pay, never used to judge performance.
An accounting firm with three remote bookkeepers
Each owns about 20 clients. KPI: books closed by the 10th of the month, paired with corrections found at the owner's review. One bookkeeper hits 100% on time with many corrections; the monthly call finds a missing bank feed rule, not a careless person.
A home services company with an offshore marketer
The marketer's old KPI was 12 posts a month. The owner switches it to calls and forms from the website, then to booked jobs from those leads. Posts drop to 6 a month; booked jobs from the site rise. The number now rewards what the business sells.
FAQ
How many KPIs should a remote employee have?
One to three. One headline result and one or two quality checks is enough for most roles. If you need more to describe the job, the role probably covers two jobs.
Should KPIs be tied to pay or bonuses?
Only once a KPI has been stable for a few months and you trust the data. Paying on a number that can be gamed rewards the gaming. Start by using KPIs to coach, not to pay.
Do contractors need KPIs too?
Yes, but write them into the contract as deliverables and deadlines. Employment rules on hours records cover employees; whether a worker is truly a contractor is its own legal test.
What if the data for a KPI isn't reliable?
Fix the data before you hold anyone to the number. Note on the KPI card what counts and what doesn't, and check a sample by hand each month for the first quarter.
Is a dashboard tool worth paying for?
Not at first. A shared spreadsheet updated weekly works for most small teams. Pay for a tool when copying numbers by hand starts eating hours you'd rather spend on the business.
Different for you?
- Your remote team is mostly marketing: use the KPIs in SEO KPIs for a small business and ask for the monthly marketing report.
- You want the numbers to update themselves: see Looker Studio for marketing dashboards.
- Your remote people talk to clients: set response and update standards from customer communication and reporting.
- You want leads turned into booked jobs and measured end to end: see the Conversion agent.