Summary
A good activity level in employee monitoring is one that fits the role and stays consistent with that person's and team's normal pattern, not a fixed number to hit. Activity level, often shown as an activity percentage, is the share of tracked work time in which the computer registered keyboard or mouse input. It measures input, not output: reading, calls, meetings and thinking all register as low activity even when they are the work. That is why 100% is neither realistic nor desirable, and why a developer, a support agent and a sales rep will show very different healthy patterns. Use activity levels to spot changes over weeks, combine them with outcomes, and let employees see their own data. Treat a sudden drop or an unnaturally high, uniform rate as a question, not a verdict.
E-Monitor logs every active and idle transition with a timestamp and shows the same activity timeline to the employee and the manager, so activity levels are read in context. Start free →
What an Activity Level Measures
An activity level is a measure of how much of an employee's tracked work time showed keyboard and mouse activity on their computer. Most monitoring tools work in short intervals: for each slice of time, the agent checks whether there was any input, and the activity percentage (sometimes called the activity rate) is the share of intervals, or minutes, that had some. If an employee was clocked in for eight hours and the computer registered input during six of them, their activity percentage for the day is 75%.
Three details matter when you read the number:
- It counts presence of input, not its quality. One mouse movement in a slice can make that slice count as active, depending on the tool. Typing a strategy document and scrolling a news site look the same.
- It depends on the idle threshold. In E-Monitor, a period counts as idle when no keyboard or mouse input is registered for a configurable threshold. A short threshold makes the same workday look less active than a long one, so numbers are only comparable when the threshold is the same.
- It only covers tracked time. E-Monitor captures activity on company devices during clocked-in hours only, so the denominator is work time, not the whole day.
Activity level is one input among several in employee monitoring software. It is useful context. It is not a measure of how much work got done.
Why 100% Activity Is Neither Possible Nor Desirable
Plenty of real work happens without touching a keyboard or mouse:
- Reading a long document, contract, spec or report on screen.
- Phone calls and video calls, especially when the employee is listening.
- In-person meetings, whiteboarding and design sessions.
- Thinking through a problem before writing code or a proposal.
- Reviewing printed material, taking handwritten notes, or working on a second device.
- Helping a colleague at their desk, or a customer at a counter.
- Short rest breaks, which are healthy and, for non-exempt employees in the U.S., generally paid time.
An employee whose input never stops is either doing very repetitive data entry, or something is off. Pushing people toward a higher activity percentage rewards busy-looking work over thoughtful work, and it encourages exactly the behavior you least want: moving the mouse to look present. Our article on why activity tracking fails explains how input targets get gamed.
What Is a Good Activity Level for Different Roles?
There is no universal good activity level. The healthy pattern depends on how the job is done. The table below describes typical patterns qualitatively; set your own reference points from your team's data rather than borrowing a percentage from another company.
| Role | Typical work pattern | What a healthy activity level tends to look like |
|---|---|---|
| Data entry, transaction processing | Continuous structured input in a few systems | Consistently high, with regular short breaks |
| Customer support (chat, email, ticket) | Steady typing in help desk and CRM, short gaps between tickets | High during queue time, dipping when volume drops |
| Customer support (voice) | Long calls with intermittent notes | Moderate, with low stretches during calls |
| Software engineering | Bursts of coding between reading, reviewing and thinking | Uneven, with long focus blocks and quieter periods |
| Sales and account management | Calls, video meetings, CRM updates, email | Moderate and variable, lower on heavy call days |
| Design and creative | Detailed mouse and pen work mixed with review | High during production, lower during feedback and research |
| Managers and team leads | Meetings, one-on-ones, reviewing others' work | Often lowest on the team, and that is normal |
| Analysts, legal, research | Long reading sessions punctuated by writing | Moderate, with long low-input stretches while reading |
Role is not the only factor. The same person can have a very different activity level from one week to the next because of the work itself: a planning week full of workshops, a release week of heads-down coding, a quarter-end week of reconciliations. Hybrid schedules add another layer, because office days often carry more meetings and conversations than home days. Before reading a week as unusual, check the calendar and the work that was assigned. A good activity level for a given week is one that makes sense for what the person was asked to do that week.
The practical takeaway: compare people with their own history and with peers in the same role, not across roles. If you customize monitoring settings by team, apply the same idle threshold within a role so comparisons stay fair.
What Low Activity Levels Can and Cannot Tell You
A low activity level means the computer saw little input. On its own, it cannot tell you why. Common explanations include:
- A meeting-heavy or call-heavy week.
- Offline work: site visits, training, printed reviews, a workshop.
- Working on a device that is not monitored, such as a lab machine or a phone call from a desk phone.
- A slow week for work coming in, which is a workload signal, not a performance one.
- Illness, burnout or personal difficulty, which deserves a supportive conversation.
- Disengagement, which is possible but is the last explanation to assume, not the first.
What low activity can usefully indicate is a change. A person or team whose activity drops well below their own normal pattern for several weeks is worth a check-in. A single quiet day is not. The employee idle time reduction guide covers how to respond when idle time is genuinely too high, and the steps in setting a productivity baseline show how to define "normal" before you judge changes.
When Very High Activity Is a Red Flag
Most managers worry about low activity. Unusually high, uniform activity can be the more informative signal. Human input is irregular: it speeds up, slows down and stops. A rate that sits near the top all day, every day, with no natural gaps, can mean:
- A mouse jiggler or input automation. Hardware or software that simulates movement produces steady input without any real work. It usually shows up as long stretches of active time with no application or window changes. See how employers detect mouse jigglers for the patterns and how to respond fairly.
- Overwork. Long hours of continuous input with no breaks can point to an unsustainable workload or after-hours pressure, which is a risk to manage, not a result to praise.
- A role designed around input volume. In some processing roles high activity is normal, which is why role context matters.
In E-Monitor, every active and idle transition, app launch and window focus change is written to the activity log with a timestamp, so a manager can see whether high activity came with real application use or with none.
Activity Level vs Idle Time vs Productivity Score
These three terms are often confused. They answer different questions:
| Metric | Question it answers | Main limitation |
|---|---|---|
| Activity level | How much of tracked time had keyboard and mouse input? | Input is not output; ignores what the input was for |
| Idle time | How much tracked time had no input for longer than the threshold? | Offline work and calls look the same as being away |
| Productivity score | How was time spent, weighted by role-relevant apps, focus and consistency? | Depends on how apps and websites are classified for each role |
Idle time is roughly the inverse of activity level for the same threshold. A productivity score goes further: in E-Monitor it is built from four pillars, active time, productive app and website usage, focus blocks of 30 minutes or more, and consistency against a 30-day rolling average, and each score can be broken down into the raw events behind it. We explain that calculation in employee productivity scoring and will not repeat it here. The key point is that activity level is one ingredient, not the whole picture.
How to Use Activity Levels Fairly
- Look at trends, not single days. Weekly and monthly patterns smooth out meeting days, travel and sick days. Our piece on productivity trends vs snapshots shows why.
- Start at team level. A team-wide drop usually points to a process, tooling or workload issue. Look at individuals only when one person diverges from their own pattern.
- Compare within roles. Use the same idle threshold for everyone in a role and compare people with role peers, never across functions.
- Combine with outcomes. Pair activity data with the results that define the job: tickets resolved, code shipped, deals progressed, reviews completed. Our guide to evaluating remote employees covers how to weigh both.
- Ask before you conclude. When a number looks wrong, ask the employee what their week looked like. Most anomalies have ordinary explanations.
- Let employees see their own data. In E-Monitor, every employee has a personal dashboard showing their own activity timeline, productive and unproductive time, and active and idle patterns. Self-access is on by default and managers cannot disable it, so nobody is judged on data they cannot see.
- Never use activity level alone for pay or termination decisions. It is context for a conversation, not evidence of performance.
Data quality also matters. Misconfigured thresholds, unmonitored devices and time zone errors can distort activity levels; see employee monitoring data accuracy for the common causes.
Do You Need Keystroke Data to Measure Activity?
No. Activity level only needs to know whether input happened, not what was typed. In E-Monitor, activity logs capture metadata only (app names, website domains, window titles, timestamps and durations), never document content or message text. Optional keystroke intensity measures typing volume, not the characters typed, and it is off by default. Most teams do not need it to read activity levels sensibly. If you do enable it for a role, disclose it in writing first.
For the broader view of how activity, focus time and app usage come together, see E-Monitor's productivity monitoring, where every number drills back to the activity events that produced it.
Related reading: Employee Productivity Scoring: How It Works (and How to Do It Fairly), Employee Idle Time Reduction: Industry Benchmarks, Strategies & ROI Guide, Can Employers Detect Mouse Jigglers? How Activity Fakers Show Up in Monitoring Data, How to Set a Productivity Baseline Before You Judge Anyone's Numbers, Employee activity tracking and monitoring software: every action logged, timestamped and audit-ready..
Frequently Asked Questions
1. What is a good activity level in employee monitoring?
A good activity level is one that matches the role and stays consistent with the employee's and team's normal pattern. There is no universal target. Roles with many calls, meetings or reading naturally show lower activity than data entry or chat support, and that is not a performance problem.
2. How is activity percentage calculated?
Activity percentage is usually the share of tracked work time, measured in short intervals or minutes, in which the computer registered keyboard or mouse input. The result depends on the idle threshold the tool uses, so numbers are only comparable between people tracked with the same settings.
3. Is 100% activity good?
No. Real work includes reading, calls, meetings, thinking and breaks, all of which register as low input. Sustained activity near 100% with no natural gaps is more likely to indicate automation such as a mouse jiggler, or unhealthy overwork, than exceptional performance.
4. What does a low activity level mean?
It means the computer saw little keyboard and mouse input. It does not say why. Meetings, calls, offline work, a slow workload or illness are common causes. Treat a sustained drop against the person's own baseline as a reason for a supportive conversation, not a conclusion.
5. Is activity level the same as productivity?
No. Activity level measures input on the computer, while productivity is about outcomes. A productivity score in monitoring software usually combines activity with app classification, focus time and consistency, and even that should be read alongside actual results.
6. Does measuring keyboard and mouse activity record what I type?
It does not have to. Activity measurement only needs to know that input happened. In E-Monitor, activity logs capture metadata only, and optional keystroke intensity counts typing volume, not characters, and is off by default.
7. Can employees see their own activity levels?
In E-Monitor, yes. Every employee has a personal dashboard showing their own activity timeline and active and idle patterns. Self-access is on by default and managers cannot turn it off.
Read activity levels in context, not as a target. E-Monitor logs active and idle time with timestamps, shows employees the same data managers see, and pairs activity with focus time and role-based classification. 7-day free trial, no credit card. Sign up →
