Authorization decides what may exist. Appropriations decides what gets paid for.
Separate committees, separate bills, separate calendars — and they contradict each other more often than most companies expect. You can win the appropriation and still be blocked by the authorizers, or carry a well-drafted authorization that nobody ever funds.
This practice is about the provision itself: the text, the sponsor, the committee of jurisdiction, the cost estimate, the section number, and the conference. Every engagement starts by naming the bill and the section. If we cannot name them, there is no case, and we will say so before you retain us.
A live example, in the bills right now
The FY2027 defense bills contain a direct contradiction about the same set of programs, in the same chamber, in the same year.
- H.R. 9495, Sec. 8010(c) — the House defense appropriations bill — authorizes multiyear contracts for the Family of Affordable Mass Missiles, ground-launched low-cost cruise missile systems, and low-cost hypersonic strike systems for a period of not more than three years, and bars initiating one until the Secretary of Defense notifies the Appropriations Committees certifying completion of qualification and operational test and evaluation, at least 30 days before contract award.
- H.R. 8800, Sec. 1839 — the NDAA as passed by the House — authorizes seven program years for the same systems, with no test-completion gate at all.
Three years against seven, and a certification requirement in one bill and not the other. The appropriators gave their reasoning in H. Rept. 119-715: the request departed from historical multiyear proposals by covering families of systems rather than specific weapon systems, and by including programs entering procurement that had not yet demonstrated mature, stable production. That is a serious argument — and one that can be answered, with data, a schedule, a narrower definition, or a gate both committees can live with.
Neither number is law. The House appropriations bill was reported by the full committee 34‑27 on June 24, 2026 and never got a floor vote; the Senate has not marked up a defense appropriations bill at all. The House passed its NDAA 216‑212 on July 22, 2026; cloture on the motion to proceed to S. 4784 failed 50‑46 on July 14. All of it is still contestable.
Why this is the work
A company operating under a seven-year framework agreement, with a three-year cap sitting in the appropriations bill, has a specific problem, a specific vehicle, and a specific deadline. That is not resolved by a general-purpose Washington presence. It is resolved by someone who knows both texts, knows which staffer owns each, and is in the room when the two bills are reconciled.
Tell us what your provision needs to say.
Where provisions actually die
- No sponsor with jurisdiction. A member who likes the idea but does not sit on the committee cannot carry it. The first question is never "who agrees with us" — it is "who can offer this in markup."
- One chamber only. A provision with no counterpart in the other bill lives or dies in conference, on what the four corners are willing to trade. S. 4784 Sec. 813 — which would condition obligations on a multiyear contract for these same systems on a written certification about the contract's terms — has no House counterpart.
- A score nobody planned for. Cost estimates arrive late and kill provisions that already had the votes. If the number will be a problem, it is cheaper to know in June.
- Stale citations. The multiyear munitions section was Sec. 1826 in the chairman's mark and Sec. 1839 in the bill the House passed; citing the superseded number tells a staffer your information is out of date. The same program is "Family of Affordable Mass Munitions" in statutory text and "Family of Affordable Mass Missiles" in the budget tables — both correct in their own document.
- The calendar. Under a continuing resolution, agencies cannot start new programs or raise production rates without a specific anomaly. The current CR, P.L. 119‑103, was signed September 2, 2026 and runs to December 11. It carries anomalies for shipbuilding and for national security systems, and none for munitions. An anomaly request is discrete, short-fuse work, and the paper has to be written well before the deadline.
What the engagement looks like
- Draft the text in the form the committee expects to receive it, with definitions and effective date already resolved.
- Identify the member with jurisdiction and the staffer who owns the file, and make the ask easy to say yes to.
- Build the record — cost, schedule, district and supplier footprint, precedent, and an answer to the committee's stated objection rather than the one you wish they had raised.
- Track the provision through renumbering, markup, floor amendment, and conference, and know at every stage which version is operative.
- Work the continuing resolution and the anomaly process when the authorization exists but the money cannot legally move.
- Say plainly when a provision will not survive. A realistic read delivered early is worth more than a year of activity reports.
KPG Policy Group's principal worked for a member of the House Armed Services Committee. KPG makes no representation or guarantee as to any legislative outcome, and no fee is contingent on one.