If you walked through the average general contractor's risk register, the largest single line item is rarely on the spreadsheet. It's the assumption baked into every project schedule that the subcontractors signed up for the work will actually finish it. When that assumption breaks, the cost is not subtle. According to Marsh's analysis of subcontractor default trends , a single default typically costs the GC 1.5 to 3 times the subcontract value once you account for completion, redesign, schedule slip, and dispute exposure. On a $4 million electrical sub, that's six to twelve million dollars of margin and schedule absorbed by a process most firms still treat as paperwork.
Prequalification is the workflow that is supposed to keep that risk at the door. It is also the workflow most GCs run worst.
Why default risk stopped being a tail event For most of the last decade, default rates were something the surety market priced in and large GCs largely ignored at the operational level. That has changed. The Liberty Company's 2026 review of subcontractor risk describes carriers tightening loss-control expectations specifically because a disproportionate share of high-severity construction claims now traces back to subcontractor selection, weak documentation, or unclear contract terms. FMI's analysis of default risk attributes the shift to material price volatility, persistent skilled-trade shortages, and cash-flow stress that have pushed traditionally stable trades — electrical especially — into much riskier territory year over year.
The AGC/FMI Risk Management Survey tells the same story from the GC seat: subcontractor default and skilled-craft shortages sit at the top of the risk list, and the firms reporting the strongest project outcomes were also the ones running the most structured prequalification programs. The conclusion is uncomfortable but simple. The cost of a bad subcontractor is rising, and the GCs that catch it before signing are quietly pulling away from the GCs that catch it during construction.
What prequalification should actually verify Most prequalification programs underperform because they were designed to produce a binder, not a decision. A useful program is built around five categories of evidence, scored continuously and tied to thresholds that drive action.
Financial health: trailing-three-year financials, working capital ratio, current backlog as a multiple of bonding capacity, and DSO trend. The signal you want is not "can they do the work" — it is "can they survive a 60-day payment delay on this project."
Insurance and surety: general liability, auto, workers' comp, umbrella, and EMR — pulled from primary documents, not self-attested PDFs. Carrier financial strength rated. Surety capacity confirmed against the contract size.
Safety: TRIR and DART trends over three years, OSHA inspection history, and a documented site-specific safety plan, not generic boilerplate.
Compliance: licenses by jurisdiction, MWBE/DBE status where relevant, sanctions and debarment lists, and a current authorized-signer list.
Operational capacity: current commitments, named PMs and superintendents, references on comparable scope, and a candid view of how much crew is already deployed elsewhere.
None of that is new. Every risk team can recite it. The reason it doesn't work is that it lives in a static questionnaire, gets refreshed once a year, and the people who actually need the answer — the project executive picking subs for next quarter's bid — are reading a snapshot that's already eight months stale.
Where the workflow breaks down Three failure modes show up in almost every default post-mortem.
The annual-snapshot trap. Most programs assess subs at intake and refresh annually. Defaults rarely cooperate with that calendar. By the time a sub's working capital ratio crosses into trouble, the GC has already awarded them three new contracts.
The unflagged expiration. Certificates of insurance, EMR letters, and license renewals all expire on different cycles. When nothing watches the calendar at the document level, expirations drift past renewal dates and the GC is exposed without knowing it.
The unanswered exception. A sub submits financials with a current ratio below threshold. The risk team flags it. Then nothing — because there is no defined exception path, no SLA on the review, and no record of who made the override decision or why.
Each of these is a workflow problem disguised as a documentation problem. Software built around static forms will not fix them. Software built around process will.
The automation workflow that actually works A prequalification program runs cleanly when it is structured as a continuous process with clear handoffs. Symphona Flow carries the spine of that process — the intake form, the document parsing, the scoring against thresholds, the API calls into carrier, license, and sanctions databases, and the routing to the right risk approver based on contract size and trade. Where a value falls in the green zone, the workflow advances on its own. Where a value drifts into yellow or red, the workflow opens a structured task in Symphona Serve for the risk analyst, with the relevant document, the threshold breach, and the review SLA already attached. The reviewer makes a decision instead of starting a research project.
Exception handling is where most programs leak risk, and it is what Symphona Resolve is designed to catch. An expiring COI does not sit in a shared inbox hoping someone notices — it becomes a tracked issue with an owner, an SLA, and an automated escalation path if the renewal slips. A sub whose EMR drifts above threshold mid-project triggers a review before the next contract is signed, not after the next incident. The audit trail becomes a byproduct of the workflow rather than a separate exercise.
What "good" looks like GCs that treat prequalification as a continuous workflow, rather than an annual binder, see two changes within the first year. The risk team spends less time chasing documents and more time interpreting them. And the project executives stop being surprised — the sub list they are working from already reflects current insurance, current EMR, current backlog, and current financial signal, because the workflow keeps the data alive between formal renewals.
If you're a GC tightening risk management ahead of the next project cycle and want to see what continuous prequalification looks like running end to end — financial intake, insurance verification, exception handling, and renewal tracking in one workflow — explore how Symphona works for construction or book a consultation . We can walk through your current process with the documents you already collect and identify where the manual steps are quietly creating exposure.
.svg)
.svg)
.avif)
.avif)
.avif)
.avif)
.svg){kind=icon}
.svg){kind=icon}
.svg)
.svg)
.svg)
.svg)
.svg)
