UAE Labour Law and Attendance: What Federal Decree-Law No. 33 of 2021 Actually Requires

UAE Labour Law — Federal Decree-Law No. 33 of 2021 and its executive regulations — sets the framework for every employment relationship in the UAE private sector. Most operations leaders know the headline numbers (8 hours a day, 48 a week, overtime calculated at a premium) but the granular requirements for what an attendance system must record are less commonly understood. This post walks through the practical attendance requirements and where most UAE workforce systems fall short.

What the law actually requires you to record

Three things, broadly:

1. Working hours per day, per staff member. Including start time, end time, and any breaks.
2. Compliance with the limits. Daily limit, weekly limit, mandatory daily rest, weekly rest, overtime caps, and sector-specific rules (Ramadan, hazardous occupations).
3. Retention of the records for the period the law specifies, available for inspection.

Where most UAE attendance systems fall short

1. They record the punch, not the working hour

A scan-in and scan-out generates two timestamps. The working hour is the gap between them, minus any breaks. Many systems leave the break-deduction logic to a manual spreadsheet at month-end. That is fragile, labour-intensive, and produces records that don’t reconcile with reality.

2. They don’t enforce mandatory rest between shifts

The law requires a minimum rest period between consecutive shifts. Most scheduling tools will happily produce a roster that breaches this rule, and most attendance systems will quietly accept the check-in regardless. The inspector will not be quiet about it later.

3. They handle prayer break inconsistently

Prayer break should be excluded from billable working hours. Most systems either include it (so paid hours are too high) or require manual deduction (so the record doesn’t match payroll). Neither is right.

4. They don’t flag overtime caps

The law caps overtime per day and per week. A worker can do six hours of overtime in a single day if you let them — but you generally shouldn’t. The system should flag breaches before you pay them, not after.

5. They don’t produce inspection-ready exports

When an inspector asks for the working-hour record of a single staff member on a single day, you need to produce it within minutes. Many systems can produce a roll-up; few can produce a clean per-staff-per-day record with breaks, overtime, and rest periods visible.

What a clean record looks like

For each staff member on each working day, the record should include:

• Check-in time (server timestamp, tamper-resistant)
• Check-out time (server timestamp)
• Total elapsed time
• Configurable break deductions (prayer break, lunch break, applied automatically)
• Net working hours
• Overtime hours, if any
• Mandatory rest period until the next shift
• Compliance status against daily limit, weekly limit, and overtime cap

Where the audit trail matters

Working-hour records are not just a payroll input; they are legal evidence. The audit trail behind every record should be tamper-resistant: each check-in cryptographically signed, edits logged with who-and-when, and retention for the full legal period plus a reasonable buffer.

Practical next steps

1. Pick one staff member, one week. Try to produce an inspection-ready record from your current system. Note where it falls short.
2. Check your retention policy. Are you keeping working-hour records for the full legal period?
3. Verify your overtime caps and mandatory rest rules are configured and enforced, not just defined.
4. Pull a random sample of 5 working days and check whether the recorded hours match what you actually paid. Drift between record and pay is a yellow flag.

Aiya is designed around UAE Labour Law from day one. Working-hour records include all eight fields above by default. Mandatory rest, overtime caps, and prayer break are enforced at the scheduling stage and at check-in. Records are retained for the legal period in a tamper-resistant audit log. Inspection-ready evidence is exportable per-staff-per-day in seconds.