Bonding capacity gets treated like a formality until the day a tender requires it and the file isn't ready. What actually goes into a bonding application, and what the three standard bond types are guaranteeing.
Key takeaways
The standard package on a public or larger private tender is three related but distinct instruments. A bid bond is issued “guaranteeing the bidder's intention to enter into a formal contract and to provide the specified contract security if the bid is accepted.” A performance bond, by contrast, is issued “guaranteeing performance of the contract by the Contractor.” And separately again, a labour and material payment bond guarantees “that the Contractor will satisfy all labour and material payment obligations incurred in performing the contract.”
Three different risks, three different triggers — a bid withdrawn improperly, a contract not completed to standard, or a sub or supplier left unpaid — even though a contractor applying for bonding capacity is usually approved for all three types together as a single facility.
A surety isn't a lender in the ordinary sense. It isn't advancing cash the contractor repays with interest — it's guaranteeing a third party (the project owner) that the contractor will perform, on the strength of the contractor's own financial position and track record, and it expects to be repaid in full if it ever has to step in and pay a claim.
That framing is worth keeping in mind because it changes what the surety is actually evaluating: not just whether the contractor can service debt, but whether the contractor can complete the specific size and type of project being bonded without the surety's money ever actually being called on. It is, in effect, underwriting the probability of a claim — a different question from a bank's credit decision, even though much of the same paperwork answers both.
The overlap with a bank credit application is real: financial statements demonstrating financial health and repayment capacity, cash flow forecasts covering the current and following year, and a clear picture of work currently in progress and its status A surety is reading the same numbers a bank reads, just asking a different question of them.
Track record matters more here than on an ordinary credit application — completed projects of comparable size and type, references, and a history free of claims are what a surety weighs alongside the numbers. A contractor moving up to a materially larger project than anything previously completed should expect that jump to be the specific thing underwriting focuses on, regardless of how strong the balance sheet looks.
One structural option worth knowing about, particularly for a contractor whose bonding needs are outpacing available collateral: Export Development Canada's Account Performance Security Guarantee gives a contractor's lender a 100% guarantee on the bonds and letters of guarantee it issues, covering “bid bonds, acquisition bonds, advanced payment guarantees, performance bonds, warranty bonds, lease bonds, supplier guarantees, regulatory guarantees.”
The practical effect: “your lender gets a 100% guarantee on any bonds … so they don't need to hold your collateral, so your cash is free for other uses.” freeing up cash or credit room that would otherwise sit tied up as collateral against the bonding facility itself — worth raising with a lender or broker for a contractor whose growth is being capped by collateral rather than by underwriting.
The single most common reason a bonding application slows down a bid is that the financial picture a surety needs wasn't already assembled — current statements, an accurate WIP schedule, and a clean explanation of anything unusual in the numbers all take time to pull together if they aren't already maintained monthly.
This is the same file that clears a bank covenant test and that a lender reviews for an operating line: keep it current once, and a tender's bonding deadline stops being a scramble. The reasoning below is drawn from what CCDC's bond descriptions and EDC's own guarantee product structure indicate about what these instruments protect against, not from a named source that publishes surety underwriting criteria directly — treat it as informed inference on how these files are typically assessed, and confirm specifics with a bonding broker before a real submission.
A worked example
A contractor with a $2M single-job bonding limit is invited to bid a $3.5M contract. Before applying to increase the limit, the surety asks for current year-to-date financial statements, the WIP schedule for all open jobs, and a reference list for the three largest projects completed in the past two years.
The WIP schedule shows two open jobs tracking within 2 percentage points of their budgeted percent-complete, with no material overbilling or underbilling — exactly the kind of clean, current file that supports a limit increase request, versus one assembled after the tender deadline is already looming, when there's no time left to explain or correct anything the numbers raise.
It's a major factor but not the only one — track record on comparably sized and typed projects, and a clean claims history, carry real weight independent of the balance sheet. A strong balance sheet with no experience at the requested project size is a harder case than a slightly thinner balance sheet with a proven history at that scale.
They overlap heavily on the financial-statement side but aren't the same review. A bank's covenant structure is about ongoing debt service A surety is pricing the probability it never has to pay a claim; a bank is pricing the probability of being repaid — related questions, not identical ones.
It happens, particularly for a contractor whose volume is outgrowing a single surety's comfort level, but it adds complexity — each surety wants its own current financial picture, and splitting a track record across two relationships can make each individual file look thinner than the whole. Most contractors consolidate with one surety relationship as long as capacity allows.
Financial statements that are stale by the time they're submitted, or a WIP schedule that doesn't reconcile to the financial statements it's supposed to support. Both are avoidable with the same monthly discipline that keeps a covenant test or a bank renewal from being a scramble either.
A 30-minute call is enough to tell you whether AI pays for itself here.
