A construction site is the hardest place to run attendance and the place where getting it wrong costs the most. The muster roll is a notebook, the supervisor is the system, and the labour bill is a negotiation.
What the site needs
- A muster that lives on a phone, marked at the site boundary.
- Daily wage handled natively, not forced into a monthly salary structure.
- Contractor labour recorded against the site, so cost per site is real.
- Overtime from marked hours.
- Payroll that reads all of it without a rebuild.
HR, GPS attendance, shifts, leave, payroll, tax declarations, onboarding, engagement, projects and timesheets — one employee record behind all of it.
Start free See the demoWhy geofencing rather than a device
Devices need power, shelter and someone to maintain them, and a site has none of those reliably. A geofenced check-in on the supervisor’s phone works on day one at a new site and keeps working when the site moves.
How MizUp BMS handles it
MizUp BMS provides GPS attendance, shifts and rosters, employee management, leave and holidays, and payroll with tax and loans on one record. Attendance is marked against the site, so labour cost per site is available without a separate ledger, and payroll reads the marked days rather than a re-keyed summary.
Access is per module, so a site engineer marks attendance without seeing salaries. Material and client billing run in MizUp Finance, and site safety induction can be delivered as a course in MizUp EOS.
What it costs
From Rs 79 per employee per month. See BMS pricing.
Where to start
One site, one month, marked on a phone. Then compare with the notebook. Explore MizUp BMS.
Where sites usually go wrong
- The muster roll as the only record. A notebook held by one supervisor is a single point of failure and an unverifiable one.
- Daily wage forced into monthly salary logic. It produces a manual adjustment every cycle, which is where errors and disputes come from.
- Contractor labour outside the system. The site then knows what it was billed, not what it cost.
- Attendance marked from the site office. If the check-in happens at the office rather than the boundary, the geofence is decorative.
- Overtime agreed verbally. On a site this is the most common source of dispute, and the easiest to remove.
- No plan for a site that moves. Sites open and close. A system that needs installation per location will not keep up.
A realistic first thirty days
| Week | Focus | What good looks like |
|---|---|---|
| Week 1 | One site | Workers loaded with daily or monthly rates; geofence set at the site boundary. |
| Week 2 | Marking at the boundary | Supervisor marks the crew where the work starts, not at the office. |
| Week 3 | Contractor labour included | Recorded against the site with the contractor as the cost centre. |
| Week 4 | Compare with the bill | Run the derived labour cost against the labour bill you would have paid. |
That final comparison is usually the entire business case. Most sites find a gap in the first month that exceeds a year of software cost.
The numbers worth watching
| Metric | Why it matters | How to read it |
|---|---|---|
| Labour cost per site | What the project is actually consuming | Derived from marked attendance, not from the bill. |
| Muster versus bill variance | The number that justifies the exercise | Compared monthly for the first quarter. |
| Attendance marked at the boundary | Whether the geofence is being respected | Share marked inside the fence versus outside. |
| Overtime hours by trade | Points at scheduling, not effort | Weekly, by contractor and by trade. |
| Days from site opening to first marked attendance | How quickly the system keeps up | Should be the same day. |
A site is a hostile environment for software
Dust, sun, no shelter, patchy connectivity and a workforce that changes weekly. Any system that assumes a desk, a stable network or a fixed installation will be abandoned within a month and replaced by a notebook.
That is why the requirements here are unusually narrow: mark a crew at a boundary, on a phone, quickly, offline-tolerant, with contractor labour treated the same as direct labour. Everything else is optional.
It is also why the business case is unusually clear. The gap between what the muster says and what the labour bill claims is rarely small, and it is not usually fraud — it is the inevitable result of a record nobody can verify.
Make the record verifiable and the gap closes on its own.
How this fits with the rest of your stack
Construction has two cost lines that decide a project: material and labour. Material is usually tracked properly; labour is usually estimated.
On MizUp, BMS holds workers, rates, geofenced site attendance, rosters and payroll with statutory deductions, and Finance covers purchase orders, material invoices, delivery challans and client billing with GST. Both sit in one organisation, so a site can be a cost centre in both.
Safety inductions can be delivered as a course in EOS against the same worker record, which is increasingly what a client audit asks to see.
Daily wage is not a smaller version of salary
The most common implementation error on a construction site is treating daily wage staff as monthly staff with a different number. They are a different payroll shape entirely: paid on days present rather than days in the month, often weekly rather than monthly, frequently with an advance against wages, and with a headcount that changes between one week and the next.
A system that handles this properly needs three things. Rates held per worker rather than per grade, because negotiation happens at the gate. Payment cycles that can be weekly for some workers and monthly for others in the same site. And advances tracked against the worker so a deduction does not become an argument on payday.
Where sites get into difficulty is with the advance. It is almost always recorded informally, usually by the same supervisor who marks attendance, and it is the single most common cause of a wage dispute.
Bringing it into the same record as attendance costs nothing and removes most of the friction on payment day.
Related reading
- HRMS for manufacturing plants
- HRMS for logistics and transport
- Attendance and leave management systems
- Payroll process in India, step by step
Frequently asked questions
How is site attendance captured without a biometric device?
Geofenced check-in on a supervisor’s phone, marking the crew present at the site boundary. It survives dust, power cuts and a site that moves.
Can it handle daily wage workers?
Yes. Keep them as employee records with a daily rate, and payroll reads the days actually marked present.
What about labour supplied by a contractor?
Record them against the contractor as the cost centre so site labour cost is one number, whoever is paying the individual.
Does it work across several sites?
Yes - attendance is marked against the site, so cost per site is available without a separate register.
How does overtime work on a site?
From marked hours against the rostered day, at the rate your policy sets.
