Iron and steel are among the goods covered by the EU Carbon Border Adjustment Mechanism, and since the definitive regime began the embedded emissions reported for those goods must be capable of withstanding third-party verification. For an Egyptian producer that means fixing the installation boundary, attributing emissions to specific production routes and CN codes, tracking precursors such as pig iron and direct reduced iron through the process, and retaining the underlying records rather than reconstructing them at reporting time.
The decision is not whether to report but whether your plant data can survive scrutiny. Build the installation boundary, the precursor chain and the evidence register first; the calculation is the easy part.
Who should use this guide, and what decision does it support?
Production, energy, quality, commercial and finance teams at Egyptian iron and steel producers exporting to the European Union, and the customers or traders who rely on their data.
Before work begins, agree the question the assessment or review must answer and who will rely on the result. A design decision, lender report and regulatory submission need different levels of detail. Defining the use case early prevents teams from collecting large amounts of information that do not change the decision.
A practical implementation sequence
- Confirm which of your exported products fall under CBAM by CN code, and for which reporting period.
Set the purpose, boundary and decision timetable in writing. Name the people who will supply information and approve the result, and record any legal, lender or client framework that changes the scope.
- Define the installation boundary and map each production route to the processes that serve it.
Build a source register before analysis begins. Check dates, units, ownership and completeness so later calculations and findings use consistent information rather than convenient but incompatible files.
- Identify every precursor that carries embedded emissions into the product and establish how its data will be obtained.
Test important claims against more than one form of evidence where practical. Site observation, interviews, measurements and operating records often reveal whether a documented control is actually used.
- Attribute fuel, electricity, process and precursor emissions to production volumes for each covered good.
Evaluate significance against the agreed decision criteria and show assumptions or sensitivity clearly. Separate observed facts, calculations, professional judgement and information that remains unavailable.
- Assemble the evidence register and test whether an independent verifier could reproduce the result from it.
Turn the result into an implementable output. Assign owners, deadlines, resources, monitoring indicators and objective closure evidence, then retain the approved version for future review.
Data and evidence required
The conclusion becomes more reliable when boundaries, data sources, responsibilities and quality checks are documented from the start. Possessing a file is not enough: record its period, unit, owner, review method and any adjustment made.
- CN codes, export volumes and customer or declarant details for the reporting period
- Fuel and electricity consumption records reconciled to invoices and meters
- Production volumes by route and by product, at the same period boundary as the energy data
- Precursor purchase records with supplier emissions data where available
- Calculation files, method notes, assumptions and the approval trail for each submission
Maintain a simple evidence register that connects each finding to its source, identifies unavailable information and explains how uncertainty was handled. This reduces review time and makes the conclusion easier to update when design, operations or requirements change.
How management should use the result
A decision-ready output distinguishes issues that prevent a decision, actions that must close before a defined milestone and improvements that can be managed through operations. Every action should have an owner, date, resources and objective closure criterion instead of a general instruction to “comply with requirements”.
Put a short executive answer first, with the analysis and evidence underneath. Management, finance, legal and technical readers can then use the level they need while the full reasoning remains traceable and reviewable.
Common mistakes to avoid
- Reporting at company level when the requirement is installation and product level
- Ignoring precursors, which for steel frequently carry a large share of the embedded emissions
- Relying on default values without checking whether they remain permitted for the goods and period
- Producing a number that nobody can trace back to a meter, invoice or production record
A recurring mistake is to confuse a completed report with effective implementation. Quality is demonstrated when the output informs a decision, changes a control or closes a gap with evidence—not by page count or table density.
Frequently asked practical questions
When should the work begin?
Start before design freeze, financing approval or a submission deadline. Early work gives teams time to resolve missing data and change options at lower cost.
Is a document review sufficient?
Not for most material assignments. Documents show the intended system; interviews, site observation and operating records test whether controls work in practice.
How should incomplete data be handled?
Record the gap and its effect, use a conservative estimate where justified and define how better data will be obtained. Do not hide uncertainty inside a final number that appears more precise than the evidence supports.
What makes an output reviewable?
Clear boundaries, traceable sources, retained versions, disclosed assumptions, internal review and an identified approval owner.
Checklist before sign-off
- Covered CN codes confirmed against the current list for the reporting period
- Installation boundary documented and consistent between periods
- Precursor data obtained or its absence explained and handled conservatively
- Energy, production and emissions data reconcile to primary records
- Evidence retained under version control and ready for verification
This checklist does not replace project-specific legal or contractual advice. Confirm the applicable framework for every assignment and obtain appropriate advice where exposure is material.