/ platform — 05 attendance · KE
Built into the platform — not a bolt-on. Clock in from a phone inside a geofence, a kiosk at the gate, or your own hardware terminals. Meridian reconciles every punch against the shift roster, across all your locations, and feeds verified hours straight into payroll, overtime and TOIL.
A geofence per site — HQ, warehouses, branches, field zones — managed from one board.
Mobile GPS · kiosk at the gate · your own hardware terminals via the device API.
Rotations, nights, split shifts, weekend crews — rostered per site, per team.
Verified hours flow into the payroll formula — overtime and TOIL computed, not retyped.
/ the ground truth problem
A geofenced office, a warehouse running two shifts on hardware terminals, and a field team on mobile GPS. Every punch lands on the same board, checked against the roster — and the one that doesn't fit gets flagged, not buried.
The flagged punch isn't rejected — it goes to the site manager with the distance, the time, and the employee's note. Honest edge cases get approved in one tap; patterns of abuse become visible. Verified hours flow into attendance.ot_hours — the same variable the payroll formula reads.
/ what's inside — 06 capabilities
Draw a radius around each location — clock-ins inside count silently, clock-ins outside get flagged with the distance for manager review. Strictness is per site, your call.
Rotations, night shifts, split shifts, weekend crews — rostered per site and per team, with punches reconciled against the shift they belong to, not just the day.
HQ, warehouses, branches, field teams — one live view of who's on site, on shift, late or absent, filterable by site and manager. No per-branch spreadsheets to merge.
Biometric readers, badge terminals, turnstiles — connect your own devices through the device API and their punches land in the same stream, tagged by gate and site.
Punches become timesheets automatically — managers only review the exceptions: missed punches, short days, flagged locations. Everything else just files itself.
Verified hours feed the payroll engine as a formula input — overtime at the right multiplier, TOIL accruing to its balance. No month-end re-typing from a register.
/ usually asked by ops leads
The punch is recorded and flagged — with the distance, the timestamp, and space for the employee's note. The site manager approves or rejects in one tap. You choose per site whether out-of-fence punches are flagged or blocked outright.
Your device — biometric reader, badge terminal, turnstile — sends each punch to the device API with an employee reference, a gate ID and a timestamp. We match it to the person and the shift, and it appears on the board like any other punch.
Mobile and kiosk punches queue on the device and sync when the connection returns, keeping their original timestamps. The board marks them as synced-late so nothing looks like it appeared out of nowhere.
Yes — that's the point of it being in-platform. Verified hours land in the payroll formula as attendance.ot_hours, overtime is computed at your multipliers, and TOIL accrues to its leave balance. One system, no export step.
/ the offer
Draw a fence around your first site and roster this week's shifts in about ten minutes. Hardware can follow once the board is live.
10 MIN TO FIRST FENCE + ROSTER · KE, UG, NG, CI, GH, ZA