For drone manufacturers
Each part in your bill of materials, screened against the rules a federal buyer asks about — the evidence dated, and anything we cannot resolve named rather than passed.
An illustration of the five steps on this page, zooming from a drone in the field to the record on one of its parts.
What the drawing names, in order: a quadcopter on station over a battlefield; its own parts labelled where they sit — airframe, flight controller, radio and data link, camera and gimbal, battery, motors, propellers; the four origins asked of it, hardware, firmware, software and data, with the chain behind your supplier fading out rather than ending; the modules screened against SAM/FASC, the FCC Covered List and 1260H while one list gets a new version; and the dated record engraved on one module's data plate, whose last line is the one item still open.
Your compliance evidence is scattered across spreadsheets, email threads and supplier PDFs. Verification usually stops at the company you bought from, not the one that made the material. And the lists move — a supplier that was fine last quarter may not be this quarter, and nobody tells you.
Step 01
Import the bill of materials you already have. Keep it where it is.
Step 02
Trace parts, materials and firmware back past your direct supplier.
Step 03
Check each part against the rules that actually reach it: 889, 1260H, DFARS specialty metals, the FCC Covered List, SAM/FASC.
Step 04
Re-check when a list changes, and say what moved, on which part, and when.
Step 05
Assemble a dated record of what was checked, against which list version, on what date.
An evidence packet you can send to a contracting officer: every part, the rule it touches, the document that supports it, the list version it was checked against, the date, and the items still open. Not a score. Not a dashboard screenshot. The paperwork.
We don’t issue compliance determinations. We flag what needs a human’s judgement, assemble the evidence behind it, and leave the ruling to the people whose job it is. When an answer is genuinely unsettled we return it as needing review rather than resolving it in your favour.
Keep your bill of materials where it is. We read the export you already produce, and nothing here asks you to move it, re-author it, or run a migration first.