UAE insurance law sits in a different place from the English-language jurisdictions earlier in this series. The doctrine of utmost good faith — uberrimae fidei — is preserved in the UAE; Federal Law No. 5 of 1985 on Civil Transactions Articles 1032 to 1043 govern insurance contracts, with Article 1033 establishing the duty of the insured to disclose material circumstances and Article 1037 giving the insurer the right to avoid the contract or reduce the sum payable where there has been non-disclosure or misrepresentation that materially affects the assessment of the risk. The UK CIDRA-style consumer reform of 2012 has no UAE counterpart; the SME consumer faces an insurance regime closer to the pre-2012 English law than to anything modern in the Common Law world.

Layered onto this is the post-2020 supervisory architecture. The Insurance Authority — the previous federal regulator — was merged into the Central Bank of the UAE (CBUAE) by Federal Decree-Law No. 25 of 2020, effective 2 January 2021. Insurance supervision now sits inside the CBUAE's prudential and conduct frame. Consumer-facing dispute resolution operates through Sanadak, the unified financial-services ombudsman launched in late 2023.

This article is for UAE fleet operators with between ten and fifty vehicles — Mussafah mechanical contractors, Khalifa Industrial Zone Abu Dhabi (KIZAD) industrial-installation fleets, Al Ain Industrial supply chains, Jebel Ali heavy-haulage operators, and Northern-Emirate cross-border movers. The four phrases below are not literary inventions — they appear, in slight variations, in every refused fleet claim in the UAE this year.

Phrase one: "the assured failed to maintain the vehicle in roadworthy condition"

This phrase invokes the policy warranty, near-universal in UAE motor and motor-fleet policies, that the assured will keep the insured vehicle in a roadworthy condition during the period of insurance. The phrase is short; the consequence is large. Where the insurer relies on this warranty, the burden under Article 1037 of the Civil Code shifts onto the operator to demonstrate roadworthiness was maintained.

The "demonstration" the insurer's surveyor expects is documentary — a contemporaneous record of the vehicle's state at the times material to the loss. A surveyor who examines the wreck and sees brake-pad wear beyond manufacturer specification, tyre tread below threshold, or hydraulic-line condition incompatible with continued service writes that finding into the engineering report. The operator's answer is the inspection record showing when the relevant component was last inspected, by whom, with what result, and what action followed.

An inspection record produced from the operator's app, sealed at capture, chained to the vehicle's prior service history, with EXIF-bound photographs of the relevant component at the time of inspection, is dispositive. An inspection record re-created from operator memory after the loss, in a Word document with no timestamp evidence, is not.

Phrase two: "the assured failed to disclose a material circumstance affecting the assessment of the risk"

This phrase invokes Article 1033. The non-disclosure case may be about the operational pattern of the fleet (route profile, hours of operation, driver-licensing position, prior loss history), about the vehicle (modifications, prior repair history, prior ownership profile), or about the operator (corporate-history, prior insurance-refusal experience). The post-2020 CBUAE conduct rules require fairer pre-contractual practice from the insurer than the pure pre-1985 Civil Code position, but the underlying doctrine still gives the insurer wide latitude.

The operator's defence is a proper file. Where modifications were declared at policy inception, that declaration must be retrievable. Where prior losses were declared, the declaration and the surrounding correspondence must be retrievable. Where the operator's renewal questionnaire was returned with figures, those figures must reconcile to operational reality.

The CBUAE's consumer-conduct rules reduce the insurer's ability to rely on minor or technical non-disclosure to avoid a claim, particularly where the policyholder is an SME consumer rather than a sophisticated commercial buyer. Sanadak applies these rules to disputes brought to it for resolution. The operator who can demonstrate full disclosure and a clean documentary trail at policy inception faces a different ombudsman picture than the operator who cannot.

Phrase three: "the loss was caused by an excluded peril or a breach of policy condition"

This phrase covers the operating-condition exclusions: vehicle outside permitted geographical scope, driver not authorised by the policy, vehicle on a use not declared (private versus commercial, light-and-medium versus heavy commercial), load profile outside policy scope. UAE motor-fleet policies typically tie cover tightly to declared use and declared driver class; departure from the declared profile is treated as an exclusion or condition breach.

The operator's defence is again documentary — the trip log shows the vehicle inside the declared geographical area, the driver-roster shows an authorised driver, the goods-movement record shows the declared use. A modern trip log produced from the operator's telematics-and-app system, sealed at capture, gives the SME consumer the same evidential standing in front of the surveyor that a sophisticated commercial assured holds. A paper trip log re-created after the loss does not.

Phrase four: "policy conditions precedent to liability have not been complied with"

This phrase covers the procedural conditions: notification within the period stated in the policy (commonly 24 to 48 hours for material loss, 7 days for non-material), provision of supporting documentation within the period stated (typically 30 days for full claim documentation), cooperation with the insurer's surveyor and engineering inspection, and continued payment of premium up to the date of the loss.

The operator's defence is a recordable timeline — date and time of the incident, date and time of the report to the insurer, date and time of supporting documentation provided, surveyor co-operation log. A timeline reconstructed from email and WhatsApp after the loss is weaker than a timeline anchored in a system whose entries are sealed at the moment of creation.

The Sanadak ombudsman path and CBUAE supervision

Where the insurer maintains the refusal after the operator's response, the SME consumer's primary access route is Sanadak — currently with jurisdiction over insurance complaints up to a defined monetary limit, with the option of court for larger or excluded matters. Sanadak considers the documentary file. The operator who arrives with a sealed-and-chained record of the inspection regime, the daily defect report, the maintenance file, the trip log, the driver-roster and the disclosure correspondence is taken differently than the operator whose file is paper-and-memory.

For matters above the Sanadak limit, or for complex contested matters, the route is the Court of First Instance with the standard Civil Code burden-of-proof framework. The CBUAE's prudential and conduct rules sit in the background, supervisorily; the courtroom dynamics are about whether the documentary file passes scrutiny against Article 1033 and Article 1037.

What the SME consumer should hold

For each of the four phrases above, the SME consumer should hold:

  • Inspection records sealed at capture for every vehicle, every operating day, with EXIF-bound photographs and OTP-verified mechanic identity at the points of inspection and repair.
  • Defect reports created at the moment of identification, chained to the vehicle's history, with status (open, in repair, repaired-and-verified, deferred-with-rationale) tracked against time.
  • Disclosure correspondence at policy inception and renewal, retrievable at the moment of the claim, with figures reconciling to operational reality.
  • Trip logs and driver rosters retrievable for any specific day, with telematics or app-based corroboration.
  • Notification timeline anchored in unalterable records, not in email and WhatsApp.

Eight steps before the next decline letter

  1. For each vehicle in your fleet, identify the policy warranties, exclusions and conditions you currently rely on. Are you sure your operating reality complies with each?
  2. Audit your inspection records for the last twenty-four months. Could a CBUAE-recognised forensic IT expert today certify they were created at the times claimed?
  3. For every defect noted in the past sixty days, can you trace receipt, repair, and post-repair verification — each timestamped and bound to a specific identifiable mechanic?
  4. Pull your last policy renewal questionnaire. Do the figures and disclosures match operational reality? Where they do not, address that gap before the next renewal.
  5. Audit your trip logs and driver rosters. Are they retrievable for any specific day in the past ninety, with corroborating data?
  6. Audit your incident notification practice. Where the last claim was made, does the timeline file demonstrate compliance with policy conditions precedent?
  7. Where Sanadak is your dispute path, ensure your customer file is presentable as a single coherent dossier.
  8. Within ninety days, replace paper records with a system producing sealed, chained, independently verifiable records. The cost is the system; the cost of not having it is a four-phrase decline letter you cannot answer.

Sources and further reading

Related Mekavo articles: When the UAE Public Prosecution opens a death-investigation file, RTA and Dubai Police on Sheikh Zayed Road, People of Determination adapted vehicles under FDL 21 of 2020, Driver defect to verified repair under MoHRE OSH.

Why this matters to us

Mekavo Fleet was built for UAE operators whose insurance position depends on a documentary record that survives the surveyor's engineering report and the CBUAE-supervised conduct framework. Every inspection, every defect report, every repair, every return-to-service verification is sealed at the moment of capture. Cryptographically chained. EXIF-bound. Mechanic identity verified by one-time passcode. Server timestamp not editable, including by us. The surveyor, the insurer's in-house engineer, Sanadak's case officer, the Court of First Instance — anyone — can re-verify the seal independently. We do not give you software. We give you the documentary record that defeats the four phrases. Mekavo Fleet for UAE operators.