A workforce that moves with the project
Sites open and close. Labour is a mix of on-roll and contractor. There is rarely an office, often patchy network, and the person approving is standing on the site rather than sitting at a desk.
What matters in construction & project sites
Attendance Without An Office
Phone-based punching at the site, with the register building itself as people arrive.
Contract And On-roll Together
Both visible in headcount and attendance, with their payroll and statutory treatment kept separate.
Approvals On A Phone
Site engineers approve leave and attendance corrections from where they actually are.
Site-wise Headcount And Cost
Manpower by site, which is the number a project review actually asks for.
Registers For Inspection
Attendance and wage registers produced from timestamps, per site, when required.
Fast Mobilisation
Documents read and drafted by AI, so staffing up a new site is not a week of data entry.
No office, no fixed reporting point
A construction workforce does not walk past a reception desk. Sites open and close, crews move between them, and the person who knows who turned up today is a supervisor standing in the open with a phone.
Attendance therefore has to work without infrastructure: a punch from a phone, bounded by the site's location, working on a weak connection, and readable afterwards as a proper register. Anything that assumes a fixed device at a fixed door is describing a different industry.
Contract and on-roll in one register
Most sites run a mix, and the compliance burden falls on the principal employer regardless of who issues the wages. Keeping contractor labour in a separate notebook is exactly the arrangement that fails an inspection.
Both categories sit in the same attendance and register structure, distinguished by their employment type rather than by being kept apart.
Mobilisation speed is the real constraint
A new site needs forty people onboarded in a week, most of them without email. Invite-based onboarding on a phone, with documents read rather than typed, is the difference between a site that starts on time and one that starts with a backlog of paperwork nobody ever clears.
How a site actually runs
Site opens
A workplace with its own location rules, holidays and statutory setup.
Crew mobilised
Invite-based onboarding on a phone; documents read rather than transcribed.
Attendance from the field
Phone punches bounded by the site, working on a poor connection.
Registers produced
Muster roll, wage and overtime registers per site, ready for inspection.
Questions from this sector
Network at our sites is unreliable. Does that break attendance?
Punches are captured on the phone and submitted when the network returns, so a weak signal delays the sync rather than losing the record.
We use labour contractors. Can we see their headcount?
Contractor workers can be tracked with their own employment type and appear in site headcount and attendance, while staying outside on-roll payroll.
Can costs be seen per project?
Headcount and payroll cost report by location, so each site’s manpower cost is visible without a manual sheet.
Our sites change every few months. Is that a problem?
Workplaces are first-class rather than an address field, so statutory profiles, holidays and policies follow the site. A new site is a setup step, not a migration.
Workers have no email and often no smartphone.
Punching works on an entry-level Android in their own language, and where phones are impractical the site device's export imports the same way. Neither route requires an app store.
How do we handle labour supplied by subcontractors?
Keep them visible on the register with their own arrangement recorded. The compliance exposure from subcontracted labour is the part most site paperwork leaves undocumented.
Can we start with one site and expand?
Yes, and most do. Start where the pain is, prove a month, then roll out. A big-bang rollout across every location is how a project acquires a reputation before it has results.
What does it take from our team each month?
After setup, the monthly job becomes reviewing what the system drafted rather than assembling it. The teams who see the biggest change are the ones who were retyping attendance into a spreadsheet.
See it on your own roster
Import your people, set your shifts, and watch the register build itself this week.