How do Utah courts distinguish between contractual covenants and conditions? Mind & Motion v. Celtic Bank Explained

The Utah Supreme Court’s decision in Mind & Motion v. Celtic Bank provides essential guidance for practitioners on distinguishing between covenants and conditions in contract interpretation. This distinction carries significant legal consequences, as covenants create enforceable duties with breach remedies, while conditions merely trigger performance obligations without creating liability for non-occurrence.

Background and Facts
Celtic Bank acquired property through foreclosure and entered into a real estate purchase contract with Mind & Motion. The contract required Celtic Bank to record condominium plats by a specified deadline, using language stating the bank “shall record Phase 1” and “agrees to complete recording.” When county approval delays prevented timely recording, Mind & Motion declined to extend the deadline again and sued for breach. The district court granted summary judgment for Mind & Motion, finding the recording provision was a covenant.

Key Legal Issues
The central question was whether the recording obligation constituted a covenant (creating enforceable duties) or a condition precedent (merely triggering performance). Celtic Bank argued the provision was a condition because recording depended on third-party county approval. The court also addressed whether latent ambiguity existed based on subjective affidavits from Celtic Bank officers.

Court’s Analysis and Holding
The Utah Supreme Court applied correctness review and affirmed the district court’s ruling. The court emphasized that mandatory language like “shall” and “agrees” creates covenants, particularly when contrasted with explicitly conditional language used elsewhere in the same agreement. The court rejected Celtic Bank’s argument that third-party control over timing converted the obligation into a condition, noting that parties can assume regulatory risks through express contractual language. The court also declined to consider subjective affidavits as evidence of latent ambiguity, requiring instead objective evidence of collateral matters that render terms unclear.

Practice Implications
This decision reinforces the importance of precise drafting when creating conditions precedent. Courts will interpret mandatory language as creating enforceable covenants even when performance depends on third-party actions. Practitioners should use explicitly conditional terms like “if,” “unless,” or “provided that” when intending to create conditions. Additionally, parties cannot create ambiguity through post-hoc subjective interpretations; latent ambiguities require objective evidence of collateral matters affecting contractual terms.