See who actually turned up, by site, today.
Attendance you can see today, approved by the person who was there, and carried straight into payroll.
Attendance is where the workforce stops being a plan and becomes a fact. PiPO HRIS Time & Attendance captures what actually happened — by site, by shift, by person — computes hours from it, routes the exceptions to the supervisor who can resolve them, and hands the approved result to payroll as a verified input. The point is not the clock. The point is that nobody has to reconstruct the month afterwards.
The gap between the roster and the reality
- Coverage is known at the site but not at head office until the week after.
- Hours are computed from a roster rather than from what was worked.
- A shift that crosses midnight is split into two partial days, and paid twice.
- Overtime is discovered when the payroll total moves.
- Late arrivals and absences are discussed rather than recorded.
- Corrections happen in a spreadsheet that payroll receives and HR never sees.
Exceptions go to the person who can actually resolve them
An attendance exception resolved three weeks later is a guess. Resolved the same day by the supervisor who was on site, it is a fact. PiPO HRIS routes exceptions by the structure you configured, so they land with the person accountable for that unit — and every decision carries who made it, when, and why.
- Late starts, missing clock-outs, absences and threshold breaches raised automatically
- Routed to the supervisor for that unit, not to a central inbox
- Corrections made on the record, with a reason
- Escalation where an exception is not resolved
- Full audit log of every change
How attendance is captured
Which method suits which site is an implementation decision, and different sites in the same organisation commonly use different ones.
Supervisor capture
The supervisor confirms attendance for their crew or unit on a device they already carry. Standard in every implementation.
Web capture
Attendance recorded through the browser, for office-based and branch environments where a terminal is unnecessary.
Biometric terminals
Integration with biometric terminals, including ZKTeco scenarios, is supported in applicable implementations. Devices are confirmed during scoping — we do not claim universal device compatibility.
What we do not claim. GPS-based location verification, facial recognition and advanced automated rostering are not presented here as standard capability. Where a requirement of that kind exists, it is assessed during scoping and answered honestly — including where the answer is that it is not available today.
A roster is a plan.
Attendance is a fact.
The two are rarely identical, and the gap between them is where labour cost, coverage and payroll accuracy are all decided.
What it produces
Common questions
As one attendance record for that person for that day. Hours are computed across the boundary, and two shifts for the same person cannot overlap.
Capture approaches are chosen per site during implementation with exactly that in mind. What will work at each of your sites is confirmed during scoping rather than assumed.
Approved attendance can be exported as a structured payroll input. The specific format and destination are confirmed during scoping.
Approved leave is reflected in the attendance position, so someone on approved leave is not counted as an unexplained absence and does not generate an exception.
Explore next
Related reading
Ready to see Time & Attendance in action?
Tell us how your workforce operates and we will tailor the conversation around what you actually need to improve.