Workday KPI

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.

---

What it measures

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.

How it's calculated

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

Three details matter:

1. Only scheduled workdays count. Weekends and other non-working days are ignored entirely, even if some time was tracked on them. A few minutes logged on a Saturday to finish a task will not affect the Workday average.
2. Approved time off is left out. Days covered by approved time off are not counted as workdays, so a week of vacation does not pull the average down. Any time tracked on those days still counts toward totals such as Total time; it just does not enter the Workday average.
3. Zero-time workdays count as zero. A scheduled workday with no tracked time (and no approved time off) is counted as a zero in the average, which pulls the number down.

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.

Example

Someone works 10 hours on Monday and records nothing for the rest of the week.

• Workday = 10 ÷ 5 scheduled workdays = 2h
• Average Time = 10 ÷ 1 day with data = 10h

Workday reflects the whole expected week; Average Time reflects only the days that had activity.

What influences it

• Work-hours schedule — defines which days count as scheduled workdays, and therefore the denominator.
• Approved time off — removes the days it covers from the denominator. Time off that is still pending approval does not.
• Idle-time settings — if idle time is saved, it is included in the workday; if discarded, the workday reflects only active periods. See the Idle Time guide for configuration.
• Tracking gaps — unrecorded meetings, offline work, or an agent that was not running will understate the workday.
• Agent type — desktop and background agents capture time differently.

How to read it

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.

• Too low (about 4–6 hours): people may be underinvesting time, or there may be tracking gaps or unrecorded work to investigate.
• Too high (about 9–10+ hours): consistently extended hours can signal burnout risk.

Related

Activity (how active that time was), Availability (how much of the expected day was covered), the Idle Time settings, the Time Off feature, and the Understanding Performance guide.