Backlog and Book-to-Bill Modeling

Introduction

Backlog modeling is the execution-level implementation of the backlog conversion revenue framework introduced in the previous article. While that article covered when and why to use the backlog framework, this article covers the mechanics: how to build the waterfall, what assumptions drive each line, and how to connect the backlog model to the broader financial forecast.

For industrials bankers covering A&D, long-cycle capital goods, and project-based businesses, the backlog model is not an appendix to the financial model. It is the revenue model. Getting the backlog dynamics right determines the quality of every downstream projection: revenue, margins, working capital, and ultimately valuation.

The backlog model follows a simple waterfall structure that tracks the flow of orders through the system.

Backlog Waterfall

A period-by-period model that tracks: Beginning Backlog + New Orders Received - Revenue Recognized (Backlog Consumed) - Cancellations/Modifications = Ending Backlog. The waterfall can be modeled monthly, quarterly, or annually depending on the precision required and the data available. For sell-side processes and LBO models, quarterly modeling provides the best balance of precision and manageability. For pitch books and preliminary valuations, annual modeling is sufficient.

Each line in the waterfall requires specific assumptions:

New orders received. This is the most forward-looking and most uncertain input. For defense companies, new order assumptions are derived from defense budget analysis: specific program funding, recompete timing and win probability, new program award pipeline, and international sales opportunities. For commercial aerospace suppliers, new orders track the OEM production rate trajectory and platform development schedules.

Revenue recognized (backlog consumed). This is the conversion rate, the percentage of backlog that translates to revenue in each period. The conversion rate varies by program type and contract structure. Production programs with active delivery schedules convert at higher rates (30-40% of program backlog per year). Development programs with milestone-based revenue recognition convert at lower, less predictable rates. The conversion rate should be modeled at the program level where possible, then aggregated to the total company level.

Cancellations and modifications. Backlog is not guaranteed revenue. Orders can be cancelled (more common in commercial equipment), deferred (pushed to later delivery dates), or modified (scope changes that increase or decrease the contract value). A reasonable cancellation assumption for defense backlog is 1-3% annually (government contracts have termination-for-convenience provisions but exercise them rarely). For commercial equipment, 3-8% annually is more typical.

Not all backlog dollars are equal, and the model should distinguish between different quality tiers of backlog.

Funded vs. unfunded. Funded backlog (money appropriated and obligated) converts with high certainty. Unfunded backlog (authorized but not yet funded) carries meaningful risk that future appropriations may not materialize. The model should apply different conversion rates and conversion timelines to each tier. A company reporting $10 billion in total backlog with 80% funded has more reliable near-term revenue than one with 50% funded.

Fixed-price vs. cost-plus. Fixed-price contracts in the backlog carry margin risk (the company may earn less than expected if costs overrun), while cost-plus contracts carry minimal margin risk. The backlog model should feed into the margin model with different margin assumptions for each contract type.

The backlog model feeds into multiple components of the integrated financial model.

Revenue forecast. The backlog conversion line (revenue recognized) is the primary revenue driver for long-cycle businesses. This should be reconciled against management's revenue guidance and against historical conversion rates to ensure consistency.

Working capital. Long-cycle businesses often receive progress payments from customers as milestones are achieved, creating a working capital dynamic where customer advances (a liability) offset work-in-process inventory (an asset). The timing of progress payments within the backlog should be modeled to accurately capture working capital flows.

Capex. For programs still in the development or early production phase, the company may need to invest in tooling, test equipment, and production facilities before revenue is recognized. The backlog model should inform the capex timing to ensure the model captures the front-loaded investment required for new programs.

Margin forecasting. The composition of the backlog directly affects margin projections. A backlog weighted toward mature production programs (where learning curve efficiencies have been achieved) will produce higher margins than one weighted toward early-stage development programs (where cost overruns are more likely). As the backlog mix shifts over time (new development programs entering, older production programs concluding), the margin trajectory should reflect this composition change. This is particularly important for defense companies where the mix of cost-plus versus fixed-price contracts within the backlog determines both the margin ceiling and the margin risk profile.

The backlog model should also incorporate a program maturity analysis that tracks where each major program sits in its lifecycle (development, low-rate initial production, full-rate production, sustainment). Programs in full-rate production typically generate the highest margins because manufacturing efficiencies have been optimized and development risk has been retired. Programs in early development may generate negative margins if fixed-price contracts were priced optimistically. Understanding the lifecycle stage of the top 10-15 programs in the backlog provides the foundation for a more accurate and defensible margin forecast than applying a single company-wide margin assumption.