Tues Tip: “Business” of architecture & engineering

Love your work but hate the “job” portion of it? You know, quoting scope of work, dealing with fees, and getting paid?  If so, check out Milton Gregory Grew’s great article about setting fees that can realistically account for your overhead and other indirect costs, “The Business of Architecture (Oxymoron?)”.

Of  the tips Greg discusses, step #2, “Put it in writing” is key,  as I’ve discussed earlier here.

Moreover, for fee issues, a written agreement is the gold standard.  In a written agreement you can even account for collection costs, higher interest charges, and “reasonable” attorney fees if you later (heaven forbid) have to sue a (former) client for payment of services.  Without a written agreement, you are stuck with statutory limits on what you can recover.

As they say, an ounce of prevention is worth a pound of cure.Gold 1 oz

 ____________________________

Photo “Gold1oz” by Olegvolk via Creative Commons Attribution 2.5 license.  

Design Error and the Spearin Doctrine (Law note)

engineering plansDesign Error.  Two words that strike fear into the heart of any architect, engineer, or lawyer representing them.  Today’s post discussion is to discuss the different obligations of each of the parties on a construction project relating to design errors.

As discussed last week, designers have an obligation to design in accordance with a reasonable standard of care.  That does not mean that the plans and specifications are perfect, however.

While the contractor is not responsible for design errors, he does have a duty to report any design errors or omissions which he discovers during his review of the plans.  If he discovers any design errors, he must report them to the owner.  See, for example, AIA A201 3-2.2.

As we have also discussed, an owner also impliedly warrants the adequacy of the plans and specifications .  This is sometimes known as the “Spearin Doctrine,” after the seminal Supreme Court  case, US. v. Spearin, 248 U.S. 132 (1918).   In Spearin, a contractor sought to recover from the government for the government’s failure to provide accurate plans reflecting the overflow issues which preexisted at the Brooklyn Navy Yard,   The Court held:

[I]f the contractor is bound to build according to plans and specifications prepared by the owner, the contractor will not be
responsible for the consequences of defects in the plans and specifications, (Citations omitted). This responsibility of the owner is
not overcome by the usual clauses requiring builders to visit the site, to check the plans, and to inform themselves of the requirements of the
work. The duty to check plans did not impose the obligation to pass upon their adequacy to accomplish the purpose in view.

Id. at 136-137. The Spearin Doctrine has been faithfully followed in the North Carolina courts. See, e.g., City of Charlotte v. Skidmore, Owings and Merrill, 103 N.C, App. 667, 407 S.E.2d 571 (1991); Burke Co Public School Bd of Education v Juno Construction Corp, 50 N.C App. 238, 273 S.E,2d 504 (1981).

One state court held, “[i]t is simply unfair to bar recovery to contractors who are mislead by inaccurate plans and submit bids lower than they might otherwise have submitted.” Battle Ridge Companies v. North Carolina Dept. of Transportation, 161 N.C. App. 156, 160, 587 S.E.2d 426 (2003), quoting Lowder v. Highway Comm., 26 N.C, App, 622, 638, 217 S.E.2d 682, 692, cert denied, 288 N.C. 393, 218 S.E.2d 467 (1975).

Obviously, the architect or engineer is the ultimate party responsible for design errors, but all parties play a role in identifying and minimizing the effect of such errors through prompt notification.

________________________

Photo “pipes” by moonlight on celluloid via Flickr via Attribution-Noncommercial-ShareAlike 3.0 License.

Even Subcontractors can sue other Prime Contractors Directly on State projects (Law note)

While we have previously looked at direct contractor-to-contractor lawsuits and contractor-to-design professional lawsuits, I have said very little about the role of subcontractors in the multi-prime system.

In the Bolton case addressed earlier, Bolton made a claim against another prime contractor on behalf of itself and its subcontractor.  

However, in 2004 the Court of Appeals dealt with the issue of a subcontractor making a direct claim against a prime contractor other than the contractor for which the sub performed its work.  Pompano Masonry Corporation v. HDR Architecture, Inc., 165 N.C. App. 401, 598 S.E.2d 608 (2004).

That case involved the Biological Science Research Center at UNC-CH .  HDR was the “project expeditor” under a separate contract with UNC, responsible for preparing the project schedule and coordinating work between the prime contractors.

Metric Constructors served as the prime general contractor, and Pompano Masonry was a subcontractor to Metric.  Pompano sued HDR directly as the project expeditor, and the court allowed the case to proceed, holding that subcontractors to prime contractors could sue other prime contractors directly.

The court held that HDR could be sued directly by a subcontractor to which it had no contract for economic injury resulting from its alleged negligent performance of its duties as project expediter.  Citing its earlier decision in Davidson, the court held that liability exits due to the “working relationship” and “community of interests” despite the fact there was no contractual privity between Pompano and HDR.

 Conclusion

The moral of the story with regard to this series of cases?  Never assume that you cannot be sued by someone because you don’t know them, you have no contract with them, you are a licensed professional, or they are on a different “tier” than you on the project.  You have duties to all parties on a construction project, and the multi-prime statute in North Carolina gives yet another arrow in the litigator’s arsenal which could be pointed at your chest.

Are you having fun yet?  Next blog post will be on a less “scholarly” topic, I promise!

Statutory liability of Architects and Engineers to Contractors on State Construction projects (Law note)

As noted in my last post, the state multi-prime bidding statute provides for liability between separate contractors on state projects.

 A specific case from the Middle District Court of North Carolina (federal court), interpreting state law, further extended this liability to architects and engineers on state multi-prime projects.  RPR & Associates v. O’Brien/Atkins Associates, P.A., 24 F. Supp. 2d 515 (M.D.N.C. 1998).

 In that case, which involved the George Watts Hill Alumni Center at UNC-Chapel Hill, the court held that an architect and consulting engineer could be held accountable to contractors who rely on their work on North Carolina construction projects based on the same statute as that imposing liability on multi-prime contractors on one another.

 The issue in the RPR case was whether the statute applied to architects and engineers, since they are not “prime contractors” under the North Carolina multi-prime contracting statute.  The RPR court held that for purposes of the statute, design professionals were “separate prime contractors” such that they could be sued directly by prime contractors on state jobs.

 While this case is now over a decade old, it still surprises many design professionals who incorrectly assume that since they are not one of the enumerated prime contractors that they are not subject to statutory liability to the prime contractors.

In my next and final (for the time being) post on this subject, I will address the application of the statute on subcontractors.

 

Contractors liable to other prime contractors on state construction projects in North Carolina (Law note)

As we discussed in the last blog post, the state legislature created the multi-prime system for many state construction projects.

One of the first cases to deal with the statute allowing contractors to sue each other is Bolton Corp. v. T.A. Loving  Co., 94 N.C. App. 392, 380 S.E.2d 796, disc. rev. denied, 325 N.C. 545, 385 S.E.2d 496 (1989)

In that case, which involved the construction of an 8 story library on the UNC-CH campus,  a HVAC prime contractor, Bolton, sued the project expeditor, TA Loving, for Loving’s breach of its contract with the State.  Bolton brought the claim on both its own behalf and on behalf of its subcontractor.

 The court allowed the suit, not based on tort, but based on the multi-prime statute (N.C. Gen. Stat. §143-128).   The court held that a prime contract can be sued directly by another prime contractor working on a state construction project:

We interpret N.C.G.S. § 143-128 to mean that a prime contractor may be sued by another prime contractor working on a construction project for economic loss foreseeably resulting from the first prime contractor’s failure to fully perform “all duties and obligations due respectively under the terms of the separate contracts.”

In my next post, I will discuss the application of this concept to design professionals.