Tag Archives: breach of contract

PRECONSTRUCTION AND PURCHASE-SALE CONTRACTS- ARGUMENTS TO REVOKE THE CONTRACT AND RECOVER THE DEPOSIT

Posted on by

images-1Upon the economic downturn, buyers of preconstruction condominiums have been looking for arguments to revoke their contracts and recover their deposit. Condominium developers have been trying to force buyers to close on the units they agreed to purchase through the contract or, alternatively, if the buyers are unwilling to close, keep the deposit money as compensation for their damages. In many instances, it is the buyer that initiates a lawsuit in order to recover their deposit and establish that the developer/seller breached the contract.

 

Two recent Florida appellate decisions involving preconstruction contracts touch upon creative arguments that buyers raise to recover the deposit money and establish that the developer/seller breached the preconstruction contract. In the first case, the buyer prevailed arguing that the seller failed to specifically comply with the terms of the contract. In the second case, the seller prevailed and the buyer lost his argument that the contract violated the Interstate Land Sales Full Disclosure Act, 15 U.S.C. §1701, et seq. (the “ILSFDA”), which is a federal statute designed to prevent fraud in the sale of property by requiring full disclosure of material information.

 

In the first case, Lowe v. Winter Park Condominium Partnership, 36 Fla. L. Weekly D1522a (5th DCA 2011), the buyer entered into a preconstruction contract on April 17, 2006 to purchase a condominium unit and tendered a substantial initial deposit. The contract required the seller to close on the unit within two years from April 17, 2006 (or April 16, 2008). The contract contained the following pertinent provisions pertaining to the closing date:

 

“[Paragraph 4.] Seller will notify Buyer at least thirty (30) days prior to the date that the consummation of the sale of the Unit to Buyer shall take place (“Closing Date”). If Buyer fails to close on or before the Closing Date, then Seller may treat such failure as a default subject to the terms of…Addendum No. 1…or Seller may, in its sole discretion, determine to extend the Closing Date upon payment to Seller by Buyer of an extension equal to $350.00 per day, but in no event shall such extension extend beyond the twenty-four (24) month period….
***
[Paragraph II(B) of Addendum No. 1.] If Buyer asserts the existence of any…defect in title which renders title to the Unit unmarketable and which Buyer does not waive (all of which are called “Defects of Title”), Buyer shall give written notice of such Defects of Title to Seller within five (5) days after its receipt of the [title] Commitment or at least five (5) days prior to the Closing Date….If Seller attempts to remove or cure such Defects of Title, Seller shall be entitled to a postponement of the Closing for a period of up to thirty (30) days in which to remove or cure such Defects of Title….If Seller is unable or unwilling to remove or cure all Defects of Title within such period, Buyer may elect to waive such Defects of Title or to terminate this Agreement by written notice to Seller within five (5) days after the earlier of (i) the expiration of such thirty (30) days, or (ii) the date of notice from Seller to Buyer stating that Seller is unable or unwilling to cure any such Defects of Title.”

 

The facts in Lowe were not in dispute. The seller notified the buyer on November 1, 2007 that closing would take place on December 6, 2007. The buyer realized that the seller never recorded the Declaration of Condominium (the legal instrument that creates the condominium and renders the units marketable) and notified the seller on November 29, 2007 that title was defective. The seller recorded the Declaration of Condominium on December 20, 2007 and notified the buyer that closing would now take place on February 3, 2008. The buyer, however, refused to close arguing that the seller breached Paragraph II(B) of Addendum No. 1 by failing to close within thirty days after receiving notice that there was a defect in title. The seller, conversely, argued that it had the unilateral right to set the closing date pursuant to Paragraph 4 of the Contract and, therefore, Paragraph II(B) of Addendum No. 1 never came into effect.

 
The Fifth District Court of Appeal held that although the seller had the absolute right to set the closing date through April 16, 2008, once the seller notified the buyer of its intent to close on a set date, Paragraph II(B) of Addendum No. 1 came into effect. Because the buyer notified to seller after the closing date was set that there was a defect in title, the seller was required to comply with the terms of Paragraph II(B). In this case, the seller failed to comply with these terms because it failed to close within thirty days from receiving the buyer’s notice. Accordingly, the Fifth District held that the buyer is entitled to recover his deposit and recoup attorneys’ fees as the prevailing party pursuant to the contract.

 
In the second case, Boynton Waterways Investment Associates, LLC v. Bezkorovainijs, 2011 WL 2694522 (4th DCA 2011), the buyer sought to revoke the preconstruction contract and recover his deposit by arguing that the seller violated the ILSFDA .  Specifically, the buyer argued that because the preconstruction contract failed to include the appropriate legal description of the condominium unit it violated §1703(d) of the ILSFDA, which provides:

 

“Any contract or agreement which is for the sale or lease of a lot . . . which does not provide

(1) a description of the lot which makes such lot clearly identifiable and which is in a form acceptable for recording by the appropriate public official responsible for maintaining land records in the jurisdiction in which the lot is located…

may be revoked at the option of the purchaser or lessee for two years from the date of the signing of such contract or agreement.”

 

Regarding the identification of a condominium unit, §718.109 of the Florida Condominium Act provides, “Following the recording of the declaration, a description of a condominium parcel by the number or other designation by which the unit is identified in the declaration, together with the recording data identifying the declaration, shall be a sufficient legal description for all purposes.” Fla. Stat. §718.109.

 

The buyer argued that because the contract did not contain any recording data for the unit, the contract did not clearly identify the unit in a form acceptable for recording under the ILSFDA.

 

The seller argued that §718.109 does not apply to a preconstruction contract that predates the recording of the Declaration of Condominium. (In this case, no different than most preconstruction condominium transactions, the buyer did receive an unrecorded copy of the Declaration included in the prospectus.)

 

The Fourth District Court of Appeal, agreeing with the Middle District in Taplett v. TRG Oasis (Tower Two), Ltd., L.P., 755 F. Supp. 2d 1197 (M.D. Fla. 2009), averred that Florida allows the sale of condominium units prior to the recording of the Declaration; thus, §718.109 does not apply until the recordation of the Declaration. Since the Buyer received an unrecorded copy of the Declaration with the prospectus which just so happened to be incorporated into the preconstruction contract, the condominium unit was clearly identifiable and in a form acceptable for recording.

 

These cases exemplify some of the arguments that are raised by buyers to revoke preconstruction and purchase-sale contracts.   These cases, however, are a snipet of the many cases involving arguments from buyers to revoke their contracts and recover their deposits.  Before a buyer makes a decision to revoke the contract to recover their deposit, the buyer should discuss their options and arguments with an attorney.  Based on the amount of the deposit (and/or loss of value in the unit from the date of contract), discussing the arguments based on the specific facts of your transaction may be worthwhile. Sellers should also be cognizant of these arguments in order to protect their interests and preserve their right to the deposit.

 

 

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.

PERSPECTIVES ON THE COMPETITIVE (OR NOT SO COMPETITIVE) PUBLIC PROCUREMENT PROCESS

Posted on by

images-1In most circumstances, public entities are required to competitively bid the construction of their projects. Sometimes, competitive bidding is as simple as the public entity publishing an Invitation To Bid (“ITB”) seeking to solicit the lowest, responsible, and responsive bidder. In this solicitation, assuming the bidder is responsible (qualified) and responsive (complies with the invitation to bid in all material respects), the public entity is seeking the lowest cost to perform the construction. The ITB process is commonly referred to as the hard bid process because the public entity knows exactly what it wants and seeks the lowest cost to construct per the plans and specifications.

 

However, seeking an ITB is not the only way a public entity selects a contractor to construct its project. Another common method is the public entity publishing a Request For Proposals ( “RFP”) whereby cost is a factor, but not the only factor in selecting the contractor. A RFP is typically the solicitation when the public entity wants to utilize the experience and sophistication of the contractor to help it determine what specifically it wants. In other words, the public entity wants to resolve a problem and relies on the contractor to submit proposals with the solution and the costs to implement the solution. The public entity then ranks the proposals based on scoring criteria and selects the contractor that has the preferred or highest ranking.

 

Contractors that participate in the public procurement process, whether through the ITB, RFP, or another approved method of procurement, can often feel frustrated with the process based on the wide latitude and discretion that are afforded to public entities in the process. This frustration is exemplified in Pensacola Builders, Inc. v. King, 36 Fla. L. Weekly D1304c (1st DCA 2011), which involved a 13 year old dispute over a public project that was not awarded to the plaintiff contractor. In this case, a public entity was soliciting a contractor to build and operate a concession stand on a pier through the RFP process. The plaintiff was the highest ranked contractor in the process and was in the process of negotiating the contract with the public entity. However, the defendant contractor that also participated in the RFP process wrote letters to the public entity threatening litigation (after apparently missing the deadline to file a bid protest) regarding the manner in which the public entity conducted the RFP. Due to the public entities apparent fear of the threatened litigation, it ceased negotiations with its highest ranked contractor, readvertised for proposals, and then ranked the defendant as its preferred contractor. This naturally was perceived as an injustice to the plaintiff.

 

The plaintiff filed suit against the public entity for breach of an implied covenant of fair dealing based on the public entity readvertising the proposals and selecting the defendant contractor as its preferred contractor. See Santa Rosa Island Authority v. Pensacola Beach Pier, Inc., 834 So.2d 261 (Fla. 1st DCA 2002). The plaintiff’s objective was to force the public entity to reengage in contract negotiations with it. The First District Court of Appeal shot down plaintiff’s lawsuit and objective holding, “Absent evidence of illegality, fraud, oppression, or misconduct, Appellee [plaintiff] is without a remedy for Authority’s [public entity] readvertising for proposals and rearranging the preference order of the parties.” Santa Rosa Island Authority, 834 So.2d at 263. Stated simpler, the plaintiff was out of luck as it is hard to establish the government committed a wrong, even though the public entity readvertised proposals due to threatened litigation from a bidder that apparently failed to timely protest!

 

The plaintiff, however, did not end its pursuit of seeking redress for what it perceived as injustice in the competitive bidding process. The plaintiff creatively asserted claims against the defendant contractor for, among other things, tortious interference with a business relationship and defamation. The plaintiff’s arguments were premised on letters that the defendant sent to the public entity when plaintiff was in the process of negotiating its contract threatening litigation due to the illegality of the RFP process and accusing plaintiff of certain illegal actions. The trial court ruled in favor of defendant on plaintiff’s claims and, unfortunately, because plaintiff did not properly preserve these issues on appeal, the First District Court of Appeal was not in a position to reverse the trial court’s ruling. (Notably, this case demonstrates the importance of preserving all issues and arguments for appeal.) However, had plaintiff preserved these issues for appeal, there may have likely been meat on the bone as to its arguments against the defendant that ultimately got the public entity not to award the contract to the plaintiff, but, instead, to defendant.

 

In an economy where private projects are not as booming as they once were and public projects being a main source of revenue for many contractors, bid protests and/or the threat of litigation are measures that are being strongly considered when a perceived injustice occurs in the public procurement process. Although this case did not work out well for the plaintiff, plaintiff’s arguments are still creative and worthy of merit against another bidder in a similar context that overtly hinders a contractor’s efforts in contracting with the public entity.

 

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.