UAE Climate Reporting Periods, Platforms and Filing Deadlines: What to Confirm with Authorities

Prepared in British English as a practitioner Knowledge Card Package: answer, explanation, application, evidence, connections and publishing layer.

The UAE climate framework combines federal law, emirate competent authorities, free-zone authorities, sector instructions and electronic systems. A national system may collect or analyse data without serving as the direct self-filing portal for every company. An emirate system can operationalise Article 6 locally without creating a nationwide rule.

The most common failure is calendar substitution: a team sees "annual", "31 March", "30 May 2026" or the name of a portal and turns it into a group-wide deadline. The correct approach is route-by-route confirmation.

Figure 1. Federal framework and local UAE climate reporting routes. Branded educational visual by London Reporting Academy.

Article 6 creates four relevant controls.

Periodic reports, not a single period in the law

Designated Sources must measure emissions regularly, prepare inventories and submit periodic reports according to standards specified by MOCCAE or the competent authority. "Periodic" signals recurrence but does not, on its own, define calendar year, financial year, monthly, quarterly or annual filing.

Approved forms

Sources must submit activity data, current and planned reduction measures and expected results in forms approved by MOCCAE. The applicable route may also require a monitoring plan, inventory workbook, evidence list, verification documentation or declarations.

Electronic system and linked systems

MOCCAE is to establish an electronic system for emissions measurement mechanisms and data submission, with mechanisms linking to systems approved by competent authorities and entities concerned. This supports a networked architecture rather than proving that every Source uses one front-end portal.

Authority verification and annual analysis

MOCCAE or the competent authority verifies data accuracy and commitment to submit. MOCCAE analyses emissions and reduction data annually. An annual government analysis cycle should not be converted into a company deadline without an implementing instruction.

Figure 2. Authority confirmation record. Branded educational visual by London Reporting Academy.

Federal system

The UAE launched an Integrated Emission Quantification Tool as part of the national MRV Transparency System. Official reporting described the tool as designed for MOCCAE, relevant federal and local authorities and data providers. That national architecture should not be described as a universal public corporate portal unless an official instruction gives the company that route.

Competent-authority or free-zone portal

A competent authority may use its own portal, template, registration process and deadline. The Environment Agency - Abu Dhabi's facility-level portal is a clear example of a local operational route. It is not evidence that a Dubai, Sharjah, Ras Al Khaimah or free-zone facility has the same filing obligation.

Internal reporting system

The company's GHG platform, workbook or data hub prepares and controls the information. It does not determine the legal deadline or replace the official submission channel. The internal system should export the required local form, preserve evidence and maintain a submission audit trail.

The EAD workshop of 12 March 2026 described the following facility-level arrangement:

• point of regulation at facility level;

• calendar-year reporting;

• covered sectors and a 25,000 tCO2e threshold;

• current reporting focused on Scope 1 CO2 and CH4;

• submission through facilitymrv.ead.ae;

• annual deadline of 31 March, with an extended grace period to 14 April;

• accredited third-party verification within the framework, described as voluntary until 2027; and

• correction of errors within 30 days of discovery.

The workshop also said the current technical guidance was v8, February 2026. These are valuable operational facts for the Abu Dhabi facility route as at the workshop date. They must not be copied into a federal or another-emirate calendar. The materials themselves direct users to prioritise relevant future legislation and current guidance.

1. Source, facility and legal basis

Record the legal entity, branch, facility, operator, permit, free-zone status, activity and emissions sources. Attach the designation notice, list, permit condition or other basis that creates the reporting route.

2. Authority and single point of contact

Identify MOCCAE, emirate competent authority, free-zone authority, sector body or another entity concerned. Record the department, named contact, official email, telephone and escalation route. For local systems, confirm whether the Source reports directly to MOCCAE as well as locally or only through the local authority.

3. Reporting period and frequency

Confirm:

• calendar or financial year;

• first and last day of the period;

• treatment of new, closed or acquired facilities;

• annual, periodic, event-driven or other frequency;

• whether a monitoring plan is filed once or annually; and

• whether zero, below-threshold or no-change declarations are required.

4. Deadline, cut-off and time zone

Record the legal deadline, any administrative grace period, time zone, weekend or public-holiday rule, and late-filing escalation. Distinguish:

• registration deadline;

• monitoring-plan deadline;

• emissions-report deadline;

• verifier-statement deadline;

• correction or resubmission window; and

• response deadline for authority queries.

A grace period is not necessarily an extension of the legal obligation. Record its source and conditions.

5. Portal, account and identifiers

Confirm the exact URL and whether it is current. Record:

• organisation or operator account;

• UAE Pass or other authentication;

• facility, permit, licence or registration number;

• authorised submitter and backup submitter;

• user-role approval and expiry;

• browser, file-size or format constraints; and

• support ticket route.

Never share a generic login or store credentials inside the inventory workbook.

6. Form version and attachments

Download the form from the official source at the start of the reporting cycle and again before filing. Record the version and checksum. Confirm attachments such as:

• monitoring plan;

• completed emissions workbook;

• source and factor register;

• verification statement or report;

• data-gap and estimate schedule;

• evidence index;

• reduction measures and expected results;

• authorised signatory declaration;

• explanatory letter for below-threshold status; and

• correction or restatement note.

Do not upload confidential evidence merely because it exists. Confirm what must be attached, what must be retained and what can be supplied on request.

7. Correction and resubmission route

Confirm whether the portal permits amendment, whether authority approval is needed and how the original submission remains visible. Record:

• discovery date;

• error and affected fields;

• materiality and threshold effect;

• authority notification;

• corrected file and version;

• approval; and

• resubmission receipt.

8. Confirmation record

A complete filing is not proved by an internal email saying "submitted". Retain:

• portal receipt or timestamp;

• submission ID;

• file names and hashes;

• screenshots where appropriate;

• status shown in the portal;

• acknowledgement email;

• authority questions and responses;

• acceptance, closure or open-status record; and

• final submitted package in read-only form.

A robust calendar contains more than one deadline.

The calendar should state assumptions. If the external deadline is not confirmed, mark it as a regulatory dependency rather than inventing a date.

A group operating facilities in different emirates should maintain:

• a group source register;

• a local route record for each facility or legal entity;

• one controlled emissions data model;

• local form and portal mappings;

• a reconciliation from local submissions to the group inventory; and

• separate local authority correspondence.

Do not let a group consolidation erase facility-level facts. Conversely, do not add local totals blindly and double count central utilities, shared fleets or intercompany energy.

Before the filing week:

• confirm user access and backup submitter;

• test file formats and sizes;

• save the official support contact;

• generate a read-only final package;

• record internal approval;

• submit early enough to address validation errors; and

• define what evidence will prove an outage or failed submission attempt.

If the portal is unavailable, do not assume email is an accepted substitute. Contact the authority through the notified route, preserve timestamps and follow written instructions.

Illustrative scenario - not legal advice. A group has an industrial facility in Abu Dhabi and a logistics subsidiary in another emirate free zone. The Abu Dhabi facility confirms its local EAD route and records the calendar-year period, local portal, form version and March deadline from current official materials.

The logistics subsidiary has not received a designation notice. The group does not copy the Abu Dhabi deadline into the free-zone calendar. Instead, it asks the free-zone and relevant emirate authority for written confirmation of Source status, reporting route and whether fleet or warehouse emissions are included.

Both operations use the same controlled source and factor registers, but the group maintains separate legal-basis, portal and filing records. The consolidated inventory clearly identifies which local submissions have been filed, which are readiness-only and which remain subject to authority confirmation.