Employee Attendance App for Factory Teams: WiFi, GPS, Device

A good employee attendance app for factory use does three things at once: it confirms the worker is physically on site, it confirms it is really that worker, and it turns every check-in into data a manager can act on the same day. The most reliable way to do this without biometrics is to combine three signals on the employee’s phone — the factory WiFi network, a GPS geofence and a device bound to the employee — and only accept a check-in when all three agree.

This guide explains how that works, why it beats paper sheets and fingerprint terminals on a real production floor, what it costs to build versus subscribe, and how to roll it out to a plant with a few hundred people. It is based on HR Attendance, the HR management app with attendance and access control that we built for a glass factory and now offer as a ready product.

Why paper sheets and fingerprint readers fail on the factory floor

Most plants we talk to use one of three methods: a paper register at the gate, a spreadsheet filled in by a shift supervisor, or a fingerprint/card terminal. Each breaks in a predictable way.

• Paper and supervisor spreadsheets depend on one person’s honesty and handwriting. Late arrivals get rounded, absences get “fixed” at the end of the month, and HR re-types everything for payroll. Nobody can answer “who is on site right now?” without walking the floor.
• Fingerprint readers struggle with the hands of people who handle glass, cement, oil or chemicals. Worn or dirty fingerprints fail to scan, queues form at shift change, and the device becomes a single point of failure. Biometric data is also sensitive personal data in most jurisdictions, which adds legal overhead.
• Card and fob terminals solve the scan problem but create a new one: a card can be handed to a colleague. That is the classic buddy-punching problem.

On top of that, a single terminal only knows that someone touched it. It does not know about breaks, the late-arrival grace rules in your policy, or the leave that was approved last week. The result is that attendance data exists, but managers still reconcile it by hand.

Three presence signals: WiFi network, geofence, bound device

A phone-based system can check several independent facts at the moment of check-in. In our build, a check-in is accepted only when all of these pass:

Signal	What it proves	How it can be faked	Why combining helps
Factory WiFi (registered network identifier)	The phone is within range of your access points	Hard to fake from outside the building	Stops “check in from the car park” or from home
Geofence (GPS/location inside a polygon or radius)	The phone is physically at the site	Mock-location apps on rooted phones	WiFi check makes spoofed GPS alone insufficient
Bound device (approved device ID, signed request)	It is this employee’s approved phone	Borrowing a colleague’s phone	Colleague would need the phone and to be on site and the login

The WiFi-based attendance system part is the strongest signal indoors, where GPS is often inaccurate among steel roofs and concrete. The employee attendance system with geofencing part covers large sites and outdoor yards. Device binding ties it all to a person.

A practical note: both iOS and Android restrict which apps can read the current WiFi network name and require location permission for it. A serious implementation handles these permissions properly, explains them to the employee at onboarding, and falls back gracefully (for example, flagging a check-in for supervisor review instead of silently rejecting it) when a signal is unavailable.

In our HR Attendance app, every request from the app is signed with an HMAC key tied to the approved device, so the server can reject requests that did not come from a registered phone.

Stopping buddy punching without biometrics

Buddy punching — one employee clocking in for another — is the main reason factories buy biometric terminals. A prevent buddy punching app approach can get most of the benefit without storing fingerprints or face templates:

1. One approved device per employee. A new phone requires admin approval. Logging in on a colleague’s phone does not work.
2. One check-in, one break, one check-out per day. The rules are enforced on the server, so repeated or out-of-order events are rejected.
3. On-site proof at the moment of the event. WiFi plus geofence means a friend cannot check you in from the canteen while you are still on the bus — the friend would need your phone, your credentials and to be on site.
4. Anomaly review. Check-ins that pass some checks but not others go into a review queue rather than being silently accepted.

No system makes fraud impossible. The goal is to make it inconvenient enough that it stops being routine, while keeping the honest majority’s check-in to a few seconds.

Employee attendance app for factory teams: off-the-shelf vs custom

There are many good GPS clock in app for employees products on the market, typically priced per user per month. For a 20-person team with standard hours, a SaaS subscription is usually the right answer. Factories are different in a few ways:

• Headcount is large and mostly hourly. Per-seat fees multiply across hundreds of workers and every year you use the product.
• Shift rules are specific. Rotating shifts, night premiums, grace periods, automatic deductions for lateness and local labour rules rarely fit a generic template.
• Payroll export must match your accounting system exactly. A CSV that HR re-formats every month is where errors come back in.
• Data location matters. Some manufacturers want attendance data on their own server, not in a vendor’s cloud in another country.

	Off-the-shelf SaaS	Custom system (e.g. HR Attendance)
Upfront cost	Low	Custom business software typically $15k–$50k+; a configured ready product costs less than a from-scratch build
Ongoing cost	Per user per month, grows with headcount	Hosting and support; does not scale per seat
Shift and late rules	Vendor’s options	Your exact policy
Payroll export	Generic formats	Your accounting format
Data ownership	Vendor’s cloud	Your server or your cloud account
Time to start	Days	Weeks for configuration; months for a full custom build

Ranges vary with scope. The honest way to decide is to put both options on a three-year cost sheet, including the time HR spends reconciling. We go deeper into this decision in custom software vs SaaS.

Architecture of our build: Flutter app + Laravel/Filament admin

Here is how our HR Attendance app is put together, as a reference for what a production-grade time and attendance app for manufacturing needs:

• Mobile app (Flutter) — one codebase for Android and iOS. Check-in, break, check-out, leave requests, personal history. Built by our mobile team.
• Admin panel (Laravel + Filament) — employees, departments, shifts, approved devices, sites and geofences, late policy, leave approvals, reports.
• Database (PostgreSQL) — attendance events stored with the signals that verified them, so every record can be audited later.
• Security — HMAC-signed requests from approved devices; the server sits behind Cloudflare Tunnel, Access and WAF, so there are no open inbound ports on the host.

Presence verification — WiFi + geolocation + approved device — happens on every event. The late policy, including grace rules and automatic deductions, is configured in the admin panel rather than hard-coded, so HR can change it without a developer.

Reports managers actually use: lateness, shifts, payroll export

Attendance data is only useful if it answers questions quickly. The reports that matter most in practice:

• Who is on site now — by department and shift.
• Lateness — daily and monthly, with grace rules applied, so a two-minute delay under the grace limit does not show as a violation.
• Weekly and monthly summaries — hours worked, breaks, absences, approved leave.
• Deductions — calculated from your late policy, visible to HR before payroll is run.
• Payroll export — in the columns and format your accountant already uses.

A useful test for any system you evaluate: can a shift manager answer “who was late more than three times this month and was it excused?” in under a minute, without Excel?

Rollout plan for a 100–500 person plant

A rollout that respects production usually looks like this:

1. Week 1 — Policy and setup. Agree shift patterns, grace periods and deduction rules on paper. Register the WiFi networks, draw the geofences, import employees and departments.
2. Week 2 — Pilot. One department or one shift (30–60 people). Keep the old method running in parallel. Watch for dead zones in WiFi coverage and phones with permission problems.
3. Week 3 — Fix and communicate. Adjust geofences and access points, finalise the FAQ for workers, train supervisors on the review queue.
4. Weeks 4–6 — Department by department. Enroll and approve devices in batches at shift change, with a help desk at the gate for the first days.
5. First payroll cycle — Parallel run. Compare the export with the old process once, then switch off paper.

Plan for employees without a smartphone. A small pool of shared, site-locked devices or a supervisor-assisted check-in keeps the system fair.

Privacy and employee communication

An attendance app is a workplace monitoring tool, and people will ask what it sees. Answer before they ask:

• Location is checked at check-in, break and check-out, not tracked all day. Say this plainly and design it that way.
• No biometrics are stored.
• Explain what data is kept, for how long and who can see it. Put it in a one-page notice and in the app.
• Follow local data-protection law. In the EU that is GDPR; other countries have their own personal-data laws. Get a lawyer’s review of the notice and retention period.

In our experience, adoption depends more on this communication than on the technology. Workers accept a system that is transparent and fair; they resist one that feels like surveillance.

How Racool Studio can help

We design and build business software and AI automation for companies that have outgrown paper and spreadsheets. For attendance, you do not start from zero: HR Attendance is our ready HR management app with attendance and access control — Flutter mobile app, Laravel/Filament admin, PostgreSQL, WiFi + geolocation + approved-device verification, late policy and leave management, weekly and monthly reports, deployed behind Cloudflare with no open ports.

We configure it for your shifts, sites and payroll format, or extend it into a custom build if you need integrations with access control, ERP or accounting. We also build the surrounding systems — see our guide on replacing Excel with custom software for what usually comes next.

Book a demo configured for your shifts — tell us your headcount, number of sites and shift pattern, and we will show you the system with your rules and give you a cost range for both a configured rollout and a fully custom build.