What "specially designed" actually means, and why your shop has to get it right.

There is a phrase in export law that decides whether a part you machine is governed by Commerce (the EAR) or by State (the ITAR). It decides whether you need to register with DDTC and pay an annual fee. It decides which licensing rules apply, which exceptions are available, and which penalty schedule you are on.

The phrase is "specially designed."

Most engineers and shop managers read it the way they would read it in English. The part was designed for a specific application, so it was "specially designed" for that application. That reading produces a lot of incorrect ITAR calls. The regulatory definition is built very differently than the English phrase suggests.

This week, what "specially designed" actually says, why the definition uses a catch-and-release structure, and the documentation move that keeps you out of trouble.

The phrase is defined in two places. The EAR definition lives at 15 CFR 772.1 under the entry "Specially designed." The ITAR definition lives at 22 CFR 120.41. They differ in detail but share a common architecture, and the EAR version explicitly tells you to "follow this sequential analysis," referencing the broader Order of Review at Supplement No. 4 to Part 774.

The architecture is two steps. First, an item is caught by paragraph (a) if it meets either of two conditions. Second, an item that was caught can be released by paragraph (b) if it meets any one of several other conditions. Caught and not released means specially designed. Caught and released means not.

That structure exists for a real reason. Without paragraph (b), every fastener on a fighter jet would be caught by the broad "for use in or with a defense article" prong of paragraph (a), including the standard hex-head bolts you can buy at a hardware store. Paragraph (b) keeps the controls on the actually-defense-specific design content.

Both regulations have a two-prong catch.

Paragraph (a)(1) catches an item if, as a result of development, it has properties peculiarly responsible for achieving or exceeding the performance levels, characteristics, or functions described in a specific USML or ECCN paragraph. The phrase "as a result of development" is doing real work. An item that incidentally meets a performance level is not caught. It has to have gotten there through development for that purpose.

Paragraph (a)(2) catches an item if it is a part, component, accessory, attachment, or software for use in or with a defense article (ITAR) or for use in or with an item enumerated or otherwise described on the CCL or USML (EAR). This prong is broader than people expect. The bolt that holds the seat in a fighter jet meets prong 2.

If either prong catches the item, you move on to paragraph (b). You do not stop.

The ITAR has five releases at paragraph (b). The EAR has six. The first five overlap closely.

Release (b)(1) is the formal-determination release. Under the ITAR, the item is released if it has been determined to be subject to the EAR through a Commodity Jurisdiction request. Under the EAR, the item is released if it has been placed in an ECCN that does not use "specially designed" as a control parameter, or if it has been determined to be EAR99 through a CJ determination or a CCATS commodity classification. This is the "you asked the government and they answered" release.

Release (b)(2) is the enumerated hardware release. The regulation says the item is not specially designed if it is, regardless of form or fit, "a fastener (e.g., screws, bolts, nuts, nut plates, studs, inserts, clips, rivets, pins), washer, spacer, insulator, grommet, bushing, spring, wire, or solder." The regulation names these by hand. If you are making a hex-head bolt or a standard washer for a defense customer, the regulation itself releases it. This is the single most relevant release for a machine shop, and it is the one most often missed.

Release (b)(3) is the commercial-equivalence release. The item has the same function, performance capabilities, and the same or equivalent form and fit as a commodity used in or with an item that (i) is or was in production, not still in development, and (ii) is not enumerated on the USML or CCL.

Release (b)(4) is the dual-development release. The item was or is being developed with knowledge that it would be for use in or with both a defense article (or CCL-controlled item) and a commodity not on the USML or CCL.

Release (b)(5) is the general-purpose release. The item was or is being developed as a general purpose commodity with no knowledge for use in or with a particular commodity. Generic by design.

The EAR adds a sixth release at (b)(6) for items developed for use with Anti-Terrorism-only controlled commodities and EAR99 items. The sixth release is EAR-only because the AT-only concept is specific to the CCL.

Two footnotes inside the regulation matter for any shop relying on releases (b)(4) or (b)(5). First, "knowledge" includes not only positive knowledge but also conscious disregard and willful avoidance of facts. You cannot defeat the knowledge prong by deliberately not asking. Second, reliance on (b)(4) or (b)(5) requires contemporaneous documentation. Concept design information, marketing plans, declarations in patent applications, or contracts, generated at the time of development, are how you prove dual-development or general-purpose intent. Reconstruction after the fact does not qualify. The regulation says so explicitly.

The two most common errors we see.

First, equating the customer with the jurisdiction. A defense prime customer does not make your part a defense article. A standard hex-head bolt sold to a missile integrator is named in release (b)(2) by the regulation itself.

Second, skipping the release analysis. Shops walk paragraph (a), conclude "yes, the part is for use in or with a defense article," and stop. They miss that the regulation explicitly directs you to walk paragraph (b) next. The catch alone is not the answer.

A third, subtler error worth flagging. The current ITAR "specially designed" definition was published as part of the March 23, 2022 reorganization of Part 120 at 87 FR 16411. If you have a classification on file from before March 2022, the file is past due for a refresh against the current paragraph structure.

Whatever you decide, write it down. The format that survives an audit is short. State the result of each catch prong (a)(1) and (a)(2) and your answer. Walk each release paragraph (b)(1) through (b)(5) or (b)(6) in order, and state your answer to each. Cite the specific subparagraph you relied on, by regulation. For (b)(4) or (b)(5), attach the contemporaneous documents the regulation requires. Sign your name, date the document, and store it where you can find it in five years.

The single most common reason a defensible classification looks indefensible at audit is that the file does not show the reasoning. The classification was right. The work to prove it was right was missing.

Pick one part you make for any customer in any defense-adjacent sector. Walk paragraph (a) on it. If either prong catches the item, walk paragraph (b) in order and stop at the first release that applies. Write the result down. Cite the specific subparagraph. Sign it. Date it. Save it.

If you want the catch-and-release walk to produce a real memo with the regulation cited and the reviewer named, run one item through ExChek at exchek.us. Want a walk-through? Book a call.

"Specially designed" is a phrase with a precise meaning. Get the meaning right, and the classification follows.

The ExChek Team

Source citations. Quoted and paraphrased regulatory language in this issue is drawn from 22 CFR 120.41 (ITAR, source 87 FR 16411, Mar. 23, 2022) and 15 CFR 772.1 (EAR, entry "Specially designed"). Both are available on the eCFR at ecfr.gov. ExChek is software, not legal advice. Every determination is reviewed and approved by you. American-owned, built to help American SMBs navigate export compliance.