This glossary will help you understand the key metrics and terminology used in ActivTrak for BI - Schedule Adherence. Use this reference to interpret dashboard data and effectively communicate findings to your operations, HR, and management teams.
Definition
The percentage of Days Worked during the selected time period when a user's productive hours met or exceeded the configured productivity target.
Calculation
Days Achieving Productivity Goal / Days Worked
Example
Amy S. worked 19 days and achieved the productivity goal on 19 of those days, resulting in a 100% score. In contrast, Bailey D. worked 19 days but achieved the productivity goal on 2 of those days (11%) — a pattern that signals a consistent output concern rather than an occasional miss.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of Days Worked where a user both met their productivity target and complied with their assigned schedule — meaning they started on time, stayed through the end, and delivered the expected productive output. This is the most comprehensive day-level adherence metric.
Calculation
Days meeting both conditions / Days Worked
Example
Amy S. achieved the productivity goal 100% of the time, but only complied with her schedule while doing so on 68% of days — meaning on roughly one-third of her workdays, she hit her output target, but outside of her scheduled hours. This distinction helps managers separate productivity issues from schedule compliance issues.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of days in the selected time period when employees ended work no earlier than the scheduled end time.
Calculation
Days ending on time / Days Worked × 100%
Example
Fridays consistently show the lowest schedule fulfillment rates across the visible date range, dropping to 51% in the second week. Even on the best week, Friday fulfillment only reached 62% — meaning nearly 4 in 10 employees left before the end of their schedule. Use this pattern to determine whether end-of-week fatigue, flexible scheduling practices, or unclear expectations around Friday schedule end times may be contributing factors.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of days in the selected time period when employees started work no later than the scheduled start time.
Calculation
Days starting on time / Days Worked x 100%
Example
Schedule punctuality remains consistently low across the visible date range, hovering around 40% each week. This flat trend suggests that late starts are not an isolated or improving issue — they are a persistent pattern across the workforce that likely requires a structural intervention rather than a one-time coaching conversation.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of users in the selected time period who achieved both the Shift Compliance Goal and the Productivity Goal.
Calculation
Users meeting both the Shift Compliance Goal and the Productivity Goal / Total users x 100%
Example
The % of User Achieved Schedule Adherence Goals dips at the end of each week before recovering at the start of the next — suggesting adherence tends to slip as the week progresses.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of users who met their productivity target on each specific date within the selected time period. This metric reveals how productive output fluctuates day to day alongside schedule compliance.
Calculation
Users meeting the productivity target / Total users x 100%
Example
In the week of 1/26/2026, the % of Users Achieving Productivity Goal fell from 53% on 1/26 to 33% by 1/30. When this metric trends downward alongside rising non-compliance, it suggests schedule misalignment may be actively impacting output — not just attendance.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of users who fully complied with their assigned schedule — starting on time and ending on time — on each specific date within the selected time period.
Calculation
Users who both started and ended within the scheduled window / Total users active x 100%
Example
On 1/30/2026, only 26% of users complied with their schedule — the lowest point in the week. Comparing this to earlier in the week (33% on 1/26) reveals a steady decline in compliance as the week progressed.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of users who did not fully comply with their assigned schedule on each specific date within the selected time period — meaning they had a late start, an early end, or both. Displayed as a yellow bar on the Schedule Adherence Trend by Date chart.
Calculation
Users who failed to meet either their scheduled start time, or scheduled end time, or both / Total users x 100%
Example
On 1/30/2026, 74% of users were non-compliant with their schedule — the highest rate in the week. When the non-compliant percentage is consistently higher than the compliant percentage across multiple days, it signals a widespread adherence issue rather than isolated incidents.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Also known as User achieved Prod. Goal and User % Achieved Prod. Goal
Definition
The percentage of users who met their productivity goal. This reflects whether employees are delivering the expected level of productive output, independent of whether they complied with their schedule.
Calculation
Users whose Productive Hrs/Day meet or exceed the configured goal / Total users x 100%
Example
35 out of 100 users achieved their productivity goal — a 35% rate. When compared against the Achieved Shift Compliance Goal (8%) and Achieved Schedule Adherence Goals (6%), this tells you that some employees are hitting output targets but doing so outside of their assigned hours.
Where it appears
Schedule Adherence Summary
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Also known as User achieved Sch. Adh. Goals, User % Achieved Sch. Adh. Goals and % of User Achieved Schedule Adherence Goals
Definition
The percentage of users who met both their Shift Compliance Goal and their Productivity Goal. This is the most comprehensive measure of schedule adherence, requiring employees to both work their full assigned shifts and deliver the expected level of productive output.
Calculation
Users meeting both the Shift Compliance Goal and the Productivity Goal / Total users x 100%
Example
For the selected time period, only 6 out of 100 users achieved both goals — a 6% rate. With 35% meeting the Productivity Goal and 8% meeting the Shift Compliance Goal, the data shows that very few employees are doing both simultaneously, pointing to schedule compliance as the primary gap. The % of User Achieved Schedule Adherence Goals also dips at the end of each week before recovering at the start of the next — suggesting adherence tends to slip as the week progresses.
Where it appears
Schedule Adherence Summary
Manager Weekly View
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Also known as User achieved Shift Comp. Goal and User % Achieved Shift Comp. Goal
Definition
The percentage of users whose Shift Compliance Ratio met or exceeded the configured Shift Compliance Goal Threshold. This reflects how many employees met their schedule — starting on time and ending on time — consistently enough to meet the compliance standard.
Calculation
Users whose Shift Compliance Ratio meets or exceeds the Shift Compliance Goal Threshold / Total users x 100%
Example
For the selected time period, 8 out of 100 users achieved the Shift Compliance Goal — an 8% rate. With the default threshold set to 100%, this means only 8 employees were fully compliant on every single schedule. Lowering the threshold in Parameter Setting & Metrics Glossary would increase this number and may be appropriate for organizations with more flexible attendance policies.
Where it appears
Schedule Adherence Summary
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average number of break periods taken per day. A break is a period of inactivity during the workday that falls between productive work sessions.
Example
A team shows an average of 5 breaks per day, with an average of 31 minutes per break. This tells a manager that employees are taking frequent breaks throughout their workday. If schedule fulfillment is also low, excessive break frequency or duration could be a contributing factor.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average number of minutes before their scheduled end time that an employee stopped working on days when they departed early.
Example
John F. worked 5 days and departed early all 5 days, with an average early exit of 67 minutes. With a scheduled end of 5:00 PM, John is consistently leaving around 3:38 PM—well over an hour before the workday ends. This pattern warrants a coaching conversation regarding schedule-fulfillment expectations.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average time at which a user ended their workday. This represents when the user's last productive activity was recorded each day, averaged over the selected time period.
Example
Ellie P. has an average end of day of 19:18 (7:18 PM), well past 5:00 PM. This indicates Ellie regularly works beyond her scheduled hours. Compare this with an employee like Charles D., whose average end of day is 3:14 PM (15:14)—nearly two hours before the schedule is complete.
Where it appears
Manager Weekly View
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average number of minutes past their scheduled start time that an employee began work on days when they started late.
Example
Caleb A. was late to work on 1 out of 5 days, with an average late time of 27 minutes. This is a relatively minor, infrequent issue. In contrast, Tabitha R. was late 4 out of 5 days with an average of 407 late minutes (nearly 7 hours), indicating a severely misaligned work schedule rather than occasional tardiness.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average duration of break periods in minutes. This helps contextualize break patterns and their potential impact on schedule adherence and productivity.
Example
A team averaging 31 minutes per break is within a reasonable range for most organizations. However, if combined with 5 breaks per day, the total break time is approximately 155 minutes (over 2.5 hours), which may significantly affect productive output.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average time at which a user began their workday. This represents when the user's first productive activity was recorded each day, averaged over the selected time period.
Example
Nick L. has an average start of day of 6:43 AM, nearly two and a half hours before 9:00 AM. Combined with 100% productivity goal achievement and 86% schedule adherence, Nick consistently starts early and delivers strong results. In contrast, Rebecca W. averages a 3:24 PM start—over 6 hours after the scheduled start—indicating a fundamentally misaligned schedule.
Where it appears
Manager Weekly View
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of days a user was active and recorded work during the selected time period. This serves as the denominator for many calculated terms and helps contextualize other metrics. A user who was late 6 out of 7 days has a different pattern than one who was late 1 out of 7 days.
Example
Maggie J. worked 3 days during the selected time period, while most other team members worked 5-7 days. Her lower Days Worked count should be considered when interpreting her adherence ratios—with fewer data points, percentages can be more volatile. Her 0% productivity goal achievement across 3 days, however, is still a pattern worth addressing.
Where it appears
Manager Weekly View
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of users who had at least one early departure during the selected week. This metric provides a quick read on how widespread early departures are across the workforce, regardless of frequency.
Example
For the week of 1/25/2026, 93 out of 144 users departed early at least once — representing 65% of the workforce. This metric also shows a comparison vs. the prior time period; in this example, early departures were down 11%, suggesting a modest improvement week over week.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Also known as Early End
Definition
The number of times a user departed before the scheduled end
time during the selected week. Used alongside Days Worked and
Avg.
Early Exit Mins. to understand the frequency and pattern of early
departures for each employee.
The scheduled end time is calculated as the
Shift End minus the Max Acceptable Start/End Time Offset; these
can
be configured in
Parameter Setting & Metrics Glossary.
Example
Michelle C. had 5 early departures out of 5 Days Worked — meaning she left before the scheduled end time every day that week. Comparing Early Departures alongside Avg. Early Exit Mins. helps distinguish between employees who are leaving slightly early versus those with a significant and consistent pattern of early departure.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of days during the selected time period when a user ended work earlier than the scheduled end time.
Example
John F. has an Early End Count of 7 out of 7 Days Worked—a 100% Early End Ratio. This means John left before the scheduled end time every single day in the selected time period, making this a consistent behavioral pattern rather than an occasional occurrence.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of Days Worked where a user ended work earlier than the scheduled end time.
Calculation
Early End Count / Days Worked
Example
Daniel O. has an Early End Count of 3 out of 6 Days Worked, giving an Early End Ratio of 50%. This means Daniel left early on half of his workdays—a notable pattern that may warrant discussion, especially when combined with his 33% productivity goal achievement.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
An organizational unit in ActivTrak that groups users together based on shared characteristics such as department, function, reporting structure, or project assignment. Teams (also known as Groups) serve as a primary filter for analyzing productivity data and enable comparative analysis across different groups within an organization.
Teams in ActivTrak:
- Created and managed by administrators
- Allow for hierarchical structures (teams within teams)
- Serve as filters for dashboards and reports
- Enable team-level goal setting and benchmarking
- Provide context for productivity comparisons
Example
A financial services company has structured its ActivTrak teams to match its organizational hierarchy:
- The Accounting team consists of 8 members, averaging 6.2 productive hours per day, which is above their 6.0-hour benchmark.
- The Investment Analysis team comprises 12 analysts, who currently average 5.8 productive hours daily, slightly below their target of 6.0 hours.
- The Client Services team, the largest group with 15 members, maintains a productivity level of 6.5 hours per day, exceeding its 6.0-hour goal.
- The IT Support team of six specialists averages 5.7 productive hours daily, exceeding their lower benchmark of 5.5 hours, due to the reactive nature of their work.
Using these team designations, executives can filter dashboard data to compare performance across departments, while team leaders can view only their specific team metrics. This structure enables appropriate goal-setting based on different job functions and provides meaningful context for productivity analysis throughout the organization.
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of days during the selected time period when a user started work later than the scheduled start time.
Example
Caleb A. has a Late Start Count of 3 out of 7 Days Worked, giving a 43% Late Start Ratio. Combined with a 57% Early End Ratio, Caleb has adherence issues on both ends of his schedule—suggesting a broader schedule compliance challenge rather than an isolated punctuality problem.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of Days Worked where a user started work later than the scheduled start time.
Calculation
Late Start Count / Days Worked
Example
Sarah L. has a Late Start Count of 6 out of 8 Days Worked, resulting in a 75% Late Start Ratio. Three out of four workdays starting late is a significant pattern that requires attention—especially when combined with a 75% Early End Ratio and 0% productivity goal achievement.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Also known as Late Start
Definition
The number of times a user started work after the scheduled
start time during the selected week. Used alongside Days Worked
and
Avg. Late Mins. to understand the frequency and pattern of late
starts
for each employee.
The scheduled start time is calculated as the configured
Shift Start plus the Max Acceptable Start/End Time Offset; these
can
be configured in
Parameter Setting & Metrics Glossary.
Example
Derek B. was late to his schedule 5 out of 5 Days Worked — meaning he started after the scheduled start time every day that week. Comparing Late to Shift alongside Avg. Late Mins. helps distinguish between employees who are arriving slightly late versus those with a significant and consistent pattern of tardiness.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of users who had at least one late start during the selected week. This metric captures the breadth of punctuality issues across the workforce, helping managers understand how widespread the problem is before drilling into individual details.
Example
For the week of 1/25/2026, 108 out of 144 users were late to their schedule at least once — representing 75% of the workforce. Combined with the Departed Early At Least Once metric (93 users), this tells managers that late arrivals are the more widespread issue for the week.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
A configurable grace period (in minutes) that defines how much flexibility employees have around their schedule start and end times before being flagged as non-compliant. This offset is applied to both the start and end of the schedule. This can be configured in Parameter Setting & Metrics Glossary
Example
With a Shift Start of 9:00 AM, a Shift End of 5:00 PM, and an offset of 15 minutes: an employee who starts at 9:14 AM and ends at 4:46 PM would be considered fully compliant. An employee who starts at 9:16 AM would be flagged as a Late Start, and one who ends at 4:44 PM would be flagged as an Early End.
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of days during the selected week when a user's productive hours did not meet the productivity goal Used alongside Days Worked and Productive Goal Gap Hrs/Day to understand the frequency and severity of productivity shortfalls for each employee.
Example
David R. missed the productivity goal on 5 out of 5 Days Worked. Comparing Missed Productivity Goal alongside Productive Goal Gap Hrs/Day helps distinguish between employees who are falling slightly short versus those with a significant and consistent productivity gap.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average shortfall in productive hours per day on days when a user did not meet their configured productivity goal This metric quantifies how far below the target the user fell, helping managers assess the severity of the gap.
Example
Justin H. missed his productivity goal on 3 out of 5 Days Worked, with a gap of 0.5 hours per day. This is a relatively small shortfall—Justin was close to the target on his off days. In contrast, Charles D. missed the goal 4 out of 5 days with a gap of 3.8 hours per day, indicating a much more significant productivity issue on days he fell short.
Where it appears
Manager Weekly View
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average number of productive hours a user logged per Days Worked during the selected time period. Productive hours represent time spent on activities classified as productive in your ActivTrak configuration.
Example
Nick L. averages 8.7 productive hours per day—well above the 6.5 Hrs/Day productivity goal—resulting in 100% productivity goal achievement. Meanwhile, Charles D. averages only 2.6 productive hours per day, a 3.9-hour shortfall from the target. This helps managers identify where targeted support or accountability is needed most.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of a user's logged hours that were classified as productive. This metric reveals not just how many hours were worked, but how efficiently that time was spent — helping managers distinguish between employees who work long hours unproductively and those who work fewer but more focused hours.
Example
A user with 6.5 Productive Hrs/Day during an 8.0 hour workday has a Productivity Eff. % of 81% — meaning roughly one-fifth of their time was spent on non-productive activity. In contrast, a user with 6.5 Productive Hrs/Day and 6.6 hour workday has a 98% efficiency rate, indicating nearly all of their time at work is productive.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of days during the selected time period when a user both started work on time and ended work on time — meeting both the punctuality and fulfillment criteria for that schedule.
Example
A user with a Shift Compliance Count of 4 out of 5 Days Worked has an 80% Shift Compliance Ratio. The one non-compliant day could reflect either a late start, an early end, or both — use the Late Start Count and Early End Count columns to identify which.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
A user-level metric indicating whether an employee's Shift Compliance Ratio meets or exceeds the configured Shift Compliance Goal Threshold. By default, this threshold is set to 100%, meaning the user must have been compliant on every schedule during the time period to achieve this goal. The Shift Compliance Goal Threshold can be configured in Parameter Setting & Metrics Glossary.
Calculation
Shift Compliance Ratio ≥ Shift Compliance Goal Threshold
Example
With the default threshold of 100%, only 17% (2 out of 12 users) achieved the Shift Compliance Goal. This means only 2 employees worked every assigned schedule from start to finish during the entire time period—a strict standard that highlights how few employees have perfect attendance records.
Plan availability
All plans with ActivConnect API (Add-on)
Definition
A configurable parameter that sets the minimum Shift Compliance Ratio a user must achieve to meet the Shift Compliance Goal. Expressed as a decimal (e.g., 1.00 = 100%, 0.90 = 90%). The Shift Compliance Goal Threshold can be configured in Parameter Setting & Metrics Glossary.
Example
The default threshold of 1.00 (100%) means users must comply with every single schedule to meet the goal. If your organization has a more lenient attendance policy, you might adjust this to 0.90 (90%), meaning a user who complies with 9 out of 10 schedules would still meet the goal. Lowering this threshold will increase the percentage of users who achieve the Shift Compliance Goal.
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of schedules where a user started work no later than the scheduled start time and ended work no earlier than the scheduled end time.
Calculation
Shift Compliance Count / Days Worked
Example
With 67 schedules in the selected time period, 37 schedules (55%) were fully compliant. This means that in 55% of all schedules, employees both arrived on time and stayed through the end of their scheduled schedule. The remaining 45% of schedules had either a late start, an early end, or both.
Where it appears
Schedule Adherence Summary
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The configured time at which an employee's shift is expected to end, entered in 24-hour format (e.g., 1700 = 5:00 PM, 1800 = 6:00 PM). This value serves as the baseline for all fulfillment calculations — including Early End events, Shift Fulfillment Ratio, and Shift Compliance Ratio. This can be configured in Parameter Setting & Metrics Glossary
Example
With a Shift End of 1700 (5:00 PM) and a Max Acceptable Start/End Time Offset of 15 minutes, the scheduled end window closes at 4:45 PM. Any employee whose last recorded activity is before 4:45 PM will be flagged as an Early End.
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of days during the selected time period when a user ended work no earlier than the scheduled end time.
Example
A user with a Shift Fulfillment Count of 5 out of 7 Days Worked has a 71% Shift Fulfillment Ratio. If their Shift Punctuality Count is 7 out of 7, this tells you the employee consistently starts on time but struggles to stay through the end of their schedule — an early departure problem rather than a tardiness problem.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Also known as % of Shifts End Fulfilled
Definition
The percentage of schedules where a user ended work no earlier than the scheduled end time. This metric specifically measures whether employees are staying through the end of their assigned schedules.
Calculation
Shift Fulfillment Count / Days Worked x 100%
Example
Out of 67 schedules, 38 (57%) met the fulfillment criteria. Compared to the 87% Shift Punctuality Ratio, this 30-point gap reveals that early departures are a much bigger challenge than late arrivals for this workforce. This insight helps managers focus their coaching efforts on schedule completion rather than start-time compliance.
Where it appears
Schedule Adherence Summary
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of days during the selected time period when a user started work no later than the scheduled start time.
Example
A user with a Shift Punctuality Count of 2 out of 7 Days Worked has a 29% Shift Punctuality Ratio — meaning they started on time fewer than one-third of their workdays. If their Shift Fulfillment Count is 6 out of 7, the data points to a specific tardiness problem rather than a general schedule compliance issue.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Also known as % of Shifts Start Punctual
Definition
The percentage of schedules where a user started work no later than the scheduled start time. This metric isolates start-time compliance from overall schedule adherence, helping you determine whether tardiness is a contributing factor to low compliance.
Calculation
Shift Punctuality Count / Days Worked x 100%
Example
Out of 67 schedules, 58 (87%) started on time. This high punctuality rate, combined with a lower 55% Shift Compliance Ratio, confirms that most employees are arriving on schedule—the compliance gap is driven by early departures, not late arrivals.
Where it appears
Schedule Adherence Summary
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The configured time at which an employee's shift is expected to begin, entered in 24-hour format (e.g., 900 = 9:00 AM, 1300 = 1:00 PM). This value serves as the baseline for all punctuality calculations — including Late Start events, Shift Punctuality Ratio, and Shift Compliance Ratio. This can be configured in Parameter Setting & Metrics Glossary
Example
With a Shift Start of 900 (9:00 AM) and a Max Acceptable Start/End Time Offset of 15 minutes, the scheduled start window opens at 9:15 AM. Any employee whose first recorded activity is after 9:15 AM will be flagged as a Late Start.
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The number of days during the selected time period when a user both started work later than the scheduled start time and ended work earlier than the scheduled end time in the same schedule.
Calculation
Shift Violation Count / Days Worked
Example
A user with a Shift Violation Count of 4 out of 5 Days Worked has an 80% Shift Violation Ratio — meaning on most of their workdays, they were both late to arrive and early to leave. This pattern is a strong indicator of a fundamental schedule misalignment that warrants immediate attention.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The percentage of Days Worked where a user both started work later than the scheduled start time and ended work earlier than the scheduled end time in the same shift.
Calculation
Shift Violation Count / Days Worked x 100%
Example
A user with a Shift Violation Count of 4 out of 5 Days Worked has an 80% Shift Violation Ratio — meaning on most of their workdays, they were both late to arrive and early to leave. This pattern is a strong indicator of a fundamental schedule misalignment that warrants immediate attention.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average hours (equivalent to Screen Time) a user logged per workday during the selected time period. Comparing Total Hrs/Day to Productive Hrs/Day reveals how much of a user's work time was spent productively.
Example
Caleb A. has 7.1 Productive Hrs/Day and 7.2 Total Hrs/Day—a very tight gap indicating nearly all of his work time is productive. Meanwhile, Bob K. has 4.9 Productive Hrs/Day and 5.0 Total Hrs/Day. While the productive-to-total ratio is also tight, the overall volume is significantly below the 6.5-hour productivity target, indicating insufficient work time rather than unproductive time.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average number of hours per day spent on activities that have not been classified as either productive or unproductive in your ActivTrak configuration. High undefined time may indicate gaps in your activity classification settings rather than employee behavior issues.
Example
A user with 7.0 Total Hrs/Day, 4.5 Productive Hrs/Day, 0.5 Unproductive Hrs/Day, and 2.0 Undefined Hrs/Day has a significant portion of their workday is unclassified. Before drawing conclusions about their productivity, it's worth reviewing whether the activities driving that undefined time have been configured in ActivTrak.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
The average number of hours per day a user spent on activities classified as unproductive in your ActivTrak configuration. This metric helps managers identify whether low productivity goal achievement is driven by insufficient work time or by time spent on non-productive activities.
Example
A user with 6.0 Total Hrs/Day and 2.5 Unproductive Hrs/Day is spending over 40% of their logged time on unproductive activity — resulting in only 3.5 Productive Hrs/Day, well below a 6.5-hour productivity target. Addressing the unproductive time rather than the total hours worked would be the more targeted intervention here.
Where it appears
User Report
Plan availability
All plans with ActivConnect API (Add-on)
Definition
Individual employees or contractors whose digital activity is being tracked through the ActivTrak agent software. In ActivTrak, a "User" typically corresponds to a specific person whose work habits, productivity, and application usage are monitored and analyzed within the platform.
Key Aspects of Users in ActivTrak
- Each user typically requires one license in the ActivTrak system
- Users are organized into teams for analysis and reporting
- User data forms the foundation for all productivity metrics
- Users can be assigned specific productivity benchmarks and goals
- User privacy settings can be configured according to organizational policies
Plan availability
All plans with ActivConnect API (Add-on)