Thought Piece

At Least They Posted the Delay

John Ferry

·

DoD's 38th year on a CR out of the last 50 — but the first one where they posted the delay in advance. Use the runway.

There are two kinds of flight delays, and every road warrior knows the difference in their bones.

The first kind is the rolling delay. Departure slips 30 minutes. Then another 30. Then "we're just waiting on the crew." You can't leave the gate area, you can't get a real dinner, you can't book the backup flight, because boarding is always allegedly ten minutes away. Three hours later you've eaten a $14 protein box standing up and accomplished exactly nothing.

The second kind is the posted delay. The board says your 6pm flight now leaves at 9pm, and it means it. Annoying? Sure. But you can work with it. You leave security. You have an actual meal. You make calls. The delay costs you three hours instead of costing you the whole evening.

Federal budget people have spent most of their careers living in the first kind of delay.

This year, for once, somebody posted the board.

The board says December 11

On September 2 the President signed H.R. 6500, the Continuing Appropriations and Extensions Act, 2027, which keeps the government running at last year's levels through December 11. The Senate passed it 90 to 6 over the summer. The House cleared it 370 to 48 on September 1. All of this happened before fiscal year 2027 even started, which is not how this movie usually goes. The normal version features a frantic week of late-September brinkmanship, a midnight signature, and a two-week stopgap that rolls into another two-week stopgap. The rolling delay.

Not this time. The departure time is posted, it runs past the November elections, and nobody serious expects appropriations before then. You have been handed something the budget world almost never gives you: certainty. Even certainty about a bad thing is worth money.

Quick refresher for the newer folks on what a CR actually does, because the mechanics matter more than the headlines. A CR is last year's money at last year's rates. The boilerplate does the real work: no new starts, no production rate increases above what you sustained last year, no new multiyear contracts. Your program got a big plus-up in the FY27 request? Congratulations on the request. The checkbook is holding at FY26's roughly $838 billion for defense until December, against an FY27 ask that tops a trillion dollars once you stack up all the pots. The gap between what was requested and what's flowing is the delay. The boilerplate is the gate agent telling you to stay seated.

And the anomaly list is priority standby. OMB sent up its exceptions this cycle, including advance procurement money for the new battleship program and above-rate production on several munitions lines. Appropriators mostly said no and kept the standard language. That's the anomaly game in one sentence: everybody asks, almost nobody boards early, and the asking itself tells you what the building believes cannot wait.

What the rolling delays have been costing us

If you think the delay is free because "the money shows up eventually," GAO would like a word. Their January report on CR effects (GAO-26-107065) is the receipt pile. DoD has operated under a CR in 37 of the last 49 fiscal years. Of 74 acquisition programs GAO surveyed, 36 reported schedule slips in contract awards or fielding. A facilities sustainment contract at Joint Base San Antonio went from a $579,000 estimate to a $1,445,000 quote while it waited out a CR. The Marine Corps' Amphibious Combat Vehicle program hung a $17.7 million price tag on CR-driven timing shifts, and the exchange-rate swings that came with them, between FY22 and FY24. And the F-35 program, of all programs, estimates 20 percent of its financial management staff's time goes to replanning budgets around CR constraints.

Read that last one again. One hour in five, spent managing the delay instead of the program.

That's what the rolling version costs. The posted version costs less, but only if you act like the board is real.

Use the runway

Here's the part where I stop complaining, because a known 90-day delay is a planning gift and most of the building will waste it out of habit.

If you're in government: you know your topline through December 11 to the dollar, which is more than you knew in most Octobers of your career. Anything executable at FY26 rates on FY26-style activities can move now. And the stuff that's gated until appropriations? The wickets don't have a funding prohibition. Do the market research, finish the acquisition strategy, get the J&A drafted, run the evaluation prep, so that when real money lands in December you're awarding in days, not rebuilding a schedule in March. If you believe your program deserves an anomaly next round, the GAO report is your homework assignment: start writing down what the delay costs you, with dollar signs, now.

If you're on the industry side: quit forecasting Q1 awards on anything that smells like a new start. It's not pessimism, it's reading the posted board. Point your energy at vehicles funded with FY26 money, and remember the shelf-life rules from a couple weeks back: last year's two-year RDT&E and three-year procurement dollars are still perfectly good groceries. Then build your December pipeline like you mean it, because when the delay lifts, the whole terminal boards at once.

The CR was never going to be the surprise this year. The only surprise left is who actually planned for it.

The flight's at 9. Go get dinner. But be back at the gate.