Explain It Simply
"If you can't explain it simply, you don't understand it well enough." - Albert Einstein
The building industry is terrible at explaining how it does what it does. And this is coming from a guy who has a Bachelor of Science in Construction Management! It’s so bad that I was once working on a construction litigation matter and needed the most basic of organizational charts to explain to a jury the most common roles, relationships, and responsibilities of the various parties involved in a typical construction project; but there was none to be found. I would have loved to have had a reliable source like American Institute of Constructors, The Construction Specifications Institute, the American Institute of Architects, or some similar organization to rely on, to tell my story to the jury. I searched and searched and there was just nothing simple enough to use for a group of people with no construction experience. Everything was overly complex, attempting to account for every possibility. So I locked myself in my office alone one weekend with a pile of flip-chart paper and made iteration after iteration, and finally I nailed it. That was more than a decade ago. Since that time almost every trial or arbitration I have testified in has included some version of this org chart to explain the roles of the parties to one another and to the physical work.
The Contracting 101 Framework
- An Owner wants a project, similar to anyone who wants to buy something, such as a car, but with a construction project the product being purchased is not something that is already built.
- The Owner goes to an Architect (or in some cases a non-architect designer) to translate his/her desires into a set of documents. This process is intended to “define” what the Owner wants to buy (often from a General Contractor).
- The Architect works with Specialty (Sub) Designers such as structural engineers, mechanical engineers and interior designers to further detail the Plans and Specifications (also referred to as Construction Documents) because buildings are so complex that many specialized professionals are required.
- The Plans and Specifications are sent to qualified and interested General Contractors, who submit proposals to the Owner. Ultimately the Owner and a General Contractor compose an Agreement (or Contract).
- An Agreement for construction is simply a promise by the Contractor to deliver what is described in the Plans, Specifications, and other contract documents, and a promise by the Owner to pay for it.
- The Agreement refers to the Plans & Specifications and should include clear definition of the Scope, Budget, and Schedule, including at Scope of Work document that includes: Inclusions and Exclusions, Allowances, a provision for handling Change Orders. The Agreement should include a Schedule of Values and Payment Milestones (for management of the Budget). And finally, the Agreement should include a Progress Schedule.
- GCs usually hire specialty trade contractors, commonly referred to as Subcontractors when they are working for a prime (or general) contractor, who are specialists in their respective trades, to help deliver what has been promised in the Agreement. This is, again, because buildings are so complex that many specialized professionals are required.
- There is nothing in this scheme that prohibits the Owner from directly hiring Specialty/Trade Contractors (that are called Subcontractors if they are working for a General Contractor) for work that is not in the Scope of Work in the Agreement with the GC. In this situation they are Prime Trade Contractors.
- Most of the Subcontractors, and Prime Trade Contractors, have their own suppliers and subcontractors: these are called Sub-Subcontractors. (See diagram below)
Using the Contracting 101 Framework
So the point of the Contracting 101 Framework is to foster understanding of the project at hand. Begin by printing the diagrams above and writing the names of the project players over the generic descriptions. Virtually every project will be different than the Contracting 101 Framework, so you might have to compose multiple iterations, moving the boxes around to fit the peculiarities of your project. I often do this in my office where we have multiple whiteboards and I move back and forth from one to the next until I get my organizational chart to accurately reflect the complexity of the roles and relationships of the current situation. The "compare and contrast," from the simple "Contracting 101 Framework," to the complexity of the real world, is often incredibly instructive.
Sample Project: Custom Single Family Residence
This project was a train wreck.
The Architecture firm and the General Contracting firm were both owned by the same person, but the Owner did not know that (which is unethical and illegal without following strict consent laws). By the time the Owner tried to get control of the project, the two firms had taken $3.5 million dollars to turn a $2.9 million home (initial purchase cost) into a lumber pile. The contract called for distinct design phases but the design was never finished, and it called for the Architect to serve as the Construction Administrator (Owner Representative), but that was a sham since the entities are so closely related and have employees who work for both businesses. The construction work, based on an incomplete design, was executed negligently at inflated prices. The construction work onsite should have been halted long before it was. When the Owners finally asked for a legitimate halt to the construction work, to sort our a plan to go forward, both entities terminated the agreements (using the same lawyer) and engaged in a scorched-earth litigation policy that ensured the maximum economic damage possible from this terrible situation.