How HoraFlow's Productivity Score Works: Activity Tracking, Screenshots, and Daily Scores Explained
HoraFlow gives every employee a daily productivity score based on keyboard activity, mouse movement, active app usage, and random-interval screenshots. Here's exactly how it's calculated and how to use it.
If you manage a remote or hybrid team, you have probably asked yourself some version of this at some point: how do I actually know if my team is working?
Not because you distrust them. But because you are accountable for output, responsible for project timelines, and you cannot walk over to someone's desk and read the room the way you would in an office.
The answer most managers reach for is time: how many hours did they log? But hours logged and actual productive work are not the same thing. Someone can be clocked in for 8 hours while spending 2 of them idle and another hour in apps with nothing to do with work.
HoraFlow uses a daily productivity score to close this gap. It gives you one number per employee that reflects how engaged they actually were during their shift, not just how long they were clocked in.
This guide explains exactly what goes into that score, how to read it, and what to do with it as a manager.
What Is a Productivity Score?
A productivity score is a single daily number, expressed as a percentage, that reflects how actively engaged an employee was during their logged work time.
A high score means the employee was consistently active across their shift: keyboard input, mouse movement, time in work-relevant applications, and low idle periods.
A low score does not automatically mean the employee was not working. It might mean they spent time in video calls (which registers lower app activity), were doing deep reading or thinking without typing, or had a connectivity issue. Score data is most useful as a trend indicator, not a moment-by-moment judgment.
What HoraFlow Measures to Calculate the Score
HoraFlow combines several data signals into the daily productivity score:
Keyboard activity. Keystrokes are monitored to measure typing volume across the shift. Active keyboard usage in work-relevant applications contributes positively to the score.
Mouse activity. Mouse movement and click patterns indicate active engagement with applications. Periods of no mouse or keyboard activity are flagged as idle time.
Active application and window usage. HoraFlow monitors which applications are in active focus during the shift. Time spent in productivity tools, communication apps, IDEs, CRM platforms, and other work-relevant software contributes to the score.
Screenshot capture. Screenshots are taken at random intervals throughout the shift. The images allow managers to verify that active time coincides with actual work. Idle screenshots, where the screen shows a lockscreen or static view, are automatically flagged.
Idle detection. When there is no keyboard or mouse input for a sustained period, HoraFlow marks that window as idle. Idle time reduces the active-time percentage that feeds into the final score.
The score is calculated per employee per shift. It reflects the ratio of genuinely active time to total clocked time, weighted by activity type.
[Image: A clean dashboard card showing a daily productivity score of 84% with a breakdown bar beneath it: green section labeled Active (72%), yellow labeled Idle (14%), gray labeled Not tracked (14%). Next to it, a 7-day sparkline trend showing daily scores. Minimal SaaS UI, white card on light gray background.]
What the Score Does Not Measure
Understanding the score's limits matters as much as understanding what it captures.
It does not capture thinking time. An engineer reviewing architecture documentation, a writer working through an outline, or a manager listening to a call recording is doing real work that may register as lower activity. Scores should be read alongside project output.
It does not differentiate between types of keyboard activity. Typing a detailed report and typing in a game both generate keystrokes. Application context and screenshots help fill in that picture.
It does not replace human judgment. It flags situations worth looking at. Whether those situations warrant a conversation is a manager's call.
A score is most useful when it identifies a pattern over days and weeks, not when it triggers a reaction on a single afternoon.
How to Read Productivity Scores as a Manager
Compare within individuals, not across roles. A developer's score looks different from a customer support agent's. The nature of work differs. Compare each person to their own historical baseline, not to someone with a completely different workflow.
Look for trend shifts. If someone's score has been consistently in the 70s for three months and drops to the 40s for two weeks, that is worth a conversation. It might indicate a personal situation, a workload problem, or a technical issue. The trend is the signal.
Use the score alongside output data. If someone has a low productivity score but consistently meets deadlines and delivers quality work, the score may reflect a work style that does not generate constant keyboard activity. Trust the output.
Use it to spot issues early. If someone's idle time is consistently high and their project work is also slipping, you have two aligned signals. That combination is more actionable than either on its own.
Random Screenshot Intervals: Why It Matters
The screenshot component of HoraFlow uses randomized capture intervals, not fixed ones.
Fixed interval screenshots (for example, one every 10 minutes exactly) are easy to work around. If the schedule is predictable, the behavior being measured becomes predictable too.
Random interval captures mean the employee cannot anticipate when the next screenshot will be taken. This produces a more accurate sample of what is actually happening on screen throughout the shift.
Screenshots are stored in the HoraFlow account and accessible to managers. Employees can see their own screenshots. There is no live feed. Managers review captures after the fact, not in real time. Idle screenshots are automatically flagged so they are easy to filter out when reviewing.
The Daily Email Digest
At the start of each morning, HoraFlow sends a daily digest to managers summarizing the previous day's activity.
The digest includes:
- Total hours logged per team member
- Productivity score per person
- Any idle alerts that were triggered
- A brief overview of project time distribution
This means you do not need to log into the dashboard every morning to know what happened the day before. The relevant numbers come to your inbox so you can start the day with context before your first meeting.
Activity Heatmap: When Is Your Team Most Productive?
Beyond the daily score, HoraFlow builds an activity heatmap showing, by hour and by day of the week, when each person and the overall team does their most engaged work.
After a few weeks of data, the heatmap becomes genuinely useful for scheduling decisions:
- Move recurring meetings out of peak focus windows
- Schedule collaborative sessions when team energy is naturally higher
- Identify individuals who do their best work at non-standard hours
- Spot consistent afternoon dips that might indicate overloaded mornings
The heatmap does not tell you what to do with the patterns. It shows you the patterns so you can decide.
Frequently Asked Questions
What data points go into HoraFlow's productivity score?
The score is calculated from keyboard activity, mouse movement, active application and window focus, idle detection periods, and screenshot sampling. It reflects the ratio of actively engaged time to total clocked time during a shift.
Is a higher productivity score always better?
Not necessarily. A score reflects activity patterns, not output quality. A high score combined with strong project delivery is a good signal. A consistently low score despite solid output might indicate a work style with extended reading or thinking time rather than a performance issue.
Who can see an employee's productivity score?
Managers can see scores for all team members they manage. Employees can see their own score. Employees cannot see other employees' scores.
How are idle periods defined?
HoraFlow flags a period as idle when there is no detectable keyboard or mouse activity for a sustained window. Short gaps are not counted as idle. The threshold is designed to exclude natural short breaks, not penalize them.
Are screenshots stored permanently?
Screenshot storage depends on your HoraFlow plan settings. Captures are retained for a defined period and accessible to managers within that window.
Can employees see their own screenshots?
Yes. Employees can view their own captured screenshots. They cannot see screenshots from other team members.
Does the productivity score account for video calls and meetings?
Video calls register differently than keyboard-heavy tasks. An employee in a 2-hour video call will show lower keyboard and mouse activity for that window, which can affect their score for that period. HoraFlow flags meeting time separately where meeting software is detected.
How long does it take to establish a meaningful productivity baseline?
Most managers find a clear baseline emerges after two to three weeks. The first week often looks slightly different as people adjust to knowing the tool is running. By week two, patterns tend to normalize.
Is the score shown to employees?
Employees can see their own daily scores. Whether managers discuss scores directly with employees is a management decision. HoraFlow gives you the data; how you use it in conversations with your team is up to you.
How is HoraFlow's productivity score different from basic time tracking?
Basic time tracking tells you how long someone was clocked in. HoraFlow's productivity score tells you how actively engaged they were during that time. The combination of both is what gives you a useful picture of actual work versus just hours on record.
The Short Version
The productivity score is a tool for spotting patterns, not for micromanaging moments. Used well, it helps managers understand how their team is actually spending their time, identify issues before they become bigger problems, and make better decisions about workload and scheduling.
Used poorly, it becomes a number people optimize for rather than a signal managers use for better decisions.
HoraFlow gives you the data. The framing is yours.
Book a 10-minute demo and see how your team's activity data looks on the HoraFlow dashboard.