%20(1).png)
.png)
ProHance doesn't give you one activity percentage to push up. It gives you a handful of states you fall into and a pile of hours it sorts into buckets, and your report is whatever comes out of that. Which changes the job. Getting your numbers up is less about moving the mouse constantly and more about staying clear of two thresholds and fixing how your work gets filed.
Here's what moves the needle, roughly in order of how much.
How ProHance measures you
It watches mouse and keyboard input. Input means active, no input means inactive, and everything in the report is built on top of that one signal.
The twist is that it splits inactivity in two, where most trackers only have one setting.
The two thresholds that matter
Your manager's report tells idle and away from system apart, and reads them very differently.
Idle kicks in after a short quiet spell with no mouse or keyboard input. It reads as being at your desk but not doing much. Away from system kicks in after a longer one, and reads as not being there at all.
When ProHance went in across some Cognizant projects, the staff training put idle at five minutes and away from system at fifteen. Those are configurable and reportedly differ between teams, so take them as a ballpark, not gospel.
The fifteen-minute one is the expensive threshold. Spend that long reading a spec on a second monitor without touching anything and you can land in the away column, which looks a lot worse than the work actually was.
So the practical version: you're not chasing a big percentage. You're avoiding one long unbroken gap. A bit of interaction is enough. Scroll the doc you're reading, move between windows while you think, and the session stays alive.
Get your applications labelled as productive
This is the biggest lever in the whole thing, and hardly anyone pulls it.
Productive hours only count inside apps your organisation has tagged productive. That tagging is a local setting, not something ProHance decides for you. The same tool can count as productive on one team and sit unlabelled on another.
If a core app for your role never made the list, that time is invisible no matter how hard you worked in it. Your productive hours come out low for a reason that has nothing to do with what you did.
Raise it, and raise it as what it is: a config gap that hits everyone in your role using the same tool, not a personal gripe. An admin fixes it in about a minute.
Close the gap between logged and productive hours
Managers rarely look at productive hours on their own. They look at the distance between hours logged and hours productive.
Which means a long session actually works against you. Stay logged in through lunch and you add an hour to the logged side and nothing to the productive side, so the ratio comes out worse than a shorter, denser day would have. Ending or pausing during real breaks gives you a cleaner record than leaving the clock running.
Use break categorisation if your deployment has it
Where break tracking is switched on, a categorised break gets logged as a break. An uncategorised one turns into idle or away time. Same twenty minutes, a very different line in the report.
If you don't know whether yours has it, find out. It's the difference between a normal lunch and fifteen minutes of unexplained nothing.
Cluster your input-heavy work
If your day is part ticket work and part reading and calls, spreading the input-heavy stuff through the day keeps each stretch looking steady. Do all your data entry in the morning and all your reading after lunch, and you get one strong half and one that looks like you left.
Know which parts of your work are invisible
A lot of real work makes almost no input, and no habit fixes that:
- Calls, client or internal. An hour of talking registers as nothing.
- Reading and review. Specs, code review, test reports, ticket triage.
- Thinking. Debugging and design run long and quiet, then spike.
- Waiting. Builds, deploys, slow queries, dead time in a queue you didn't choose.
That's the measurement, not a verdict on you. Data-entry-heavy roles score well because of what the work physically looks like. Analysis and engineering score lower for the exact same reason.
When the work genuinely produces no input
Labelling sorts out categorisation. Session habits sort out the logged-hours ratio. Neither one helps during a ninety-minute call or a long afternoon of reading, because that work is real and makes nothing ProHance can see.
That's the gap activity software fills: keeping a session reading as active through work the agent simply can't detect. Our ProHance activity guide walks through the setup, and LazyWork has a free trial if you want to run it against your own deployment.
One warning worth keeping in mind: aim for a normal-looking pattern, not a maximum. An unbroken perfect day stands out more than an ordinary one with gaps in it.
Frequently asked questions
What is a good ProHance activity level?
ProHance reports states and hours rather than a single score, so there's no universal target. What counts is the ratio of productive to logged hours, and your own team sets that benchmark. Ask what the team average is before deciding your number is bad.
How long before ProHance marks you idle?
Often five minutes with no mouse or keyboard input, with away from system landing around fifteen. Both are set per organisation and can vary by team, so check your own.
Does ProHance take screenshots?
It offers screen recording for off-premise staff, which is a setting rather than a default, and plenty of deployments run without it. Worth checking whether yours has it on.
Why is my ProHance productive time low when I worked all day?
Usually one of two things: the apps central to your role aren't labelled productive, or a big chunk of your day went into calls, reading and review that make no measurable input. Both are worth raising, and the first is an easy fix.
Related reading: