AN OWNER’S “INTENDED THIRD PARTY BENEFICIARY” STATUS UNDER A SUBCONTRACT

Posted on March 29, 2014November 8, 2024 by Edward Garber

Sometimes, during a dispute, there are arguments as to whether an owner is an INTENDED third party beneficiary of the subcontract by and between the general contractor and the subcontractor. There are instances where an owner desires to be an intended third party beneficiary of a subcontract so that it could pursue a breach of contract claim directly against the subcontractor. (These instances can relate to concerns over the solvency of the general contractor and/or the insurance coverage limits of the general contractor.)

“A party is an intended [third party] beneficiary only if the parties to the contract clearly express, or the contract itself expresses, and intent to benefit the third party or a class of persons to which that party claims to belong.” Dingle v. Dellinger, 2014 WL 470679, *1 (Fla. 5th DCA 2014). In other words, an intended third party beneficiary is not a signatory or party to the contract. Rather, it is expressly clear from the contract that the contract’s intent is to directly benefit that third party. Dingle, 2014 WL at *1 (finding to assert a breach of an intended third party beneficiary contract, the third party must show an intent that the contract was to directly and primarily benefit the third party). Because the intent of the contract is to directly benefit the third party, the third party is entitled to enforce the contract and, thus, sue for a breach of that contract.

However, if a third party is not an intended third party beneficiary of the contract, it will be deemed an incidental beneficiary that maintains no rights whatsoever to enforce the contract. McKinney-Green, Inc. v. Davis, 606 So.2d 393, 396 (Fla. 1st DCA 1992).

Now, a property owner is typically not regarded as an intended third party beneficiary of a subcontract between a general contractor and subcontractor. See J.W. Hodges Drywall, Inc. v. Mizner Falls, LLP, 865 So.2d 681 (Fla. 4th DCA 2004) (owner could not enforce arbitration provision in subcontract between general contractor and drywall subcontractor); accord Lillibridge Health Care Services, Inc. v. Hunton Brady Architects, P.A., 2010 WL 3788859 (M.D. Fla. 2010) (owner not intended third party beneficiary of mechanical engineer’s subconsultant agreement with architect); City of Tampa v. Thornton-Tomasetti, P.C., 646 So.2d 279 (Fla. 2d DCA 1994) (public owner not intended third party beneficiary of subconsultant’s agreement between subconsultant and architect); Vogel Bros. Bldg. Co. v. Scarborough Constructors, Inc., 513 So.2d 260 (Fla. 2d DCA 1987) (public owner not intended third party beneficiary of subcontract). Indeed, the Fifth District of Florida maintained: “As one court put it, ‘[a]lthough the work performed by subcontractors ultimately accrues to the property owner, the owner is ordinarily regarded as only an incidental beneficiary of the subcontract.” Publix Super Markets, Inc. v. Cheesbro Roofing, Inc., 502 So.2d 484, 488 (Fla. 5th DCA 1987) (superseded on other grounds) quoting National Cash Register Co. v. Unarco Indus., Inc., 490 F.2d 285, 286 (7th Cir. 1974). In addition, a subcontractor is not going to be deemed an intended third party beneficiary between the prime contract between the owner and the general contractor that would entitle it to assert a breach of contract claim against the owner. Esposito v. True Color Enterprises Const., Inc., 45 So.3d 554 (Fla. 4th DCA 2010).

If an owner wants to be an INTENDED third party beneficiary of the subcontracts, it should require the general contractor to include certain buzz language in the subcontracts that expressly sets forth this intent. Such buzz words would be something to the effect:

“It is understood and agreed that this subcontract is to primarily and directly benefit the Owner; therefore, the Owner is deemed an intended third party beneficiary of the subcontract and can enforce the subcontract as an intended third party beneficiary.”

This language clearly indicates the required intent for the intended third party beneficiary status that will enable the owner to enforce the subcontract. Without such language that clearly articulates this intent, an intended third party beneficiary status should not be extended to all situations where an owner decides to sue a subcontractor for breach of subcontract when the subcontractor was not hired by the owner. Although the owner will make the argument that the subcontractor’s work is to benefit the owner under the subcontract, the subcontractor could make a similar argument that the owner’s payment obligations to the general contractor under the prime contract is to benefit the subcontractors since the owner knew that the general contractor was not self-performing the work. If however the owner is an intended third party beneficiary of the subcontract and enforces the subcontract, it should be deemed bound by all of the terms, conditions, and burdens of the subcontract. See Woods v. Christensen Shipyards, Ltd., 2005 WL 5654643 (S.D.Fla. 2005); accord Consolidated Bathurst, Ltd. v. Rederiaktiebolaget Gustaf Erikson, 645 F.Supp. 884, 886 (S.D.Fla. 1986).

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.

TIPS FOR DRAFTING RESTRICTIVE COVENANT (SUCH AS NON-COMPETE / ANTI-COMPETITION) LANGUAGE IN EMPLOYMENT AGREEMENT

Posted on March 16, 2014November 8, 2024 by Edward Garber

Parties sometimes seek counsel to enforce a restrictive covenant in an agreement or a provision in an agreement that prohibits the other party from doing something or limiting the use of something. Such provisions are sometimes found in employment agreements to prevent an employee from learning how the employer conducts business, obtaining valuable information such as client contacts and client and pricing lists, and then starting a competing business. The recent decision of Richland Towers, Inc. v. Richland Towers, LLC, 39 Fla. L. Weekly D535b (Fla. 2d DCA 2014), is a new opinion that emphasizes the importance of including the following language in any agreement that contains a restrictive covenant such as an agreement that contains a non-compete / anti-competition provision:

“Covenants Independent. Each restrictive covenant…set forth in this Agreement shall be construed as a covenant independent of any other covenant or provisions of this Agreement or any other agreement which the Corporation and Employee [parties to the agreement] may have, fully performed and not executory, and the existence of any claim or cause of action by the Employee against the Corporation, whether predicated upon another covenant or provision of the Agreement or otherwise, shall not constitute a defense to the enforcement by the Corporation of any other covenant.” Richland Towers, supra.

By identifying that each covenant in the agreement is INDEPENDENT instead of dependent on one another, it should prevent the party opposing the restrictive covenant from arguing that the party enforcing the covenant committed a prior material breach of contract and, thus, can no longer enforce the restrictive covenant. This is a common argument from parties opposing the enforcement of a restrictive covenant such as non-compete language.

The above language was in the employment agreement in the dispute. The former employer moved for a temporary injunction to enforce non-compete / anti-competition language in the employment agreement. The trial court denied the injunction finding that because the employer did not pay certain bonuses, the employer committed a prior breach of contract and, thus, the restrictive covenant (non-compete provision) was not enforceable. The Second District, however, reversed the trial court court’s denial of the temporary injunction based on the above quoted language in the agreement. Since one covenant was independent of the other, whether the bonuses were paid would not render the non-compete language unenforceable. So, if drafting a restrictive covenant, having language that clarifies the intent that the covenants in the agreement are independent is important. On the other hand, if agreeing to non-compete language, consider the significance of the provision and the fact that the provision may be deemed independent of any other provision in the agreement.

Restrictive covenants are enforced through requesting a temporary injunction. To prevail on a temporary injunction, the moving party must establish: “the threat of irreparable harm to the movant for which there would be no adequate legal remedy, the movant’s substantial likelihood of success on the merits, and a determination that granting the injunction would serve the public interest.” Richland Tower, supra, citing Atomic Tattoos, LLC v. Morgan, 45 So.3d 63, 64-65 (Fla. 2d DCA 2010). Furthermore, if a temporary injunction is ordered, the court should require the moving party to post an injunction bond to cover damages in the event the injunction is determined to have been wrongly ordered. Richland Tower, supra (reversing trial court’s denial of the injunction and holding that if the injunction is ordered, the trial court must require the moving party to provide an injunction bond.)

For more on the requirements for temporary injunctions, specifically in the bit protest arena, please see: https://floridaconstru.wpengine.com/the-difficulty-in-prevailing-in-a-bid-protest/

MAKE SURE INDEMNIFICATION PROVISIONS CLEARLY REFLECT THE REQUIRED SCOPE OF THE INDEMNIFICATION

Posted on February 20, 2014November 8, 2024 by Edward Garber

Indemnification provisions are a vital component of construction contracts. Every construction contract (whether a prime contract, subcontract, professional services contract, etc.) should absolutely require that the party receiving compensation for performing a service to indemnify the party paying for that service (referred to as the indemnitee). No exception! Moreover, it is crucial that indemnification provisions are carefully drafted to not only comply with Florida law, but to eliminate any uncertainty regarding the scope of the indemnification. In other words, make sure the indemnification provision unequivocally reflects the scope of the indemnification that is sought and that the scope complies with Florida law.

In Florida, indemnification provisions for construction contracts are governed by Florida Statute s. 725.06, which is recited below. Also, please see https://floridaconstru.wpengine.com/buttoning-up-contractual-indemnification-language/ and https://floridaconstru.wpengine.com/the-scope-of-a-release-in-a-settlement-and-contractual-indemnification/ for more information on the application of this statute to ensure the indemnification provision, whether for a private or public project, complies with Florida law.

The recent Third District Court of Appeal decision in Royal Palm Hotel Property, LLC v. Deutsche Lufthansa Aktiengesellschaft, Inc., 2014 WL 444150 (Fla. 3d DCA 2014), albeit a non-construction dispute, exemplifies the significance of making sure the indemnification provision accurately reflects the scope of indemnification that the party receiving the indemnification (the indemnitee) truly wants or requires.

In this case, the indemnification provision read: “The Hotel agrees to indemnify and hold Lufthansa harmless from all liabilities, including damage to property or injury or death of persons, including Lufthansa property and Lufthansa personnel that may result from the negligence or wilful (sic) misconduct of the Hotel.”

The indemnification provision was between a hotel and an airline which had its employees stay at the hotel. In this personal injury action, the hotel was sued for negligence when a window fell out of a frame and injured a guest. Also, the airline was sued under the theory that it was vicariously liable for the negligence of its employee staying at the hotel. The issue was whether the hotel was required to indemnify the airline for the negligence of the airline and its employees staying at the hotel. However, a look at the indemnification clause above does not articulate that the hotel will be responsible for indemnifying and holding the airline harmless for the negligence of the airline or the airline’s employees. Rather, it says the hotel will indemnify the airline for its negligence or willful misconduct. This is a huge difference as the indemnification written is much narrower than the indemnification that the airline perhaps wanted.

Again, the airline was never sued for the hotel’s negligence. It was sued for the negligence of its employee staying at the hotel under a vicarious liability (respondeat superior) theory. While the airline prevailed in the underlying personal injury action, it wanted to recoup its defense costs against the hotel. The Third District construing the indemnification provision held that the provision was never kicked into effect because the hotel was not required to indemnify the airline for the negligence of the airline or its employee and the basis of the underlying claims against the airline related to the negligence of the airline’s employee.

The reason this case is worth discussing is because if an indemnitee wants an indemnification provision to cover its own negligence, the provision needs to clearly reflect this intent. Now, for construction contracts, an indemnitee should never negotiate an indemnification that covers it for its negligence without making sure the provision undoubtedly complies with Florida Statute s. 725.06. Otherwise, the indemnitee risks an unenforceable indemnification provision! In a nutshell, s. 725.06 provides that if an indemnification provision is going to indemnify an indemnitee for its negligence, the contract must contain a “monetary limitation on the extent of the indemnification that bears a reasonable commercial relationship to the contract and its part of the project specifications or bid documents, if any.”

Section 725.06

(1) Any portion of any agreement or contract for or in connection with, or any guarantee of or in connection with, any construction, alteration, repair, or demolition of a building, structure, appurtenance, or appliance, including moving and excavating associated therewith, between an owner of real property and an architect, engineer, general contractor, subcontractor, sub-subcontractor, or materialman or any combination thereof wherein any party referred to herein promises to indemnify or hold harmless the other party to the agreement, contract, or guarantee for liability for damages to persons or property caused in whole or in part by any act, omission, or default of the indemnitee arising from the contract or its performance, shall be void and unenforceable unless the contract contains a monetary limitation on the extent of the indemnification that bears a reasonable commercial relationship to the contract and is part of the project specifications or bid documents, if any. Notwithstanding the foregoing, the monetary limitation on the extent of the indemnification provided to the owner of real property by any party in privity of contract with such owner shall not be less than $1 million per occurrence, unless otherwise agreed by the parties. Indemnification provisions in any such agreements, contracts, or guarantees may not require that the indemnitor indemnify the indemnitee for damages to persons or property caused in whole or in part by any act, omission, or default of a party other than:

(a) The indemnitor;

(b) Any of the indemnitor’s contractors, subcontractors, sub-subcontractors, materialmen, or agents of any tier or their respective employees; or

(c) The indemnitee or its officers, directors, agents, or employees. However, such indemnification shall not include claims of, or damages resulting from, gross negligence, or willful, wanton or intentional misconduct of the indemnitee or its officers, directors, agents or employees, or for statutory violation or punitive damages except and to the extent the statutory violation or punitive damages are caused by or result from the acts or omissions of the indemnitor or any of the indemnitor’s contractors, subcontractors, sub-subcontractors, materialmen, or agents of any tier or their respective employees.

(2) A construction contract for a public agency or in connection with a public agency’s project may require a party to that contract to indemnify and hold harmless the other party to the contract, their officers and employees, from liabilities, damages, losses and costs, including, but not limited to, reasonable attorney’s fees, to the extent caused by the negligence, recklessness, or intentional wrongful misconduct of the indemnifying party and persons employed or utilized by the indemnifying party in the performance of the construction contract.

(3) Except as specifically provided in subsection (2), a construction contract for a public agency or in connection with a public agency’s project may not require one party to indemnify, defend, or hold harmless the other party, its employees, officers, directors, or agents from any liability, damage, loss, claim, action, or proceeding, and any such contract provision is void as against public policy of this state.

(4) This section does not affect any contracts, agreements, or guarantees entered into before the effective date of this section or any renewals thereof.

WHAT IS SUBSTANTIAL COMPLETION?

Posted on November 8, 2013November 8, 2024 by Edward Garber

The term “substantial completion” is in most construction contracts. And, it should be. This date marks the date the owner expects to be able to use its project for its intended purpose and, if it cannot, the contractor will (likely) be assessed liquidated damages for the delay to the substantial completion date. The owner’s contractual ability to assess liquidated damages serves to motivate the contractor to substantially complete the project by the agreed date and to reimburse the owner for delay-related damages that cannot be ascertained with a reasonable degree of certainty at the time of the contract.

A. How is Substantial Completion Defined

Under the general conditions of the AIA (American Institute of Architects A201 Document 2007), substantial completion is the “stage in the progress of the Work when the Work or designated portion thereof is sufficiently complete in accordance with the Contract Documents so that the Owner can occupy or utilize the Work for its intended use.” (AIA Document A201 s. 9.8.1) Under the AIA, the architect is required to conduct inspections to determine the date of substantial completion and certifies this date.

The general conditions of the EJCDC (Engineers Joint Contract Documents Committee C-700 Document 2007) defines substantial completion similarly as:

“The time and date at which the Work has progressed to the point where, in the opinion of Engineer, the Work is sufficiently complete, in accordance with the Contract Documents, so that the Work can be occupied and/or utilized for the purposes for which it is intended….Substantial Completion cannot occur before the Project is issued a Certificate of Occupancy (or Completion, if applicable) by the governing building department that allows Owner to utilize the entire Project for the purposes for which it is intended.” (EJCDC Document C-700 s. 1.01.46)
Whether it is an AIA, EJCDC, or other industry form document, substantial completion is routinely defined as that point in time when the owner can utilize its project for the purposes for which it is intended.

A leading case in Florida discussing substantial completion is J.M. Beeson Co. v. Sartori, 553 So.2d 180 (Fla. 4th DCA 1989). This case involved an owner assessing liquidated damages against its contractor. The contractor was hired to construct a shopping center that required substantial completion within 300 days of commencement. The contract provided that substantial completion occurred when “construction is sufficiently complete in accordance with the Contract Documents, so the owner can occupy or utilize the work or designation portion thereof for the use for which it is intended.” J.M Beeson, 553 So.2d at 181. Although two anchor tenants in the shopping center received Certificates of Occupancy within the 300 days, another tenant did not. The owner took the position that substantial completion had not been achieved, irrespective of the Certificates of Occupancy, because items such as landscaping were not completed. The Fourth District dismissed the owner’s position finding:

“[W]hen the owner can put tenants in possession for fixturing and can begin to collect rents, the owner begins to utilize the work for its intended purpose. When the owner was able to occupy and fixture the constructed space, the construction was substantially completed.” J.M. Beeson, 553 at 182-83 (internal citations omitted).

The Fourth District indicated that the substantial completion date occurred no later than the date the shopping center was able to obtain certificates of occupancy for the tenants. Notably, if the contractor in J.M. Beeson was simply required to build shell retail space where the tenants were responsible for their own tenant improvements, the substantial completion would likely occur when an applicable certificate of completion was issued for the shell space pursuant to the shell permit that would entitle the tenants to begin their individual improvements. See, e.g., Hausman v. Bayrock Investment Co., 530 So.2d 938 (Fla. 5th DCA 1988) (finding that test for substantial completion for property tax purposes is the date property is put to use for which it is intended; in this case, since contactor was building shell retail space, substantial completion occurred when shells were completed).

If an owner is in a position to use its project for its intended purpose (whether for personal use, public use, whatever the project entails), this really should mark the substantial completion date. This is more of an objective date determined by the governing building department through the issuance of a certificate relating to the permit.

B. Contract Drafting / Understanding Tips

I prefer the substantial completion definition in the general conditions of the EJCDC (above) because it references that this point in time should not be earlier than the issuance of a Certificate of Occupancy (or applicable Certificate of Completion). Even though most contracts give certain discretion to the design professional to determine and certify the date, the fact remains that the Certificate of Occupancy is realistically the date that determines when an Owner can use its project for its intended purpose since it permits occupancy. I often like to tie the substantial completion date in the contract to the Certificate of Occupancy date or Temporary Certificate of Occupancy date (since the TCO date may be the date that allows occupancy under certain conditions) since this more accurately reflects the date the Owner can use its project for its purpose (or, if it is a project for shell space, the Certificate of Completion date that authorizes the tenant to construct finishes / improvements). Also, this removes some of the discretion from the design professional and shifts their focus to generating the punchlist and working towards final completion.

From an owner’s perspective, if it agrees to a mutual waiver of consequential damages in the contract, it must absolutely include a liquidated damages provision tied to the substantial completion date. If it does not want to include a liquidated damages provision, then the owner needs to ensure there is not a mutual waiver of consequential damages provision and, if there is a delay to the substantial completion date, be in a position to prove its actual delay-related damages.

From a contractor’s perspective, it wants to agree to a substantial completion date where arguably there is float built into its schedule to ensure it has enough time to substantially complete the project. Also, it will want to ensure through flow-down provisions in its subcontracts that it has the ability to flow down assessed liquidated damages to responsible subcontractors that impact its critical path.

From a subcontractors’ perspective, it needs to understand the contractor’s schedule and how the work is sequenced and ideally have input particularly relating to durations for its activities based on the sequencing of the work. Otherwise, the subcontractor could be putting itself in a position where it will be notified of delays since it is unable to meet its required durations.

THE INCLUSION OF LIMITATION OF LIABILITY PROVISIONS FOR DESIGN PROFESSIONALS

Posted on October 8, 2013November 8, 2024 by Edward Garber

Design professionals need to remember the benefit of newly enacted legislation effective July 2013 that authorizes a limitation of liability provision for design professionals in their individual capacity. Florida Statute s. 558.0035 authorizes a design professional to limit their personal liability if: (a) the professional’s company entered into the contract for professional services; (b) the contract does not name the professional as a party to the contract; (c) the contract provides in uppercase and at least 5 font points larger than the rest of the contract that an employee or agent of the professional’s company cannot be held individually liable in negligence, and (d) the professional’s company maintains professional liability insurance. See Fla. Stat. s. 558.0035 set forth below. Complying with this statute can limit a professional’s liability in an individual capacity for economic damages, although based on the language of the statute, it would not extend to personal injury or property damage not subject to the professional services contract.

When negotiating a contract for a design professional, it is good to include a limitation of liability provision to protect professionals working with the design professional company/ entity entering into the contract. I would include a provision identifying that it is specifically understood that employees or agents of the contracting party are not parties to the professional services contract. The reason being is many times professional services contracts will call out the specific professional(s) that is to act as the company’s representative or the professionals that will be performing the professional services. Additionally, I would include in uppercase and 5 font sizes larger than the balance of the text in the contract a provision to the effect: “PURSUANT TO FLORIDA STATUTE S. 558.0035, AN INDIVIDUAL EMPLOYEE OR AGENT OF_______ [CONTRACTING PARTY] MAY NOT BE HELD INDIVIDUALLY LIABLE IN NEGLIGENCE FOR ANY CLAIMS, DAMAGES, OR DISPUTES ARISING OUT OF AND SUBJECT TO THE CONTRACT.”

Although the statute provides that the limitation of liability provision does not apply to damages to personal injuries or property not subject to the contract, it does not define the circumstances in which this would apply. For instance, if a structure is deficiently engineered and a portion falls down or collapses and damages persons or property other than the structure itself, it would seem that the limitation of liability provision would not extend to these types of damages since the other property and personal injuries were not subject to the professional services contract. On the other hand, there could be the argument that these damages are subject to the professional services contract because they arose out of errors and omissions in the performance of professional service contractual obligations.

When negotiating a contract for an owner, the key is to ensure that the design professional has sufficient professional liability insurance based on the requirements of the project (i.e., sufficient insurance limits and potentially tail / extended reporting period coverage). An owner willing to agree to the limitation of liability provision could put a disclaimer that reflects that should the contracting party not continue its professional liability insurance for “x” years after the project’s completion with a date retroactive to the contract date or purchase tail coverage for the same period of time, the limitation of liability provision shall be deemed null and void.

Florida Statute s. 558.0035

(1) A design professional employed by a business entity or an agent of the business entity is not individually liable for damages resulting from negligence occurring within the course and scope of a professional services contract if:
(a) The contract is made between the business entity and a claimant or with another entity for the provision of professional services to the claimant;
(b) The contract does not name as a party to the contract the individual employee or agent who will perform the professional services;
(c) The contract includes a prominent statement, in uppercase font that is at least 5 point sizes larger than the rest of the text, that, pursuant to this section, an individual employee or agent may not be held individually liable for negligence;
(d) The business entity maintains any professional liability insurance required under the contract; and
(e) Any damages are solely economic in nature and the damages do not extend to personal injuries or property not subject to the contract.
(2) As used in this section, the term “business entity” means any corporation, limited liability company, partnership, limited partnership, proprietorship, firm, enterprise, franchise, association, self-employed individual, or trust, whether fictitiously named or not, doing business in this state.

LIEN TRANSFER BONDS AND VENUE

Posted on August 12, 2013November 8, 2024 by Edward Garber

The Fourth District Court of Appeals in Attaway Electric, Inc. v. Kelsey Construction, Inc., 38 Fla. L. Weekly D1693a (Fla. 4th DCA 2013) recently ruled that an action on a lien transfer bond (posted pursuant to Fla. Stat. s. 713.24 in the county where the project is located and lien recorded) needs to be initiated in the county where the bond is recorded. This means that even if there is a contract between the parties that requires a different venue outside of where the lien transfer bond is posted, that venue provision will not be enforced so that an action as to the lien transfer bond and an action under the contract can both be brought in the same county, i.e., where the lien transfer bond is posted.
In Attaway Electric, a subcontractor recorded liens for alleged nonpayment on Broward County projects with the same general contractor. The liens were transferred to lien transfer bonds by the general contractor. The subcontractor moved to foreclose the liens in Broward County and also sued the general contractor for breach of contract. The general contractor then moved to transfer venue to Orange County pursuant to a forum selection provision in the subcontract. The trial court granted the motion and transferred venue. The Fourth District, however, reversed finding that an action on a lien transfer bond must be brought in the county where it is recorded and “contract claims involving the same matters should be brought in the same place to avoid inconsistent rulings.” Attaway Electric.

This recent decision is important because contractors that want to obtain the benefit of a forum selection provision in a subcontract probably need to have a payment bond and ensure in the subcontract that the forum selection provision covers claims as to the payment bond surety. If there is no payment bond, specifically for a private project, a subcontractor can lien the private project for monies owed. If the general contractor (or even perhaps the owner) then transfers the lien to a lien transfer bond, the subcontractor will be able to foreclose the lien as to the lien transfer bond in the county where the bond is recorded as well as pursue a breach of contract claim against the contractor in the same county, even if the subcontract contains a forum selection provision with a different venue.

VENUE FOR PAYMENT BOND DISPUTES IN FLORIDA

Posted on July 9, 2013November 8, 2024 by Edward Garber

Two main Florida payment bond statutes are Florida Statute s. 713.23 (payment bonds for private projects) and Florida Statute s. 255.05 (payment bonds for Florida public projects-not federal projects). Both statutes prohibit a payment bond issued after October 1, 2012 from restricting venue. In other words, if the payment bond contains a venue provision after this date, it is not enforceable.

This prohibition is important because there are times where the project is located in a venue that is not where the subcontractor resides and/or is contrary to the venue provision in the subcontract (typically, a venue where the general contractor resides).

It is good practice for the general contractor to include in its subcontract a venue provision that applies to its surety such that the subcontractor must sue the payment bond in the same venue that governs the subcontract. While it is uncertain how the new prohibition from restricting venue in a payment bond will apply in this context, the counter-argument is that the payment bond is not restricting venue, rather the “negotiated” subcontract governs the venue of any and all disputes between the parties including claims against the general contractor’s surety (and the general contractor is indemnifying and defending the surety). Worst case scenario is that the venue provision is deemed inapplicable to the surety. However, courts do not favor splitting causes of action (due to, among other things, the concern for conflicting results over the same facts) and should not favor a subcontractor lawsuit against the general contractor in one venue and a simultaneous subcontractor lawsuit against the general contractor’s payment bond surety in another venue. Indeed, courts have refused to enforce venue provisions in subcontracts in order to avoid splitting of causes of action. See, e.g., Miller & Solomon General Contractors, Inc. v. Brennan’s Glass Co., Inc., 837 So.2d 1182 (2003) (refusing to enforce subcontract venue provision when action as to lien transfer bond was filed in correct venue). Including a venue provision that also covers claims against the payment bond surety is useful in the event the general contractor wants to countersue the subcontractor or simply wants to create an argument that its subcontractor disputes should be confined to its preferred venue versus the subcontractor’s preferred venue.

On the other hand, there are situations where a subcontractor may not want to sue the general contractor and strategically prefers to just sue the payment bond surety. One situation may be the subcontractor knows the general contractor was not paid and the subcontract contains a pay-when-paid provision which would be enforceable as to the general contractor, but not against the payment bond surety. Another situation may be due to the venue provision in the subcontract; the subcontractor prefers to sue in a venue outside of the venue provision in the subcontract and has a better argument around the venue provision if it does not join the general contractor. There is caselaw that supports an argument to sue a payment bond surety in a venue where the subcontractor (lienor) resides that, depending on the dispute, could be appealing to the subcontractor. See, e.g., American Insurance Co. v. Joyner Electric, Inc., 618 So.2d 799 (Fla. 1st DCA 1993) (finding that action under s. 255.05 public payment bond was proper where lienor / subcontractor resided); Coordinated Constructors v. Florida Fill, Inc., 387 So.2d 1006 (Fla. 3d DCA 1980) (finding that venue was proper under s. 713.23 private payment bond action where lienor / supplier resided).

Venue is a pretty heavily litigated procedural strategic issue. Just like any dispute, venue as to a payment bond claim should not be ignored and should absolutely be considered at the onset of a dispute.

For more information on venue provisions, please see:

https://floridaconstru.wpengine.com/venue-provisions-read-what-you-sign/

and

https://floridaconstru.wpengine.com/subcontractors-read-and-understand-the-implications-of-venue-provisions/

SUBCONTRACTORS – READ AND UNDERSTAND THE IMPLICATIONS OF VENUE PROVISIONS

Posted on May 15, 2013November 8, 2024 by Edward Garber

Subcontracts often have venue provisions. However, these are often overlooked until a dispute arises. In many instances, the venue provision requires disputes to be brought in a court in a different venue than where the project is located. This could have the adverse effect of exposing a subcontractor, in particular, to disputes in multiple forums. The recent case of East Coast Metal Decks, Inc. v. Boran Craig Barber Engel Construction Co., Inc., 38 Fla. L. Weekly D1061a (Fla. 2d DCA 2013), explains the undesirable dynamics of venue provisions.
In East Coast Metal Decks, the general contractor hired the subcontractor on two public projects in Brevard County and Sarasota County. The general contractor, however, sued the subcontractor in Collier County due to a venue provision in the subcontract. The subcontractor brought the general contractor’s payment bond surety into the fold and then tried to transfer the venue to Brevard County because the subcontractor was being sued by material suppliers in that County. The trial court denied the transfer of venue because of the Collier County venue provision in the subcontract.

On appeal, the Second District affirmed the trial court’s ruling. The Second District found that (i) the parties were bound by the subcontract venue provision as there was not a compelling reason not to enforce the provision and (ii) because the payment bond was a public payment issued under Florida Statute s. 255.05, venue for a claim against the bond did not have to lie in Brevard County (where the project was located).

What does this case mean? Well, it means that the subcontractor needs to litigate with the suppliers in Brevard County and litigate with the general contractor in Collier County even though the disputes are related. Most likely, the suppliers sued the subcontractor because they were not paid and the general contractor did not pay the subcontractor due to the facts related to the general contractor’s claim against the subcontractor in Collier County.
Litigation in different counties over a related dispute can become expensive and undesirable. It is important to understand and consider the impact of venue provisions in contracts. Sometimes, it makes sense to argue the compelling reasons why the venue provision should not be enforced. However, courts do favor venue provisions because that is what parties negotiated and agreed to on the front-end. Other times, it makes sense to resolve the smaller lawsuits or lawsuits where the facts may not be in your favor (such as a subcontractor’s lawsuit with a supplier) to focus on the lawsuit with more upside (the subcontractor’s lawsuit with the general contractor or payment bond surety).

VENUE PROVISIONS – READ WHAT YOU SIGN!

Posted on November 16, 2012November 8, 2024 by Edward Garber

Venue provisions, also known as forum selection provisions, are commonly included in contracts. These provisions state that if there is a dispute arising out of or relating to the contract, the dispute must be brought in the exclusive venue of a certain locale. (For example, the provision might say disputes must be brought in the exclusive venue of Miami-Dade County.) Parties should be aware of this provision when executing a contract.

In Espresso Disposition Corp. 1 and Rowland Coffee Roasters, Inc., 37 Fla. L. Weekly D2643a (Fla. 3d DCA 2012), the parties entered into a contract. However, the party that prepared the contract cut-and-pasted the venue provision / forum selection provision from another contract. In doing so, there was no realization that the venue provision required disputes to be brought in Illinois. When a dispute arose, the drafter filed suit in Miami and argued that the Illinois venue provision was in error because it was simply cut-and-pasted. The problem was that venue provisions are enforceable and presumptively valid. The Third District Court of Appeal ruled that the drafter’s lawsuit must be dismissed because according to the parties’ contract, disputes could only be brought in Illinois. In entering this ruling and enforcing the cut-and-pasted venue provision, the Third District maintained “be careful what you ask for!” In other words, review the contract you are preparing and executing.

This case stands for the important proposition that parties need to review the contracts they are executing. Failure to do so could result in you being required to resolve your dispute in a different state and inconvenient forum as was the circumstance in the above case.

THE ENFORCEABILITY OF TERMINATION FOR CONVENIENCE PROVISIONS

Posted on November 8, 2012November 8, 2024 by Edward Garber

Termination for convenience provisions are common in construction contracts, whether it’s a contract between an owner and a general contractor or a general contractor and a subcontractor. These provisions allow either a general contractor, by way of example, to terminate its subcontractor for its convenience without cause. While the subcontractor would be entitled to its costs incurred through the date of the termination (typically the recoverable costs are itemized in the termination for convenience provision), it would lose out on all of the profit it anticipated on receiving for that project. Termination for convenience provisions are enforceable.

The case of Vila & Son Landscaping Corp. v. Posen Construction, Inc., 2012 WL 4093545 (Fla. 2d DCA 2012), illustrates the enforceability of termination for convenience provisions. In this case, the general contractor terminated the subcontractor for convenience because it found another subcontractor that would do the same work cheaper. The terminated subcontractor asserted that the termination was wrongful and sued the general contractor. The subcontractor’s main argument was that the general contractor needed to utilize good faith in terminating the subcontractor for convenience and it did not by terminating it for a better price. The Second District Court of Appeal essentially found that the termination for convenience provision was enforceable, i.e., there was no wrongful termination simply because the general contractor terminated the subcontractor to obtain better pricing.

Contractors need to be aware of termination for convenience provisions. Subcontractors should be especially aware because these provisions can allow a general contractor to terminate it in order to obtain a different subcontractor to do the same scope of work at a reduced price. If this is a concern, one approach is to try to negotiate the recoverability of some profit (or termination damages) in the event the termination for convenience provision is exercised.