Category Archives: Law Notes

NC State Construction projects– Privity, Multi-Prime Contracts, and the Ability to Be Sued by Parties You Don’t know (Law note)

Posted on by

At the recent seminar on construction law in North Carolina, I was asked whether parties could be sued by other parties on state construction projects when there is no contract between those parties.  The answer is yes. In the following series of blog posts, I will address three major cases which address this question in several different permutations.

For today’s post, I will discuss contractual privity, the multi-prime statute, and how the two apply on North Carolina state construction projects.  In later posts, I will discuss the application of that statute to different parties in the construction context.

Multi-prime contracts

In North Carolina, the state entity who is the owner of the construction project must bid the project pursuant to one of several designated ways.  One common method sometimes required of public bidding is the “mulit-prime” contract, in which the State has at least 4 separate contracts, for:

(1) Heating, ventilating, and air conditioning

(2) Plumbing and gas fittings

(3) Electrical wiring and installations

(4) General construction relating to erection, alteration, or repair on public property

N.C. Gen. Stat. §143-128(a). 

The purpose of the multi-prime statute is two-fold:

  1.  It encourages lower bids by preventing pass-through cost mark-ups to the state
  2. It allows smaller specialty contractors to enter bidding directly with state without having to have a working relationship with a general contractor, thereby opening up state jobs to a wider array of potential contractors
Contractual Privity

 In general, contractual privity is required to sue another entity on a construction project—that is, you have to be in a contractual relationship with the party you are suing.  There are exceptions to this rule.  For example, you can be sued in negligence for property and personal damage by a party that you do not have a contract with.  (See my post discussing the architect’s liability for economic loss  resulting from breach of architect’s common-law duty of due care  ).  In addition, the state legislature has provided the ability for contractors to sue one another, or other entities involved in the construction project, without having to sue the owner or deal with the State Construction Office.

 NC statute on liability:

Each separate contractor shall be directly liable to the State of North Carolina, or to the county, municipality, or other public body and to the other separate contractors for the full performance of all duties and obligations due respectively under the terms of the separate contracts and in accordance with the plans and specifications, which shall specifically set forth the duties and obligations of each separate contractor. For the purpose of this section, “separate contractor” means any person, firm or corporation who shall enter into a contract with the State, or with any county, municipality, or other public entity to erect, construct, alter or repair any building or buildings, or parts of any building or buildings.

N.C. Gen. Stat. §143-128(b).   [Emphasis added].

This statute has been interpreted over the past decade to allow essentially any party to sue any other party directly on state construction projects.  In the next blog post, I will discuss the first of three major cases dealing with this issue.

How Long Should My Construction Contract Be?

Posted on by

The answer, as is always the answer when you ask an attorney a question, is “it depends.”  Lawyers don’t say “it depends” just to drive clients mad—really, we don’t.  The thing is, lawyers, by their very nature, are cautious.

Lawyers want to plan for all situations and possibilities.  Likewise, a construction contract can become an unwieldy document that only a lawyer could love, as it provides for all conceivable areas of dispute and all possible contingent situations.  Such a contract does no one much good.

The best contract for you is the contract that is appropriate for your construction project and the players in that project.  If the project is a multi-million dollar, multi-year project, you probably should not skimp on having a well-crafted, attorney-vetted contract specific to your deal.  If, on the other hand, the project is a one-day residential job, you can get by on much less.

Do not assume, however, that just because a contract is small in terms of dollars or man-hours that you do not need a contract. You do. (See my earlier post on the importance of a written contract.) Paradoxically, some of the most hotly contested lawsuits involve homeowners.  After all, their home is their castle.

In fact, a house is usually the single largest investment decision that most people will ever make, often involving a mortgage that may take as many as 30 years to pay off.     It is only natural, therefore, that homeowners will be extra exacting when it comes to issues relating to their home.

To go back to the original question—how much contract you need depends very much on the situation.  A two page, simple contract may be sufficient for your purposes, if it is carefully crafted to account for all common areas of dispute which may arise.  It is vital, however, that you have one, and that it is in writing.

Of Mice and Men: Yes, you need a written construction contract!

Posted on by
Field mouse

Photo by delphywnd via Flickr*

 

Does a written contract *really* matter?   Yes; yes it does.

While you can get by for years- decades, even- on handshake deals—when something goes wrong you will wish you had a written contract.  Even the best projects, with familiar clients and trusted contractors, can go awry.  (“The best laid plans of mice and men often go awry”).

Many of my clients come to me after having been in business 20, 30 years or more.  They come to me because they have either already been sued, or the handwriting is on the wall and they are about to be brought into litigation.  They tell me they’ve never needed a written contract before now.  That’s well and good.  However, I’d bet dollars to donuts those same folks have fire insurance, and yet very few if any of them have actually experienced a house fire.  What’s different about business contracts?

The goal, of course, is that you will never need to rely on the written provisions in your contract.  But if you ever find yourself facing a lawsuit, you’ll wish you had a written contract.

A written contract spells out expectations, rights, and responsibilities.  It sets standards that may be understood by the parties, but very different from what the common law would allow.  Without a written contract, you are trusting yourself to laws you may not agree with or giving up protections you may otherwise have.  Why chance it?

Get something in writing—a signed proposal, an email which is confirmed—something that spells out basic agreements that might come into dispute later.  A thorough contract written for each project is ideal, though not always practical on smaller, quick-turn deals.  That’s fine.  But get something on paper.  You’ll be glad you did, if and when you ever find yourself on the courthouse steps.

 ————–

*Photo: Have you seen the Muffin Mouse by delphwynd via Flickr and made available via Creative Commons license.

NC Construction Law Seminar in Greensboro

Posted on by

Excuse the little self-promotion here, but if you want a quick way to learn more about construction issues in North Carolina, I’m speaking at a seminar on May 7, 2010 in Greensboro, NC.

The seminar topics include:
* Understanding Liens, Bonds, and Payment Issues
* Risk Transfer (including insurance and indemnity issues)
* Making Changes & Resolving Disputes during the Construction Process
* Contracts and Subcontracts on Public Projects
* Recent Bankruptcy Cases Impacting Contractors’ Lien Rights

The seminar qualifies for 6.0 PDHs for NC Engineers, 0.6 CSI CEUs, and NC Attorney CLE credit is pending.

Joining me in speaking are Eric Biesecker, Jennifer Maldonado, and Brian Edlin. For more details or to register, go to Half Moon Seminars.

What is not in your construction contract can be just as important as what is in the contract

Posted on by

excludedEver wonder why lawyers like to write contracts that seem to go on, and on, and on? By nature, lawyers are doomsayers. We try to minimize risk, and sometimes that takes the form of a contract that “only a lawyer could love”.

We will cover important contract terms in future blog posts, but for now, did you know that what is not in your construction contract is just as important as what is in there? Many times the heart of a construction dispute stems from confusion or mistaken assumptions about what, exactly, was agreed upon.

In addition to having a very detailed “Scope of Services,” in which you specify exactly what you will be doing on a project, you should also develop a standard “Exclusions from Services” list, and that list should be a part of every contract.

Such an exclusion list should include:
— anything you were specifically asked not to perform
— anything the owner indicated was to be provided by others
— anything which involves specific contractor coordination (unless
you are providing this service)
— a listing of anything above and beyond normal conditions (for
example, “attendance at more than X meetings a month”)
— a general “catch all” statement that anything not specifically
specified in the Scope of Services is not covered

Of course, what specific things should be listed in your Exclusions list depends on what field of construction you are in. Design professionals need to focus on coordination issues, duties with respect to other design professionals on a large project, duties relating to oversight of contractor work, and related issues. Contractors should focus on their responsibility to work with and/or around other trades as well as related work that the owner does not intend to pay for which can result in scope creep.

While it might seem like wearing belts and suspenders at the same time to write out a Scope of Services and also include an Exclusion from Services list, the minimal extra effort in developing such an Exclusion list will pay you back in volumes should a dispute on the project ever arise.

Photo (c) Markus Spiske.