Availability KPI

Availability is a straightforward, attendance-style measure: of the time a person was expected to work, how much of it did they actually spend working at the computer? It says nothing about how active or productive that time was — only how much of the scheduled day was covered.

---

What it measures

The portion of the day the user was working, out of the total amount of time they were expected to work.

How it's calculated

Availability = Tracked work time ÷ Expected work time × 100

If someone is expected to work 8 hours and is at the computer working for all 8, Availability is 100%. If they are there for 4 of the 8 expected hours, Availability is 50%. If idle time is configured to be saved, it counts toward the time worked.

Example

Expected work time is 8 hours and the person tracked 6h 48m of work. Availability = 6.8 ÷ 8 ≈ 85%.

What influences it

• Work-hours schedule — sets the expected time, which is the denominator.
• Time off, meetings, and absences — reduce the time worked and therefore Availability.
• Non-computer work — work done away from the computer is not tracked, so it lowers Availability even though real work happened.
• Idle-time settings — whether idle periods are saved or discarded changes the numerator.

How to read it

• 85–100% is typical for active workdays.
• Low Availability can signal time off, meetings, absenteeism, or work happening away from the computer. Treat it as a prompt to look at why scheduled time is not being logged, not as an automatic sign of underwork.

Related

Workday, the Time Off feature, the Idle Time settings, and Reports (attendance patterns).