The main metrics
| Metric | What it measures |
|---|---|
| Time on versus time worked | The gap between being at the machine and producing |
| Productivity versus idle | The share of the shift with real activity |
| Programs and sites | Where the shift's time went |
| Clicks and words typed | The day's volume of work |
| Daily balance | Hours above or below the agreed workload |
How to read the numbers
The numbers are there to find bottlenecks, not to punish people. A drop in productivity usually points at slow tooling, a stuck process or overload — things that only surface once there is a measurement.
Compare a person with themselves
The useful comparison is the same person across weeks, not a ranking between people in different roles. A support analyst and a developer have activity curves that do not compare.
Look at the series, not the day
One bad day is noise. Three weeks of steady decline is a signal — and that is when a conversation with the team makes sense.
Reports and export
The dashboard closes the day on its own, per device and per team. Reports can be filtered by period, group and person, and exported to take into a management meeting without manual work.
Frequently asked questions
- Does idle time count meetings?
- A meeting with little keyboard and mouse activity shows as idle. That is why the reading has to account for the team's calendar, not just the number.
Up next
Typing monitoring
What it is, what it is for, where the limits are and how to enable it responsibly.
Keep reading