Short answer
The answer, before the reasoning
Start with applicability and authority confirmation, not with an emissions spreadsheet. A defensible UAE MRV programme identifies the legal entity and facilities, records which authority and instrument apply, locks the organisational and operational boundary, creates a complete emissions-source register, approves methods and data owners, builds reproducible calculations and evidence controls, prepares for verification or regulator challenge, links the inventory to current and planned reduction measures, and obtains management and board approval.
A first implementation cycle can be organised over 6-12 months, but the applicable authority controls the actual form, period, method and deadline.
A practitioner guide to building an MRV system before a filing request, inspection or verification exercise exposes gaps that could have been resolved earlier.
Technical status
EDUCATIONAL STATUS
This article explains a proportionate implementation approach. It is not a legal opinion, a regulator designation, a filing instruction or evidence that an entity has complied. Entity-specific conclusions require current written instructions and appropriate UAE legal and technical review.
In practice
Article map
| Stage | What the reader will be able to do |
|---|---|
| Answer | Explain why a regulator-controlled applicability and authority record comes before calculation. |
| Design | Build the boundary, source register, methodology, RACI, calculation and evidence architecture. |
| Operate | Run a pilot inventory, resolve gaps, prepare for verification and connect emissions to reduction measures. |
| Approve | Create a board-ready basis, limitations note, release decision and next-cycle improvement plan. |
| Control | Use a 6-12 month roadmap without confusing project timing with a statutory reporting calendar. |
Technical status
SOURCE AND LEGAL-STATUS WARNING
Federal Decree-Law No. 11 of 2024 has been in force since 30 May 2025 and applies to emission Sources in the State, including free zones. Article 6 MRV duties, however, are framed for Sources determined by MOCCAE and the competent authority, in coordination with the entity concerned, and rely on applicable standards, approved forms and implementing resolutions or authority instructions. The one-year adjustment period stated in Article 18 reached its nominal end on 30 May 2026 unless extended. At this source cut-off, do not substitute a consultant timetable for a regulator deadline or assume that one UAE-wide method applies in every emirate and free zone. The Arabic legal text is authoritative.
Why the first compliance task is not “calculate the footprint”
The UAE Climate Law creates a broad federal framework, but the operational MRV question is fact-specific. Article 3 reaches emission Sources across the State, including free zones. Article 6 then requires the Sources determined by MOCCAE and the competent authority, in coordination with the entity concerned, to measure emissions, prepare an inventory, submit periodic information, retain records and take reduction measures under the applicable standards and approved forms. A team that begins with a generic Scope 1 and Scope 2 workbook may therefore calculate the wrong legal entity, omit a locally regulated facility, use an unapproved boundary or miss the reporting route entirely.
The purpose of an implementation roadmap is to make the eventual reporting event reproducible and governable. It should leave an evidence trail showing why the team believed a duty applied, which authority was contacted, which version of an instruction was used, how the boundary and sources were determined, how the data were transformed, how gaps were handled and who approved the final submission and reduction plan.
Rule
REQUIREMENT VERSUS IMPLEMENTATION PRACTICE
The law establishes MRV, record-retention, verification and reduction duties for determined Sources. The ten-workstream roadmap below is London Reporting Academy implementation practice. It organises compliance work but does not replace the form, method, portal, deadline or verification requirement issued by the relevant authority.
The ten-workstream UAE MRV compliance model
Figure 1. A first-cycle UAE MRV programme should connect authority clarity, boundary and source completeness to methods, evidence, reduction planning and board-approved release.
1. Complete an applicability and authority review
Build an entity-and-facility map before asking whether “the group” is covered. Record each UAE legal entity, branch, licence, free-zone or mainland status, physical facility, operating emirate, sector, source of direct emissions, purchased-energy profile and existing environmental or carbon-reporting obligations. Then test at least four possible routes: the broad federal Climate Law; an Article 6 determination or instruction; Cabinet Resolution No. 67 of 2024 for the National Carbon Credit Registry; and any emirate, facility, sector, permit or free-zone requirement.
Open an authority register. It should distinguish MOCCAE, the competent authority in the relevant emirate, an entity concerned, a free-zone or licensing contact, and any separate body with a defined role. Ask for written confirmation where the reporting route, designation, organisational level, portal, form, period, deadline or verification expectation is unclear. Preserve the facts supplied with the question, because an answer given for one facility or entity may not support another.
2. Approve the reporting boundary memorandum
The boundary memorandum should identify the reporting legal entity, consolidation basis, facilities, operational-control assumptions, included and excluded activities, gases, emission scopes, base period, reporting period and treatment of acquisitions, disposals, joint operations, leased assets and outsourced processes. It should also explain any difference between the financial reporting group, the federal or registry reporting entity and a facility-level local scheme.
Do not allow the word “boundary” to hide several decisions. Organisational boundary answers which entities and operations belong in the report. Operational boundary identifies emission categories. Metric boundary states which facilities, periods and data sources support a particular figure. Authority boundary identifies where the submission is made. Each difference needs a reason, owner and review control.
3. Create a complete emissions-source register
Walk the operational processes rather than copying the headings of a generic GHG template. The register should identify stationary and mobile combustion, process emissions, flaring or venting where relevant, refrigerants and other fugitive sources, purchased electricity or energy, waste and wastewater where required, and any additional categories required by the applicable instrument. Link each source to a facility, equipment or activity, data system, unit, frequency, owner, method and evidence location.
4. Document methods in a monitoring plan
A monitoring plan converts the legal or authority instruction into an operating procedure. For each source, specify the activity data, measurement equipment, frequency, units, conversion rules, emission factor, global warming potential where relevant, calculation formula, treatment of missing data, quality checks, material changes and approval route. Record the instrument and version that justify the method.
Where no final authority-specific method has been communicated, the team may use a recognised GHG accounting approach as an interim implementation basis, but it should label that basis, identify the unresolved regulatory decision and preserve the ability to remap the calculation. An interim method is not evidence that the authority has approved it.
5. Assign data owners and control roles
MRV usually crosses facilities, procurement, fleet, production, engineering, finance, HR, legal and sustainability. Give every data stream a named owner, preparer, reviewer and approver. Separate preparation from review for material calculations. Assign an evidence custodian and a release owner. The reporting calendar should state when source data close, when reconciliations are performed, when estimates are approved, when regulator questions must be escalated and when the board or delegated committee signs off.
6. Build reproducible calculations and an uncertainty record
Use a controlled calculation environment with protected formulas, defined input cells, unit checks, factor references, version history and reviewer sign-off. Reconcile consumption to invoices, purchases, inventory movements, production or financial records where meaningful. Explain significant movements against the prior period, operational changes and boundary changes. Record every estimate, proxy, extrapolation and missing-data treatment with the population affected, reason, method, limitation and improvement action.
Use a factor register containing the source, version, gas coverage, unit, geography, period and approval status.
Prevent silent overwriting of prior submissions; retain the calculation and evidence version used at release.
Create a correction log showing the original issue, impact, action, approver and whether a resubmission or authority notification was required.
Separate gross emissions calculations from any carbon-credit, offset or reduction narrative unless the applicable form instructs otherwise.
7. Operate evidence and internal controls
Article 6 requires determined Sources to retain records of measured emissions for five years and enable access by authorised judicial officers. A practical evidence repository should go further: link every submitted field to source records, calculations, method versions, review controls and release approval. Apply access restrictions to commercially sensitive or personal information without making the evidence unavailable to authorised reviewers.
8. Prepare for verification and regulator challenge
The federal law states that MOCCAE or the competent authority verifies the accuracy of emissions-related activity data and the extent of submission. Separate instruments may specify an independent verification body or a local transition timetable. Do not make a universal statement that third-party assurance is mandatory for every Article 6 Source. Instead, record the exact verification route and prepare a file that another competent person can reproduce.
Run a dry review before submission. Select material sources, trace them from the report to the calculation and back to original evidence, recalculate the result, challenge unusual movements, review estimates and test the boundary. Close findings through a controlled issue log. Management representation may confirm responsibilities and known limitations, but it does not replace evidence.
9. Connect the inventory to a reduction plan
Article 6 requires determined Sources to provide information on current reduction measures, planned future measures and expected results, and to take reduction measures in accordance with relevant resolutions. Build the reduction plan from the same source register and boundary as the inventory. For each measure, state the baseline, affected source, owner, action, milestone, expected result, calculation basis, dependency, cost or investment where approved, and evidence of implementation.
10. Obtain management and board approval
The approval pack should not ask the board merely to “approve the carbon footprint”. It should summarise the applicable reporting route, boundary, main sources, methods, material estimates, significant controls, unresolved issues, verification status, regulator correspondence, current and planned reduction measures, expected results, limitations and the authority to submit. The minutes should record the decision and any conditions or follow-up actions.
Figure 2. An illustrative 6-12 month first-cycle roadmap. The authority-controlled reporting calendar must replace these programme phases where dates or forms have been issued.
In practice
| Applicability record | Minimum content | Control evidence |
|---|---|---|
| Entity and licence facts | Legal name, trade licence, branch/subsidiary status, free zone or mainland, responsible signatory. | Current licence, legal structure chart and authority correspondence. |
| Facility facts | Location, operator, ownership/control, processes, meters, permits, landlord arrangements and outsourcing. | Facility register, site map, permits, contracts and meter responsibility matrix. |
| Potential legal route | Federal Climate Law, Article 6 designation, Resolution 67 registry test, local MRV, permit or sector rule. | Instrument-and-version register with source link and applicability conclusion. |
| Authority route | Who sets the method, receives data, verifies accuracy, inspects and decides or hears a challenge. | Authority register, named contacts, written response and follow-up date. |
In practice
| Source-register field | Why it matters | Typical evidence |
|---|---|---|
| Source ID and description | Prevents duplicate or missing sources and supports year-on-year change control. | Equipment register, process map, permits and engineering records. |
| Facility and boundary status | Shows whether the source belongs to this entity, facility or reporting route. | Boundary memorandum and facility register. |
| Activity data and unit | Defines what is measured and avoids mixed-unit calculations. | Invoices, meter exports, fuel logs, production systems and maintenance records. |
| Factor and method | Makes the calculation reproducible and identifies authority-specific requirements. | Approved methodology, factor register and calculation specification. |
| Owner and reviewer | Creates accountability and segregation between preparation and challenge. | RACI, control matrix and sign-off record. |
| Data-quality status | Identifies estimates, missing periods, uncertainty and improvement priority. | Gap log, estimate note and remediation action. |
In practice
| Role | Core responsibility | Do not confuse with |
|---|---|---|
| Executive sponsor | Resources, cross-functional authority and escalation. | Technical approval of every factor or calculation. |
| Reporting owner | Boundary, calendar, consolidation, status control and submission coordination. | Ownership of all underlying operational data. |
| Data owner | Completeness and accuracy of source-system records. | Final approval of the public or regulatory submission. |
| Method owner | Method specification, factors, assumptions and changes. | Independent verification. |
| Reviewer | Recalculation, reconciliation, challenge and issue closure. | Reperforming preparation without documented challenge. |
| Board / delegated committee | Approval of basis, key judgement, limitations, reduction plan and release authority. | Day-to-day data collection. |
In practice
| Control objective | Example control | Evidence of operation |
|---|---|---|
| Completeness | Reconcile the source register to facilities, permits, equipment and general-ledger or procurement populations. | Signed reconciliation and unresolved-source log. |
| Accuracy | Recalculate material sources; compare factors and conversions to the approved register. | Reviewer worksheet and factor check. |
| Cut-off | Test invoice, meter and production periods against the reporting period. | Cut-off schedule and exception resolution. |
| Change management | Approve boundary, method, factor, system and estimation changes before use. | Change request, impact assessment and approval. |
| Access and retention | Restrict editing, retain released evidence and make it retrievable for at least the applicable period. | Access report, repository index and retention policy. |
| Submission integrity | Compare the approved report or portal entry to the signed calculation and narrative pack. | Final tie-out and portal receipt. |
In practice
| Reduction-plan element | Strong record | Weak shortcut |
|---|---|---|
| Measure | Specific operational or technology change linked to an emission source. | “Improve sustainability” without source or action. |
| Expected result | Quantified or clearly qualitative result with method and timing. | Unexplained percentage detached from inventory boundary. |
| Dependency | Grid, supplier, technology, permit, capital, data or operational dependency. | Assuming implementation is entirely within management control. |
| Progress evidence | Purchase order, commissioning record, meter trend, project gate or verified operational data. | Treating a board-approved intention as completed action. |
| Governance | Owner, budget status, decision gate and escalation. | No accountable owner or review cadence. |
In practice
A practical 6-12 month programme
| Phase | Main actions | Exit evidence — Primary owner |
|---|---|---|
| Month 0-1: mobilise | Sponsor; entity/facility map; legal and authority scan; preliminary emissions estimate; authority register. | Approved scope of project, responsibility map and open regulator questions. — Executive sponsor + legal/compliance. |
| Month 1-3: define | Boundary memorandum; source register; method and monitoring plan; data-owner RACI; reporting calendar. | Approved boundary, source population and method specifications. — Reporting owner + facility/method owners. |
| Month 3-5: build | Data extracts; calculation model; factor register; evidence repository; completeness and accuracy controls. | Reproducible draft inventory and evidence index. — Data owners + finance/internal control. |
| Month 5-7: dry run | Pilot close; variance review; estimate approvals; issue log; draft authority submission; reduction options. | Dry-run findings and prioritised remediation plan. — Reporting owner + reviewers. |
| Month 7-9: challenge | Internal technical review; legal/status check; verifier engagement where applicable; correction closure. | Signed findings, corrected inventory and controlled draft. — Independent reviewer / verifier where applicable. |
| Month 9-12: approve and improve | Final tie-out; board paper; filing or response; reduction plan; lessons learned; next-cycle calendar. | Approved submission pack, receipt, reduction roadmap and control improvements. — Board sponsor + reporting owner. |
Hypothetical scenario
HYPOTHETICAL EXAMPLE
A UAE logistics group has a DIFC holding company, operating subsidiaries in Dubai and Abu Dhabi, leased warehouses, a vehicle fleet and one Abu Dhabi facility with material direct fuel use. The team initially plans one group GHG inventory. The applicability review instead creates three records: the federal entity/facility map, a Dubai authority query for the Dubai operations and an Abu Dhabi facility-level assessment. One controlled dataset supports all three, but the organisational level, reporting route and verification expectation are documented separately. The example is illustrative; it does not conclude that any real entity is designated under Article 6.
Illustrative only. It shows how the decision is made, not wording that can be copied or relied on.
In practice
Weak versus stronger implementation
| Area | Weak approach | Stronger approach |
|---|---|---|
| Applicability | Assume every group entity has the same duty because the law is federal. | Record entity, facility, instrument, authority and written instruction separately. |
| Boundary | Use the financial consolidation perimeter without testing facility or registry rules. | Start from the group, then document every regulatory or metric-specific difference. |
| Methods | Use an online calculator with no controlled factor or version record. | Approve method specifications, factors, units, estimates and change controls. |
| Evidence | Keep a final spreadsheet and a folder of invoices. | Link each submitted field to evidence, method, review and release approval. |
| Reduction plan | List aspirations unrelated to the emissions sources. | Link each current or planned measure to the source register, expected result and owner. |
| Approval | Obtain an email saying “approved”. | Use a board or delegated-committee paper with judgements, limitations and conditions. |
Readiness
Pre-submission checklist
- The entity, facility, emirate, free-zone status and potential reporting instruments have been recorded.
- The relevant authority and current reporting route have been confirmed or an unresolved query is visible.
- The boundary memorandum explains organisational, operational, metric and authority-specific differences.
- The source register reconciles to facilities, equipment, permits, purchases and processes.
- Every method, factor, conversion, estimate and material change is controlled and reproducible.
- Data owners, reviewers, approvers, evidence custodians and release authority are named.
- The inventory is tied to original evidence and significant movements have been challenged.
- The five-year federal record-retention requirement and any longer local requirement are addressed.
- Verification expectations have been identified for the applicable instrument; readiness is not described as assurance.
- Current and planned reduction measures are linked to sources, expected results, owners and evidence.
- Management and the board or delegated committee have approved the basis, limitations and release.
- The portal receipt, signed report, calculation version and correspondence will be retained as one release pack.
In practice
Common mistakes
| Mistake | Why it fails | Correction |
|---|---|---|
| Waiting for the first regulator request | The team may have insufficient time to resolve boundary, source and evidence gaps. | Build the controlled foundation now while keeping legal status and deadlines conditional. |
| Treating 0.5 million tCO2e as the Climate Law threshold | That number belongs to a separate registry instrument and does not define Article 6 designation or local schemes. | Maintain an instrument-specific threshold and trigger register. |
| Using one group footprint as every regulatory submission | Entity, facility and local reporting routes may differ. | Map one dataset to controlled, instrument-specific outputs. |
| Calling internal review “verification” | The term may imply a role or conclusion that was not performed. | Name the actual procedure, provider, scope and output. |
| Keeping only the final value | A number without boundary, method, source and control evidence is difficult to defend. | Retain the full data lineage and release version. |
Rule
MYTH VERSUS REALITY
Myth: “Once we have calculated Scope 1 and Scope 2, we are compliant with the UAE Climate Law.” Reality: an inventory is only one component. Compliance depends on the applicable legal route and may also require approved forms, periodic reporting, data on activities and reduction measures, record retention, access, verification, reduction action and authority-specific controls.
Start with applicability and authority confirmation, not with an emissions spreadsheet. Map the legal entities and facilities, test the relevant federal, Article 6, registry and local routes, and record the authority, reporting unit, method, period, form, deadline and verification expectations before locking the boundary.
The final submission should be approved by the named management and board or delegated release authority for the applicable route. The file should identify data owners, reviewers, approvers, evidence custodians and release authority, and preserve who approved the final submission and reduction plan.
Self-check
- Can the team explain, with a source and correspondence record, why this entity or facility follows this MRV route?
- Can an independent reviewer reproduce a material number from the submission to original evidence and back?
- Would the reduction-plan boundary and source IDs reconcile to the reported inventory?
- Does the board approval identify unresolved uncertainty rather than imply certainty that the source pack does not support?
Questions
Questions people ask
What should a UAE MRV project do first?
Start with applicability and authority confirmation, not with an emissions spreadsheet. Map the legal entities and facilities, test the relevant federal, Article 6, registry and local routes, and record the authority, reporting unit, method, period, form, deadline and verification expectations before locking the boundary.
Is third-party verification always mandatory?
Separate instruments may specify an independent verification body or a local transition timetable. Do not make a universal statement that third-party assurance is mandatory for every Article 6 Source.
What evidence should be retained?
Article 6 requires determined Sources to retain records of measured emissions for five years and enable access by authorised judicial officers. A practical evidence repository should go further: link every submitted field to source records, calculations, method versions, review controls and release approval.
Who approves the submission?
The final submission should be approved by the named management and board or delegated release authority for the applicable route. The file should identify data owners, reviewers, approvers, evidence custodians and release authority, and preserve who approved the final submission and reduction plan.
Sources
Primary sources
- Federal Decree-Law No. 11 of 2024 on the Reduction of Climate Change Effects
- Cabinet Resolution No. 67 of 2024 Concerning the National Register for Carbon Credits
- Environment Agency - Abu Dhabi, GHG Emissions Measurement, Reporting and Verification Technical Guidance
- Environment Agency - Abu Dhabi, Facility MRV Workshop Presentation, 12 March 2026
- Dubai Law No. 11 of 2024 Establishing the Dubai Environment and Climate Change Authority
Take it with you
The checklists as a working spreadsheet
Every checklist and table on this page, with empty status, owner and evidence columns for your team to fill in and keep.
✓ LRA AI Assistant · Human-in-the-loop
Ask about this guide
It answers from this page, and reaches into the linked disclosure cards when your question is about the standard itself. Your first two answers are free without signing in.
Go deeper · UAE FDL 11 / 2024
UAE Climate Law training
Obligations under Federal Decree-Law 11 of 2024, from inventory to the reduction plan.
Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.
