Understand the Workday KPI — how it measures the average length of a workday and what healthy values look like.
The Workday KPI tells you, on average, how much time a person spent at their computer doing something on a given workday. "Doing something" is the key idea: the computer was on and there was at least some non-idle activity. It does not say how intensely they were working — that is what Activity measures — only that time was tracked and the machine was not sitting completely idle.
Note: Like every KPI, Workday is always calculated in each user's local time zone.
The average amount of time tracked on a workday. A workday is any day the person is scheduled to work (for example, Monday–Friday). If idle time is configured to be saved, it is included in the total.
Workday divides the total time tracked across scheduled workdays by the number of scheduled workdays in the period:
Workday = Total tracked time on scheduled workdays ÷ Number of scheduled workdays
Two details matter:
This is what separates Workday from Average Time, which counts every day that has tracked time (including weekends) and ignores days with no time at all. On the same data, the two can tell very different stories.
Someone works 10 hours on Monday and records nothing for the rest of the week.
Workday reflects the whole expected week; Average Time reflects only the days that had activity.
You generally want Workday close to what you expect for the role. For an 8-hour expectation, roughly 7h 30m to 8h 30m is healthy.
Activity (how active that time was), Availability (how much of the expected day was covered), the Idle Time settings, and the Understanding Performance guide.
Up next
Activity KPI →