Two questions that must never be answered slowly: who is on site right now, and who worked how long.
Last updated
Zepth Core module
1 per 20
the evacuation-warden ratio OSHA suggests — one trained warden for roughly every twenty employees
OSHA Publication 3088
A suggested ratio for planning, not a rule with a penalty attached. The number matters less than the fact that somebody is counted BY someone, and that the someone knows who they were counting.
12:30–15:00
the UAE midday work ban — 15 June to 15 September, every year, on every outdoor site
UAE MOHRE
Reported compliance now runs above 99%, which makes the exceptions conspicuous rather than routine. Attendance data is how compliance is evidenced — and how heat-stress duty of care is demonstrated afterwards.
AED 5,000
per worker, for a midday-break violation — a LABOUR penalty, capped at AED 50,000 per site
UAE MOHRE (midday break rules)
Distinct from the civil-defence fine range cited on our asset-inspections page: different regulator, different regime, different violation. Per worker is the part that catches people — a single hot afternoon with ten men out is not one fine.
~3 m²
minimum sleeping space per worker in UAE labour accommodation
UAE Ministerial Decision 212/2014
Accommodation standards sit adjacent to attendance for a reason: on a site with camp-based labour, the attendance system is usually the only complete list of who the workforce actually is.
Site attendance answers those two questions, and they are not the same question. The first is an emergency question, and the answer has to be correct within seconds. The second is a money question, and the answer has to be correct within a payroll cycle.
The gate log is the source of truth for both. The muster roll and the daily report’s manpower figure are derived from it — and when they are maintained separately instead, they disagree, which is how you discover the problem at the worst possible moment.
When the alarm goes, the roll call has to be read from the LIVE gate log. Not from yesterday’s list, not from a printed roster, and not from the subcontractor’s recollection of who he brought this morning.
And the gap that kills is always the same gap: visitors and new inductions. The people who are least familiar with the site, least likely to know where the assembly point is, and least likely to be on anybody’s list — because they were not there yesterday, and yesterday is what the printed list describes.
OSHA suggests roughly one trained evacuation warden per twenty employees. The ratio is worth less than the principle underneath it, which is that every person on site must be counted by a specific someone, and that someone must know who they were counting. A headcount that comes out right by luck is indistinguishable, at the assembly point, from one that comes out right by design — until the day it does not.
Gate attendance, timesheets and the WPS salary file must all agree — and in the GCC, the consequence chain when they do not is severe and largely undocumented. A worker on the gate log who is not on the timesheet. A timesheet that does not match what was paid through the Wage Protection System. Any of these mismatches can raise a flag with the labour authorities, and the escalation that follows is not a fine — it is a freeze. A company with a WPS flag cannot issue new work permits. Which means it cannot mobilise labour. Which means the schedule stops, and it stops for a reason that has nothing to do with construction and cannot be solved by anybody on the project.
That is a payroll problem that arrives as a programme problem, and almost nobody plans for it. The commercial team treats WPS as an accounts matter. The project team treats mobilisation as a resourcing matter. The link between them is invisible right up to the moment it is the only thing that matters — and by then the remedy is administrative, slow, and entirely outside the project’s control.
Midday-break compliance is evidenced from attendance, or it is not evidenced at all. From 15 June to 15 September, outdoor work stops between 12:30 and 15:00. Reported compliance is now above 99%, which is worth reading carefully: it means a violation is no longer ordinary, it is conspicuous. And the penalty is per worker — AED 5,000 each, to a cap — so one hot afternoon with ten men working is not one fine. Attendance records are how you demonstrate you complied, and, if something goes wrong, how you demonstrate you took heat-stress duty of care seriously.
The subcontractor roll-up is the same unified-register problem that defeats toolbox talks. “How many of whose workers are on site?” must be answerable across twenty subcontractors, as one number, right now. Siloed per-subcontractor attendance produces twenty correct answers and no usable one — and at the assembly point, twenty correct answers is the same as none.
Biometrics: real benefits, real friction, and a client mandate that is arriving anyway. Biometric gates eliminate buddy punching, which is their entire point and a genuine one. They also meet gloves, dust, and a throughput requirement that at a 2,000-worker peak is brutally unforgiving — a two-second read is a sixty-seven-minute queue. Increasingly, GCC megaproject clients simply mandate them, which makes the trade-off academic; but plan the throughput, because a gate that cannot clear the shift change will be propped open, and a propped-open gate records nothing.
The muster is read from a stale list, so the visitor who arrived at nine is not on it — and the site spends the worst twenty minutes of its year trying to work out whether somebody is inside.
Gate counts do not match the daily report’s manpower figure, because the two are maintained separately by people with different incentives — and the discrepancy is discovered by a claims consultant, three years later, in a document that was supposed to be helping.
And attendance, timesheets and the WPS file drift apart quietly until a flag lands, permits freeze, and the project cannot mobilise. That failure looks like a schedule problem. It is a records problem, and it was visible for months.
Gate capture per worker — badge or biometric — carrying company, trade and induction status, so an unbadged or un-inducted person is a rejection rather than a conversation. Live on-site headcount by zone, and a muster mode that reads the live log rather than a printout.
Daily reconciliation to timesheets and to the manpower figure in the daily report, so the three cannot drift. And induction and certification expiries are checked at the gate — which is the only place where an expired certificate is cheap to discover, because everywhere else it is discovered by an inspector.
The muster roll is correct in seconds, including the visitor who arrived an hour ago.
Gate, timesheet and daily-report manpower agree — so the discrepancy is not discovered by the other side’s consultant.
WPS mismatches surface before they become a labour-authority flag, which is the difference between a correction and a permit freeze.
Midday-break compliance and heat-stress duty of care are evidenced from records rather than asserted from memory.
Badge or biometric, per worker, carrying company, trade and induction — so the un-inducted worker is stopped at the gate.
Who is on site, and where. During an evacuation these are the same question, and normally only one of them can be answered.
A roll call read from the live log rather than yesterday’s printout — which is where visitors and new inductions go missing.
One number across twenty subcontractors. Twenty siloed correct answers is the same as none, at an assembly point.
Daily, so gate, timesheet and salary file cannot drift into a labour-authority flag and a permit freeze.
The only place an expired certificate is cheap to find. Everywhere else, it is found by an inspector.
Badge or biometric, carrying company, trade and induction status. An un-inducted worker is a rejection at the gate, not a discovery on the scaffold.
Because “who is on site” and “where are they” are the same question during an evacuation, and only one of them is usually answerable.
Never from a printed roster. The people missing from yesterday’s list are exactly the people least likely to know where to go.
Three numbers that must agree and will not, unless something makes them. The discrepancy is cheap today and expensive in a claim.
Before the flag, not after it. A WPS flag freezes permits, and a permit freeze stops mobilisation — a payroll failure that arrives disguised as a programme failure.
Before it becomes a labour-authority flag. This is the highest-value check on the page, because the consequence at the far end is not a penalty — it is a permit freeze, and the project finds out when it tries to mobilise.
Workers on the gate log but never on a timesheet. Timesheets for workers who never passed a gate. Both are ordinary data errors, and both are also what fraud looks like.
Flagged at the moment of entry, which is the only moment at which it is cheap. The alternative is an inspector finding it, which is the same information at a much worse price.
The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.
Live on-site headcount by zone, company and trade — and the muster roll, generated from it rather than from a roster. Attendance reconciled daily against timesheets and against the manpower figure in the daily report. WPS consistency, ahead of any flag. Midday-break compliance evidenced by record. And induction and certification expiries, ranked by how soon they will stop somebody at the gate.
A muster roll answers “who is on site right now”, and it has to be right within seconds, because somebody is standing at an assembly point counting heads. A timesheet answers “who worked how long”, and it has to be right within a payroll cycle. Both derive from the gate log. Maintained separately, they will disagree — and you will discover that at the least convenient moment available.
Read the full answerBy reading the roll call from the live gate log, not from a printed roster — with wardens counting to a plan (OSHA suggests roughly one per twenty people) and a headcount rolled up across every subcontractor as a single number. The gap that kills is always visitors and new inductions: the people least likely to be on yesterday’s list, and least likely to know where to go.
Read the full answerBecause they are usually produced by different people, from different sources, with different incentives — one counting entries and one reporting productivity. The discrepancy is trivial to fix today and expensive later: in a delay claim, the other side will read both documents, and they will read the difference aloud.
Gate attendance, timesheets and the Wage Protection System salary file must reconcile. When they do not, the labour authorities can raise a flag — and the escalation is not a fine, it is a freeze on new work permits. A company that cannot issue permits cannot mobilise labour. So a payroll records failure arrives on your project as a schedule failure, with no construction cause and no construction remedy.
Read the full answerFrom 15 June to 15 September, outdoor work stops between 12:30 and 15:00. Reported compliance runs above 99%, which means a violation is now conspicuous rather than ordinary. The penalty is AED 5,000 per worker, capped per site — and “per worker” is the part that surprises people: one hot afternoon with ten men working is not one fine. Attendance records are how compliance is evidenced.
Read the full answerThey eliminate buddy punching, which is the point and a real benefit. They also meet gloves, dust and a throughput problem that is unforgiving at scale — a two-second read at a 2,000-worker shift change is an hour of queue. GCC megaproject clients increasingly mandate them anyway, so the question is usually not whether but how: plan the throughput for the peak, because a gate that cannot clear the shift change gets propped open, and a propped-open gate records nothing.
Related modules
Related answers
Terms defined here
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
A short, tailored walkthrough on your real workflow — no generic demo.