01
Program Plus-Ups
An increase over the request for a named line, decided at markup, recorded in a table, itemized with a reason. Winning one means being in the request queue before the markup — not reacting to the mark after it posts.
Money moves through named accounts and numbered lines. Most companies cannot name theirs.
An appropriations bill is two documents. The bill text is short, legally binding, and almost never names your program. The committee report is long, not legally binding, and names it, numbers it, and assigns it a figure.
The Department follows the report because the committee that wrote it also writes next year's. Which is why the sentence that decides your fiscal year usually never gets a vote.
Every number in a defense appropriations bill begins as the President's request. The committee then adjusts it, line by line, in a table called the explanation of project level adjustments. Each adjustment carries a dollar figure and a short stated reason. In the FY2027 House defense bill, the Air Force Family of Affordable Mass Missiles procurement line moves from a $55 million request to a $355 million committee recommendation, itemized as a program increase of $300 million. Nobody debated that on the floor. Somebody asked for it, in writing, months earlier, and staff agreed.
Those requests come from members, and members make them because someone handed them a reason that survives scrutiny — a capability gap, a schedule, a supplier map, a cost comparison. The request goes to subcommittee staff on a form, by a deadline, with a justification attached. Miss the deadline and there is no mechanism to fix it afterward. Most of the work is knowing the deadline, knowing the staffer, and having the justification already built.
The reverse is where companies get hurt. The same table records decreases, and a line can be cut with a four-word reason and no hearing — "unjustified request," "excess to need" — with the first notice arriving when the report posts. By then the position is written, and unwriting a position is far harder than shaping one.
Appropriations advocacy is not general representation. It is four specific, nameable things, each with its own deadline.
An increase over the request for a named line, decided at markup, recorded in a table, itemized with a reason. Winning one means being in the request queue before the markup — not reacting to the mark after it posts.
Direction on how money is spent without changing how much of it there is. Report language names systems, sets second-source and reporting requirements, and decides which companies a general-purpose account actually reaches.
A program element with no prior-year appropriation cannot be started under a continuing resolution, and one that has an appropriation cannot raise its production rate. Both require explicit authority, drafted in advance, because someone asked in time.
A named exception written into a continuing resolution that lets one program do what the CR otherwise forbids. The FY2027 CR carries two on the defense side: shipbuilding cost increases and national security systems. Everything else sits at FY2026 posture.
There is exactly one FY2027 defense appropriations text in existence. H.R. 9495 was approved by the House Appropriations Committee 34–27 on June 24, 2026 and reported as H. Rept. 119-715. It has never had a floor vote. The Senate Appropriations Committee has not marked up a defense bill at all — no Senate number, no Senate table, no Senate report.
The government is running on a continuing resolution. H.R. 6500 became Public Law 119-103 on September 2, 2026 and expires December 11, 2026. Section 102(a) bars new production of items not funded in FY2026, bars increasing production rates above FY2026 levels, and bars initiating or continuing any project, budget activity, program element, or subprogram within a program element that had no FY2026 funding. Section 102(b) bars initiating a multiyear procurement.
The authorization bills are split and stationary. The House passed H.R. 8800 by 216–212 on July 22, 2026. In the Senate, cloture on the motion to proceed to S. 4784 failed 50–46 on July 14. There is no conference — and therefore no conference report to react to.
Read together, the conclusion is unusual: most of FY2027 has no adopted position, and the Senate mark is still being drafted. An unwritten document is the only kind anyone can still influence, and nobody announces the day the drafting closes.
One structural problem catches companies that have done everything else right. The administration requested $350 billion for defense through budget reconciliation. The budget resolutions carried $60 billion, and it has not moved.
A continuing resolution funds only what received a prior-year discretionary appropriation. So a program whose growth was parked in the reconciliation column is not merely delayed — it is stranded twice: no discretionary base to continue from, and no reconciliation bill arriving. If that describes your program, the work is drafting the discretionary fallback now, while there is still a Senate mark being written to put it in.
Send a short note with the account or program element that determines your revenue and the date you are working against. If there is no vehicle, we will say so.
justin@kpgpolicy.com