Attended hours
Objective. Define attended hours as presence time and separate it cleanly from scheduled paid hours and from productive time.
Attended hours answers 'was the person here?' - nothing more. It sits between what was scheduled and what was produced, and it is routinely mistaken for both.
See it in the demo
Definition
Attended hours is the time an employee was actually present and logged on during the period - the realised counterpart to scheduled paid hours. It records presence, not effort and not output. A full attendance day can still contain idle time, breaks and low productivity.
How it is calculated
At app-logic level it is the time captured as present/active-session between arrival and departure for each person, summed over the period. Included: logged presence within the working window. Excluded or configurable: unpaid breaks, idle beyond a threshold, and time outside the shift, depending on the customer's rules. The attendance percentage then compares attended hours against scheduled paid hours. Confirm with product how idle, breaks and grace are treated for a given customer - do not assume the formula.
How to read it and the common misread
Read attended hours (and the attendance percentage) as a presence and reliability signal. The common misread is reading it as productivity or as hours worked on tasks. Attendance and utilization answer different questions: someone can be fully present yet lightly utilised, and attendance says nothing about the quality or quantity of output. Never let a high attendance figure stand in for a work result.
Where it appears
Attended hours and the attendance percentage appear in Time and Activity under attendance and hours and in daily operations. Exact capture thresholds and break handling are SME-validation-pending; confirm with product.
Interpretation check
Attended hours measures presence only; it is not scheduled paid hours and it is not productive time or output.
Practical task
In attendance and hours, pick one team, record attended hours and the attendance percentage, then write one line stating what question this answers and one question it cannot answer.
Self-check
Attendance is 98 percent but the team is behind on work. Is that a contradiction?
No. Attendance measures presence, not output. People can be present and still under-produce. You need utilization and output metrics to explain the shortfall; attendance alone cannot.
What is the difference between an attendance percentage and a utilization percentage?
Attendance compares attended hours to scheduled paid hours - were they here? Utilization compares used time to available hours - was the present time used? They answer different questions and should never be swapped.
What would you confirm with product before quoting attended hours to a customer?
How idle time, breaks and grace periods are treated, and what counts as a logged session, since these are configurable and change the figure.
Verified vs demo. Attendance figures are shown in the Time and Activity demo; capture thresholds, idle and break handling are configurable and SME-validation-pending - confirm with product.