Перейти к основному содержимому

Working time analytics

Path: HR Analytics Overview / Role Center → Working Time Activities

The Working Time family answers: are people working too much, is time recorded completely, and how well is planned time used? It draws on the timesheet status of closed periods and the timesheet actuals of the open one.

IndicatorCodeMeasuresRead it as
Overtime HoursWT-OVERTIMEOvertime for the period vs a basisHours — spike warning
OT Yearly Limit ComplianceWT-OT-LIMITEmployees near/over the yearly OT limitCount — compliance
Unfilled TimesheetsWT-TS-GAPSWorking days with no recorded actualsCount — should reach zero
Weekend Holiday WorkWT-WEEKENDWork on nonworking daysPeople + hours
Utilization RateWT-UTILIZATIONActual vs planned hours% — over/under capacity
OT Sick CorrelationWT-OT-SICKOvertime spikes followed by sickness spikesEarly-warning signal

Overtime Hours​

  • What it measures — total overtime hours for the current period compared with the chosen basis (previous period, same period last year, or rolling average), with a per-period series and a per-organizational-unit split.
  • Why it matters — sustained overtime is a cost, fatigue and compliance risk.
  • How it is calculated — closed periods use the stored timesheet-status overtime hours; the current open period is computed from the timesheet actuals in the configured overtime activity group (the 1.5 overtime group by default) and is preliminary.
  • How to read it — unfavorable when it exceeds the basis by more than Threshold 1 (default 30%).
  • Drill-down — the overtime timesheet records in that same overtime activity group, so the list reconciles to the headline figure.
  • Settings — Threshold 1; Comparison Basis. Refreshes daily.

OT Yearly Limit Compliance​

  • What it measures — per employee, overtime hours accumulated in the current calendar year against the configured yearly limit, plus how many employees are over the limit or approaching it.
  • Why it matters — the statutory overtime ceiling is a compliance obligation.
  • How it is calculated — the yearly figure is the actual overtime hours recorded on the timesheet from 1 January to the reporting date for the configured overtime activity group. By default that group is the 1.5 overtime group; to also count 50% and holiday-out-of-calendar overtime toward the limit, assign a Time Activity Group that includes all those codes. Per-employee detail appears only when person-level results are enabled.
  • How to read it — two counts: employees over the limit and employees approaching it (past the warning level).
  • Drill-down — the overtime timesheet records (same group, year-to-date) that make up the figure.
  • Settings — Threshold 1 = yearly limit (default 120 hours per КЗпП article 65; 150 hours per Kodeks pracy article 151 when the Polish localization is enabled), Threshold 2 = warning level (default 80% of the limit), Time Activity Group (which overtime codes count; default the 1.5 group). The limit is a field because wartime legislation can suspend the statutory 120-hour cap. Refreshes daily.

Unfilled Timesheets​

  • What it measures — the number of in-scope employees who have at least one working day in the last closed period without any recorded timesheet actuals.
  • Why it matters — unfilled timesheets block an accurate payroll calculation, so this should reach zero before the period closes.
  • How it is calculated — a working day is a planned timesheet line not marked nonworking; an unfilled day is one with no actual detail. By default the last closed period is checked; enable Include Open Period to check the current open period up to the reporting date instead, so gaps can be chased before close. Shown as a total and per organizational unit.
  • Drill-down — the timesheet status rows for the checked period.
  • Settings — Include Open Period (off by default). Refreshes daily.

Weekend Holiday Work​

  • What it measures — work recorded on nonworking days (weekends and holidays) in the current period: the number of distinct employees who worked and the total such hours.
  • Why it matters — weekend/holiday work carries premium pay and rest-rule implications.
  • How it is calculated — a nonworking day is a timesheet line marked nonworking; work on it is a timesheet actual with a work-type activity (the configured time activity group, default the work-time group). Shown as a total and per organizational unit.
  • How to read it — unfavorable when the total nonworking-day hours exceed the allowed tolerance (Threshold 1, default 0 — so by default any nonworking-day work flags). Raise the tolerance for shift operations that legitimately work weekends.
  • Drill-down — the nonworking-day timesheet records.
  • Settings — Time Activity Group; Threshold 1 (allowed nonworking-day hours). Refreshes weekly.

Utilization Rate​

  • What it measures — for the last closed period, actual work hours over planned work hours as a percentage, per organizational unit, plus a company-total series per period.
  • Why it matters — shows whether capacity is over-stretched or idle.
  • How it is calculated — hours come from the stored timesheet status; employees with no planned hours (no schedule) do not contribute to the denominator.
  • How to read it — above 100% means work beyond the plan (overtime), below it means idle capacity.
  • Drill-down — the unit's timesheet status.
  • Settings — refreshes weekly.

OT Sick Correlation​

  • What it measures — per organizational unit, quarters in which overtime spiked and the following quarter saw a sick-leave spike (both above the configured number of standard deviations).
  • Why it matters — a possible early-warning signal that pushing overtime is followed by absence.
  • How it is calculated — overtime and sick days use the definitions shared with the overtime and absence analytics. Departments below the Minimum Group Size are skipped for anonymity.
  • How to read it — correlation is not causation. A coincidence of two spikes does not prove overtime caused the sickness — treat it as a prompt to investigate, not a conclusion.
  • Drill-down — the unit's overtime and sick-leave records.
  • Settings — Sigma Multiplier; Minimum Group Size. Refreshes monthly.

See Also​

© 2008 - 2026 SMART business