Time & Attendance
Clock in/out, break tracking, and comprehensive attendance management.
Overview
Time & Attendance is the system of record for when your people actually worked. Employees clock in and out from the web or their phone — or, with kiosk mode turned on for the organization, from a shared tablet at the door. Every punch can be checked the way that shift demands: GPS geofencing, IP allow-lists or trusted-device pairing, plus an optional photo at the punch (on the desktop page and the mobile app) kept for a manager to compare. Breaks are tracked against the break types you define, so paid and unpaid time separate cleanly and meal-break compliance is evidenced rather than assumed. Managers get a live view of who is on the clock right now, who is late, and who never showed, plus a review queue for missing-punch requests and absence reports — each with a full edit trail showing who changed what and why. Overtime shows as it accrues and in the weekly summary. Scheduled CSV and SFTP import/export move hours into payroll on your timetable, and the optional AI Attendance Monitor — turned on under Autonomous Ops — alerts the right manager to tardiness patterns and attendance exceptions.
How clock-in and clock-out track against each scheduled shift, how shared Time Clock Kiosks and mobile punches work, and how managers review flagged records, missing-punch corrections, and no-shows.
Highlights
Capabilities
Time Tracking & Corrections
-
Scheduled shift clock-in and clock-out
-
Ad-hoc (unscheduled) clock-in
-
Break tracking with auto-complete of in-progress breaks at clock-out
-
Employee missing-punch requests (manager-reviewed; managers and admins add their own missed day directly)
-
Time Card report — worked vs. payable hours per employee and day, printable with CSV export
-
Real-time timesheet sync and pay-period hours-vs-target view
Clock-In Methods
-
Web browser (desktop and mobile web)
-
Time Clock Kiosk (shared device, Employee ID + PIN)
-
Biometric time clock device integration (IDCube) Beta — the connection is set up with IDCube support
-
REST API (read:attendance / write:attendance scopes)
-
CSV / Excel bulk import
-
Native iOS / Android app Through the MangoApps app for iOS and Android, which clocks in and out over the same REST API
Manager Review & Approvals
-
Live manager dashboard — currently clocked-in, no-shows, absence rate, and expected-vs-actual attendance
-
Review queue for flagged and no-show records
-
Approve, reject, or adjust clock times (fully audited)
-
Bulk approve or flag selected records in one action
-
Context-specific outcomes (excused/unexcused absence, tardiness violation, security verified, time corrected)
-
Missing-punch request review and approval
-
Manager clock-in / clock-out on an employee's behalf
-
Absence and delay reports with configurable reason codes + high-severity no-show escalation
-
Re-list a no-show's shift to the open-shift marketplace for pickup
-
Attendance calendar (month / week / list) color-coded by status
Location & Fraud Prevention
-
GPS coordinates captured at clock-in and clock-out
-
Geofence enforcement per location (clock-in and clock-out GPS checked; outside the fence or without GPS flags review; the paired kiosk counts as on site)
-
IP address verification (passive / warning / strict modes)
-
Device fingerprint verification
-
Photo verification at clock-in and clock-out (desktop and mobile app; the photo is kept for a manager to compare, and a punch without one is flagged)
-
Kiosk rate-limiting and PIN brute-force lockout
Compliance & Premium Pay
-
Overtime calculation (weekly threshold)
-
Double-time calculation (weekly threshold)
-
Daily overtime (California-style daily thresholds)
-
Labor-law rule overrides per location
-
Meal and rest break compliance (required breaks auto-created; ending one short warns the employee and marks the break short)
-
Absence-policy attributes per reason code (paid/unpaid, documentation threshold, advance-notice days, occurrence limits)
-
Premium pay types on timesheet entries
Notifications, Reporting & Integrations
-
Late-arrival, no-show, auto clock-out, and missed clock-out alerts
-
Configurable notification rules by trigger, threshold, severity, and recipient targeting
-
Notification channels: in-app, email, and SMS
-
AI Attendance Monitor — optional alerts for clock anomalies, approaching overtime, no-shows, and weekly team summaries (every alert logged; each waits for approval until the monitor has earned trust)
-
Ask AI attendance agent — hours, clock status, punch records, tardiness, breaks, and exceptions answered in chat (read-only)
-
Admin attendance analytics (by location, by employee, fraud metrics) with CSV export
-
Scheduled SFTP attendance import / export (daily / weekly / monthly)
-
Payroll Connect — push approved timesheets to payroll
-
Leave Management — approved leave suppresses no-show flags
Limits & Specs
-
Auto clock-out max hours (default): 12 hours (admin-configurable, max 24)
-
Auto clock-out after shift end (default): 30 minutes (admin-configurable, max 480)
-
Early clock-in buffer (default): 15 minutes (admin-configurable)
-
Late clock-in grace period (default): 30 minutes (admin-configurable)
-
Kiosk PIN brute-force lockout: 5 attempts → 5-minute lockout
-
Pricing: License required — part of the Frontline Operations suite, or licensed on its own
Screenshots
Use cases
Resources
FAQ
It compares the clock-in timestamp against the scheduled shift start. A clock-in up to the late grace period after the shift starts (the Late Clock-in Buffer, default 30 minutes) counts as on time; later clock-ins are still accepted until the shift ends, but are marked late. Clock-in opens the early clock-in buffer (default 15 minutes) before the start. Ad-hoc shifts are always treated as on-time. Both buffers are admin-configurable.
Records can be created from the web, a Time Clock Kiosk, an IDCube biometric time clock (beta — the connection is set up with IDCube support and an admin), the REST API, CSV/Excel import, or a missing-punch request. Every record stores its punch source for audit.
A manager pairs a kiosk to a location, generating a passcode. Employees connect with that code and identify themselves by Employee ID plus a personal PIN. The kiosk takes no photo; where photo verification is required, a kiosk punch is flagged for the manager to review. Rate limiting locks out after 5 failed attempts for 5 minutes to block brute-forcing.
They can file a missing-punch request from the Time & Attendance app with the correct clock-in/out times, any breaks, and a reason. It is sent to their manager for review and must fall within the retroactive window (default 7 days, following the timesheet lockout setting). A request is never auto-approved; someone who holds the Time & Attendance write permission (managers and admins by default) skips the request and adds the day to their own record directly, and their timesheet is still approved by their own approver. The AI agent can only direct users to the form — it cannot log time on their behalf.
Yes. Every clock event syncs into the corresponding timesheet in real time, including break records. Hours feed overtime, double-time, daily-overtime, and premium-pay calculations, and approved timesheets can be pushed to payroll via Payroll Connect.
Time & Attendance records discrete clock events — each clock-in/out is a record with an on-time, late, or missed status, a punch source, and location/device verification. Timesheets aggregate those events into pay-period hours for review and approval. Every clock event (including breaks) syncs into the matching timesheet in real time, where the hours roll up into overtime, double-time, and premium-pay totals. In short: attendance answers "when did they punch and was it valid?"; timesheets answer "how many payable hours this period, ready to approve?"
When an employee clocks in, the system auto-creates each break type your business has marked as required — for example a 30-minute unpaid Meal Break and a 15-minute paid Rest Break. Paid break time stays in payable hours; unpaid break time is subtracted. If an employee ends a required break short of its configured duration, they are warned and the break is marked short (the record is not sent for review), and any break still in progress is auto-completed when they clock out.
Yes. Each punch can capture GPS coordinates, IP address, and a device fingerprint. Per-location geofencing checks the GPS position at clock-in and clock-out against the site's allowed radius, and where the geofence is enforced a punch made without GPS is flagged for review (a punch at the paired kiosk counts as on site); IP validation runs in passive, warning, or strict mode; and unrecognized devices are flagged. Punches made in the app, on the web or at the kiosk that fail an enabled check are flagged for the manager's review (strict IP mode refuses them). Optional photo verification keeps a clock-in and clock-out photo, taken on the desktop or in the mobile app, on the record for a manager to compare; a punch without one is flagged.
Yes, in beta. Time & Attendance connects to IDCube biometric and badge-based time clock devices. An IDCube connection is set up with IDCube support and an admin, as a system integration; punches from the device then sync in with a "time_clock" punch source and flow into the same timesheets and alert rules as web and kiosk punches. Device punches are trusted as on-site: the geofence, IP, device and photo checks do not run on them.
It is an optional autonomous agent that watches clock activity and sends alerts to the employee or their managers. Two switches decide what it watches: Clock Monitoring (clock anomalies, follow-ups and approaching-overtime warnings) and Tardiness Alerts (no-shows and alerts to managers). Every alert it sends is logged. While the monitor is new, each alert waits for approval; as it earns trust, routine alerts send on their own, and bulk or high-impact ones keep waiting until it reaches the highest trust level. It never changes a punch or timesheet.
