Attendance Tracking

The gap at 13:00 is your lunch break. Nothing is recorded during a break and the agent shows a gap rather than filling it in.

Ruben Castilho has no clock-in and no message. The board says so plainly rather than marking him absent, because at 09:00 the difference between late and unwell is usually a phone call.

An offline claim is how somebody gets credit for work the agent could not see: a site visit, a workshop, a laptop left behind. Without it, every hour away from a keyboard looks like an hour not worked, which is both wrong and the fastest way to lose people.

Support runs lowest every week and it is the only team on a single-cover rota. One person off is a nine-point drop, so the number is about the rota rather than the team.

Driver absence clusters after long routes, which is a scheduling finding rather than a sickness one. Recording the pattern is what makes the difference visible; recording only the days does not.

One hundred and eighteen thousand dollars of overtime is about 2.4 full-time people. Whether that is cheaper than hiring depends on numbers nobody has put next to each other, which is what this screen is for.

Return interviews are the only intervention with evidence behind them and the team that needs them most holds them least. Nothing about that is a mystery; it is a night shift with one supervisor.

The first row costs about $61,000 a year to fix and is currently a saving. Calling it a saving requires nobody to have added it up, which is what this report does.

A clock record cannot be edited or deleted by anybody; an adjustment sits beside it with a reason and the employee is told. Time somebody was actually at work is a fact, and what gets paid for it is a decision.

Notification rules are yours to set. What is here is a starting point drawn from how the queue actually behaves.