HR & Geofenced Attendance
I will build an HR and attendance system with geofenced clock-in and payroll
About this gig
A signed register tells you who signed it. It doesn't tell you who was at work.
I build HR and attendance systems where staff can only clock in inside the geofence around their work location. Each record carries device and session history, leave and shifts come from the same data, and payroll is calculated from what happened instead of what someone typed.
What you get:
- Staff records, documents and contracts
- Geofenced clock-in and clock-out on staff phones
- Device and session history on each record
- Shifts, rosters, leave requests and approvals
- Payroll calculation, payslips and exports
- Review of flagged records by a manager or peers, guided by your policy
Geofenced attendance and HR are modules in WeSelling, my business operating system, and I built HR dashboards inside the appraisal platforms used by the NCAA, NIMC and RMAFC.
Tell me how many staff and locations you have, and how attendance is recorded today.
Use cases
Retail and restaurant shifts
Rosters, swaps and clock-ins limited to each branch.
Field staff
Site visits logged with location for sales reps, technicians and inspectors.
Schools
Teacher attendance and leave with automatic substitutes.
Factories
Shift patterns, overtime and late-arrival rules.
Remote teams
Check-ins, timesheets and leave without a physical site.
Payroll
Hours, allowances, deductions and payslips from the same records.
Onboarding and documents
Contracts, IDs and certificates stored per employee with expiry reminders.
Private clock-in
Optional zero-knowledge proof that a phone is inside the geofence, without sending GPS.
What changes
Today
- Buddy punching and signed registers nobody trusts
- Leave requests live in WhatsApp and get lost
- Payroll gets rebuilt from attendance sheets every month
- Staff records sit in paper files and personal laptops
After
- Clock-in allowed only inside the work location's geofence
- Device and session history attached to every attendance record
- Leave, shifts and payroll computed from the same data
- Staff records, documents and contracts in one place
How it works
- 01Staff arrives on site
- 02Phone confirms location
- 03Clocks in
- 04Shift and leave checked
- 05Payroll calculated
Compare packages
| Package | Starter$720 | Business$1,850 | Scale$4,200 |
|---|---|---|---|
| What it is | Staff records and geofenced clock-in for one location, with attendance reports | Multiple locations, shifts, leave, payroll calculation and exports | Appraisals, documents, review of flagged records and a staff mobile app |
| Locations | 1 | Up to 5 | Unlimited |
| Staff records | ✓ | ✓ | ✓ |
| Geofenced clock-in | ✓ | ✓ | ✓ |
| Device and session history | ✓ | ✓ | ✓ |
| Shifts and rosters | – | ✓ | ✓ |
| Leave requests and approvals | – | ✓ | ✓ |
| Payroll calculation and payslips | – | ✓ | ✓ |
| Review of flagged records | – | – | ✓ |
| Appraisals | – | – | ✓ |
| Staff mobile app | – | – | ✓ |
| Delivery | 10 days | 20 days | 32 days |
| Revisions | 2 | 3 | 4 |
Add-ons
- Faster delivery+30% of the package
- Matching mobile app screens (React Native)+$600
- Reporting dashboard+$150
- 90 days of support and small changes+$240
Built before
Who it's for
- Retail chains
- Restaurants
- Schools
- Factories
- Field service companies
What I'll need from you
- Number of staff and locations, with addresses
- How attendance, leave and payroll work today
- Your payroll rules and pay schedule
- Who approves leave and reviews flagged records
Questions, answered
Can staff fake their location?
Location on its own can be spoofed. I layer it with device and session history, and flagged records go to a reviewer who weighs them against your company policy.
Does it need fingerprint scanners or biometrics?
No. It's designed for teams that can't use biometrics or passkeys, and it can add them where you can.
Which payroll rules does it support?
Yours: hourly or monthly pay, overtime, allowances, deductions and tax. For Nigeria I can include PAYE and pension calculations using rules you confirm with your accountant.
Who owns the code and accounts when we finish?
You do. Code goes to your repository, and services run on accounts in your name, so you are never locked to me. I hand over logins, keys and a short guide.
What if my project doesn't fit a package?
Send a message describing what you need. I reply with a custom offer priced to the actual scope, often after a short call.
The thinking behind it
Tools and tags
- Next.js
- PostgreSQL
- Prisma
- Geolocation API
- React Native
- Telegram
- Expo Location
- Paystack Transfers
- Noir
- Metabase
- #hrsoftware
- #attendancesystem
- #geofencing
- #payrollsystem
- #employeemanagement
