Table of Contents
AMRT updates do not usually introduce new legal obligations. They introduce new expectations about data structure, consistency, and interpretation.
Version 1.3 is a good example of this pattern.
Many suppliers reacted to AMRT 1.3 by assuming they needed more precision or new upstream detail. In reality, most of the changes were designed to reduce ambiguity, not raise the data bar.
This article explains what changed in AMRT 1.3, why those changes were made, and what suppliers actually need to update—without turning AMRT into a traceability exercise.
What an AMRT “Version Change” Really Means
AMRT version updates are not the same as regulatory amendments.
They are intended to:
- clarify interpretation issues seen in prior submissions
- standardize responses across suppliers
- improve data comparability for customers
- reduce inconsistent or misleading answers
Version 1.3 was driven largely by reviewer feedback—not by new mineral requirements or compliance mandates.
Key Areas Impacted in AMRT 1.3
While AMRT 1.3 did not change the fundamental purpose of the template, it did refine how suppliers are expected to express data.
The most meaningful changes relate to:
- declaration logic clarity
- reference data alignment
- reduction of free-text ambiguity
These adjustments aim to make AMRT responses easier to interpret and harder to misread.
The Role of Reference Data in AMRT 1.3
One notable evolution in AMRT 1.3 is the greater emphasis on standardized reference data where available.
This does not mean suppliers are expected to suddenly know all processors or upstream actors. It means:
- responses should align with known industry references when cited
- invented or speculative entries are discouraged
- consistency across submissions is prioritised
The intent is to reduce noise, not demand certainty.
What Did Not Change in AMRT 1.3 (Important)
It is just as important to understand what did not change.
AMRT 1.3 did not:
- introduce smelter-level traceability requirements
- require full upstream processor identification
- convert AMRT into a compliance template
- eliminate the acceptability of “unknown” responses
Suppliers who reacted by adding artificial precision often created new credibility issues rather than solving old ones.
Why Suppliers Over-Correct After Version Updates
A common pattern after AMRT updates is over-correction.
Suppliers often:
- rework answers that were already appropriate
- force mineral certainty that doesn’t exist
- align AMRT answers to CMRT logic
- add excessive narrative to “look complete”
This usually backfires.
Version updates aim to standardize, not to raise maturity expectations overnight.
What Suppliers Should Actually Review After AMRT 1.3
When updating for AMRT 1.3, suppliers should focus on:
- consistency of declaration answers across business units
- alignment between product logic and mineral responses
- removal of copied CMRT or EMRT language
- clarity around “unknown” justifications
- internal alignment on mineral scope
These updates improve credibility without introducing unnecessary risk.
AMRT 1.3 and Data Comparability Over Time
One reason customers care about version alignment is trend analysis.
AMRT 1.3 improves the ability to:
- compare responses year-over-year
- identify improvement trajectories
- detect unexplained changes
Suppliers that treat version updates as a chance to “start fresh” often raise more questions than those who maintain continuity and explain changes clearly.
What AMRT 1.3 Signals to Reviewers
AMRT 1.3 is less about what you report and more about how consistently you report it.
Reviewers look for:
- structured, repeatable answers
- alignment with prior submissions
- logical evolution, not abrupt certainty
A supplier whose data matures gradually is viewed as far more credible than one that suddenly claims full visibility after a template update.
What AMRT 1.3 Means for Suppliers
AMRT 1.3 does not raise the bar on traceability. It raises the bar on interpretability.
Suppliers that approach AMRT 1.3 correctly:
- adjust structure, not substance
- improve clarity, not certainty
- align internally before submitting
Version updates are not tests of sophistication.
They are tests of discipline.