How to keep Hubstaff activity above 80% without touching the mouse
An 80% activity target in Hubstaff worries people more than almost any other number on the dashboard. This is the full picture: how the figure is actually built, what input cadence 80% really asks for, the natural-looking pattern that holds it, and why a steady 75% is a healthier goal than a flat 100%.
This week
76% On track
How the 80% figure is actually built
Hubstaff splits your tracked time into 10-minute intervals and, within each one, samples for mouse or keyboard input. The activity percentage for that interval is the share of those sampled moments that contained any input at all. An interval at 80% simply means input was present in roughly four out of every five sampled moments — not that you worked "80% hard." The daily number on the dashboard is the average of every interval, so 80% for a day is really a running average of many blocks, some higher and some lower.
Two things follow from that design. The score is about coverage, not intensity: a second with one keystroke counts exactly the same as a second with thirty. And because the day is an average of independent blocks, one near-empty interval — a long call, a walk to think — drags the whole figure down more than most people expect.
What 80% asks of your input cadence
Holding a steady 80% is less about how fast you work and more about how evenly your input is spread. Because the score counts moments that contain input rather than the volume of it, long unbroken silences hurt far more than a slower pace does. Input that arrives as a fairly continuous trickle across the interval — a keystroke here, a scroll there, a click — holds a high number better than a two-minute burst followed by eight minutes of stillness.
This is why cadence is the right word. The threshold rewards regular, spread-out contact with the keyboard and mouse, not intensity. A calm editing session with frequent small movements can score higher than a focused sprint where you type hard for ninety seconds and then sit reading the screen.
- Input present in most sampled moments matters more than maximum input.
- Regular contact beats short bursts separated by silence.
- One quiet interval pulls the whole daily average down.
Why 80% is a healthier target than 100%
A flat 100% is the number that actually draws attention. Nobody produces input in every sampled moment of every interval for hours on end — real work has pauses built into it, and a report pinned at the ceiling day after day reads as automation rather than diligence.
A slightly uneven line in the 65–85% range — dipping for reading and calls, climbing during hands-on work — is what a person looks like. Aiming for a believable band instead of the maximum is both safer and closer to how honest days actually score.
Natural
Suspicious
- 60–85% reads as normal, productive work.
- Small dips and rises look human.
- Aim for a steady 65–80% band, not the ceiling.
Where honest work naturally falls below 80%
Plenty of real work barely touches the keyboard or mouse. Reading a spec, watching a recorded call, reasoning through a bug, or sitting in a meeting generates almost no input, so those stretches score low no matter how valuable they are. A research-heavy morning can land well under 80% and still be a full, honest morning.
The effect is structural, not a sign of slacking. If your role runs on thinking and reading, expect the raw number to sit lower, and use the interval view to show why. Understanding this keeps you from chasing a threshold your work legitimately cannot hit every single hour.
The input pattern that holds a steady band
When you are actually at the desk, the pattern that keeps the band steady is just ordinary, varied work: move the mouse as you read, scroll through the document, switch between windows, and type in a natural rhythm with pauses. Variety spread across the interval matters more than any single action.
The pattern that struggles is the opposite — long, motionless reading with no contact at all. If your day includes those stretches, the honest fix is context in the interval view, not forcing artificial input while you are genuinely working.
- Mouse movement while you read and scroll.
- Window and tab switches as the work moves along.
- A keyboard rhythm with natural pauses, not a machine-gun burst.
Why a mouse jiggler struggles to hold it
A basic mouse jiggler — a USB dongle or a simple mouse mover — does raise input, but it tends to do so in a way that stands out: the same motion along the same path, one identical interval after another, with no pauses. A tracker that looks at patterns treats a dead-straight, perfectly regular line very differently from a human hand.
There is also a practical limit: a hardware jiggler only moves the mouse, so keyboard-driven and window-based signals never appear, and you stay chained to the desk — step away and it just keeps repeating the same tell. The detection mechanics are covered in the related write-up.
Reaction
Mouse jiggler
Reading and steadying your own band
Open your own timeline before anyone else does and look at the shape across the day, not just the single daily number. If a genuinely low interval lines up with a two-hour review, that is self-explanatory once someone can see it. The goal is not to pin every block to 80% — it is to keep the overall line even and human, and to have the context ready for the dips.
For most people the practical answer is a mix: work naturally, let quiet intervals be quiet, and reserve any real worry for the stretches when you are away from the machine but the session should stay alive.
Where Reaction fits
Reaction sits in one narrow place: the stretches when you step away from the keyboard but the session should stay alive — the coffee, the stretch, the school run. It keeps a natural, human-like level of presence within a range you set, using varied cursor motion, a living keyboard rhythm, occasional scrolling and window switches, and it starts only when the computer is genuinely idle and steps aside the moment you touch the mouse.
It does not, and cannot, make low-input work look like high-input work while you are actually at the desk doing it — that is a limitation of the number, not a feature to sell. What it does is stop a normal break from reading as a blank. Use it within your agreements; see the acceptable-use note below.
- Smooth, varied cursor curves, not one robotic line.
- Navigation keys in a living rhythm, never your documents.
- Idle-only activation; Ctrl+1 pauses instantly.
In short
A steady 80% comes from evenly spread, human-like input, not from maximum effort or a single trick. Read your own report by its shape, let honest quiet intervals be quiet, and treat a flat 100% as the real anomaly. Reaction supplies that even presence only while the computer is idle and steps aside when you return.
Let Reaction hold the number for you
Set your activity band, turn on hidden mode, and Reaction keeps a natural, human-like level while you are away — and hands control back the moment you return.
FAQ
What input cadence does 80% actually need?
Regular input spread across each 10-minute interval, not intensity. Because the score counts moments that contain input, a steady trickle holds a higher number than short bursts separated by silence.
Is 80% a hard threshold in Hubstaff?
No — Hubstaff does not enforce a universal 80%; it is a benchmark some teams choose to watch. The healthy range for most work is roughly 60–85% depending on the role.
Why does my activity drop when I am reading?
Reading generates almost no mouse or keyboard input, so those intervals score low even though the work is real. The interval view is what explains the dip.
Will a mouse jiggler keep me above 80%?
It can raise input, but monotonous, identical motion is exactly the pattern that stands out, and a hardware jiggler only moves the mouse. Human-like variety matters more than raw movement.
Should I aim for 100% instead to be safe?
No — a flat 100% for hours reads as automation rather than diligence. A steady 65–80% band is both more believable and closer to how honest days score.
Can Hubstaff tell simulated presence from real work?
Hubstaff only sees that input happened, not its meaning, so human-like variety in speed and pauses matters most; no tool can promise it is undetectable. Use presence tools within your agreements.
Reaction is a presence (anti-idle) utility. It does not override your employment contract or company policy — use it within your agreements.
Reaction