Check every purchase order, not just the ones someone flagged.

What changes on January 1, 2027

The clause covers samarium-cobalt and neodymium-iron-boron magnets, tantalum metals and alloys, tungsten metal powder, and tungsten heavy alloy, including finished or semi-finished components that contain it. The covered countries are North Korea, China, Russia and Iran. Through December 31, 2026, the restriction applies to covered material melted or produced in a covered country. From January 1, 2027, it extends to material mined, refined, separated, melted or produced there, which for magnets means the supply chain from mining of the raw elements through the finished magnet.

Paragraph (d) requires the contractor to include the substance of the clause, including that flow-down paragraph, in subcontracts for items containing covered material, including subcontracts for commercial products. That is how a prime’s obligation reaches a machine shop several tiers down. Paragraph (c) sets out exceptions, including most commercially available off-the-shelf items (the threshold for excluded COTS items changes to 50 percent or more covered material by weight in 2027), electronic devices unless the contract says otherwise, and items covered by a nonavailability determination. Read the clause as it appears in your own contract and confirm its application with your prime or counsel. This guide is an operating framework, not legal advice.

The gap is coverage, not knowledge

Most suppliers who receive the flow-down know what the clause says. The harder problem is that origin questions tend to be answered one PO at a time by whoever has time. The lines that were flagged get checked. The ones nobody flagged go unreviewed. The gap surfaces only when a prime asks for the paper trail, and by then the evidence is spread across inboxes, shared drives and a supplier’s PDF from last spring.

A sales floor has the same problem. Manual call review is sampling. A manager listens to whatever they have time for, and the reps who most need coaching are the least likely to have their calls pulled. In both cases, more diligence doesn’t fix it. The fix is a system that applies the same standard to every record and points a person at the exceptions.

The pattern DBAI built for sales calls

SentiVox is a call-coaching platform DBAI designed, built and operates as its own venture. Each campaign carries one profile of weighted grading pillars, set in a form rather than re-decided by each reviewer. Every uploaded call is graded against that profile, coaching reaches the rep the same shift and is anchored to quotes from that call, and missed follow-ups surface to a manager exception view instead of leaving no trace. One deployment feeds roughly 120 calls a day through the platform, coaching SDRs across three countries.

None of that is about calls specifically. Write the standard down once, apply it to every record, tie each exception to its evidence, and give the follow-up an owner. The table below maps each part to origin evidence.

What to require from the system

• A written clause profile you can read and change. It should list which materials and part families are in scope, which exceptions you rely on and why, and what counts as acceptable evidence. It should not be a prompt nobody on your side can see.
• Coverage you can count. The system should report how many PO lines it checked, how many it treated as out of scope and why, and how many are still open.
• No silent passes. A missing or vague supplier declaration is an open question with an owner, not a pass. A model should never infer country of origin from a part description.
• Evidence attached at the line. Every finding should open to the document and page it relied on, so a reviewer can confirm it without searching.
• People make the compliance decisions. The system checks and routes, and a named person accepts the exception or the evidence. Record who decided and when.
• An export a prime can read: the line, the material, the evidence, the decision and the open items, without access to your systems.
• A data boundary written down before any records move. DBAI scopes this work to non-CUI, non-ITAR records by design. If your origin documents include controlled information, they stay out of scope.

Start with one part family and real records

Don’t start by trying to cover the whole shop. Pick one part family that you know contains covered material, pull its recent POs and the supplier declarations behind them, and run the clause profile across that set. You will learn quickly where declarations are missing, which suppliers answer in a usable form, and which exceptions you have been relying on without writing them down. Treat that first pass as a pilot with explicit acceptance criteria, and widen scope only after a person has reviewed the exceptions it produced.

What the SentiVox case study does and does not show

SentiVox is a sales-operations system. Its published case study describes a platform that grades every uploaded call against a per-campaign profile and surfaces exceptions to a manager. It is not a defense engagement, and nothing in it is evidence of results on a defense contract. The supplier mapping above shows how DBAI would apply the same architecture to compliance documentation. Ask for a demonstration on your own records before treating it as more than that.

Copy this origin-evidence brief

# 7052 origin-evidence brief
Prime(s) flowing down the clause:
Subcontracts / POs where it appears:
Covered materials you buy (magnets, tantalum, tungsten):
Part families likely to contain them:
Exceptions you rely on, and the basis for each:

## Records today
Where POs live (ERP / email / drive):
Where supplier declarations live:
Mill certs and attestations: format and location:
Who answers origin questions today:
How a prime request is answered today:

## First pass
Part family for the pilot:
PO date range:
What counts as acceptable evidence:
What counts as an open question:
Owner for open questions and due-date rule:
Who accepts an exception, and how it is recorded:

## Boundary
Records confirmed non-CUI, non-ITAR:
Records explicitly out of scope:
Who can see results and exports:

## Decision
Coverage achieved (checked / out of scope / open):
Gaps found and owners:
Widen scope / repair first / stop:

January 1, 2027 is about ten weeks from this guide’s publication. That is too little time to clean up every supplier relationship, but enough to know which lines are covered, which are open and who owns each gap, and to be able to show that to a prime.