Geofenced clock-in validation
Attendance validated against job-site or yard geofence, not just a badge tap. Anomalies are flagged before they become payroll disputes.
Pillar 02 · Ports Pillar
Time and attendance that survives a grievance or HOS review.
Every punch is validated, every exception is logged, and every supervisor decision is attributable. Payroll gets a clean file. Grievances and HOS challenges resolve themselves when the data is clean.
What this pillar does
The specific work this pillar automates.
Missed-punch reconciliation
AI-assisted reconstruction of missed punches based on work orders, dispatch assignments, ELD events, and supervisor attestation.
Shift anomaly detection
Unusual in-out patterns, unexplained overtime, and conflicting assignments surface to supervisors in real time.
Break and rest compliance
Break windows, DOT rest hours, and fatigue rules enforced and logged — surfaced to dispatch for the next shift.
Grievance-defensible audit trail
Every entry, edit, and override is attributable, timestamped, and replayable. If a grievance or HOS challenge arises, the record speaks for itself.
Supervisor review queues
Exception cases surface to a supervisor queue with all context attached — no hunting across separate systems.
How the workflow runs
From trigger to completion.
- Step 01
Clock event captured
Events arrive via mobile, kiosk, biometric, badge reader, or ELD. Geolocation and device metadata come with the event.
- Step 02
Validation runs
The event is checked against the worker's dispatch assignment, geofence, and rule set.
- Step 03
Anomaly surfacing
Any deviation — late, early, out-of-zone, no matching assignment — is flagged and routed to the right supervisor queue.
- Step 04
Supervisor attestation
Missed punches and exceptions are reconciled with context attached. Supervisor decisions are logged with reasoning.
- Step 05
Payroll handoff
Clean, rule-applied time records pass to the payroll reconciliation pillar — no re-keying, no guesswork.
Integrations
Systems we already speak.
Badge readersBiometric clocksMobile kiosksELD devicesPayroll systemsHRIS
Modeled · terminal pilot
90%+
Modeled auto-reconciliation rate for missed punches against dispatch assignments and work-order context.
FAQ
Questions buyers ask us first.
The honest answers. If your question is missing, book a fit call and we will answer it live.
Do you replace our time clocks or ELDs?
No. Kavell works with your existing clocks, badge readers, mobile apps, and ELD devices. We ingest the events and run the validation, reconciliation, and audit trail on top.
How are union pay codes and DOT HOS handled?
Pay-code interpretation is configurable by classification, shift, and rule. DOT HOS is enforced against driver profiles. Interpretation happens before hand-off to payroll, so payroll receives a ready file.
What about biometric privacy?
Biometric data, when used, is stored per your regulatory posture. Kavell does not retain raw biometric templates — we record match events and supervisor overrides only.
Can supervisors edit time entries?
Yes, with proper attribution. Every edit is logged with supervisor identity, reason code, and before/after values. Edits are fully reversible.
How long is the audit trail retained?
Default retention is seven years, configurable per regulatory and union-contract requirements.