Build guide
Building an employee attendance app with location check-in
In short
An attendance system is a field app for employees, an admin console for managers and a server that sends reminders and reconciles records. The hard parts are location accuracy, store location rules and employee privacy. A first release takes roughly 10-16 weeks.
Who this is for
Business owners and HR teams who want staff to check in from their phones and managers to see accurate attendance.
What the product has to do
- Employee field appCheck in and out, view own history, request corrections and receive reminders.
- Admin consoleManagers set up employees, sites and shifts and review attendance.
- Location check-inVerifies that a check-in happened at or near the work site, with a clear rule for what counts as valid.
- Shifts and schedulesWho works when, with rules for late arrival and overtime.
- ReconciliationA scheduled job that closes open days, flags missed check-outs and corrects records.
- Push notificationsReminders for shifts, missing check-ins and approvals.
- Leave and correctionsRequests and approvals that adjust the attendance record.
- Reports and exportAttendance summaries for payroll.
The stack, and why
| Layer | Choice | Why |
|---|---|---|
| Apps | Two Flutter apps: field and admin | Shared code and one skill set for both the employee and manager sides. |
| Server | Node.js with Express | Small, well-understood back end that is easy to host. |
| Push | Firebase Admin SDK | Sends push from the self-hosted server. |
| Scheduled jobs | node-cron | Runs reconciliation on a schedule on the same server, with no cloud-functions plan needed. |
| Hosting | A VPS with PM2 | Predictable cost for a business tool. Today I would add a managed job queue once the number of companies grows. |
What ships first, and what waits
Version one
- Employee check-in and check-out
- Admin console for employees and sites
- Simple location validation
- Daily attendance report
- Push reminders
Later
- Shift planning and overtime rules
- Leave management
- Payroll export
- Offline check-in with later sync
- Photo or biometric verification
Build order and timeline
- 1-2 weeksPolicy and designAttendance rules, location policy, privacy notice and screens agreed.
- 3-5 weeksServer and admin consoleAPI, employee and site management, reports.
- 3-5 weeksField appCheck-in flow, history and reminders.
- 2-4 weeksReconciliation and pilotScheduled jobs, edge cases and a pilot with one team.
Want a number for your own scope? The app cost calculator turns platforms and features into an estimate.
Rules you cannot skip
- Background location on Google Play
Play allows background location only when it is core to the app and gives significant user benefit, and requires a prominent in-app disclosure and a Play Console declaration. Attendance taken when the employee taps check-in works with foreground access, which Google prefers.
Official source - Location services on iOS
Use location only when directly relevant to the app's features, tell users why and get their consent before collecting it.
Official source - Foreground location services on Android
A foreground service of the location type needs the matching permission and cannot start from the background without background location access.
Official source - Employee data
If you process data of people in the EU, GDPR principles such as purpose limitation, data minimisation and storage limitation apply. Tell employees what you collect and keep it only as long as needed.
Official source
Where these projects go wrong
- Tracking staff outside work
Continuous tracking is a privacy and store-review problem. Collect location only at check-in and check-out unless there is a stated work reason.
- Missing check-outs
People forget. A scheduled reconciliation job that flags and closes open days is part of the core, not an extra.
- Inaccurate GPS indoors
Location can drift inside buildings. Define a tolerance and give managers a way to approve exceptions.
- Buddy check-ins
Location alone does not prove who is holding the phone. Decide early if you need photo or device checks.
- Usage-priced cloud bills
Running push and jobs on cloud functions can make costs unpredictable. Workforce uses a self-hosted server to keep them steady.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
Problems you will meet on this stack
req.cookies is undefinedreq.cookies is undefined or empty in a Firebase Cloud Function behind HostingTarget of URI doesn't exist: 'firebase_options.dart'.firebase_options.dart does not exist in a Flutter projectUndefined class 'FirebaseUser'.FirebaseUser no longer exists in firebase_authCORS header 'Access-Control-Allow-Origin' missingFlutter web request fails with a CORS error and Dart code cannot fix itCould not find com.google.firebase:firebase-analytics-ktx:.Gradle cannot find com.google.firebase:firebase-analytics-ktxCannot GET /Angular app shows 'Cannot GET /' when served by a Node.js server