CBAM readiness is a data governance problem before it is a calculation problem. An exporter is ready when it can state which goods are covered, demonstrate the installation boundary, produce energy and production data that reconcile to primary records, evidence precursor emissions, and hand a verifier a file that reproduces the reported figure without further explanation.
Readiness is binary in practice: either a verifier can reproduce your number from your files, or they cannot. Work backwards from that test.
Who should use this guide, and what decision does it support?
Exporters in covered sectors preparing for their first verified submission, and teams tidying up after a difficult first reporting cycle.
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 coverage by CN code and identify the reporting period and declarant relationship.
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.
- Document the installation boundary and the production routes within 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.
- Build the data map: every input, its source, owner, unit, period and quality check.
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.
- Close precursor gaps through supplier engagement or documented conservative estimates.
Evaluate significance against the agreed decision criteria and show assumptions or sensitivity clearly. Separate observed facts, calculations, professional judgement and information that remains unavailable.
- Run an internal dry-run verification before the real one, and fix what it exposes.
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.
- Coverage analysis and reporting calendar with named responsibilities
- Installation boundary description and process flow documentation
- Reconciled energy, production and feedstock datasets for the period
- Supplier emissions declarations and the register of outstanding gaps
- Calculation files under version control with an internal review record
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
- Starting the work at reporting deadline rather than at the start of the period
- Leaving supplier data requests until after the period has closed
- Treating the calculation as a finance task disconnected from production data
- No internal review step, so the verifier becomes the first reader
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 goods, period and declarant confirmed in writing
- Boundary and routes documented and unchanged from the stated basis
- All inputs traceable to a primary record with a named owner
- Precursor data obtained or gaps disclosed and conservatively handled
- Internal dry-run completed and findings closed before submission
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.