Construction Backlog Reporting: The Metric Surety and Lenders Watch
Revenue tells you what a contractor did last year. Profit tells you how well it did it. Neither tells you whether the company will still be standing eighteen months from now. For that, sureties and lenders look at backlog — the value of signed, awarded work that has not yet been performed. Backlog is the construction industry's clearest forward-looking solvency indicator, and a contractor that does not report it cleanly is leaving its most important credibility metric to interpretation.
The logic is simple. A contractor's overhead is a moving train — salaried staff, equipment, insurance, facilities — and it has to be fed by gross profit from active work. Backlog is the fuel already in the tank. A healthy backlog means the company has enough committed work to cover overhead and generate margin well into the future. A thin or shrinking backlog means the company will soon be running its overhead against work it has not yet won, which is the position from which contractors get into trouble. That is why backlog appears near the top of every surety underwriting file and every construction bank's credit memo.
But backlog is also one of the easiest numbers to report carelessly, and a carelessly reported backlog actively misleads the people relying on it. Counting work that is not really committed, ignoring whether the backlog carries any profit, or letting stale jobs inflate the figure all produce a number that looks reassuring and means very little. Reporting backlog well — and understanding what a sophisticated reader does with it — is a core construction-finance discipline.
0 months
Average construction backlog reported by contractors industry-wide in a recent reading — the typical amount of committed work measured in months of activity (Associated Builders and Contractors Construction Backlog Indicator)
At its core, backlog is the unearned portion of the contracts a company holds. For any single project, backlog is the total contract value — the original contract plus approved change orders — minus the revenue earned to date on that project. Sum that across every active and awarded project and you have the company's total backlog as of a point in time.
Two of the inputs deserve care. The first is what gets counted as a contract: backlog should reflect signed contracts and formal, executed awards — work the contractor and owner are both legally committed to. The second is revenue earned to date, which on most commercial work is measured by the percentage-of-completion method, typically cost-to-cost: the share of total estimated cost incurred so far. Get either input wrong and the backlog figure drifts away from reality.
A raw backlog dollar figure is hard to interpret on its own — $40 million of backlog means something very different for a $20 million contractor than for a $200 million one. To make it comparable, readers convert backlog into a ratio or a duration. The most common framing is the backlog-to-revenue ratio: total backlog divided by trailing annual revenue. A ratio of 1.0 means the company is carrying roughly a year of work. The same idea expressed in time — backlog divided by average monthly revenue — gives backlog in months, which is how the industry's backlog indicators are usually published.
How readers interpret the backlog-to-revenue ratio
- Well below 1.0 — the company has less than a year of committed work; overhead coverage is at risk and the contractor is dependent on near-term wins
- Around 1.0 to 1.5 — generally a comfortable range; enough committed work to plan, hire, and cover overhead without being overextended
- Well above 1.5 to 2.0 — a large book of work, which can signal strength but also raises questions about whether the contractor has the capacity and capital to execute it all
- A falling ratio over consecutive periods — often more telling than the absolute number; a clear downward trend is a warning sign regardless of the current level
There is no single correct ratio. It varies by sector, by project duration, and by how a contractor sequences its work. What a surety or lender watches for is the trend and the story behind it — a stable or rising ratio backed by quality work reads very differently from a high ratio padded with thin-margin or speculative jobs.
Backlog is a balance, and like any balance it moves with two flows. New work signed during a period is booked into backlog; work performed during the period is burned out of it. The relationship between these two flows is what makes the backlog figure dynamic.
If a contractor books more new work than it burns, backlog grows. If it burns faster than it books, backlog shrinks — the company is consuming its committed work faster than it is replacing it. A single period of net burn is not alarming; project timing is lumpy. But a sustained pattern of burning more than booking is one of the clearest early signals that a contractor's pipeline is weakening, and it shows up in backlog long before it shows up in a revenue decline. Reporting both the booking and the burn — not just the ending balance — gives a reader the trajectory, not just the snapshot.
A surety underwriter is, in effect, guaranteeing that a contractor will complete its bonded work. A construction lender is betting that the borrower will generate enough cash to service its debt. Both are making a forward bet, and both need a forward metric. Financial statements are inherently historical — they describe a period that has already closed. Backlog is the bridge to the future: it tells the underwriter how much work is already committed to keep the contractor's overhead covered and its crews productive in the months ahead.
This is why a contractor with strong historical financials but a collapsing backlog can still trigger underwriter concern. The historicals say the company executed well; the backlog says the work is running out. Conversely, a contractor coming off a weak year but holding a solid, well-margined backlog presents a recovery story an underwriter can support. Backlog reframes the entire credit conversation from what happened to what is coming.
A sophisticated reader never stops at the size of the backlog. The next question is always quality — because $50 million of backlog at healthy margins with a diversified customer base is a fundamentally different asset than $50 million of thin-margin work concentrated with one owner. Quality of backlog is assessed across several dimensions.
What 'quality of backlog' actually measures
- Gross margin in backlog — the estimated profit embedded in the unearned work; a large backlog at compressed margins generates revenue but little contribution to overhead and profit
- Customer concentration — backlog heavily weighted to a single owner or developer carries the risk that one cancellation, dispute, or slow-paying client damages the whole book
- Geographic concentration — work clustered in one market exposes the backlog to a regional downturn or a single permitting environment
- Contract-type mix — fixed-price (lump-sum) work puts cost overrun risk on the contractor, while cost-plus or guaranteed-maximum-price work shares more of that risk; a backlog dominated by fixed-price work in a volatile cost environment carries more execution risk
- Project duration and timing — backlog stacked with long-duration projects that have not yet started behaves differently from backlog in active, mid-stream work
- Owner and funding strength — committed work for a well-capitalized, reliably-paying owner is worth more than the same dollar amount for an owner whose project financing is uncertain
When you present backlog to a surety or bank, present its quality alongside its size — margin profile, customer mix, fixed-price vs. cost-plus split, and key project owners. A reader who has to ask those questions assumes the answers are unflattering. Volunteering them signals a contractor who understands its own book.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
How Backlog Feeds Bonding Capacity
Bonding capacity — the total and single-project bonding a surety will extend — is not set by backlog alone, but backlog is a central input. Sureties evaluate the classic capital, capacity, and character framework, and backlog informs the capacity question directly: can this contractor take on another bonded project without overextending the organization it already has committed?
The interaction runs both ways. A healthy, well-margined backlog supports a surety's confidence and can underpin an increase in a contractor's program. But a backlog that is already large relative to the contractor's working capital and equity can constrain capacity — the surety sees a company that has bitten off close to what its balance sheet can chew, and is reluctant to add more until some of that backlog burns down into completed, profitable work. Contractors managing toward a bonding increase have to manage backlog deliberately: not just winning work, but winning the right work at the right margins, and not letting the book outrun the capital behind it.
Most backlog misreporting is not deliberate. It comes from treating backlog as a sales figure rather than a financial one. A handful of mistakes recur often enough to be worth naming.
The most common error is including work that is not actually committed — a letter of intent, a verbal award, a project the contractor expects to win but has not signed. This is pipeline, not backlog. A letter of intent can evaporate; a signed contract cannot, short of a formal change. Backlog should reflect only executed contracts and formal awards. Mixing in probable-but-unsigned work inflates the figure and, when an underwriter discovers it, undermines the credibility of every number the contractor reports.
Reporting backlog as a single revenue number, with no view of the profit inside it, hides the most important thing about it. A contractor can grow its backlog dollar figure while quietly accepting worse and worse margins to win work — and the headline number will look better even as the company's financial health deteriorates. Backlog reporting that does not surface embedded gross margin tells half the story, and it is the less important half.
Backlog should reflect work that is genuinely going to be performed. Projects that have been indefinitely delayed, are caught in a dispute, or have effectively stalled should not continue to sit in backlog at full value as if they were about to start. Stale backlog inflates the figure with work that may never burn, and it distorts the booked-versus-burned trend. Backlog needs periodic scrubbing so that what is reported is live, committed, and executable.
Change orders move backlog, and how they are handled matters. Approved change orders increase contract value and belong in backlog. Unapproved or unpriced change order work is more uncertain and should be treated more conservatively. A contractor that counts optimistic, unapproved change order value as firm backlog is, again, mixing pipeline into a figure that is supposed to mean committed work.
Backlog is the construction industry's forward-looking solvency metric, and it is the number a surety underwriter or bank credit officer reaches for first — because revenue and profit describe a year that is already over, while backlog describes the work that will carry the company through the next one. Reported well, backlog tells a clear story: how much committed work the contractor holds, what margin lives inside it, how concentrated and how risky that work is, and whether the book is growing or burning down faster than it is being replaced. Reported carelessly — padded with unsigned letters of intent, presented without margin quality, inflated by stale projects — it actively misleads the people whose confidence the contractor most needs. The discipline is straightforward: count only committed work, report margin alongside dollars, scrub stale jobs, and tell the booked-versus-burned trend honestly. A contractor that reports backlog with that rigor gives its surety and its bank exactly what they came to see — and earns the credibility that backlog, done right, is supposed to convey.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts