Hubstaff activity levels measure how much of your tracked time contains mouse or keyboard input—not how much useful work you completed. A low percentage can accompany productive reading, planning, or calls. A high percentage can accompany routine clicking. You need the task context before treating either number as a verdict.
If your report looks lower than expected, the useful next step is to understand the calculation, check the session being measured, and explain legitimate low-input work. This guide focuses on interpreting your percentage. It does not offer a target score to fake or repeat the broader Hubstaff employee monitoring guide.
Key takeaways
- Activity percentage counts seconds with input, not the value of the work.
- Mouse and keyboard percentages can overlap; do not simply add them.
- A meeting-heavy day and a data-entry day should not be judged as identical work.
- Check the date, time zone, project, tracking source, and relevant settings before comparing reports.
- Resolve missing context with accurate work records, not unnecessary clicking.
In this guide
- How Hubstaff Calculates Activity Percentage
- Why Mouse and Keyboard Percentages Do Not Add Up
- What Is a Good Hubstaff Activity Level?
- Check That You Are Reading the Right Report
- Why Your Activity Can Be Low During Real Work
- What to Check When a Familiar Task Suddenly Scores Lower
- How to Explain a Low Score Without Creating Extra Busywork
- Can a Jiggler Increase the Percentage?
- Frequently Asked Questions
- The Bottom Line
How Hubstaff Calculates Activity Percentage
Hubstaff’s calculation guide says each tracked second is classified by whether mouse or keyboard input occurred. For a complete ten-minute segment, divide active seconds by 600 and multiply by 100. Multiple actions within one second do not create multiple seconds of total activity. Hubstaff says it records input presence rather than the content of typed keys.
Here is an illustrative calculation, not a benchmark or measured test: 240 active seconds in a complete 600-second segment produces 40% activity. That tells you about the distribution of input. It does not say the remaining 360 seconds were wasted, nor does it describe the quality of anything produced.
| Illustrative ten-minute segment | Active seconds | Activity percentage | What still needs context |
|---|---|---|---|
| Mostly reading with occasional navigation | 90 | 15% | Whether the reading advanced the task |
| Mixed editing and thinking | 270 | 45% | What decisions or changes were made |
| Input-heavy task | 450 | 75% | Accuracy and usefulness of the result |
The scenarios are deliberately hypothetical. They show why the same calculation can describe very different jobs. Do not use the example percentages as desired employee scores; no number in this table is a performance recommendation.
Why Mouse and Keyboard Percentages Do Not Add Up
You may use the mouse and keyboard within the same second. That second belongs to both input categories, but it is still only one second in the total. Adding the two category percentages can therefore overstate combined activity.
For example, suppose an illustrative 100-second period contains 30 seconds of keyboard-only input, 20 seconds of mouse-only input, 10 seconds containing both, and 40 seconds containing neither. Total activity is 60%. Keyboard activity is 40% and mouse activity is 30%; adding those last two numbers gives 70%, because the overlap was counted twice.
This is a counting distinction, not evidence of a faulty report. Before raising a discrepancy, ask whether you are comparing total activity with one input category or with the sum of both. Keep the time interval identical throughout the comparison.
What Is a Good Hubstaff Activity Level?
There is no single percentage that demonstrates good work across every role. Hubstaff’s own calculation guidance discourages activity quotas and recommends interpreting trends with context. Jobs and tasks differ in how much physical input they require.
A designer adjusting objects, a support agent listening to a caller, and an analyst reading a long report may all be working effectively while generating different input patterns. Even one person’s day can alternate between these modes. Compare similar tasks before drawing conclusions from a change.
If you have been given a minimum score, ask what it is intended to measure and how approved low-input work is handled. A useful question is: “Does this expectation apply to calls and research, or only to input-heavy tasks?” That turns a vague argument over a percentage into a specific discussion about the job.
A high score is not automatically better. More activity might reflect unnecessary navigation, repeated corrections, or a cumbersome workflow. Less activity might reflect a better shortcut, a clearer plan, or work happening away from the screen. The output still matters.
Check That You Are Reading the Right Report
Hubstaff’s activity overview documents filters for dates, time zones, projects, tracking source, time type, and activity levels. It also distinguishes activity percentage from other report measures, such as application classifications and focus time. Those labels should not be used interchangeably.
The overview says mobile and web-timer time, manual time, breaks, and projects excluded from activity tracking are not included in the activity calculation. That means total time and the time represented by an activity percentage may have different scopes. A missing percentage is not necessarily a zero.
- Choose the same date and time zone. A late shift can cross a calendar boundary.
- Check the project. A project filter can hide part of the day you remember.
- Check the tracking source. Do not compare a desktop activity segment with a different source as though both collect the same data.
- Check the duration. A short fragment and a full work block are not equally informative.
- Read the exact metric label. Input activity is not the same thing as productive-app classification.
Take a note of the filters when asking someone else to review the report. “Tuesday, my local time, the customer-research project, desktop tracking” is more actionable than “my numbers are wrong.” Avoid sharing screenshots that reveal customer information unnecessarily.
Why Your Activity Can Be Low During Real Work
Reading and analysis
Understanding a document is not continuous typing. A person can spend several minutes evaluating a clause, comparing figures, or thinking through a problem without generating many input events. Write the resulting decision or finding in the normal task record instead of scrolling solely to create activity.
Calls and meetings
Listening, discussing, and presenting may require limited interaction with the monitored computer. A task note and meeting record can explain the interval more accurately than an input graph. If meetings are a regular part of your role, agree in advance how that time should be categorized.
Background jobs
A build, upload, export, or render can run while you monitor its progress or work through the next step. Separate a genuinely supervised task from a job you started and then left unattended. Describe what you actually did, and follow the team’s time-recording rules.
Off-screen work
Planning on paper, reviewing printed materials, and in-person collaboration can be important parts of an assignment. If the role expects these activities, the reporting process needs a way to represent them. Do not invent keyboard activity to fill a measurement gap.
What to Check When a Familiar Task Suddenly Scores Lower
Start with a comparison you can explain. If you normally write in one app but spent today reviewing a document, the task changed. If the task really stayed similar, note what else changed: computer, input device, remote session, client version, project, or organization policy.
Check that the expected desktop client is running and tracking the intended task. Use ordinary work to observe the behavior; do not generate synthetic traffic or delete records as a test. If a keyboard or mouse also misbehaves in normal applications, describe that symptom separately.
For a remote desktop, be precise about where the tracker runs and where you are interacting. Do not assume a locally displayed remote session behaves identically to every native application. Give support the setup and a timestamp, rather than asserting a cause without evidence.
When requesting help, provide the operating system, client version, affected interval, expected task, tracking source, and what you observed. Do not include passwords, customer records, or a full private screen recording unless the organization has an appropriate secure support process.
How to Explain a Low Score Without Creating Extra Busywork
Use evidence that already belongs to the task: a short research summary, a completed ticket, a reviewed document, a meeting outcome, or the delivered file. The goal is context, not a second surveillance system you maintain for yourself.
A concise message could be: “The lower-input period from 10:00 to 10:40 was the requirements review. The resulting questions are in the project note. Can we confirm how review tasks should be categorized so the report reflects that work?” This example is a communication template, not a statement about an actual employee.
Ask for a repeatable rule if the issue recurs. Which task category should you use? Who approves corrections? Which deliverable shows completion? What should happen when the day is mostly meetings? A clear answer is more useful than repeatedly defending a number after the fact.
Our Hubstaff setup and reporting guide provides broader navigation context. For the difference between input counts and content capture across tools, see the keystroke monitoring guide.
Can a Jiggler Increase the Percentage?
Generated input may affect an input-based metric, but that does not make it a reliable or appropriate way to account for work. It cannot supply the missing explanation for a task, improve a deliverable, or establish that an employee was present. It may also conflict with company policy.
Mouse movement, keyboard simulation, screenshots, app usage, and work output are different signals. Changing one does not hide the others. More aggressive automation can interfere with documents or trigger actions in an open application.
If the legitimate problem is a computer sleeping during an approved task, address power behavior. If it is a low-input job being judged by an input metric, address the reporting convention. The broader employee monitoring guide explains why one activity number never describes the whole system.
Frequently Asked Questions
Does 40% Hubstaff activity mean I worked only 40% of the time?
No. It describes input activity within the measured period, not the percentage of useful work completed. Reading, calls, and planning need additional context before anyone interprets the score as performance.
Why do mouse and keyboard percentages exceed the total when added?
The categories can overlap within the same second. Total activity counts that second once, while both categories can include it. Compare the combined metric directly rather than adding the component percentages.
Is there a good activity percentage for every employee?
No universal score fairly represents every role. Input-heavy tasks and low-input tasks produce different patterns. Agree on expectations for comparable work instead of treating one threshold as proof of productivity.
Should I keep clicking while reading?
Unnecessary clicks do not explain the reading or improve its result. Record the task and its outcome in the normal work system. If reading is repeatedly misinterpreted, ask how it should be categorized.
What should I do if the score looks technically wrong?
Check the date, time zone, project, tracking source, and exact metric first. Note the client version and an affected interval if the discrepancy remains. Ask support or your administrator to investigate without deleting or falsifying work records.
Does a higher activity score guarantee better work?
No. Input frequency says little about accuracy, judgment, or the value of a result. Review the task and deliverable alongside the number. A useful report starts a conversation rather than replacing one.
The Bottom Line
Treat Hubstaff activity as a narrow input measure. Understand the denominator, compare like-for-like tasks, and document legitimate work through the channels your team already uses. When a number and the job disagree, fix the interpretation or workflow instead of manufacturing a busier screen.
Method: official Hubstaff calculation and activity-report documentation checked September 18, 2026. Numerical examples are illustrative calculations, not benchmarks or hands-on test results.
Understand the limits before choosing an activity tool
Trick Tack offers configurable mouse, keyboard, scrolling, and app activity. It does not disable screenshots or hide screen content. Use it only where permitted.
Try Free for 7 DaysRead the documentation
