The amendment adding a new launch integrator comes back from DDTC on a Monday. Approved. By Wednesday, your integration lead has walked the integrator’s engineers through the payload interface drawings on a video call. The amendment is still sitting in a foreign partner’s legal queue, unsigned.

That call may have been an unauthorized defense service. Under the ITAR, DDTC approval of a technical assistance agreement (TAA) or amendment is not the starting gun. Execution by every party is. The gap between the two is short, routine and almost invisible to the engineers working inside it.

This year’s two largest DDTC settlements both put agreement management at the center. If your program works with foreign launch providers, integrators, ground station operators or payload partners, that gap is in your schedule right now.

Approval is not authorization to start

The ITAR is explicit about when an amendment can be used. Under 22 CFR 124.1(c), changes to the scope of an approved agreement, including modifications, upgrades and extensions, must be submitted for approval and may not enter into force until DDTC approves them. DDTC’s agreement guidelines add the second condition: no technical data, defense articles or defense services may be exported against an agreement or amendment until all parties have executed it.

Then comes the paperwork that proves it. Section 124.4(a) requires the US party to file a copy of the concluded agreement with DDTC no later than 30 days after it enters into force.

So there are three separate milestones, and teams tend to merge them into one. DDTC approval. Full execution by every signatory. Filing the executed copy. Engineering hears “approved” and starts. Compliance often learns the foreign party has not signed only when it chases the filing.

There is one narrow exception. For amendments whose only purpose is adding sublicensees, DDTC’s guidelines allow the applicant’s signature to count as execution. Even then, every other signatory must receive the approved, signed amendment before any transfer, and new sublicensees must sign a non-disclosure agreement. It is an exception with its own conditions, not a shortcut.

What the 2026 settlements show

BAE Systems’ $36 million settlement in August reads like a catalog of this exact failure. According to Volkov Law’s analysis of the charging letter, BAE was managing more than 120 DDTC agreement authorizations. Its violations included technical proviso breaches, TAA amendments implemented before all signatories had executed them, and missing foreign-party forms.

Two specific incidents should worry any space program:

1. Work in the gap between agreements. BAE performed qualification testing services abroad after one TAA had terminated and before its successor was fully executed. An export compliance official approved the trip without catching the gap.
2. Data shared with an unlisted party. A project team passed controlled specification data to a manufacturer that had never been added as an authorized sublicensee, because nobody checked recipient authorization first.

GE Aerospace’s April settlement points the same way. Of its 116 charged violations, 103 came from mismanaging DDTC authorizations, including proviso violations and exports outside a TAA’s build-to-print scope. GE’s own root cause: authorization procedures that had not been updated in over a decade.

These are two of the most experienced defense exporters in the world. A NewSpace program with one part-time Empowered Official and agreements tracked in a spreadsheet is far more exposed, not less.

Where space programs open the gap

Most amendments in a space program are triggered by schedule changes, not legal strategy. That is why they move fast and why engineering starts early. Common triggers include:

1. Launch manifest changes. A slip moves you to a different vehicle or rideshare aggregator, and the new provider or its integrator needs adding. As we covered in launch provider regulatory drop and the manifest bottleneck, providers ask for export documentation late, which compresses the window further.
2. New subcontractors on the partner’s side. A foreign integrator brings in a test house or harness supplier. They need sublicensee status before they see anything controlled.
3. Scope creep in the hardware. A late design change adds a component or data set the original agreement never described. If it changes the scope, it needs an approved and executed amendment before it is shared.

Classification sits underneath all three. You cannot tell whether a data package falls inside an agreement’s scope if you are not sure which parts are ITAR-controlled in the first place. Our post on ITAR over-classification shows how often that answer is wrong in both directions.

Closing the gap before the next amendment

Treat “fully executed” as the only green light. Make it a named status in whatever system tracks your agreements, owned by one person, and visible to the engineering leads who schedule partner calls.

Then add three checks to every amendment:

• Confirm signatures from every party, with dates, before the first technical exchange.
• Check every recipient against the current list of signatories and sublicensees before data leaves.
• Diary the 30-day filing deadline the moment the last signature lands.

Finally, ask one question in your next program review: for every foreign partner your engineers spoke to this quarter, can you show the executed agreement or amendment that covered the conversation?

If the answer is no, you are carrying unnecessary regulatory risk. We built Astrolytics specifically to eliminate this blind spot, giving you automated ITAR and EAR classification with an immutable, user-attributed audit trail for every BOM decision so you can know exactly which hardware and data an agreement must cover before anyone shares it. See how we secure your mission architecture at Astrolytics.