On an Abu Dhabi construction project, dust should appear as a defined management subject within the project's occupational safety and health documentation. The central published reference is ADOSH-SF Code of Practice 53.1, OSH Construction Management Plan, Version 4.1, dated 16 February 2026 and effective from 27 February 2026. It does not provide a complete technical dust-control manual. It requires the OSH Construction Management Plan to address the subject, leaving the project to develop arrangements appropriate to its work.
ADOSH-SF is the Abu Dhabi Occupational Safety and Health System Framework and is administered by the Abu Dhabi Public Health Centre. ADPHC states that "Codes of practice are mandatory to all entities, regardless of risk classification". Each Code of Practice states that it "applies to all employers within the Emirate of Abu Dhabi".
Those statements establish the stated application of the Codes to employers in Abu Dhabi. They do not support describing the Codes as federal legislation or writing that UAE law requires a particular dust-control technique. The distinction is important because a project document should identify the instrument that actually applies rather than converting an Abu Dhabi framework into a nationwide claim.
The full ADOSH-SF published index was read on 3 August 2026. It contained no Code of Practice dedicated to dust and none dedicated to airborne contaminants. A construction plan should therefore not cite an invented "dust CoP", imply that one exists or attribute detailed technical requirements to it.
Dust enters the published Abu Dhabi construction framework through Codes 53.1 and 53.0. Their relevant wording is concise, so the project-level detail must be created through competent assessment and planning.
Code of Practice 53.1 contains a table of required OSH-CMP contents. Under section 5.38, Waste / emission Arrangements, it includes the topic "Air Pollution Protection". The stated requirement reads in full: "Dust emissions / suppression program. Air emissions."
The wording requires the subject to be addressed but does not prescribe a single suppression method, monitoring instrument, numerical boundary criterion, watering frequency or reporting format. No such specification should be invented and attributed to the Code. The project must translate the requirement into arrangements suited to its activities, materials, site layout and receptors.
A credible section should explain how dust sources are identified, how control methods are selected, how subcontractors are coordinated and how performance is checked. It should cover occupational exposure within the site as well as emissions capable of travelling beyond a work zone or site boundary, while keeping those assessment questions distinct.
The section should also integrate with other parts of the OSH-CMP. Dust controls can affect traffic management, waste handling, housekeeping, water use, electrical safety, heat-stress management, emergency arrangements and public protection. Treating dust as a stand-alone paragraph can leave these interfaces unresolved.
ADOSH-SF Code of Practice 53.0, OHS Management during Construction Work, Version 4.0, dated 15 July 2024, connects control detail to the proposed work methodology. Among the documents substantiating that methodology, it lists: "details of control measures to be implemented (eg. dust control)".
This wording supports a two-level documentation structure. The OSH-CMP establishes the project-wide system, while task documentation describes how particular activities will be controlled. The Code does not supply the technical method for cutting, drilling, demolition or earthworks. Those details must come from the site dust risk assessment, equipment information and competent planning.
A method statement should therefore do more than repeat the OSH-CMP. It should identify the material, tools, sequence, suppression or extraction arrangement, access restrictions, cleaning method, personal protective equipment, inspection points and stop-work conditions for the task. The level of detail should reflect the severity and complexity of the work.
The programme should begin with scope and ownership. It should state which project activities it covers and identify who maintains the site-wide arrangements, who approves task methods, who inspects implementation and who responds to failures or complaints. Client, consultant, main-contractor and subcontractor functions should be distinguished rather than merged into a statement that "all parties are responsible".
A source register can group foreseeable work by project stage: demolition, earthworks, concrete and masonry work, façade operations, fit-out, road traffic, batching, waste handling and cleaning. The register should link each source to the relevant assessment and method statement without attempting to replace those documents.
Material identification should be part of the programme. Concrete, cement, gypsum, plaster, wood and mixed demolition material do not present identical hazards. The types of construction dust page explains why inhalable dust, respirable dust and material-specific contaminants must not be combined into one undifferentiated category.
The programme should define the control hierarchy used by the project. Avoidance, substitution or prefabrication may eliminate some dusty tasks. Wet methods, on-tool extraction, enclosure, screened transfer, maintained haul surfaces and controlled loading can reduce release. Segregation, housekeeping and respiratory protective equipment then address residual risks.
Water-use arrangements should specify where water comes from, how it reaches the source, how supply is checked and what happens when it fails. They should also address slurry, drainage, slip hazards and unnecessary consumption. Extraction arrangements should cover tool compatibility, shrouds, hoses, filtration, collection-unit capacity, inspection and safe emptying.
The OSH-CMP should avoid assuming that boundary controls protect tool operators or that personal respiratory protection prevents off-site emissions. Occupational and off-site controls share sources but answer different questions.
For workers, the programme should require task-based evaluation of the breathing-zone risk, including other trades who may enter the affected area. It should set expectations for source control, exclusion, cleaning, respiratory protection where required, training, supervision and occupational-health referral for workers reporting relevant symptoms.
For emissions, the programme should address exposed soil, haul roads, stockpiles, loading, tipping, demolition faces, work above hoardings, track-out and nearby sensitive receptors. It should describe inspection and escalation during changing wind or site conditions. No generally applicable numeric UAE construction-boundary dust limit has been identified from the regulatory facts supplied, so the plan should not manufacture a threshold.
Where boundary monitoring is used, the plan should state its purpose. Visual inspection, complaint investigation, trend monitoring and attribution of a source are different objectives. Instrument location, upwind conditions, weather, work logs and nearby non-project sources all affect interpretation.
A written programme has little value unless implementation is checked. Inspections should examine whether wetting reaches the actual point of generation, extraction is operating, shrouds and hoses are intact, roads remain serviceable, stockpiles are stable, waste is contained and cleaning methods avoid re-suspension.
The programme should state the frequency or triggering basis for checks, while recognising that Code 53.1 supplies no specific inspection interval for dust. More frequent checks may be necessary during demolition, major earthworks, high winds, changing work fronts or repeated control failures. The project should choose and document a defensible schedule rather than present it as wording taken from the Code.
Records may include completed inspections, equipment checks, photographs, water-supply interruptions, extractor maintenance, worker briefings, monitoring information, complaints, corrective actions and close-out evidence. Records should demonstrate what occurred and what response followed, not simply accumulate unsigned forms.
Verification can include observation of the task, examination of deposited dust, direct-reading investigation or appropriately designed occupational sampling. Each method has limitations. A general particulate monitor does not determine respirable crystalline silica, and a personal exposure sample does not by itself characterise emissions at the boundary.
The programme should define conditions requiring intervention. Examples include uncontrolled visible release, failure of extraction or water supply, dust crossing an exclusion zone, significant track-out, migration towards an occupied receptor, damaged containment or work proceeding by a method different from the approved statement. The response may involve stopping the particular activity, restoring the control, extending segregation, changing the method, cleaning affected areas or conducting further assessment.
A complaint should be logged with its time, location, reported effect, weather and activities taking place. The investigation should consider natural background dust and unrelated nearby sources without using them as automatic explanations.
Corrective action should address the cause. Repeatedly wetting a boundary after dust has escaped does not resolve an uncontrolled cutting task. Cleaning a public road without correcting internal track-out arrangements is similarly incomplete.
The programme requires review as excavation progresses, structures rise, internal areas become enclosed, new trades arrive and neighbours occupy nearby buildings. It should also be reconsidered following monitoring evidence, a significant complaint, a health concern or a recurring control failure.
In this way, Code 53.1's requirement for "Dust emissions / suppression program. Air emissions." becomes a functioning project system, while Code 53.0's requirement for "details of control measures to be implemented (eg. dust control)" is carried into the methods used at the workface. The broader orientation is set out in construction dust in the UAE, and the practical source descriptions appear in dust-generating activities on site.
The Abu Dhabi Occupational Safety and Health System Framework (ADOSH-SF) is administered by the Abu Dhabi Public Health Centre (ADPHC). ADPHC states that "Codes of practice are mandatory to all entities, regardless of risk classification", and each Code of Practice states that it "applies to all employers within the Emirate of Abu Dhabi". They are mandatory for employers in the Emirate of Abu Dhabi. They are not federal law, and nothing on this site describes them as "UAE law". ADPHC publishes no Code of Practice on dust or on airborne contaminants. Dust reaches an Abu Dhabi construction project through the project's own documentation instead: CoP 53.1 OSH Construction Management Plan (Version 4.1, effective 27 February 2026) requires the OSH Construction Management Plan to cover, under "Air Pollution Protection", a "Dust emissions / suppression program. Air emissions."; and CoP 53.0 OHS Management during Construction Work (Version 4.0, 15 July 2024) lists "details of control measures to be implemented (eg. dust control)" among the documents substantiating the proposed methodology.
ADOSH-SF Code of Practice 53.1 section 5.38 and Code of Practice 53.0, Abu Dhabi Public Health Centre
Code of Practice 53.1 contains a table of required OSH-CMP contents. Under section 5.38, Waste / emission Arrangements, it includes the topic "Air Pollution Protection". The stated requirement reads in full: "Dust emissions / suppression program. Air emissions." The wording requires the subject to be addressed but does not prescribe a single suppression method, monitoring instrument, numerical boundary criterion, watering frequency or reporting format.
The full ADOSH-SF published index was read on 3 August 2026. It contained no Code of Practice dedicated to dust and none dedicated to airborne contaminants. A construction plan should therefore not cite an invented "dust CoP", imply that one exists or attribute detailed technical requirements to it.
The programme should state the frequency or triggering basis for checks, while recognising that Code 53.1 supplies no specific inspection interval for dust. More frequent checks may be necessary during demolition, major earthworks, high winds, changing work fronts or repeated control failures. The project should choose and document a defensible schedule rather than present it as wording taken from the Code.