Backlog is one of the most quoted figures in space and defense, and it is also one of the most misread, because the single word hides two very different things. Funded backlog is the part of a company's signed work for which money has already been appropriated and obligated by the customer, so the company can perform it and bill for it now. Unfunded backlog is contracted scope the company reasonably expects to perform, but for which the customer, often a government agency, has not yet released the money. Both are real contractual relationships. Only one is presently billable, and the gap between them is where near-term revenue estimates go wrong.

The distinction is not a matter of opinion; it is disclosed in the filings. In its annual report on Form 10-K for the year ended December 31, 2025, filed with the U.S. Securities and Exchange Commission, Redwire Corporation reports a total contracted backlog of $411.2 million and pins down what that number contains.

"Contracted backlog represents the estimated dollar value of firm funded executed contracts for which work has not been performed (also known as the remaining performance obligations on a contract)."— Redwire Corporation, Form 10-K (FY2025), source

The word "funded" in that sentence is doing deliberate work. By restricting its reported backlog to firm, funded, executed contracts, Redwire is telling investors it is excluding scope that is contracted but not yet financed. Companies with heavy exposure to multi-year government programs frequently disclose a larger total backlog that includes unfunded portions, then separately break out the funded slice. When they do, the funded number is the one that maps to revenue the company can recognize in the near term, because it is the only part the customer has actually paid to put in motion.

Where the unfunded portion comes from

Unfunded backlog is common in defense and civil-space work because government contracts are routinely structured with a base period plus option years, or as ceilings under which task orders are issued over time. The full ceiling, or the full set of option years, may be contracted scope, but the money is appropriated incrementally, often year by year, subject to budget cycles and the customer's decision to exercise each option. Until an option is exercised and funded, the associated revenue sits in unfunded backlog. That is why a company can hold a large contracted relationship while only a fraction of it is funded backlog at any given balance-sheet date.

This structure also explains why funded backlog can be volatile in ways unrelated to a company's performance. A government shutdown, a delayed appropriation, or a decision not to exercise an option can leave contracted scope stranded in the unfunded column. The same Redwire filing warns, in its risk factors, that failure of the U.S. government to approve budgets or other disruptions to federal operations "could result in contract terminations, delays in contract awards, reduction in contract scope, the failure to exercise contract options, the cancellation of planned procurements and fewer new business opportunities." Each of those outcomes acts directly on the boundary between funded and unfunded backlog.

How to read the two numbers

For an analyst, the practical rule is to never treat a total backlog headline as committed near-term revenue without checking how much is funded. A company reporting, say, a large total backlog with only a modest funded portion is describing a long-dated relationship whose near-term billable work is much smaller than the headline implies. Tracking the funded figure quarter over quarter is the more reliable read on momentum, because it moves only when money is actually committed and work is actually performed. The ratio of funded to total backlog is itself a signal: a rising share suggests the customer is releasing money against contracted scope, while a falling share suggests scope is accumulating faster than it is being financed.

It also helps to connect funded backlog to the accounting figure it most resembles. When a company equates its funded, contracted backlog with remaining performance obligations, as Redwire does in the passage above, it is tying the operational backlog number to the audited revenue-recognition disclosure in its financial statements. That linkage is useful because it anchors the funded figure to something an auditor has reviewed, rather than to a management estimate of total opportunity. Unfunded backlog, by contrast, generally does not appear in the remaining-performance-obligations line at all, precisely because the consideration attached to unexercised options and unfunded scope is excluded from that disclosure under the revenue-recognition standard. So the funded-versus-unfunded split is not merely a presentational choice; it tracks a real line in the accounting between commitments that meet the recognition standard's threshold and scope that does not yet. A reader who internalizes that mapping can move between the operational backlog discussion in management's analysis and the revenue-recognition note in the financial statements without losing the thread.

None of this makes unfunded backlog meaningless. It represents contracted scope the company has a reasonable basis to expect, and over a program's life much of it typically converts to funded backlog and then to recognized revenue. But the conversion is not automatic, the timing is controlled by the customer's budget rather than the company's pace of work, and the company itself flags the risk that orders in backlog may not convert to revenue. The disciplined reading keeps the two numbers separate: funded backlog answers "how much can they bill now," while total backlog answers "how big is the relationship." When a filing reports backlog as firm and funded, it is drawing exactly that line, and the careful reader keeps it drawn.