The international news resource for industrial & municipal water professionals
Contract negotiations require that the terms be spelled out and thoroughly understood
By John P. Bachner January 1, 2007
A contract comprises a set of promises -- set out in writing and
enforceable by law -- usually made by two parties, each to the other.
Generations of fledgling project managers have groaned their dislike of contracts and learning about them. While most begrudgingly acknowledge that contracts are essential, many fail to realize how vital they really are.
Imagine what would happen if the parties to contracts were unable to enforce reasonable, legal terms. A promise would only be as good as its maker's willingness to live up to it, thus converting the rule of law to the law of the jungle. In fact, it's not overstating the case to say that contracts are the linchpin not only of the United States' economic system, but of the world's system -- and not just economic systems -- think about marriage contracts, international treaties, and other related contracts.
At its root, a written contract serves to memorialize mutual understandings. Realistically, there is no reason for a contract to be anything but fair. Unfortunately, all too many of them are unfair, leading to a variety of unfortunate outcomes.
Essential Contract Elements
I'm most familiar with contracts between an owner, such as a water authority, and a consultant retained to design a new facility or expand or update an existing one. In an ideal world, such contracts comprise six elements:
Although people often roll their eyes whenever a contract exceeds two or three pages (explaining why long contracts tend to be written in a type size even an ant would need "cheaters" to read), longer contracts almost always are better, because they provide more explanations and definitions, especially when they're written (as they should be) in "plain" (nonlegalese) English.
Many attorneys will not provide that advice, because they're unaware of the rough-and-tumble business their clients actually are involved in. In essence, they're just too inexperienced to understand that, as air-tight as some contractual provisions may seem, when it comes right down to it, those provisions are just words.
Here's an example of the type of provision I'm talking about. If you represent an owner, it's time to change this one-sided contractual condition that is heavily weighted against the consultant (without losing any reasonable protection). And if you represent a firm that ordinarily would accept the requirement, it's time for that firm to join ASFE/The Best People on Earth! The provision in question involves use of the word "defend," as in:
CONSULTANT agrees to hold harmless, indemnify, and defend CLIENT from any losses arising from CONSULTANT's negligent performance of its services.
This provision requires the consultant to defend the client if the consultant is accused of professional negligence, even though the claim might be meritless. How could such a situation arise? Easily. Party A sues the client -- a public agency, say -- alleging that the agency has caused damage by virtue of an activity in which the consultant was involved. This causes the client to sue the consultant, alleging it was the consultant's negligence that created the situation that caused Party A to file its claim. And that being the case, the consultant would be required to defend not only itself, but its client as well.
That situation puts the consultant in a huge "one-down" position: While its PLI would cover its own defense costs (less the deductible), the insurance would not cover the cost of the client's defense if, in fact, the client's damages were not caused by the consultant's negligence, or if it were found that the client did not damage Party A.
It's All in the Wording
Now, suppose the consultant was negligent and, as a consequence of that negligence, the client had to pay money to defend itself. Am I advocating that the client should bear that expense? Not at all. One could cover that exposure with wording such as:
CONSULTANT agrees to hold harmless and indemnify CLIENT from losses arising from CONSULTANT's negligent performance of its services, such losses to include, but not be limited to, a proportionate share of CLIENT's reasonable attorney's fees and other reasonable defense costs.
This is a completely fair provision, because it requires the consultant to pay a proportionate share of defense costs if it's found negligent; that is, were the consultant adjudged to have been 70 percent at fault for a loss, it would have to pay 70 percent of the client's damages, including 70 percent of the client's reasonable defense costs. Because if those defense costs would be considered damages, they would be covered by the consultant's PLI. (It's also fair when one considers that the consultant's share of defense costs is likely to exceed the consultant's fee, and that a consultant generally needs to earn $10 in order to generate the $1 profit required to pay for an expense; that is, consultants commonly have to generate $500,000 in fees to cover a $50,000 deductible. Even when fairness prevails, acceptance of a commission exposes a consultant to a loss risk 10 or more times greater than the consultant's fee, and 100 or more times greater than the benefit profit the consultant hopes to derive from fulfilling the commission.)
To require a consultant to face such a risk even when it has performed in a wholly satisfactory manner is grossly unfair, and an astute firm is not likely to accept the bargain unless it can somehow modify the risk without being caught (which, thanks to conservative and, thus, far more costly-to-construct design, is not that difficult a trick). In the event a client insists on its "defend" language, an alternative provision might be:
To the extent of CONSULTANT's negligence, CONSULTANT agrees to hold harmless, indemnify, and defend CLIENT from losses arising from CONSULTANT's negligent performance of its services.
Unfortunately, a provision like this is not very good because it probably would be subject to differing interpretations. Clearly, the consultant would interpret it to require reimbursement of the client's legal costs to the extent of the consultant's liability. Given that, at the outset of the claim, the consultant would claim zero negligence, it would cover zero percent of the client's defense costs. If the consultant paid anything at all, the amount would/could be determined only after it was decided that negligence actually occurred. But the client would probably say the provision required the consultant to pay its defense costs "from the get-go" with the possibility -- a contestable one -- that it might have to reimburse the consultant if it's subsequently found the consultant was less than 100 percent at fault or not negligent at all.
Were I an owner's representative, I'd certainly want an attorney to offer these various alternatives to me, providing the attorney explained each and discussed the problems they could generate, in addition to the benefits. If I recognized the potential problems while fully endorsing the language for its potential (unfair) benefits, so be it. My lawyer and my consultant would be on the same side of the fence for a change: Both would have a fool for a client.
This Why Risk It? column originally appeared in the January/February 2007 issue of Water & Wastewater Products.
About the author
John P. Bachner
John P. Bachner is executive vice president of ASFE/The Best People on Earth. He authors several columns for engineers and allied professionals and is a frequent seminar leader and instructor. ASFE is a not-for-profit trade association comprising geoprofessional, environmental, and civil engineering firms, design/build contractors, and educators.
American Rivers, a river conservation organization, recently commended the Georgia Environmental Facilities Authority for promoting water efficiency as the first source of supply in its recently released study,