Managing Subcontractor Defaults: Early Warning Signs and Response Playbook

A subcontractor default happens when a sub fails to perform its contractual obligations in a way that requires intervention — walks off the job, can't complete the work, files bankruptcy, or stops showing up. Defaults are relatively rare on any individual project but common enough across a portfolio that every GC eventually faces one. The cost of the default depends almost entirely on how early the GC recognizes it and how quickly they respond.

The typical default cost is meaningful. Direct costs: completion contractor premium, remobilization, schedule impact, rework of defective sub's work. Indirect costs: GC team time managing the transition, strain on other subs, relationship damage with the owner. For a significant scope, the total impact of a mid-project default is often 20-50% of the original sub's contract value. Early recognition and good response cut this dramatically; delayed response lets it compound.

The Early Warning Signs

Most sub defaults are preceded by warning signs the GC could have seen weeks or months in advance. The signs fall into three categories.

Financial Signs

Operational Signs

Administrative Signs

The Response Playbook

Once the GC recognizes a default is likely or occurring, a structured response prevents improvisation. The sequence:

Stage 1: Preliminary Response

Contact the sub's leadership directly to understand what's happening. Sometimes the signals point to a solvable problem (cash flow gap awaiting owner payment, temporary supply issue). Sometimes they point to a genuine default trajectory. Either way, direct communication is faster than inference.

Document the conversation in writing with a formal letter following up. The documentation becomes essential if the situation escalates — later claims against the surety or in litigation rely on the contemporaneous record.

Stage 2: Notice of Intent

If the sub's response doesn't resolve the concern, the GC issues a formal notice of intent to declare default. This is a letter stating the specific performance failures, the cure period (typically 10-15 days), and the consequences if cure doesn't happen. The notice is required by most subcontracts before formal default can be declared.

The cure period is critical. It gives the sub a structured chance to fix the problem, and it's the period during which the GC gathers information and prepares for the alternative. If the sub cures — brings the crew back up, catches up on payments to suppliers, returns to schedule — the process pauses. If they don't, formal default is the next step.

Stage 3: Formal Default Declaration

Formal default is declared in writing per the subcontract's termination provisions. This is a legal step with significant consequences: the sub's right to continue performing ends, the GC can take over the work or replace the sub, and any performance bond can be called.

If the sub is bonded, the surety is notified simultaneously with the default declaration. The surety then has options — complete the work themselves, find a replacement contractor, pay the GC to complete, or dispute the default. The surety's response time is usually a few weeks during which the GC is often carrying project costs without surety support.

Stage 4: Taking Over or Replacing

If no surety or if the surety's response is delayed, the GC takes over directly. Options include self-performing the remaining scope with GC personnel, hiring a replacement sub at cost-plus pricing (expensive but fast), or mobilizing a different sub on the GC's existing roster.

Documentation continues throughout this phase. Every cost incurred in the transition — mobilization premium, replacement contractor pricing, overtime to maintain schedule, equipment rentals, supervision — becomes part of the claim against the defaulting sub's bond or remaining contract balance.

Financial Recovery

After the project is completed, the GC's financial recovery path runs through the sub's contract balance and any performance bond.

Preventive Measures

Default risk can be reduced meaningfully at the front end of the sub relationship.

The Relationship Dimension

Managing a sub default well protects the GC's reputation with other subs. Subs watch how GCs handle other subs' failures. A GC who handles a default fairly — honest communication, reasonable cure period, proper documentation — maintains the trust that keeps other subs engaged. A GC who handles a default poorly — surprise termination, public disputes, refusal to pay legitimate earned amounts — damages its reputation with the whole sub base.

Bottom Line

Subcontractor defaults are rare individually and inevitable across a portfolio. The companies that manage them well watch for early warning signs, respond structured rather than improvised, document everything throughout, and use preventive measures at sub selection and during contract administration. The cost differential between well-managed and badly-managed default response is large — often the difference between a minor project disruption and a multi-hundred-thousand-dollar loss plus a schedule slip.