Backlog is the bridge between historical performance and management's forecast — but only the funded portion carries the certainty a buyer will actually underwrite.

Backlog is the value of contracted work a company has been awarded but has not yet performed. It is a point-in-time measurement of future revenue that already sits under contract, and it should be separated from the two things it is most often confused with.

• Pipeline is unawarded opportunity — bids submitted, proposals outstanding, prospects identified. It is not backlog.
• Revenue is work performed. Backlog converts to revenue only as work is performed.

There is no GAAP definition of backlog, though public filers disclose remaining performance obligations under ASC 606. Private companies define backlog by internal convention. That flexibility is precisely why buyers test a company's definition alongside its reported number.

The most important distinction inside backlog is whether the customer has committed money to the contract.

Funded backlog is the portion of awarded work for which the customer has obligated funding — a released purchase order, an executed task order, or, in federal contracting, an appropriated or obligated increment. The contract exists, the money exists, and the only remaining variables are execution and timing.

Unfunded backlog is awarded work not yet funded. This includes unexercised option years, future incrementally funded contracts, and remaining ceiling value on an IDIQ vehicle or master service agreement. The customer relationship is real, but conversion depends on future appropriations, option exercises, or additional task orders the company may still have to compete for.

For example, a contractor holding a five-year, $80 million IDIQ ceiling against a $6 million funded task order has both, and the two carry very different levels of certainty. Commercial businesses face the same structure under different labels: executed contracts with released POs on one side; MSAs, letters of intent, and verbal commitments on the other.

Backlog is the bridge between historical financial performance and management's forecast. A buyer underwriting next year's EBITDA wants to know how much of that forecast is already contracted, how much of the contracted portion is funded, and how much depends on wins that have not happened yet.

In practice, diligence reviews several components that comprise backlog:

• Coverage. What share of the next twelve months of forecast revenue is supported by funded backlog? Strong coverage reduces perceived risk; thin coverage can lead to earnouts or discounted projections.
• Burn and timing. How quickly has backlog historically converted into recognized revenue?
• Attrition. What work has historically decreased through cancellations, de-scopes, funding lapses, and modifications? A documented record of low attrition is an asset; an undocumented one can be a liability.
• Concentration and recompete exposure. How much backlog sits with a small number of customers or contract vehicles, and when do those come up for renewal or recompete?

In a Quality of Earnings analysis, answering these questions helps support a company's short- and long-term forecast.

Backlog should be tracked on a regular monthly or quarterly basis. Prospective buyers frequently ask for internal backlog reports spanning two to three years, and a reporting record that begins the month a process starts carries far less weight than one that predates it.

Funded backlog should also drive staffing plans, capacity decisions, working capital, and cash-flow forecasting. Tracked at the contract level, it reveals funding lapses and expiring periods of performance early enough to act on.