Taiwan asked for a delivery date. Washington…

Build. Approve. Train. Release. Deliver.

Taiwan’s defence minister said Washington recognised the urgency of accelerating delayed weapons, including a 66-aircraft F-16V programme. Many deliveries were already moving, but the slowest large orders still shaped readiness. Taipei can create project teams and press its partner; it cannot set the pace of American factories or export procedures. An arms package reassures politically on announcement day. Militarily, it matters only when the equipment arrives and crews can use it.

There is a procurement fact hiding behind the public announcement: signing the order feels like the hard decision has been completed. What actually matters is the production queue, government release authority and the unglamorous sequence of training, infrastructure, spares and ammunition. That is the control point hiding behind the headline fact: Taiwan asked for a delivery date.

For Taiwan, first delivery is not fighting strength.

The supplier may never issue a written refusal. It can explain, review, consult and postpone. The result may still be to keep the contract alive while moving the useful capability into a later political or military reality. Your forces experience the result long before your lawyers agree on the label. For Taiwan, the warning is captured by what followed: Washington delivered a 'we recognise the urgency' reply.

This is where scenario planning has to become specific. Do not write 'seek alternate supplier' in the risk register and move on. Name the supplier. Confirm the legal route. Price the integration. Hold the stock. Train the people. Until those steps are complete, the alternative is a comforting noun rather than an operational capability. The exercise has a concrete starting point in this case: Taiwan asked for a delivery date.

If you are buying, start with the questions the salesman would rather answer later. How many trained crews exist on the promised delivery date? How much ammunition arrives with the first platform? What happens to the current fleet if the replacement slips by two years?

The force commander needs a different set of answers. Who else is ahead of you in the production queue? Which customer can be moved ahead of you during a crisis? What part of the system depends on a third country? Procurement success is not contract signature. It is usable strength on the required date.

This is where the procurement team earns its keep. It can obtain rights to inspect progress at the factory, buy an interim bridge rather than pretending the gap will not occur and align crew training with realistic delivery windows. A penalty clause may recover money later. These measures protect capability now.

The finance ministry should see this risk too. Resilience can look expensive because its cost appears in the tender. Dependence often looks free because its cost appears later, in emergency purchases, redesign work, lost readiness and political concessions. That accounting difference does not make dependence cheaper. It merely hides the invoice. The headline fact, 'Taiwan asked for a delivery date', should carry that exposure in its score.

This is not an argument for buying the first system available. It is an argument for treating time as a performance specification, alongside range, accuracy and payload. That distinction matters here: Washington delivered a 'we recognise the urgency' reply.

The final test for Taiwan is simple: can the replacement become operational before the capability it replaces has to retire? If the honest answer begins with 'provided that somebody else agrees', that condition belongs on the first page of the procurement decision, not in an annex nobody reads.

The dangerous gap is the period between retiring what you have and fielding what you bought. Adversaries are under no obligation to respect that transition plan. The queue is part of the weapon, even though nobody puts it in the specifications. That exposure sits behind the claim that 'Taiwan asked for a delivery date'.