AMRT Compliance Guide: Everything Manufacturers Need to Know

AMRT requests show up in supplier inboxes with no warning and no clear deadline attached to a law. A customer asks for an Additional Minerals Reporting Template, gives a short turnaround, and offers little explanation of why. That gap between "this feels mandatory" and "there is no regulation behind it" is the single biggest source of confusion around AMRT, and it shapes almost everything else on this page.

What AMRT Actually Is

The Additional Minerals Reporting Template (AMRT) is published by the Responsible Minerals Initiative (RMI), the same group behind the Conflict Minerals Reporting Template (CMRT) and the Extended Minerals Reporting Template (EMRT). Where CMRT covers tin, tantalum, tungsten and gold, and EMRT covers cobalt, copper, graphite, lithium, mica and nickel, AMRT exists for everything else. It is not tied to a fixed mineral list. The requesting company, usually a customer further up the supply chain, specifies which minerals it wants reported on, up to ten per request, and your business answers using the RMI-maintained template.

That flexibility is also what makes AMRT confusing. Understanding the Additional Minerals Reporting Template (AMRT) walks through the template structure in more depth if you want the full breakdown before going further.

Why You’re Being Asked When No Law Requires It

Most teams assume a reporting request this detailed must trace back to a regulation. It usually doesn’t. Why Suppliers Are Asked for AMRT Before Laws Exist and AMRT Applicability Explained cover this directly: large OEMs and brand owners build AMRT into supplier onboarding and ESG due diligence ahead of anticipated rules, not because of one already in force. Why EMRT and AMRT Requests Are Rising Even Without a Regulation Mandate explains the broader trend across both templates.

This is also why "voluntary" is a misleading word for how AMRT actually functions in a commercial relationship. Who Is Expected to Submit AMRT (and Why "Voluntary" Is Misleading) covers the practical reality: no regulator will fine you for ignoring an AMRT request, but a customer can and will treat a refusal as a reason to escalate, delay a purchase order, or move the business elsewhere.

Which Minerals Actually Trigger a Request

Because the mineral list is set by the requester rather than fixed in the template, the minerals that show up vary by industry and by customer. Which Minerals Trigger AMRT Requests from OEMs breaks down the patterns: rare earth elements, tungsten carbide outside the CMRT scope, and specialty metals used in electronics and defense components are common targets. If a request lists a mineral you don’t recognize from CMRT or EMRT, that is expected. AMRT exists precisely to cover that gap.

How to Actually Fill AMRT Template Out

The template itself has a declaration tab, a product or company-level reporting structure depending on what the requester asks for, and a smelter list section. How to Fill the AMRT: Declaration Questions and Data Expectations Explained is the practical walkthrough for the declaration section specifically. The part that trips up most first-time respondents is the smelter list: if a processor or refiner in your supply chain isn’t on the RMI’s Standard Smelter List, you can’t just leave the field blank. AMRT Smelter Look-up Tab Explained covers what to do when that happens, including how to flag an unlisted processor without stalling the whole submission.

Version control matters here too. RMI updates AMRT periodically, and using an outdated version is one of the fastest ways to get a submission bounced back. As of this writing, RMI’s published version is 1.31, released April 17, 2026, with the next update expected in fall 2026. AMRT 1.3 Changes Explained covers what changed in the most recent update. Given how often RMI revises these templates, confirm the current version directly on the RMI reporting templates page before submitting rather than relying on a cached copy from a prior reporting year.

What is Typical AMRT Request in Practice

A mid-size electronics supplier receives an AMRT request from a Tier 1 OEM customer asking it to report on three minerals: a rare earth element used in a magnet component, a specialty alloy metal, and tungsten carbide used outside the scope already covered by its CMRT. The supplier has clean smelter data for two of the three, collected during its last CMRT cycle, but the third traces to a processor that isn’t on RMI’s Standard Smelter List. Rather than leaving that field blank, the supplier flags it through the unlisted-processor process and documents the source relationship. The declaration goes back within the customer’s deadline, and because the data was reused from the existing CMRT pipeline rather than collected from scratch, it takes a fraction of the time a first-time AMRT response would.

That pattern, reusing existing supplier data, flagging gaps instead of skipping them, and checking the template version before submitting, is the difference between AMRT being a recurring headache and a routine part of supplier reporting.

Common Mistakes That Get Submissions Rejected

• Using a stale template version instead of checking for the current release before each reporting cycle.
• Leaving smelter fields blank instead of using the look-up or unlisted-processor process.
• Treating AMRT like CMRT and reporting on 3TG minerals that belong in a different template entirely.
• Inconsistent answers across product lines when a company-level declaration would have been simpler and more defensible.

AMRT Data Quality Mistakes: The Most Common Errors That Trigger Customer Rework goes deeper on each of these, with the specific error patterns that cause a customer to send a submission back. Read it here: AMRT Data Quality Mistakes.

What Happens When a Submission Gets Flagged

A rejected or flagged AMRT doesn’t go through a legal process, but it does go through an escalation process that behaves a lot like one internally at the customer’s organization. How AMRT Is Enforced Without Regulation explains how validation and escalation actually work in practice. Why AMRT Submissions Get Flagged Even When They’re "Accepted" and What Triggers AMRT Escalation cover the specific patterns, such as inconsistent smelter data across reporting periods, that put a supplier under closer review even after an initial submission was marked accepted.

The Real Cost of Getting It Wrong

Because there’s no regulator attached to AMRT, it’s tempting to treat a flagged submission as low stakes. It isn’t. AMRT Failure Is Commercial, Not Legal: What Suppliers Actually Lose lays out what actually happens: delayed purchase orders, a supplier being moved to a watch list, or being quietly dropped from a bid. When AMRT Data Creates ESG and Reputational Risk for Customers covers the other side of that risk, where your data quality becomes a reflection of your customer’s own ESG disclosures and ratings.

How to Manage AMRT When You Handle Dozens of Requests a Year

A single AMRT response is manageable in a spreadsheet. Twenty requests a year across different customers, each specifying different minerals and different reporting scopes, is not. Running AMRT at Scale: Why One-Time Responses Always Fail and Why Email and Spreadsheets Can’t Sustain AMRT at Scale cover why the manual approach breaks down as volume grows.

Two operational questions come up constantly once a company is handling AMRT at any real scale: how often does the template actually need updating, and who inside the organization should own it. How Often AMRT Must Be Updated covers a practical review cycle, and Who Owns AMRT Internally (and Why Shared Ownership Fails) addresses the ownership question directly, since AMRT tends to fall into a gap between procurement, compliance, and sustainability teams. Why Product and Supplier Changes Break AMRT at Scale covers the maintenance problem that follows: a declaration is only accurate until your bill of materials or supplier base changes, and most companies don’t have a trigger in place to catch that.

AMRT vs CMRT vs EMRT: Picking the Right Template

If you’re not sure whether a request should be answered with CMRT, EMRT, or AMRT, that confusion is common and worth resolving before you start filling anything out. CMRT vs EMRT vs AMRT: Key Differences (and Which Template You Need) breaks down the scope differences directly. As a quick reference: CMRT covers tin, tantalum, tungsten and gold; EMRT covers cobalt, copper, graphite, lithium, mica and nickel; AMRT covers whatever the requester specifies outside those two lists, up to ten minerals per request.

Where AMRT Fits Into Your Broader ESG and Supply Chain Picture

AMRT rarely arrives on its own. It usually shows up alongside a CMRT request, an EMRT request, a supplier code of conduct attestation, and sometimes a separate ESG questionnaire from the same customer. Treating each as a one-off intake creates duplicate work: the smelter and supplier data underlying an AMRT response overlaps heavily with what you already collected for CMRT and EMRT. Companies that build a single supplier data pipeline covering all three templates spend far less time per request than companies answering each from scratch, because the underlying question, "where does this material actually come from," doesn’t change between templates even though the mineral list does.

This overlap also means a data gap in one template tends to resurface in the others. If your smelter list was incomplete on your last CMRT submission, expect the same gap to show up in an AMRT request for a different mineral sourced from the same supplier. Fixing supplier data at the source, rather than template by template, closes that gap once instead of three times.

What a Defensible AMRT Program Actually Looks Like

1. A single current copy of the template, checked against RMI’s published version before each reporting cycle rather than reused from the last request.
2. A maintained internal smelter and supplier list, cross-checked against RMI’s Standard Smelter List, with a defined process for flagging unlisted processors instead of leaving fields blank.
3. A named internal owner, not a shared responsibility split across procurement, compliance, and sustainability, so requests don’t stall waiting for someone to pick them up.
4. A trigger tied to bill-of-materials or supplier changes, so a declaration gets revisited when the underlying sourcing changes rather than only when a customer asks again.
5. A shared data layer across CMRT, EMRT, and AMRT, so supplier and smelter information collected for one template doesn’t have to be re-gathered for the others.

None of this requires a large team. It requires a defined process and a single source of truth for supplier and smelter data, which is the piece most companies are still missing when AMRT requests start arriving from more than one customer at a time.

Key Takeaways

• AMRT is published by RMI and covers minerals outside the CMRT and EMRT scopes, with the requester choosing up to ten minerals per submission.
• There is no regulation mandating AMRT today. The business pressure to complete it comes from customer ESG programs and supply chain due diligence, not from a government requirement.
• Version control and smelter list accuracy are the two most common causes of rejected submissions.
• A flagged or rejected AMRT carries commercial consequences, delayed orders, watch-list status, lost bids, even without any legal exposure.
• Companies handling more than a handful of AMRT requests a year need a defined internal owner and a system built for recurring updates, not a one-time spreadsheet response.

How Regilient Helps

Regilient centralizes AMRT, CMRT, and EMRT reporting so your team isn’t rebuilding each submission from scratch, tracks which template version you’re on, and flags smelter list changes before they cause a rejected declaration. If your company is fielding these requests from multiple customers with different mineral scopes, that’s exactly the kind of recurring operational load Regilient is built to take off compliance and procurement teams.