Short answer
The answer, before the reasoning
A useful corporate MRV platform should control the entity, facility and source register; factor and methodology versions; unit conversions and calculations; estimates and uncertainty; evidence and approvals; immutable audit logs; verifier access; authority-ready exports; five-year retention; and security. The UAE National MRV System was launched in October 2025 as an integrated national platform, but public launch information does not replace entity-specific filing instructions or disclose every interface specification.
Current legal and digital context
Article 6(2) requires the Ministry to establish an electronic system and link it with local systems. In October 2025, MOCCAE announced the launch of the final, ready-for-use National MRV System as an integrated platform covering greenhouse-gas emissions and air pollutants. The public announcement describes national objectives, governance and process simplification; it does not publish every entity-facing schema, API, role or filing instruction.
Rule
PROCUREMENT RULE
Build or buy the corporate platform to produce controlled, authority-ready data. Do not hard-code an assumed official interface until the competent authority publishes or confirms the required schema, identifiers, portal process and attachments.
In practice
Minimum platform architecture
| Layer | Minimum capabilities |
|---|---|
| Governance and legal | Reporting entity/facility perimeter, designation status, authority register, reporting period, source edition, approvals and correspondence. |
| Master data | Emission-source register, units, gases, equipment, factors/GWP versions, users, roles, effective dates and controlled dictionaries. |
| Data and calculation | Imports, validation, duplicate/cut-off tests, unit conversion, formulas, estimates, uncertainty, recalculation and comparatives. |
| Evidence and workflow | Evidence IDs, document versions, maker-checker approvals, verifier workspace, requests/findings, legal review and immutable audit trail. |
| Output and security | Authority forms/exports, locked submission package, receipt, five-year retention, access logs, encryption, backup, recovery and legal hold. |
1. Entity, facility and source master data
The platform should not start with a spreadsheet tab called “emissions”. It should start with controlled master data: legal entities, facilities, leases, joint ventures, emission sources, equipment, utility accounts, relationships, designation status, competent authority, owners and effective periods. Every calculation and evidence record should reference these stable IDs.
2. Factor and methodology version control
A factor library should store publisher, edition, geography, technology, units, heating-value basis, GWP, effective dates and superseded versions. The platform should prevent silent replacement, show which calculations used each version and support an approved recalculation decision.
3. Calculation and estimate engine
• Validate units, signs, duplicate records and reporting-period cut-off before calculation.
• Make formula logic inspectable and testable; avoid vendor-only black-box calculations.
• Label estimates, proxies, missing periods, coverage and uncertainty.
• Preserve both original and corrected values with change reason and approval.
• Support source-, gas-, facility- and entity-level reconciliation to the final submission.
4. Evidence and approvals
Every material datapoint should link to source evidence, method, calculation and approval. The workflow should separate data preparation, review, legal/claim review and final representation. A verifier workspace should allow controlled read-only access, questions, findings, responses and closure without exposing unrelated restricted files.
5. Audit logs, retention and exports
• Immutable log of data, factor, formula, access, status and approval changes.
• Locked reporting-period package with checksum or integrity reference.
• Five-year retention policy for Article 6 source records, with legal-hold override.
• Configurable exports to authority forms, local systems and verifier requests.
• Submission receipt, resubmission history and correspondence linkage.
• Backup and recovery testing, not only a backup configuration screen.
Separate automatable work from required human approval gates.
Human judgement gates
Software should automate repeatable work while pausing for named approval where facts, legal status or professional judgement control the answer.
In practice
| Can be automated | Requires human approval |
|---|---|
| Import validation, unit conversions and duplicate checks. | Legal applicability, source designation and competent authority. |
| Approved factor application and formula execution. | Organisational/operational boundary and lease/JV treatment. |
| Workflow reminders and evidence links. | Material data gaps, estimates and methodology departures. |
| Version and period comparisons. | Carbon-credit and Article 6 claim rights. |
| Export generation and package locking. | Final representation, authority submission and inspection response. |
In practice
Vendor due-diligence scorecard
| Test | Evidence to request | Red flag |
|---|---|---|
| Source/version transparency | Factor register export, methodology references, change history. | “Proprietary calculation” with no inspectable source or version. |
| Boundary model | Entity/facility/source demo, effective dates and relationship types. | One global boundary field for every metric. |
| Audit trail | Old/new values, user, timestamp, ticket and approval. | Editable history or log visible only to vendor. |
| Evidence workflow | Datapoint-to-document links, reviewer and verifier permissions. | Documents stored without stable IDs or access classification. |
| Exports | Configurable schema, locked package, receipt and resubmission history. | Promise of an official API without published authority specification. |
| Security and continuity | Access review, MFA, encryption, data location, backups and recovery test. | No recovery evidence or unrestricted administrator access. |
Hypothetical scenario
ILLUSTRATIVE SCENARIO
A diversified group compares two carbon platforms. Vendor A has attractive dashboards but cannot show factor versions, formula logic or a recoverable audit trail. Vendor B has a strong data model, evidence IDs, maker-checker workflow, verifier access and configurable exports, but requires the company to define authority rules. The group selects Vendor B and treats legal configuration as an owned implementation workstream rather than a vendor warranty.
Illustrative only. It shows how the decision is made, not wording that can be copied or relied on.
Illustrative RFP requirement
“The solution shall maintain version-controlled entity, facility, source, factor and methodology registers; link each reported datapoint to source evidence, calculation and approval; preserve immutable access and change logs; support read-only verifier access; retain locked reporting packages and receipts for the required period; and generate configurable authority exports. The supplier shall not represent that the solution determines legal applicability or guarantees compliance.”
Common software mistakes
• Buying software before defining reporting scope and data owners.
• Using one factor library without effective dates.
• Importing invoices without completeness reconciliation.
• Allowing formulas to change without maker-checker approval.
• Storing documents without stable evidence IDs.
• Granting the verifier broad administrator access.
• Assuming a dashboard is an audit trail.
• Hard-coding an unofficial portal format.
• Ignoring data location, backup recovery and vendor exit.
• Letting the vendor approve legal or Article 6 claims.
Rule
MYTH / REALITY
Myth: an MRV platform makes the company compliant. Reality: software can enforce workflow and evidence discipline, but the organisation remains responsible for applicability, boundaries, methods, estimates, claims, approvals and the accuracy of the filed information.
Readiness
Minimum software checklist
- • Stable entity/facility/source IDs.
- • Designation and authority register.
- • Versioned factor/GWP library.
- • Inspectible formulas and unit conversions.
- • Estimate and uncertainty workflow.
- • Evidence-to-datapoint lineage.
- • Maker-checker and management approvals.
- • Immutable access/change log.
- • Read-only verifier workspace.
- • Configurable UAE/local exports.
- • Five-year retention and legal hold.
- • MFA, encryption, backup and tested recovery.
- • Vendor exit and full data export.
- • Human legal and claim approval gates.
Rule
CONTROLLED PRODUCTION RECORD
This section supports CMS publication, technical review, AI/RAG reuse and future updates. It is not intended to appear in the final public web article unless the publisher chooses to expose selected fields.
Questions
Questions people ask
What is the minimum master data model?
The platform should not start with a spreadsheet tab called “emissions”. It should start with controlled master data: legal entities, facilities, leases, joint ventures, emission sources, equipment, utility accounts, relationships, designation status, competent authority, owners and effective periods. Every calculation and evidence record should reference these stable IDs.
Which calculation and factor controls are needed?
A factor library should store publisher, edition, geography, technology, units, heating-value basis, GWP, effective dates and superseded versions. The platform should prevent silent replacement, show which calculations used each version and support an approved recalculation decision.
How should verifier access work?
Every material datapoint should link to source evidence, method, calculation and approval. The workflow should separate data preparation, review, legal/claim review and final representation. A verifier workspace should allow controlled read-only access, questions, findings, responses and closure without exposing unrelated restricted files.
Which exports and retention features matter?
A useful corporate MRV platform should control the entity, facility and source register; factor and methodology versions; unit conversions and calculations; estimates and uncertainty; evidence and approvals; immutable audit logs; verifier access; authority-ready exports; five-year retention; and security. The UAE National MRV System was launched in October 2025 as an integrated national platform, but public launch information does not replace entity-specific filing instructions or disclose every interface specification.
What decisions must remain with people?
Software should automate repeatable work while pausing for named approval where facts, legal status or professional judgement control the answer. Reality: software can enforce workflow and evidence discipline, but the organisation remains responsible for applicability, boundaries, methods, estimates, claims, approvals and the accuracy of the filed information.
Sources
Primary sources
- Federal Decree-Law No. (11) of 2024 on the Reduction of Climate Change Effects
- UAE launches National MRV System, WAM, 16 October 2025
- Cabinet Resolution No. (67) of 2024 concerning the National Register for Carbon Credits
- GHG Protocol Corporate Accounting and Reporting Standard, Revised Edition
- UAE data protection laws overview
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.
