I will be a facilitator at the Orange County (California) CSI Product show in late May on the topic above.
Any suggestions and comments are appreciated:
Some of the questions:
What is a Well Written Spec?
How is a Well Written Spec different from a purchased, prewritten, standardized specification system? (ie MasterSpec and Speclink)
Who controls the product decisions for a Well Written Spec?
How is product research conducted?
How does the specifier make the early product decisions?
How do substitutions impact the creation and use of specifications?
Some top of mind thoughts:
Challenges related to getting the project architect to edit the spec, provide necessary data to the specifier, coordinating with interiors finish schedules, how to handle the architect’s consultant specs when they are wrong, incorrect format, incorrect references, etc… When should the specifier’s first draft to the project architect be issued for editing, what items should be included in Appendix’s to the spec, etc…
Odd that you are juxtaposing “Well Written Specs” with MasterSpec specifications. In my experience, MasterSpec sections are consistently the best written specs i have ever read/used.
MasterSpec is, indeed, a well written specification, but it is a master specification. I assume Colin is interested in project specifications. It is possible to have a project section based on MasterSpec that is clear, concise, nicely formatted and compliant with CSI language – but not complete nor correct for the project.
Well said (written) Mr. Chusid. If I could sum up the solution in one word it would be the one Nathan mentioned above: COORDINATION! The other factors are important too of course but poorly coordinated documents are the growth medium for RFIs and, worse, change orders.
More and more, I am convinced (maybe that is too strong a word) that one of the keys is using the specs. Well written specs (that are well coordinated) will not be much help unless they are implemented during construction (and before).