Not every case law you read makes sense. This sentiment goes to the uncertainty and grey area of certain legal issues.  It is, what you call, “the nature of the beast.”  You will read cases that make you say “HUH?!?” This is why you want to work with construction counsel to discuss procedures and pros / cons relative to construction liens.

An example of a case that makes you say “HUH” can be found in Woolems, Inc. v. Catalina Capstone Creations, Inc., 2023 WL 2777506 (Fla. 3d DCA 2023) dealing with a construction lien foreclosure dispute.

Here, a contractor filed a lawsuit against a subcontractor with a summons to show cause why the subcontractor’s construction lien should not be discharged.  This is a specific complaint filed under Florida Statute s. 713.21(4). This statute requires the lienor to essentially foreclose on its construction lien within 20 days after it was served with a “show cause” summons.  The subcontractor filed its answer and counterclaim but did NOT assert a claim to foreclose its construction lien.

Around the time of subcontractor’s answer and counterclaim, the contractor transferred the subcontractor’s lien to an all-cash lien transfer bond in accordance with Florida Statute s. 713.24. Once the lien transfer bond was recorded, the owner recorded a notice of contest of lien under Florida Statute s. 713.22. The notice of contest of lien shortens the limitations period to foreclose on a lien to 60 days.

The subcontractor did NOT timely foreclose its lien against the lien transfer bond and the general contractor moved to have its all-cash lien transfer bond returned, as it should do. The subcontractor filed its lien foreclosure against the lien transfer bond AFTER the 60-day window expired. The trial court, and affirmed by the appellate court, denied the general contractor’s request to have the lien transfer bond returned and allowed the subcontractor to assert its (dilatory) claim against the lien transfer bond claiming it related back in time to the subcontractor’s initial counterclaim.  HUH?!?

ISSUES GIVING RISE TO THE HUH

Here are the issues with this ruling:

1. The subcontractor should have foreclosed its construction lien with the 20-day time period from receiving the summons to show cause. The case reflected the subcontractor asserted claims, but not the lien foreclosure claim subject to the summons to show cause. (The appeal did not discuss this point for reasons currently unknown.)
2. Regardless of (1), the lien was transferred to a bond and a notice of contest of lien was recorded shortening the time period to foreclose the lien (as to the bond) to 60 days. There is case law referencing this procedure. Yet, the subcontractor still did not timely assert its claim against the lien transfer bond.
3. The trial court applied the relation back doctrine which does nothing but completely water down the statutory purpose of a notice of contest of lien (not to mention the summons to show cause complaint).

RECOMMENDATIONS IN LIGHT OF RULING

In light of this ruling, here are my recommendations:

1. If you are going to transfer a lien to a lien transfer bond, do it from the get-go. Then, record the notice of contest or pursue the summons to show cause complaint.
2. If filing the summons to show cause complaint, wait for the 20-day time period to expire. If the time period expires, move to have the lien discharged before making the decision to transfer the lien to a lien transfer bond.
3. If recording a notice of contest of lien, wait for the 60-day time period to expire before taking action.

The reality is that the procedure implemented in this case should have been fine but for the application of the relation back doctrine that makes you say HUH?!?

As mentioned, if dealing with a lien, please make sure to discuss strategic considerations with a construction counsel that can help navigate the process and advise on the pros and cons.

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.