Tag: general contractor

New York’s Public Policy On Construction Dispute Venue Trumps Illinois Forum-Selection Clause – IL 2d Dist.

Dancor Construction, Inc. v. FXR Construction, Inc., 2016 IL App (1st) 150839 offers a nuanced discussion of forum selection clauses and choice-of-law principles against the backdrop of a multi-jurisdictional construction dispute.

The plaintiff general contractor (GC) sued a subcontractor (Sub) in Illinois state court for breach of a construction contract involving New York (NY) real estate.  The contract had a forum selection clause that pegged Kane County Illinois (IL) as the forum for any litigation involving the project.  

The trial court agreed with the Sub’s argument that the forum-selection clause violated NY public policy (that NY construction litigation should be decided only in NY) and dismissed the GC’s suit.  Affirming, the Second District discusses the key enforceability factors for forum-selection clauses when two or more jurisdictions are arguably the proper venue for a lawsuit.

Public Policy – A Statutory Source

The Court first observed that IL’s and NY’s legislatures both addressed the proper forum for construction-related lawsuits.  Section 10 of Illinois’ Building and Construction Contract Act, 815 ILCS 665/10, voids any term of an IL construction contract that subjects the contract to the laws of another state or that requires any litigation concerning the contract to be filed in another state.

NY’s statute parallels that of Illinois.  NY Gen. Bus. Law Section 757(1) nullifies construction contract terms that provide for litigation in a non-New York forum or that applies (non-) NY law.

Since a state’s public policy is found in its published statute (among other places), NY clearly expressed its public policy on the location for construction litigation.

Forum Selection and Choice-of-Law Provisions

An IL court can void a forum-selection clause where it violates a fundamental IL policy.  A forum-selection clause is prima facie valid unless the opposing side shows that enforcement of the clause would be unreasonable.

A forum-selection clause reached by parties who stand at arms’ length should be honored unless there is a compelling and countervailing reason not to enforce it. (¶ 75)

A choice-of-law issue arises where there is an actual conflict between two states’ laws on a given issue and it isn’t clear which state’s law governs.  Here, IL and NY were the two states with ostensible interests in the lawsuit.  There was also a plain conflict between the states’ laws: the subject forum-selection clause was prima facie valid in IL while it plainly violated NY law.

Which Law Applies – NY or IL?

Illinois follows Section 187 of the Restatement (Second) of Conflicts of Laws (1971) which provides that the laws of a state chosen by contracting parties will apply unless (1) the chosen state has no substantial relationship to the parties or the transaction and there is no other reasonable basis for the parties’ choice, or (2) application of the law of the chosen state would violate a fundamental policy of a state that has a materially greater interest than the chosen state on a given issue.

The Court found the second exception satisfied and applied NY law.  

Section 757 of NY’s business statute clearly outlaws forum-selection clauses that provide for the litigation of NY construction disputes in foreign states.  As a result, the contract’s forum clause clearly violates NY’s public policy of having NY construction disputes decided in NY.

The question then became which state, NY or IL, had the greater interest in the forum-selection clause’s enforcement?  Since NY was the state where the subcontractor resided, where the building (and contract’s finished product) was erected and the contract ultimately performed, the Court viewed NY as having a stronger connection.  Since allowing the case to proceed in IL clearly violated NY’s public policy, the Court affirmed dismissal of the GC’s lawsuit.

Afterwords:

Forum selection clauses are prima facie valid but not inviolable.  Where a chosen forum conflicts with a public policy of another state, there is a conflict of laws problem.  

The Court will then analyze which state has a more compelling connection to the case.  Where the state with both a clear public policy on the issue also has a clearer nexus to the subject matter of the lawsuit, the Court will apply that state’s (the one with the public policy and closer connection) law on forum-selection clauses.

 

Pay-When-Paid Clause in Subcontract Not Condition Precedent to Sub’s Right to Payment – IL Court

Pay-if-paid and pay-when-paid clauses permeate large construction projects

In theory, the clauses protect a contractor from downstream liability where its upstream or hiring party (usually the owner) fails to pay.

Beal Bank Nevada v. Northshore Center THC, LLC, 2016 IL App (1st) 151697 examines the fine-line distinction between PIP and PWP contract terms. a lender sued to foreclose

The plaintiff lender sued to foreclose commercial property and named the general contractor (GC) and subcontractor (Sub) as defendants.  The Sub countersued to foreclose its nearly $800K lien and added a breach of contract claims against the GC.

In its affirmative defense to the Sub’s claim, the GC argued that payment from the owner to the GC was a condition precedent to the GC’s obligation to pay the Sub.  The trial court agreed with the GC and entered summary judgment for the GC.  The Sub appealed.

Result: Reversed.

Reasons:

The Subcontract provided the GC would pay the Sub upon certain events and arguably (it wasn’t clear) required the owner’s payment to the GC as a precondition to the GC paying the Sub.  The GC seized on this owner-to-GC payment language as grist for its condition precedent argument: that if the owner didn’t pay the GC, it (the GC) didn’t have to pay the Sub.

Under the law, a condition precedent is an event that must occur or an act that must be performed by one party to an existing contract before the other party is obligated to perform.  Where a  condition precedent is not satisfied, the parties’ contractual obligations cease.

But conditions precedent are not favored.  Courts will not construe contract language that’s arguably a condition precedent where to do so would result in a forfeiture (a complete denial of compensation to the performing party). (¶ 23)

The appeals court rejected the GC’s condition precedent argument and found the Subcontract had a PWP provision.  For support, the court looked to the contractual text and noted it attached two separate payment obligations to the GC – one was to pay the Sub upon “full, faithful and complete performance,”; the other, to make payment in accordance with Article 5 of the Subcontract which gave the GC a specific amount of time to pay the Sub after the GC received payment from the owner.

The Court reconciled these sections as addressing the amounts and timing of the GC’s payments; not whether the GC had to pay the Sub in the first place. (¶¶ 19-20)

Further support for the Court’s holding that there was no condition precedent to the GC’s obligation to pay the Sub lay in another Subcontract section that spoke to “amounts and times of payments.”  The presence of this language signaled that it wasn’t a question of if the GC had to pay the Sub but, instead, when it paid.

In the end, the Court applied the policy against declaring forfeitures: “[w]ithout clear language indicating the parties’ intent that the Subcontractor would assume the risk of non-payment by the owner, we will not construe the challenged language…..as a condition precedent.” (¶ 23)

Since the Subcontract was devoid of “plain and unambiguous” language sufficient to overcome the presumption against a wholesale denial of compensation, the Court found that the Subcontract contained pay-when-paid language and that there was no condition precedent to the Sub’s entitlement to payment from the GC.

Take-aways

Beal Bank provides a solid synopsis of pay-if-paid and pay-when-paid clauses.  PIPs address whether a general contractor has to pay a subcontractor at all while PWPs speak to the timing of a general’s payment to a sub.

The case also re-emphasizes that Section 21(e) of the Illinois Mechanics Lien Act provides that the presence of a PIP or PWP contract term is no defense to a mechanics lien claim (as opposed to garden-variety breach of contract claim).

Course of Dealing Leads to Implied-In-Fact Contract Judgment in Construction Spat – IL First Dist.

While a signed agreement is almost always preferable to an oral one, the absence of a writing won’t always doom a breach of contract action.

Trapani v. Elliot Group, Inc., 2016 IL App (1st) 143734, examines what happens when parties don’t sign a contract but still act as if an agreement exists.

In a construction dispute, the First District affirmed a trial court’s finding that an implied-in-fact contract existed between the contractor plaintiff and the real estate developer defendant.  In upholding the $250K-plus judgment for the plaintiff, the Court highlights the nature and scope of implied contracts and discusses the agent-of-a-disclosed-principal rule.

The plaintiff submitted a draft contract that identified the defendant as “owner.”  The defendant, who wasn’t the owner (it was the developer), never signed the contract.

Despite the absence of a signed contract, the plaintiff performed the work contemplated by the draft agreement and was paid over $2M over a several-month period.  Plaintiff sued to recover for its remaining work after the developer refused to pay.  The developer denied responsibility for the plaintiff work: it claimed it merely acted as the owner’s agent and that plaintiff should have looked to the owner for payment.

The trial court entered judgment for the plaintiff.  It found that the plaintiff and developer, while lacking a signed written agreement, had an implied-in-fact contract.  The developer appealed.

Result: affirmed.

Reasons:

Whether an implied in fact contract (or “contract implied in fact”) exists depends on the surrounding facts, circumstances and expressions of the parties demonstrating an intent to be bound.

A contract implied in fact is a classic contract by conduct.  It arises where the court imposes a contractual duty on a party based on the party’s promissory expression that shows an intention to be bound;

The promissory expression can be inferred from the parties’ conduct and an implied in fact contract can be found even where there is no express contract between the parties;

An implied in law contract differs in that it is an equitable remedy based on the principle that no one should unjustly enrich himself at another’s expense;

Acceptance of an implied in fact contract can be shown by conduct of the parties and a course of dealing that demonstrates the parties’ intent to form a binding agreement.

(¶¶ 40-44)

The Court agreed with the trial court that the parties’ conduct supported a finding of an implied in fact contract.  The Court noted that throughout the construction project, the plaintiff communicated regularly with the defendant and provided lien waivers and payment certificates to the defendant.  The defendant also provided project specifications to the Plaintiff and approved multiple change orders over the course of plaintiff’s work on the site.  Significantly, the defendant never rejected plaintiff’s work or demanded that plaintiff stop working at any time during the project.

Next, the Court tackled the developer’s argument that it wasn’t liable to the plaintiff since the developer was acting as the agent of the property owner.  In Illinois, an agent who contracts with a third party generally is not liable so long as he discloses his principal’s identity.  Where the agent fails to identify his principal, it creates an “undisclosed principal” scenario which will make the agent personally liable if the contract is later breached. (¶ 60)

The reason for the undisclosed principal rule is reliance: the third party (here, the plaintiff) relies on the agent’s credit when entering the contract.  As a result, it would be unfair to immunize the agent and have the undisclosed principal shoulder the financial burden when the agent fails to reveal the principal.  The dearth of evidence showing a relationship between the developer (agent) and the owner (principal) led the Court to sustain the trial court’s finding that the developer was responsible for the outstanding amounts owed the plaintiff contractor.

Afterwords:

1/  An implied in fact contract is a valid, enforceable contract, despite a lack of express agreement.  Instead, the parties’ intention to be contractually liable can be shown through course of dealing between parties;

2/ The agent of a disclosed principal is generally immunized from liability.  However, where the agent fails to sufficiently disclose its principal’s identity, the agent remains liable if the plaintiff can show it relied on the agent’s credit and lacked notice of the agent’s principal’s identity.