Forms in Specifications

To Unregistered Guest:

Disagree with me about what? Don’t shoot the messenger! Some selected excerpts from the MOP SP/050 (for those that don’t want to drag it out):

*The Project Manual contains the bidding requirements, contract forms, conditions of the contract, and specifications.

*Generally, the following tasks should be performed in this order:
Review Owner A/E agreement
Request information from owner on contract, insurance, bonds
Review proposed Owner/Contractor agreement
Review proposed general conditions of the contract
Prepare supplementary conditions to modify general conditions in order to coordinate conditions of the contract with specific requirements of the agreement
Prepare Division 1 Gen Reqs
Send proposed conditions of contract and Div 01 to owner and consultants for review.
Prepare specifications

Dennis, I think yall have outdone yourselves with that list of forms. Ill have to add yet another volume to my typical Project Manuals just for blank sample forms (is it really appropriate to include blank sample forms as Contract Documents?). I dont include any blank sample forms for my typical projects (except for a substitution request form at the end of Section 01600), unless there is a requirement to use an extremely unusual one with which bidders may not be familiar. Instead my CCA group distributes required forms at the first preconstruction meeting.

As far as the legal portion of this discussion goes, we spec guys arent doing our job if we dont read, and understand, the legalese in Owners documents to ensure proper coordination with the documents for which we are responsible.

Nice listing Dennis. Glad to see I managed to second guess MF04 with what I have been doing the last many years including even a couple of the numbering sequences. I have always put all the forms of a various typse together up front and each form has its own ‘document’ number.

For those that keep dragging out the MOP about how the architect is responsible for including forms and conditions or coordinating them - that doesn’t really work very well if the Owner is not forthcoming or if the Owner is modifying his General and Supplementary Conditions right to the last minute.

Of course when we see them we review and provide comment. But when they take it upon themselves to prepare them, and our experience is about 60% of them seem to do this, then thre is nothing we can do about it.

And its just plain incorrect to make Division 1 coordinate with the Owner prepared Conditions when the Owner prepared conditions provide incorrect information about the Archtect’s obligations as relates to the Owner Architect Agreement. We will modify our Division 1 to the Owner’s requirements in all regards except that. We tell him where he has errors and should change his documents - or recommend he simply omit requirements that are inappropriate to the Conditions. But we are not ever going to obligate ourselves to efforts that contradict the Owner/Architect agreement. If the Owner udertakes to negotiate changes in our agreement or undertake supplementary services for additional obligations, then we will of course revise Division 1 accordingly.

To do otherwise will actually legally obligate you. If you write it, if you even just publish it, the legal system has decided that you are neither blind nor mute, so you buy what you write and publish.

MOP is not incorrect. In the best of all worlds, everything works correctly, the owner lets the architect prepare the documents with coordination through his legal and insurance groups, or there is clear and timely coordination with those that are preparing them and they are all nicely published in the Project Manual. But in the real world when coordination breaks down, when an owner does not wish to coordinate, or their idea of timely is a schedule for the front end that gets attached 3 days after the owner requires the project manual be printed for him and no coordination opportunity, then you have to protect yourself.

The MOP is about how projects are supposed to go, how we would like to see them go. The MOP is like a text book or a reference guide on the history of the best methods of practice. When other members of the construction group take it upon themselves to ignore these guides, it is foolish for the architect or the specifier not to move to protect themselves from the errors of others.

The MOP is a great guide and a great tool. I never miss an opportunity to even reference its suggestions to owners, lawyers, insurers and contractors who ignore it or force me due to their practices to deviate from its advice.

William

Doug:

No, you don’t need a second volume for your projects. Not all projects need all these forms. Since MasterFormat must incorporate (excuse the terms) Broadscope and Narrowscope titles, we tried to have an inclusive of the most common forms used on projects. We are picking up the subject matter which was only referenced in MF95 and assigning titles and numbers.

If your projects don’t need these forms, don’t use them. But if they do, we are trying to create one place for all forms. Today most firms either include them in Series 0, or include them as an attachment to the end of the Division 1 section where they are referenced.