COMPLY WITH THE CONDITIONS OF THE PERFORMANCE BOND

If you are bargaining for a contracting party to obtain a performance bond, it is imperative that you honor the conditions precedent to the bond in the event you need to trigger the bond’s obligations.  If you do not, then you will breach the terms of the performance bond and lose the benefit of the bond.  This is definitely NOT what you want because if you are looking to the performance bond than you are dealing with the default of its bond-principal and an incurred or anticipated loss.   This is particularly true if dealing with an AIA performance bond form where the surety can rely on good case law that failing to comply with the conditions of the bond discharges the obligations under the bond.

To exemplify, in a recent opinion out of the District of Columbia Circuit, Western Surety Co. v. U.S. Engineering Construction, LLC, 2020 WL 1684040, (D.C. Cir. 2020), a performance bond surety filed a lawsuit seeking declaratory relief that it had no liability under the bond because the obligee failed to comply with a condition precedent to trigger the bond’s obligations.

In this case, a subcontractor hired a sheet metal subcontractor.  The sheet metal subcontractor  (principal of bond) obtained an AIA A312 performance bond for the subcontractor (obligee of bond).  During construction, the prime contractor notified its subcontractor that it was causing delays. The delays were caused by the sheet metal subcontractor.  The subcontractor, in turn, notified its sheet metal subcontractor that it had 72 hours to cure.  The sheet metal subcontractor did not cure and the subcontractor formally terminated its sheet metal subcontractor.  Prior to the termination, the subcontractor did NOT notify the surety that it was considering declaring the sheet metal subcontractor in default and terminating the subcontract. In fact, the surety was not notified of the default termination until the subcontractor sent a claim under the bond to the surety many months after the sheet metal subcontractor was terminated.

Notably, section 3.1 of the AIA performance bond required the obligee (subcontractor) to notify the principal  (sheet metal subcontractor) and surety that it was considering declaring the principal in default.  Section 4 excused the failure to do this except if the surety demonstrated actual prejudice by the lack of notice.   Section 3.2, however, required the obligee, if ending the relationship with the principal, to declare the principal in default, terminate the contract, and notify the surety.  Section 3.3 provided that the obligee must agree to provide the balance of the contract price to the surety or to a contractor selected to perform the contract. Section 5 provided that when the obligee satisfies the conditions of section 3, the surety shall promptly and at its expense take one of the actions in sections 5.1 through 5.4.

The subcontractor-obligee failed to comply with any of the obligations in the bond, which resulted in a harsh outcome to the subcontractor:

The A312 bond at issue in this case states that, in order to trigger Western Surety’s [surety] obligations under the bond, U.S. Engineering [subcontractor-obligee] must declare a United Sheet Metal [sheet metal subcontractor-principal] default, terminate the subcontract, and notify Western Surety. Similar to the A311 [AIA performance] bond, the A312 [performance] bond provides four alternative methods by which the surety can respond to the default [per Section 5 of the bond]. By unilaterally completing United Sheet Metal’s remaining contract obligations before notifying Western Surety [per Section 3.2 of the performance bond], U.S. Engineering deprived Western Surety of its contractually agreed-upon opportunity to participate in remedying United Sheet Metal’s default [per Section 5 of the bond].

In other words, despite the bond’s lack of an explicit timely notice requirement [as to when the surety must be notified of the default and termination], the performance bond is properly read as requiring U.S. Engineering to notify Western Surety of the default before engaging in self-help remedies. Otherwise, “the explicit grant to the surety of a right to remedy the default itself would be operative only if the obligee chose to give it notice,” thereby rendering the options in section 5 “nearly meaningless.” Accordingly, because the bond expressly provides the surety with the opportunity to participate incurring the subcontractor’s default, we hold that it is a condition precedent to the surety’s obligations under the bond that the owner must provide timely notice to the surety of any default and termination before it elects to remedy that default on its own terms. In light of U.S. Engineering’s failure to provide such timely notice, Western Surety was not obligated to perform under the bond.

Western Surety Co., 2020 WL at *4.

The morale is that if you are bargaining for a performance bond, do not neglect to comply with the very bond conditions you need if defaulting and terminating the principal of the bond.  Otherwise, you may wind up with a similar harsh result, as the subcontractor did in this case by looking to the surety many months after it default terminated the bond-principal, and started remediating the default.

Please contact David Adelstein at dadelstein@gmail.com or (954) 361-4720 if you have questions or would like more information regarding this article. You can follow David Adelstein on Twitter @DavidAdelstein1.

 

PRESERVING PERFORMANCE BOND CLAIMS

 

rPerformance bonds can be a valuable source of protection to owners that want their general contractors to provide a performance bond and, likewise, to general contractors that want certain subcontractors to provide a performance bond. The performance bond is designed to benefit the obligee in the event the contractor that issues the bond defaults under its contractual obligations. It is absolutely crucial that parties take the proper steps under the terms of the performance bonds to preserve their rights and arguments under the bond. To do this requires an unequivocal formal default of the contractor that issued the bond and that the party will be looking solely to the surety to complete the defaulted party’s contractual obligations. Otherwise, a court will rule in favor of the surety finding that the obligee of the bond did not comply with conditions precedent to preserve the performance bond claim and/or breached the terms of the bond by not allowing the surety to investigate and complete performance. This is exactly the situation in two federal district court summary judgment opinions relying on Florida law: North American Specialty Insurance Co. v. Ames Corp., 2010 WL 1027866 (S.D.Fla. 2010) and CC-Aventura, Inc. v. Weitz Co., 2008 WL 2699577 (S.D.Fla. 2008). Both of these cases illustrate the importance of formally and unequivocally declaring the party that issued the performance bond in default irrespective of whether the issue arises pre-completion or post-completion. Both cases also pertain to a subcontractor that provided a performance bond identifying the general contractor as the obligee (or beneficiary) of the bond.

 

I. North American Specialty Ins. Co. v. Ames Corp. (Pre-Completion)

 
In this case, a general contractor hired a roofer for a federal project. The roofer provided performance bonds identifying the general contractor as the obligee. The bonds provided as follows (which is common language in performance bonds):

 

“Whenever Principal shall be, and be declared by Obligee to be in default under the subcontract, the Obligee having performed Obligee’s obligations thereunder:

(1) Surety may promptly remedy the default …;

(2) Obligee after reasonable notice to Surety may, or Surety upon demand of Obligee may arrange for the performance of Principal’s obligation under the subcontract …;

(3) … If the Surety arranges completion or remedies the default, that portion of the balance of the subcontract price as may be required to complete the subcontract or remedy the default and to reimburse the Surety for its outlays shall be paid to the Surety at the times and in the manner as said sums would have been payable to Principal had there been no default under the subcontract.”

Ames Corp., 2010 WL at *1.

 

During construction, the general contractor notified the surety that the roofer was refusing to perform and that the general contractor will look to the surety for costs incurred above the roofer’s subcontract amount. A follow-up notice advised the surety that expenses were being incurred to finish the roofer’s subcontract amount and no one from the surety visited the jobsite. The surety then commenced an investigation while advising the general contractor that the “prior letters were not accompanied by supporting documentation and/or prior notice to the principal of default and/or potential default.” Ames Corp., 2010 WL at *3. A meeting was coordinated with the owner, the general contractor, the roofer, and the roofer’s surety at which time the surety represented it would need up to 5 months to assume responsibility and take action. After this meeting, the general contractor sent another letter to the surety and the roofer explaining that the roofing subcontract was not terminated or declared in default and that the surety needed to appreciate the short time allotted for completing the roofer’s contract. The surety responded that because the general contractor had not declared the roofer in default, the surety had no obligation to act under the performance bonds.

 

Notwithstanding the general contractor never formally declaring the subcontractor in default, it supplemented the roofer’s scope of work. Both the roofer and the surety objected; the surety even advised that such efforts would be a material breach of the bonds. However, due to leaks with the roofing system (the manufacturer of the roofing system inspected the roof and found that there were installation defects), the general contractor incurred substantial costs to complete the roofer’s scope of work which exceeded the roofer’s subcontract balance. In addition, the general contractor incurred delay damages associated with completing the roofer’s scope of work.

 

The surety initiated this lawsuit based on the monetary demands from the general contractor. The surety moved for summary judgment based on the argument that a condition precedent to the bonds obligations was never triggered, that being that the general contractor never declared the roofer in default. The surety also argued that the general contractor breached the bonds by not allowing the surety the right to remedy any default and by not making available to the surety the unpaid subcontract balance in connection with the surety remedying the default.

 

Relying on Florida law, the Southern District found:

 

[A] surety’s liability on a bond is determined strictly from the terms and conditions of the bond agreement. The purpose of a performance bond is to guarantee completion of the contract upon default by the contractor.

***

A declaration of default sufficient to invoke the surety’s obligations under the bond must be made in clear, direct, and unequivocal language. The declaration must inform the surety that the principal has committed a material breach or series of material breaches of the subcontract, that the obligee regards the subcontract as terminated, and that the surety must immediately commence performing under the terms of the bond.

Ames Corp., 2010 WL at *6 (internal citations and quotations omitted).

 

Based on this law, the Southern District held that none of the letters the general contractor sent to the surety defaulted the roofer in clear, direct, and unequivocal language. While the letters urged the surety to become involved and threatened default, they did not formally and unequivocally default the roofer. Accordingly, the court granted summary judgment in favor of the surety.

 

Furthermore, the Southern District agreed with the surety that the general contractor breached the bond by completing / supplementing the subcontract without giving the surety the opportunity to remedy any default under the subcontract. As the court explained: “‘[O]nce Ames/Dawson [general contractor] engaged in the supplementation of work without allowing NAS [surety] to perform, its conduct constituted a material breach that voided the bond.” Ames Corp., 2010 WL at *9.

 

II. CC-Aventura, Inc. v. Weitz Co. (Post-Completion)

 

In this case, the general contractor was hired to construct a senior living facility. The general contractor hired a painter with a subcontract that contained an indemnification provision and a provision that required the painter to correct defective work. The painter provided a performance bond identifying the general contractor as the obligee.

 

pAfter completion of the project, the owner sued the general contractor for water intrusion and damage. The general contractor sued subcontractors including its painting subcontractor. The general contractor also asserted a claim against the painting subcontractor’s performance bond surety for breach of the bond. The surety moved for summary judgment arguing that the bond obligations were never triggered because the general contractor never formally declared the painting subcontractor in default.

 

The general contractor argued that it did provide default notices when it transmitted the owner’s expert and its expert reports regarding the paint that the painter applied. In the notices, the general contractor demanded that the surety correct the defects and that the painter’s failure to take corrective action will be a default under the subcontract.

 

The surety took the position that these types of notices were insufficient. The Southern District of Florida agreed and granted summary judgment in favor of the surety finding:

 

“Both of Weitz’s [general contractor] letters do state that Delta [subcontractor] is in ‘default’ of its Subcontract-and had Weitz maintained that position and indicated that Weitz now looked to American Casualty [surety] alone, both of its letters could reasonably be interpreted as declarations of default sufficient to trigger American Casualty’s liability on the Bond. However, in its December 30, 2005 letter Weitz also advised Delta to ‘please accept this letter as The Weitz Company’s final written demand that Delta Painting or its Surety take appropriate corrective action’….In its April 11, 2006 letter, Weitz reiterated that it had made ‘numerous demands upon both Delta and American to correct [the painting] deficiency.’ Weitz then stated its intention to perform the corrective work itself and announced that ‘Weitz will seek such costs and all other damages from Delta and American.’ If Weitz wanted to trigger American Casualty’s obligations on the Bond, it would have had to clearly and unambiguously notify American Casualty that it now looked to it to complete Subcontract obligations, in accordance with the Bond.”

CC-Aventura, 2008 WL at *4.

 

 

As illustrated above, there are certainly procedural hurdles that are required to take place in order to properly default a contractor that provided a performance bond. Not doing so can be fatal to the performance bond claim. Default is always viewed as a last resort because parties do not want to be in material breach for incorrectly defaulting or terminating a party. However, by not defaulting a party, the performance bond’s obligations are not triggered. Due to these hurdles, general contractors are now obtaining subguard (subcontractor default insurance) instead of requiring individual subcontractors to provide performance bonds. This allows the general contractor to be more involved in the process since it is the one obtaining subguard and it eliminates subcontractors from having to obtain the bond (which could be problematic for certain subcontractors).

 

For more on performance bonds, please visit: https://floridaconstru.wpengine.com/statute-of-limitations-on-performance-bond-claims/

 

 

Please contact David Adelstein at dadelstein@gmail.com or (954) 361-4720 if you have questions or would like more information regarding this article. You can follow David Adelstein on Twitter @DavidAdelstein1.