By Moneer Hussain · Published October 14, 2026 · 8 min read
Short answer: In employee monitoring software, active time is tracked work time when the computer is receiving keyboard or mouse input. Idle time is tracked time with no input for longer than a set threshold. Together they make up total tracked time. Idle does not mean someone stopped working: reading, phone calls, meetings, thinking and offline tasks all look idle. Read active and idle time as weekly patterns, compare them with the role and the output, and ask before concluding anything.
This guide explains how active and idle time are measured, why the numbers differ between roles, how to read them in a weekly review and which mistakes to avoid. It is written for managers of remote and office teams who use, or are considering, monitoring software.
The definitions
| Term | What it usually means | What it does not mean |
|---|---|---|
| Tracked time | Time the desktop app was recording during work hours | Paid hours, unless your policy says so |
| Active time | Tracked time with keyboard or mouse input | Productive or high-quality work |
| Idle time | Tracked time with no input for longer than the idle threshold | Time someone was not working |
| Idle threshold | How long without input before time counts as idle | A judgement about the person |
| Activity share | Active time as a share of tracked time over a period | A performance score |
Exact definitions vary between vendors. Some tools label each second as active or inactive and summarise it in blocks; others mark a period as idle once input stops for longer than a limit the organisation sets. Before you compare numbers from two tools, check how each one defines them.
How software measures active and idle time
A desktop app on the work computer watches for input signals, keyboard presses and mouse movement, while tracking is running. It does not need to know what was typed. The logic is simple:
- Tracking runs during work hours.
- While there is input, time counts as active.
- When input stops for longer than the idle threshold, the time from that point counts as idle.
- When input resumes, time counts as active again.
The threshold matters. A very short threshold marks normal pauses (reading an email, listening to a customer) as idle. A very long one hides genuine breaks. Choose one that fits the work, and state it in your policy.
Why idle is not the same as not working
Many legitimate tasks involve little or no keyboard and mouse input:
- Reading: supplier contracts, marketplace policy updates, a customer's long complaint.
- Calls and meetings: especially on a phone or a separate device.
- Thinking and planning: working out a pricing strategy or a listing structure.
- Training: watching a walkthrough video.
- Physical work: packing orders, checking stock, labelling returns.
- Interruptions outside anyone's control: a power cut, an internet outage, a frozen computer.
The reverse is also true: active time is not proof of useful work. Someone can be very active in the wrong spreadsheet. That is why active and idle time should always be read alongside other information.
What normal looks like depends on the role
There is no universal "good" percentage. Compare people with their own history and with the nature of the role, not with a target picked from the internet.
| Role | Typical reasons for idle time | What to read alongside it |
|---|---|---|
| Order processing / data entry | Short pauses between batches | Orders or records processed |
| Customer service (chat and email) | Reading long messages, waiting for replies | Messages answered, response times |
| Voice support / call center | Calls on a headset with little typing | Calls handled, attendance |
| Product research | Reading, comparing, thinking | Products researched and approved |
| Design and content | Planning and reviewing | Listings or designs delivered |
| Team leads and managers | Calls, meetings, reviews | Team outcomes |
How to read active and idle time in a weekly review
1. Look at the week, not the hour
Single hours are noisy. A long idle stretch on Tuesday afternoon tells you very little; a pattern across three weeks tells you something worth a conversation.
2. Compare each person with themselves
A change from someone's usual pattern is more informative than a difference between two people in different roles. If a usually steady team member's active time drops for two weeks, ask how they are doing and whether something changed in their work.
3. Check the apps and websites used
App and website usage gives context. A high idle share with a video-call app open suggests meetings. Low active time with a helpdesk open may mean a quiet queue. Our guide to tracking remote employees' hours fairly explains how these records fit together.
4. Check attendance
Make sure the shift itself was right before reading the activity inside it. A short tracked day might be an approved early finish or a missed check-in, not a performance issue.
5. Compare with output
The question that matters is whether the work got done: orders shipped, tickets resolved, listings published. If output is good, an unusual activity share is rarely worth acting on.
6. Ask before concluding
When something looks wrong, start with a private, neutral question: "I noticed Tuesday afternoon looks quiet in the records, was there anything going on?" Most of the time there is a simple answer.
Patterns worth a conversation vs common false alarms
| Worth a conversation | Usually a false alarm |
|---|---|
| A sustained drop over several weeks with lower output | One quiet afternoon |
| Regular long idle stretches during peak queue times with tasks left open | Idle time during scheduled meetings |
| Checked in, but no tracked time for most of the shift | Idle time during a known power or internet outage |
| Active time far beyond shift hours, suggesting overwork | Lower activity in reading-heavy roles |
Note the last item in the left column. Monitoring data can also show when someone is working too much. That is a wellbeing and workload issue worth acting on just as quickly.
Mistakes to avoid
- Setting a target activity percentage for everyone. It pushes people to generate input rather than do good work.
- Deducting pay automatically for idle minutes. Agree in your policy how idle time is treated, and review it in context.
- Ranking people publicly. Share individual numbers privately, if at all.
- Using a very short idle threshold. It turns normal reading and listening into "idle".
- Reading activity without attendance and output. One number never tells the whole story.
Explaining active and idle time to your team
People worry less about activity tracking when they understand it. Tell your team:
- What counts as active and idle, and the idle threshold.
- That idle time is expected and is not treated as wrongdoing.
- How meetings, calls, breaks and outages are handled.
- That they can see their own records and ask about any entry.
Our employee monitoring policy template includes a section you can copy.
Active and idle time in ECOMHUTSY Team Monitoring
ECOMHUTSY Team Monitoring records active and idle time during work hours through its desktop app and shows it in the web portal, next to the information you need to read it fairly:
- A live view of who is working right now.
- Attendance and check-in.
- Apps and websites used, and for how long.
- Screenshots at an interval you choose, deleted automatically after 3 to 15 days.
- Reports for people and teams.
- Company time zone settings and roles and access controls.
Monitoring is transparent: your team knows it is running, and company data stays private to your company. Pricing is $3 USD per user per month, minimum 2 users, with a 1-month (30-day) free trial; a card is required to start. See pricing.
Frequently asked questions
What is the difference between active time and idle time?
Active time is tracked time with keyboard or mouse input. Idle time is tracked time with no input for longer than a set threshold. Both are measured during work hours.
Does idle time mean an employee is not working?
No. Reading, calls, meetings, planning and physical tasks can all register as idle. Treat idle time as a prompt for context, not as evidence.
What is a good active time percentage?
There is no universal figure. It depends on the role. Compare each person with their own usual pattern and with their output, rather than with a fixed target.
Can idle time be used for payroll?
Only if your policy says how, and staff have agreed to it. Many teams pay on attendance and approved hours, and use active and idle time as context rather than as an automatic deduction.
How is idle time handled during meetings or calls?
It depends on the tool and your policy. Agree a simple rule, such as noting scheduled meetings, so that reviewers know to expect idle time in those periods.
See active and idle time in context
Book a free live demo to see how active and idle time sit alongside attendance, apps and websites, and reports in Team Monitoring. Or start the 1-month free trial and review a real week with your team.
Book a free live demo · Start the 1-month free trial
Sources
- Clockify Help, Activity monitoring basics (example of a vendor idle-time definition): https://clockify.me/help/activity-monitoring/overview/activity-monitoring-basics
- UK Information Commissioner's Office, Data protection and monitoring workers: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/employment/monitoring-workers/data-protection-and-monitoring-workers/
