.svg){kind=logo}
On this page
Measure the work, not the signal.
See productive time and utilization by team, not just what looks active.
Key takeaways
- The strongest evidence that remote work is getting done is whether agreed outcomes are delivered at the expected time and quality.
- Online status, instant replies, and constant computer activity may look productive, but they don't show whether meaningful work is getting done.
- Choose productivity measures that fit each role, using realistic team benchmarks and the employee's past performance to assess results fairly.
- When commitments are missed, check for unclear priorities, workload issues, and dependencies before drawing conclusions.
- When issues arise, discuss the change with the employee, agree on what happens next, and follow up on a set date.
- Work data gives you a clearer view of time use and work patterns, but it can't explain someone's intent or replace a conversation.
If you're asking how to know if remote employees are working, start by measuring clear outcomes based on set expectations. Check whether work is delivered on time and meets the agreed quality standards, look at how work moves through the team, and ask when something changes. That tells you whether work is getting done, which a status light can't.
Online status, instant replies, and visible computer activity are weak substitutes for evidence. If you're not measuring outcomes, you're measuring presence.
Why it's hard to know if remote employees are working
From a distance, it can be hard to tell if employees are working because managers lose the visual cues and physical interactions they had in the office. Replacement signals like online status and instant replies aren't as reliable.
This can create uncertainty that turns into productivity paranoia, where leaders doubt whether people are productive because they can't directly see work happening.
The gap showed up clearly in Microsoft's Work Trend Index. In its 2022 survey of over 20,000 workers, 87% of employees reported feeling productive at work. However, 85% of leaders said the shift to hybrid work made it challenging to feel confident that employees were productive.
The problem is that familiar office visibility was never an especially strong measure of output either. Someone could be at a desk all day while a project stayed stuck, and a manager would assume they were working. Replacing office visibility with green status indicators or expectations for instant replies doesn't solve this.
A more reliable approach is to decide in advance what good work should produce, when tasks should be completed, and how responsibilities move from one person to another.
What the research says about remote work productivity
Research suggests that remote or hybrid work doesn't necessarily lead to lower performance. Results still depend on how well leaders adapt expectations, communication, and support to the way their teams work.
A randomized trial published in Nature found that hybrid work reduced quit rates by one-third over the six-month experiment. The study involved 1,612 university-educated employees at Trip.com in China working in areas including engineering, marketing, accounting, and finance.
The researchers found no meaningful effect on performance-review outcomes over the following two years and no evidence of a difference in promotion rates. For computer engineers, hybrid work had no effect on the lines of code they wrote.
The evidence doesn't present a universal verdict on fully remote work. For a manager, the practical lesson is simple: don't begin with the assumption that location explains a performance change.
How to know if remote employees are working: five signals that matter
1. Committed work is delivered
Start with the clearest question: did the work you agreed on arrive when it was supposed to, at the level you expected?
Keep in mind that measuring outcomes only works if the commitment was clear in the first place. "Make progress on the project" is difficult to evaluate. A defined deliverable, customer response, or milestone gives you and the employee something concrete to work from.
Don't be quick to judge a missed outcome. It could be evidence of a delivery problem, not a performance one. A dependency may have failed, or priorities may have changed.
2. Work moves
When work moves between people without hiccups or delays, it's a sign of healthy remote work productivity.
Look at whether handoffs happen, decisions get made, and people have what they need to continue. When work repeatedly stops at the same point, you have something specific to investigate.
Check the dependency before blaming the person closest to the delay. A stalled task can reflect missing information, an overloaded reviewer, or another upstream problem.
3. Quality holds
Consistent quality is a stronger signal than raw output volume.
Look at whether issues like rework, errors, and rejected deliverables are staying within the person's normal range. A sudden change can justify a conversation even when the person's overall output appears unaffected.
Context is important here too. A harder assignment may take longer or require more revision without representing weaker performance. Compare like with like before turning a quality change into a conclusion.
4. Responses arrive within agreed windows
Remote employees don't need to answer every message immediately to be working effectively. Measuring instant replies may push people to interrupt focused work or cut customer conversations short just to respond.
What matters is that communication meets agreed-upon expectations. A support lead handling urgent escalations may need short response windows, while an analyst doing deep research may have longer ones.
Make those expectations explicit. If someone repeatedly misses an agreed response window and work is affected, you have a useful signal. An unanswered message by itself tells you very little.
5. Workload is reasonably distributed
A person's share of the work should be similar to that of their peers, with room for differences in employee experience and task complexity. Workload differences don't mean the affected employee is at fault.
A consistently light load can indicate that someone is underused, but it doesn't tell you why. Work may not be reaching them, or their responsibilities may be unclear. Another teammate may be taking on tasks before they're distributed. On the other hand, someone carrying too much work may be slower because the team has assigned too much.
Good team workload management looks at distribution before interpreting an individual result.
Signals that mislead
Some cues feel reassuring because they're easy to see, such as green status, instant replies, and mouse or keyboard activity. But they're still weak evidence of whether useful work is being completed.
These visible cues mislead managers most often:
| Signal | Why it misleads |
|---|---|
| Green online status | Online status shows availability or software state. It says nothing about whether work is getting done. |
| Instant replies | Just because someone doesn't reply immediately doesn't mean they aren't working. Fast responses are important for some roles, but they can interrupt focused work for others. Judge against agreed response windows instead. |
| Camera always on | Camera presence says little about the quality, difficulty, or completion of someone's work. |
| Late-night messages | Working late isn't proof of high productivity. In fact, it may reflect poor workload distribution or a difficulty disconnecting. It may also relate to scheduling or time zones. |
| Constant mouse or keyboard activity | Computer activity isn't the same as quality output. Someone can be on their computer all day and deliver very little. Employees may also use devices such as mouse jigglers to simulate activity when they feel pressured to be constantly active. |
The above cues are often interpreted as positive productivity signals when they may in fact indicate the opposite. Repeated late-night activity, for example, may be a reason to examine workload and other early signs of burnout. It doesn't mean you should expect the same availability from everyone.
How to measure remote work productivity fairly
When determining how to measure remote work productivity, start with defining and measuring outcomes that fit the role. Remote employee productivity isn't one universal number. A useful measure tells you whether the person is producing the results their role exists to produce.
Managers must also take into account quality, experience, collaboration, and responsibilities that don't fit neatly into a count. Recent hires shouldn't be expected to match the output of senior employees, and people whose work depends on others shouldn't be held solely responsible for delays beyond their control.
Three rules keep the measurement fair:
- Define outcomes by role: A support agent, salesperson, engineer, and operations specialist contribute in different ways, so measuring them with the same output formula would distort the work. The table below offers starting points for what to measure in each role.
- Compare results against relevant team baselines: Don't invent an imaginary ideal output number. Set a realistic baseline that reflects how your team operates, including its service levels, work mix, staffing, and responsibilities.
- Compare people with their past performance: Comparing someone's current work with their past performance can reveal changes that team comparisons alone may miss.
Starting points by role:
| Role | What to measure |
|---|---|
| Support | Resolved cases, resolution time, quality of resolution |
| Sales | Relevant pipeline activity, opportunities advanced, deals moved |
| Engineering | Completed or merged work, review turnaround, quality and reliability |
| Operations or back office | Cases processed, turnaround time, accuracy and rework |
None of these measures should serve as a stand-alone productivity score. Ideally, they should be used together to avoid missing important context. For example, two support employees may close different numbers of cases because one handles much more complex issues.
What to do when you think someone isn't working
When you're concerned someone may not be working, don't jump to conclusions. Look at the evidence in a consistent order, and start a conversation if you still have concerns.
- Check the work first: Look at the five signals above. Identify the specific commitment, handoff, quality measure, communication expectation, or workload pattern that changed. Compare that with the employee's past performance and any relevant baselines before taking action. Avoid acting on a general feeling that someone seemed unavailable.
- Check the conditions: Ask whether priorities were clear, the workload was reasonable, required tools were working, and dependencies arrived on time. This is important because managers often see the result of a process problem at the individual level first. Acting without that context can lead you to hold the wrong person responsible.
- Ask about the change without assigning a motive: When discussing an issue with an employee, keep the conversation anchored to the change in productivity. Avoid assigning blame or making assumptions about an individual. For example, you could say: "The last two reviews came in after the date we agreed, and that delayed the next handoff. That's different from the previous few months. What changed?"
- Agree on what happens next: Clarify the next expected result and when it's due. Then choose a date to review it. Discuss what support is needed or which dependencies need attention to make the work go more smoothly. Give the employee room to explain what's realistic and show that you're willing to work together to make the change happen.
- Follow up: Review the outcome on the agreed-upon date. If performance has recovered, you have useful evidence that the change was addressed. If it hasn't, you now have a clearer pattern and a more specific management issue to handle.
Keep in mind that the process above is different from dealing with time theft, a separate situation in which paid time was recorded but work wasn't performed. Missed output alone doesn't suggest time theft.
How work data helps, and where it stops
Work data is useful when it gives managers and employees more context for a conversation. On its own, it explains very little. A manager may see that output has slowed but still need to understand whether the team is dealing with overload, uneven assignments, or changing demands.
Having shared data about time use and work progress gives you and your employee a clearer starting point for discussing what's getting in the way.
Instead of relying on green status or webcam activity, read work patterns alongside agreed outcomes. They show where progress is slowing and what to discuss with your team.
Work data can't tell you why a change happened. It can't show whether someone meant to miss a commitment, had a family emergency, or got an unclear instruction, and it can't measure effort or intent. Tools for remote and hybrid teams can give you and your employees a shared view of work patterns, but the conversation still has to happen. Tell your team what you measure and why before you start, so everyone works from the same facts.
Measure the work, not the presence
When you can't see your team working, it's easy to look for reassurance in online status or quick replies. But those presence signals can't tell you if work is getting done. To improve remote and hybrid visibility, you need to measure the work itself.
Insightful's Workforce Analytics shows how remote and hybrid teams spend their time, with workload and capacity by team. You and your team can then discuss a doubt with the same facts in front of you.
Start a free trial to see how work actually happens on your remote team.
Frequently asked questions
How can I tell if my remote employees are actually working?
Review completed assignments against the deadlines and standards you agreed on. Reliable results give you more useful evidence than a green status light. For longer projects, check meaningful milestones. If progress slips, discuss the gap with the employee before deciding what it means.
Do remote workers work less than office workers?
Working remotely doesn't automatically mean someone does less work. Research in Nature found no drop in performance among more than 1,600 employees on a hybrid schedule with two days a week at home. But that result doesn't prove that every remote arrangement will have similar outcomes. Job design, expectations, collaboration, and management all impact remote performance.
How do you measure remote employee productivity?
Choose measures that reflect each role's contribution, such as the quality and timeliness of completed assignments. Consider comparable work across the team as well as the employee's previous results. Adjust your interpretation for task difficulty and other responsibilities. A higher count shouldn't automatically earn a better assessment.
What are the signs a remote employee isn't working?
Repeatedly missed commitments, stalled handoffs, declining quality, or a persistent change in workload contribution can indicate that someone isn't working. However, none of these alone prove someone isn't working. First check priorities, dependencies, workload, and other conditions that could explain the change.
What is productivity paranoia?
Productivity paranoia describes leaders' doubts about whether employees are productive. This may occur when leaders can't directly see work happening, such as in remote or hybrid work situations. In a report, Microsoft found a wide perception gap between employees who said they felt productive and leaders who said hybrid work made assessing productivity more difficult.
Should I use software to check if remote employees are working?
Work data software can provide useful context about time use, workload, capacity, and changes in work patterns across your team. It shouldn't be the only basis for judging performance. Use it alongside agreed outcomes and quality expectations to address productivity concerns.
