The Program Objective Memorandum is the Pentagon's draft five-year spending plan: the funding proposal each component sends the Secretary of Defense in the programming phase of Planning, Programming, Budgeting, and Execution, or PPBE, per the Congressional Research Service. The POM adjusts programs inside the Future Years Defense Program, and Congress sees only the resulting budget documents, not the POM itself.
How does the POM fit into PPBE?
PPBE runs in phases, and each phase produces a known artifact. CRS, in its primer on the process, describes the sequence plainly: planning produces the Defense Planning Guidance; programming generates the Program Objective Memorandum, a funding plan for each DOD component covering a five-year period that adjusts programs in the FYDP; and budgeting produces the Budget Estimate Submission, which covers the first budget year in detail.
In practice the calendar looks like this, in a normal cycle:
- Planning: the Secretary of Defense issues guidance that sets priorities and fiscal constraints.
- Programming: components build the POM to fit that guidance over five future years.
- Review: OSD staff and the Comptroller examine, adjust, and decide among POM issues.
- Budgeting: the approved program becomes the BES and then the president's budget request.
- Execution: Congress appropriates, and DOD manages against the enacted levels.
The POM is where the services trade: a shipbuilding increment against a fighter squadron's readiness account, a modernization program against end strength. Those trades are visible in the FYDP that accompanies the budget request, which is the version Congress and the public can read.
Why is the FYDP only partially transparent?
The FYDP is the most detailed public map of planned defense spending, and the Government Accountability Office has long documented its limits. GAO found in a review of the Future Years Defense Program that the FYDP provides Congress with mixed visibility over DOD's projected spending for the current budget year and at least four succeeding years, and that in some areas DOD likely understates future costs because it has historically employed overly optimistic planning assumptions.
The same review noted that the FYDP does not reflect the costs of ongoing operations funded through supplemental appropriations. That gap is the historical root of the base-versus-war-budget problem: for years, contingency operations were funded outside the base budget through Overseas Contingency Operations accounts, glossed once as OCO, which let base plans look cheaper than the total enterprise. The budget lines changed; the lesson about reading projections against their assumptions did not.
What is reform doing to the POM?
The Commission on PPBE Reform, created by the fiscal 2022 National Defense Authorization Act, reported in 2024 that the process should be restructured around faster, clearer resourcing decisions, with software acquisition and budget flexibility as central cases. Its recommendations respond to the same friction GAO documented: multi-year internal planning cycles colliding with annual appropriations and technologies that change faster than budget justification books.
For readers of defense budgets, the practical takeaway is a rule of attribution. A program's appearance in a POM-derived budget line is a plan, not a purchase; the appropriated amount is the binding figure; and the out-years in the FYDP are projections whose assumptions, as GAO put it, have historically run optimistic. The CRS primer on PPBE remains the clearest public description of how the phases and documents connect.
How does Congress change the POM after the fact?
The POM is an executive planning document, but its outputs are not immune once they reach Congress. Authorization and appropriations marks add, cut, and fence program lines; report language directs reprogramming notification rules; and unspent or redirected funds move through transfer authorities that OSD must justify. The practical consequence is that the five-year plan the services build in the POM is a starting position for a negotiation, and the FYDP columns in any given budget book reflect last year's negotiation, not this year's intent.
Reprogramming is where the friction is most visible. When execution departs from the plan, because a program slips or a new requirement appears, the department shifts funds between accounts, and Congress reserves the right to object. GAO's long-running observation about optimistic planning assumptions feeds directly into this loop: plans that understate costs generate more reprogramming actions, and more reprogramming erodes the credibility of the next POM cycle's projections.
What is OCO's legacy in the current budget?
The clearest lesson of the contingency-funding era is definitional. When war costs sat outside the base budget in what were labeled Overseas Contingency Operations accounts, the base plan looked leaner than the enterprise it actually sustained, and GAO's FYDP review flagged exactly that distortion: projected resources that excluded the costs of ongoing operations funded through supplementals. Those dedicated accounts were phased out in the early 2020s, but the mechanism they exploited, funding defense through bills that bypass base-budget discipline, returned through reconciliation funding in the current cycle.
For the POM itself, the reconciliation era raises a drafting question the services live with: whether to plan against the discretionary topline alone or against the combined total. Planning to the combined number risks building programs whose base funding vanishes if a future reconciliation package does not repeat; planning to the discretionary base leaves capacity unbuilt that the combined budget would fund. The FYDP's documented optimism problem predates this dilemma, but the two-account structure gives it new room to operate.
That is why analysts now read the defense topline in pieces: a discretionary request subject to the regular appropriations process, and reconciliation funding enacted outside it. The POM still builds the five-year plan inside one accounting world, while the money increasingly arrives through two. Any reader comparing a service's program plan to enacted totals has to reconcile those worlds first, or the comparison is meaningless.
