Mission Execution Brief · 004 · Semiconductors

A milestone can be late without being in default.

Programs often collapse several dates into one status label. GAO's 2026 semiconductor review shows why anticipated completion, contractual due dates and clawback dates should be managed as different controls.

PUBLISHEDSeptember 2026
LAST REVIEWEDOctober 29, 2026
PRIMARY FOUNDATIONGAO-26-109121
EDITORIAL OWNERAssemble Teams — Mission Intelligence

The operating signal

As of July 15, 2026, Commerce had funded 49 semiconductor projects across 24 companies. GAO reported that, as of April 2026, awardees had completed all required milestones by their contractual due dates even though some milestones had slipped past their anticipated schedules. Commerce had disbursed $13.1 billion—about 42% of direct funding at that point.

3 clocks

GAO distinguishes an anticipated completion date, a contractual milestone due date tied to disbursement, and a project completion clawback date that can support recovery of funds if the project is not completed.

GAO found nine milestones past their anticipated completion dates as of April 2026, while all required milestones had still been completed by their due dates. It also documented amendments that changed milestone schedules for some projects, including two projects whose expected completion moved two years later after an awardee added a new project at another location.

The three-clock review

01 · OPERATING FORECAST

Anticipated completion date

This is the management signal. Slippage here can be an early warning even when no contractual breach exists.

Track: variance + cause + downstream dependency effect.
02 · CONTRACTUAL CONTROL

Due date

This is the enforceable milestone boundary associated with funding or another contractual consequence.

Track: evidence required for acceptance + reviewer + consequence.
03 · PROGRAM BACKSTOP

Clawback or final completion date

This is a larger program-level backstop. It should not be the first time leadership discovers chronic schedule erosion.

Track: cumulative variance + recovery rights + escalation threshold.

What this changes

Assemble Teams analysis: a mission dashboard should not flatten “late” into a red/green status. A milestone can be behind its operating forecast while still compliant with contractual terms. Both facts matter. The first is an execution signal; the second is an accountability boundary.

What the evidence does not prove

GAO's semiconductor findings do not show that schedule amendments are inherently improper or that every anticipated-date slip predicts default. Award structures differ and amendments can reflect legitimate changes. The transferable control is to preserve the distinction between forecast variance and contractual nonperformance.

Use this in funded programs.

For every major milestone, record all three clocks and require a written explanation when the operating forecast moves—even if the legal due date does not.

Browse semiconductor and infrastructure missions →

Editorial standard: GAO findings are descriptive; Assemble Teams' “three-clock review” is a practitioner synthesis, not a Commerce or GAO framework.

MISSION INTELLIGENCE · PUBLICATIONS

Get the next evidence-backed release.

Subscribe for occasional Mission Intelligence, research and newly published articles from Assemble Teams. This subscription is separate from Directory listing consent and GameChangers reservations.

Optional. We use your email for requested publication updates. See the Privacy Policy. You can ask us to stop future messages at any time.