Time and Activity: Overtime and after-hours
Objective. Identify overtime and after-hours activity for a team against policy, and explain why it is a cost and risk signal rather than proof of extra output.
This screen surfaces time beyond scheduled hours and activity outside normal windows. It answers 'who is working beyond their schedule, by how much, and does it fit policy?' - a cost, compliance and burnout signal, not a productivity trophy.
See it in the demo
What this screen answers
Overtime is a direct cost line and, unseen, a compliance and burnout risk. The screen answers: which teams or people are logging time beyond schedule or active outside normal hours, how much, and is it inside the agreed policy? It is the evidence a manager needs when an overtime pattern is questioned.
The task
Scope to a team and period, then look for sustained or policy-breaching overtime and recurring after-hours activity rather than one-off spikes. The move is to separate occasional, expected overtime from a pattern that signals understaffing, uneven load or a schedule that does not match the work.
How to read it
Overtime is time, not output. More hours beyond schedule does not prove more work was produced - it may mean the same work took longer, or load is badly distributed. Read after-hours activity carefully too: in flexible or multi-timezone teams, activity outside a standard window can be legitimate, not a breach. The misread is treating high overtime as high contribution, or after-hours work as automatically a problem, without the policy and timezone context.
Honest limits
Whether a block counts as overtime or 'after-hours' depends entirely on the schedule, policy and timezone configured for that team - confirm these with product and the customer before reading the flags. This screen shows the time pattern; it does not explain the cause (understaffing, a deadline, poor scheduling) and does not value the output of those hours. Pair it with Work Output to ask whether the extra hours produced anything.
Interpretation check
Overtime and after-hours flags are cost, compliance and burnout signals, not evidence of extra output. Their meaning depends on the configured schedule, policy and timezone - confirm those before treating a flag as a breach.
In the field
In an RCM BPO where labour is the dominant cost line, visible overtime per team lets a leader ask whether extra paid hours are producing proportional output - a cost-control conversation, not an effort ranking.
Practical task
On the demo overtime view, find one team with notable overtime or after-hours activity and write a one-line read that states the policy/timezone caveat and flags it as a cost/load question to investigate, not a productivity verdict.
Self-check
A manager says 'this agent does the most overtime, they're our hardest worker.' What do you challenge?
Overtime is hours beyond schedule, not output. It can mean the same work took longer or load is uneven; contribution is a Work Output question, not an overtime count.
Why can after-hours activity be a false alarm?
In flexible or multi-timezone teams, activity outside a standard window may be legitimate. The flag depends on the configured schedule and timezone, which must be confirmed first.
What does sustained team overtime more likely indicate than individual effort?
Understaffing, uneven load distribution, or a schedule that does not match the real work volume - a planning signal to investigate, not a merit badge.
Verified vs demo. Screen is live in the demo at /#/overtime; exact controls and figures are SME-validation-pending.