Every Word Counts: Critical Lessons in Contract Language
The failure to adequately address issues in a contract is often a cause of later frustration, disagreement and even legal actions between contracting parties.
Related Content
Stories
Related Terms
Disputes are an unfortunate part of construction. Complex projects invite disagreement, and while most disputes are resolved by the project participants, a very few end up in court or arbitration. To that end, anyone who has gone through the painful process of allowing third parties such as arbitrators, judges or juries who were not involved in the project, to decide a dispute will tell you that contract language takes on a whole new meaning when disputes are decided by people who were not involved in the project.
Contracting parties often pay little attention to contract clauses - until disputes arise. A recent decision of the North Carolina Court of Appeals, Cleveland Construction, Inc. v. Ellis-Don Construction, Inc. et al, ____ S.E.2d ____ , 2011 WL 1238364 (N.C. App. 2011), focused on several issues that arose between the general contractor, Ellis-Don ("ED") and one of its subcontractors ("CCI") on a hospital construction project ("Project"). At the completion of the Project, ED had submitted a claim for extras, delay and inefficiency to the Project's owner and architect, and had eventually settled the claim. Prior to submitting the claim, ED had solicited claims from many of its subcontractors, including CCI, and those subcontractor claims were included in what ED presented to (and ultimately settled with) the owner and architect. The issue in the ED/CCI lawsuit was how much, if any, of the settlement proceeds should be paid to CCI.
As any experienced construction professional knows, "pass-through" claims, in which the general contractor essentially "sponsors" a subcontractor's claim to the owner, are common on construction projects. The handling of such claims (who controls the processing, how money obtained by settlement or judgment is distributed among the participants in the claim, payment of attorney and expert witness fees and more) is often addressed in the subcontract. If not addressed in detail there, these issues are almost always addressed in a liquidating agreement, a document signed by the parties once claims are imminent containing the specifics on the handling of claims. The goal is to make sure that once the claim is resolved between the general contractor and the owner, the general and the subcontractor do not end up in their own fight over who gets how much of the proceeds. The CCI v. ED case illustrates what happens when the parties are unable to reach an agreement on these issues.
The subcontract between ED and CCI stated that CCI could only recover on account of delay and inefficiency if ED decided to pursue such claims from the owner and/or architect and actually recovered money. As noted above, ED did recover from the owner and architect, but the settlement proceeds were not allocated, the subcontract did not specifically address how much of the settlement funds belonged to CCI, and the parties never entered into a liquidating agreement. When the parties were unable to settle on an amount, they went to court.
After a 16 day trial, a significant judgment was entered in favor of CCI. However, the judgment was reduced by an amount that the Court felt was "fair" to compensate ED for having pursued the claim in the first place. In other words, the Court concluded that CCI should contribute to ED's costs of having pursued the claim since, absent that pursuit, there would not have been any recovery in which CCI could share.
When ED appealed the underlying judgment in CCI's favor, CCI cross-appealed on this single issue, arguing that since the subcontract did not require CCI to share in the costs of pursuing the claim and there was no liquidating agreement, the trial court erred in reducing the judgment to require CCI to pay its "fair share" of the claim pursuit costs. The North Carolina Court of Appeals agreed with CCI and reversed the trial court on this issue.
- « Previous Page
- 1
- 2
- Next Page »

