Enterprise Resource Planning

The deeper problem wasn't attendance. It was that nobody could answer a simple question — who is where, right now, and what is it costing us? — without a day of detective work.

So we solved it in two connected moves: a smart attendance app designed around how field workers actually move, and a full ERPNext implementation underneath it, so that every check-in flows straight into payroll, projects, and HR without a human re-typing anything.

The Challenge: One App, Four Very Different Workers

The hard part of this project wasn't the technology. It was the people. The company needed one attendance system that worked for four distinct types of workers — each with different routines, different locations, and very different levels of comfort with a smartphone.

Site workers report to a fixed location and needed something nearly invisible: open the app, mark in, done. Roaming supervisors move between multiple sites a day and needed attendance that followed them — logging not just that they worked, but where. Office staff needed simple in-out tracking. And drivers, the hardest group to account for anywhere, needed trip-based logging tied to actual movement rather than a checkbox at the end of the day.

A one-size-fits-all punch clock would have failed three of the four groups. So we didn't build one.

The Solution, Part One: Attendance That Verifies Itself

We built a mobile app with role-specific check-in flows on a common backend. Each worker sees only the flow designed for their job, and every punch — regardless of role — passes through two layers of verification.

The first is location. Every check-in is GPS-tagged, and geofencing ensures a fixed-site punch only counts inside the site boundary. A site worker can't mark attendance from home; a supervisor's day reconstructs itself as a verified trail of site visits.

The second is identity. AI-powered face verification confirms the person checking in is the person on the roster. That quietly killed the oldest trick in field attendance — buddy punching, where one worker marks in for an absent colleague. There's no card to share, no PIN to pass along. The face is the credential.

Because tech comfort varied wildly across the workforce, we designed for the least technical user, not the most. Check-in is two taps and a glance at the camera. Adoption didn't come from training sessions — it came from there being almost nothing to learn.

The Solution, Part Two: ERPNext as the Backbone

Attendance data is only as valuable as what it connects to. That's why, alongside the app, we implemented a complete ERP system for the company on ERPNext — the open-source platform covering HR, payroll, projects, purchasing, and accounting in one place.

This is where the project stopped being an attendance app and became an operating system for the business. Every verified check-in lands in ERPNext as a clean attendance record, mapped to an employee, a site, and a project. Payroll picks it up automatically — hours, overtime, and site allowances calculated from data that already proved itself, with no month-end reconciliation marathon. Project managers see labour hours posting against their projects in real time, which means project costing finally reflects reality instead of estimates. And HR runs leave, shifts, and employee records from the same system the attendance flows into, instead of a parallel spreadsheet universe.

Choosing ERPNext also kept the economics sane for a growing company: no per-user licensing spiral, full ownership of their data, and a platform that can grow into inventory, procurement, and equipment management as the business does.

What Changed

The company went from end-of-week guesswork to a live, timestamped, GPS-tagged, AI-verified log of their entire field workforce — one that feeds payroll and project costs on its own. Disputed hours dropped to near zero, because every record carries its own proof. Supervisors got back the twenty minutes per shift they used to spend on registers. And management gained something they'd never had: a single dashboard answering who is where, what each project's labour is actually costing, and how crews are being utilized — all from one system.

The Takeaway

Most attendance projects fail in the last mile: the data gets captured and then dies in a silo. The lesson from this build is to treat attendance not as an HR checkbox but as the front door to your ERP. When a two-tap, AI-verified check-in flows straight through to payroll and project costing, you don't just know who showed up — you know what your business is really spending, in real time. That's the difference between collecting data and running on it.

Running a field workforce on spreadsheets and registers? Talk to us about a smart attendance and ERPNext implementation designed around how your people actually work.