Abu Dhabi's Department of Municipalities and Transport (DMT) has updated several OSHAD-SF Mechanisms to align more closely with ISO 45001:2018, tightening requirements around leadership commitment, worker participation, and management of change. If your OHS management system in Abu Dhabi hasn't been reviewed against these updates, there's a real gap between what you think you're compliant with and what an OSHAD inspector will actually check.

For context: OSHAD-SF is Abu Dhabi's own occupational safety and health regulatory framework, administered by the DMT, and it applies to every employer in the emirate — construction, hospitality, retail, oil and gas, all of it. Employers with 30 or more workers must maintain a documented OHS management system built on the same Plan-Do-Check-Act structure as ISO 45001. This update sharpens exactly where the two frameworks now overlap, and where OSHAD-SF still asks for more.

What actually changed

Three areas of OSHAD-SF compliance got noticeably more specific:

  • Leadership commitment now requires visible, documented senior management involvement in safety decisions — not a policy signed once and filed away.
  • Worker participation now requires formal channels for employees to raise hazard concerns, with a paper trail showing those concerns were logged and addressed.
  • Management of change now requires a documented process before altering equipment, processes, or site conditions — meaning a change to a piece of machinery or a site layout needs a recorded risk review before it happens, not after.

None of these are new concepts to anyone running ISO 45001. What's changed is that OSHAD inspectors now expect to see them as living, dated records — not policy statements.

Why ISO 45001 certification doesn't automatically cover you

This is the part that catches out ISO-certified organizations specifically: ISO 45001 provides strong alignment with OSHAD-SF's PDCA framework, but it does not automatically satisfy every OSHAD-SF requirement. OSHAD-SF's Codes of Practice are prescriptive in ways ISO 45001 is not — specific incident reporting timelines, specific competency levels, specific controls per hazard type.

An organization with a functioning ISO 45001 system already produces most of the evidence an OSHAD-SF review looks for: hazard identification, risk assessment, competence records, incident investigation, management review. What it doesn't automatically produce is Code of Practice-specific compliance and OSHAD's particular KPI submissions and reporting formats. Running both as one integrated system is normal practice — and considerably less work than maintaining two separate ones.

What this means for your training records specifically

Worker participation and leadership commitment both live or die on documentation. If an OSHAD auditor asks how a hazard concern raised by a site worker three months ago was resolved, or wants to see that a supervisor completed leadership-track HSE training before signing off on a management-of-change decision, "we did that, trust us" isn't an answer. You need a timestamped, role-mapped record.

That's the recurring theme across every UAE HSE update this year, from MOHRE's heat stress rules to this OSHAD-SF alignment: compliance is shifting from policy documents to provable, ongoing training and competency records. An LMS that tracks completion by role, flags expiring certifications, and produces an audit trail on demand isn't a nice-to-have anymore — it's the difference between passing an OSHAD-SF review and scrambling to reconstruct one after the fact.