Skip to content

Direct vs. Consequential: Why precise contract language matters

August 25, 2025

When entering into a construction contract, it is important to understand and account for the differences between direct damages and consequential damages, as these differences can determine what damages may be recoverable.

Direct damages, sometimes referred to as general or proximate damages, follow from the type of breach alleged or the damages that directly, immediately, and naturally result from the act complained of. Direct damages compensate for the value of the promised performance and are typically limited to expectation damages, which measure what it would take to put a party in the same position that it would be in had the breaching party performed as promised under the contract. For example, many states permit the recovery of the cost incurred to retain another contractor to complete or correct defective construction work as expectation damages.

Consequential damages include damages that do not directly flow from the breach of contract. Consequential damages are derivative or collateral losses beyond the immediate scope of the contract, and include costs that a party might not have incurred if the breaching party had not breached the contract, but they are not part of what such party was originally supposed to get from the breaching party. Some common examples of consequential damages include lost profits, loss of use, lost rental income, additional payments to contractors due to delays, additional administrative costs, diminution in value, financing costs, rental expenses, and reputational damage.

The distinction between direct and consequential damages can be critical because many contracts, including widely used forms such as the AIA, contain clauses that waive the right to recover consequential damages for claims or disputes arising on a project. In the event of a breach, such a waiver clause would leave direct damages as a party’s only avenue for recovery. Unfortunately, many contracts do not define or list specific examples of consequential damages in conjunction with such waiver clauses, which creates uncertainty for parties by leaving the task of categorizing the different types of damages claimed to the courts.

The importance of the distinction between direct and consequential damages, and the impact of such a waiver clause, were illustrated in a recent decision in Florida. In Orlando Health, Inc. v. HKS Architects, Inc., the owner sought to recover over $5.5 million in repair costs from an architect that the owner incurred due to the defective plans, including costs for repairing a slab, adequately supporting an overhang, evening out a floor, reinforcing beams, and demolishing and reinstalling previously completed work, and costs for peer review services, site visits, and extended project management costs. The parties’ contract contained a non-specific waiver of consequential damages, and the Court found that the owner’s costs of remediation and repair were not consequential damages because the need for extensive repairs arose within the scope of the immediate transaction between the owner and the architect and the costs to repair and remediate were direct, natural, logical, and necessary consequences of the architect’s deficient plans.

The Orlando Health case illustrates the importance of understanding the differences between direct and consequential damages during contract negotiations. From an owner’s perspective, this case illustrates the possibility of recovering repair costs incurred to fix problems caused by design defects, even in cases involving a contractual waiver of consequential damages. For design professionals and contractors, this case illustrates the risk that could potentially be avoided with a robust and explicit waiver of consequential damages.

This publication is intended for general informational purposes only and does not constitute legal advice or a solicitation to provide legal services. The information in this publication is not intended to create, and receipt of it does not constitute, a lawyer-client relationship. Readers should not act upon this information without seeking professional legal counsel. The views and opinions expressed herein represent those of the individual author only and are not necessarily the views of Clark Hill PLC. Although we attempt to ensure that postings on our website are complete, accurate, and up to date, we assume no responsibility for their completeness, accuracy, or timeliness.

Subscribe for the latest

Subscribe

Related

Event

Webinar: Special Education Bootcamp - Compliance Foundations Under IDEA

Whether you are new to special education leadership or looking to reinforce your foundational knowledge, this interactive webinar will provide a comprehensive overview of the core compliance requirements under the Individuals with Disabilities Education Act (IDEA). Designed for school leaders who are responsible for ensuring legally sound practices, this session will offer practical tools and strategies to help participants navigate common procedural and substantive pitfalls, support sound decision-making, and build a compliant and student-centered special education program.

Explore more
Event

Telehealth Week Webinar 2025: Navigating Legal Changes and Future Trends for Healthcare Providers

Join Paul Schmeltzer, Carrie Foote, and John Howard for our one-hour annual Telehealth Week webinar, focused on the evolving legal landscape of telehealth. This session will cover key topics, including the upcoming DEA final rule on prescribing controlled substances via telehealth, federal reimbursement concerns for telehealth, and what healthcare providers need to prepare for other upcoming changes.

Explore more
Event

2025 Cybersecurity and Data Privacy Laws Summit

Join us for an immersive half-day seminar exploring the rapidly evolving landscape of cybersecurity, data privacy, and AI-related regulation. This year’s summit will feature dynamic discussions with industry leaders, offering practical insights into the tools, tactics, and legal implications shaping incident response and AI accountability in 2026 and beyond.

Explore more