Attendance

The Attendance module tracks when employees are actually working — clock-ins and clock-outs, lateness, overtime, and corrections when something needs fixing. It's used by every employee day to day, with reporting managers and HR administrators reviewing and validating the record.

This guide gives the big picture: what the module is for, how a day's attendance comes together, who sees what, and what can be customized. Deeper guides for each area are linked below. No technical background needed.

Purpose

Attendance answers a simple daily question: "Was this person working, and for how long?"

Instead of attendance being a manual timesheet, it's built from real activity:

• Clock-ins and clock-outs, from the web or from a biometric device, feeding the same record either way.
• Automatic flags for lateness, early departure, and overtime, based on each employee's shift.
• A way to fix a missing or incorrect day, reviewed and approved by HR.
• Optional biometric, face, and location-based verification.

What's Included

Attendance is made up of a few connected areas, each covered in its own guide:

Area	What it covers
Clocking In & Out	Daily punches, late-come/early-out tracking, grace time, and minimum working hours.
Requests & Overtime	Fixing a missing or incorrect day, HR validation, and overtime approval.
Biometric, Face & Location Verification	Device-based clock-ins, face photo capture, and location restrictions.
Attendance Dashboard	The module's own at-a-glance view of attendance activity — see below.

How a Day's Attendance Comes Together

1. An employee clocks in and out — from the system's web interface, or automatically via a biometric device if the company uses one. Every punch pair becomes an "activity"; the day's activities roll up into a single attendance record.
2. The system checks it against their shift. Coming in late or leaving early is flagged automatically, softened by any grace period the company allows. Working beyond the shift's expected hours is tracked as overtime.
3. Most days validate themselves. As long as the worked hours stay within a sensible range, the record needs no manual review. Unusually long days are flagged for HR to check before they're considered final.
4. If something's wrong, a request fixes it. A missing punch, a forgotten clock-out, or an incorrect day can be corrected through a request, which HR reviews and approves.
5. Overtime gets approved. Depending on how the company has it configured, overtime either needs a manual nod from HR or approves itself automatically once it clears a configured threshold.

What Each User Sees

Attendance area	Employee	Reporting Manager	HR Administrator
Clock in / out	✅	✅	✅
View their own attendance	✅	✅	✅
View their team's attendance	—	✅	✅
View every employee's attendance	—	—	✅
Submit a correction request	✅ (their own)	✅	✅
Approve or reject a correction request	—	✅ (their team)	✅
Validate attendance / approve overtime	—	✅ (their team)	✅
Configure grace time, validation rules, devices	—	—	✅

In short:

• Employees clock in and out, and can see and request corrections to their own attendance.
• Reporting Managers see their team's attendance and can approve corrections, validations, and overtime for their people, without needing a separate permission.
• HR Administrators see everything and configure how the module behaves company-wide.

How Visibility Is Decided

1. Ownership. Everyone can always clock in and out, and see their own attendance.
2. The reporting line. A reporting manager can see and act on their team's attendance — reviewing requests, validating records, and approving overtime — following the standard manager-hierarchy pattern used across the system (see User Roles & Access).
3. Permissions. Company-wide visibility and configuration require the relevant permission.
4. Company. Attendance records belong to the company the employee works in.

Customization Options

• Grace time for late arrivals and early departures can be set company-wide, or overridden per shift.
• Validation rules — the worked-hours threshold that separates a self-validating day from one needing manual review, and the rules for auto-approving overtime — are configurable.
• Auto clock-out can be enabled per shift, so a forgotten clock-out doesn't leave a day open indefinitely.
• Location and network restrictions can limit where clock-ins are accepted from — see Biometric, Face & Location Verification.

Attendance Dashboard

Alongside the daily attendance screens, the module has its own at-a-glance view. It shows:

• On-time vs. late-come counts for the day.
• Expected attendance — active employees minus anyone on approved leave.
• Overtime and pending-hours charts, broken down by department.
• Who's currently on a break, based on early-out activity.

Good to Know

• Biometric punches use the exact same logic as the web clock-in button — late-come, grace time, and overtime rules apply identically no matter how someone punched in.
• Holidays and company off-days don't count against minimum hours. A day that falls on a holiday or a configured company leave doesn't get flagged for missing hours.
• Numbers reflect the selected company. In a multi-company setup, attendance is scoped to the company currently selected.

Every minute, accounted for.