Remaining performance obligations, usually shortened to RPO, are the portion of a company's signed contracts for which it has promised to deliver goods or services but has not yet recognized revenue, because the delivery has not happened. For a space company that builds satellites, flies launches or delivers lunar payloads, RPO is the clearest filing-level measure of revenue that is already under contract and waiting to be earned. The number lives in the audited financial statements and the management discussion, and it is governed by the same revenue-recognition rules that determine when a company may book a sale at all.

The cleanest way to see the definition is in a real filing. 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, split between $299.8 million in its Space segment and $111.4 million in its Defense Tech segment. In the same passage, the company tells investors exactly what that backlog is and ties it directly to the accounting term.

"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

Three words in that sentence do most of the work: "firm," "funded" and "executed." Executed means the contract is signed. Funded means money has actually been appropriated or committed to it, not merely authorized as a ceiling. Firm means it is not contingent on an option the customer has yet to exercise. Read together, those qualifiers narrow the RPO figure to commitments that are real today, which is precisely why RPO tends to be smaller and more conservative than the headline "deal value" numbers that appear in award announcements.

Why RPO is not the same as a press-release backlog

When a company or an agency announces a contract "worth up to" some large figure, that number frequently includes option years, ceiling amounts on indefinite-delivery vehicles, or work that depends on future funding decisions. RPO strips most of that away. Under the revenue-recognition framework the SEC requires public companies to apply, the transaction price allocated to remaining performance obligations counts only the consideration tied to enforceable, presently committed promises. A multi-year ceiling of a billion dollars can correspond to a far smaller RPO if only a fraction has been funded and placed on contract. That gap is the entire reason RPO exists as a separate, audited disclosure: it gives investors a measure of forward revenue that does not move just because a press release used a bigger number.

RPO also carries timing information. Companies typically disclose how much of the balance they expect to recognize within twelve months versus later, which lets a reader separate near-term revenue from long-dated commitments. For a satellite builder working multi-year programs, a large RPO with most of the recognition pushed out several years describes a very different cash and revenue trajectory than the same RPO front-loaded into the coming year. The figure is a snapshot at a balance-sheet date, and it changes every quarter as new contracts are signed, as funded work is performed and moves into recognized revenue, and as contracts are modified or canceled.

What RPO does not tell you

RPO is a disclosed accounting figure, not a guarantee and not a forecast. It does not include revenue the company hopes to win, the unfunded or option portions of existing awards, or pipeline that has not been placed on contract. It also does not promise that every dollar will convert: contracts can be terminated, descoped or delayed, and the same companies that report RPO routinely warn, in their risk factors, that they may not convert orders in backlog into revenue. Redwire's own filing lists, among its risk factors, that it "may not be able to convert our orders in backlog into revenue." That caution is standard across the sector and is the reason RPO should be read as contracted potential, not booked results.

It is worth being explicit about where RPO sits in the accounting framework, because the term is not marketing language a company invents. It comes from the revenue-recognition standard the SEC requires public companies to follow, which directs them to disclose the transaction price allocated to performance obligations that are unsatisfied, or partially unsatisfied, at the end of a reporting period. That is a deliberately narrow construct. It captures only the consideration tied to enforceable promises in existing contracts, and it excludes constraints the standard imposes, such as wholly unexercised options and amounts that are not yet probable of collection. When a space company labels a backlog figure as its remaining performance obligations, as Redwire does, it is signaling that the number has been built under that disciplined definition rather than assembled from announcements. The same standard is why two companies' "backlog" figures can mean different things unless each is reconciled to RPO: a company that reports a broad backlog including unfunded option scope is describing something larger and looser than the audited RPO that ties to its financial statements.

For an analyst covering space and defense names, RPO is most useful as a trend and as a ratio. Tracked quarter over quarter, a rising RPO indicates that new contracted work is outpacing the work being delivered and recognized; a falling RPO indicates the reverse, that the company is recognizing revenue faster than it is signing new funded commitments. Compared against trailing revenue, RPO gives a rough sense of how many quarters of already-contracted work sit on the books. Neither reading replaces the income statement, but both are grounded in a number the company has put in front of the SEC and its auditors, which is more than can be said for most of the figures that travel through award announcements. When the filing defines its own backlog as the remaining performance obligations on a contract, it is telling investors exactly where the receipts begin and where the wishful arithmetic ends.