What follows is an updated version of an article I first published in December 2002 edition of the Central Virginia CSI Parameter. As is typical of these old articles I am posting, it is as pertinent today as it was eight years ago.
REFERENCE STANDARDS: NOT JUST ALPHABET SOUP
Specification writers often use reference standards in construction specifications. Their use or misuse can make the difference between a specification that is enforceable and one that is rife with conflicts and ambiguities.
Consensus standards are nothing new. ASTM International (formerly American Society for Testing and Materials) which develops and publishes consensus standards for materials, products, systems, and services has been around since 1898, and ANSI (American National Standards Institute) was established in 1918. These are just two of the organizations that produce consensus standards used in the construction industry. Others that produce frequently used standards are AAMA, ACI, AISC, AITC, NFPA to name a few. This is, of course, not an exhaustive list by any means.
Reference standards are frequently cited in construction specifications as well as building codes. Their inclusion in these types of documents by reference makes them part and parcel of the code or specification. Chapter 35 of the International Building Code is a listing of the standards that are referenced in the text of the code including the dates of publication of the various standards. Inclusion of the publication date is extremely important, as these standards are periodically reviewed and updated. The building code, however, incorporates a specific version of a given reference standard. Compliance with a later (or earlier) version of the same standard doesn’t necessarily assure compliance with the code.
The same is true of specification writing. When incorporating a standard by reference it is important for the specification writer to be specific as to which edition of the standard is to be used. In the event that a more recent version of a particular standard is referenced, it is incumbent on the specification writer to ensure that the referenced document is not in conflict with pertinent provisions of the building code.
A common mistake made by specifiers is to restate provisions of a standard referenced in the same specification such as specifying curing procedures for concrete when a reference to the appropriate ACI standard is sufficient. Another common error is to reference two conflicting standards such that compliance with one creates a conflict with of the provisions of another. Phrases such as “latest edition” or “current edition” should be avoided as well for similar reasons. Specifying blind should also be avoided.
These are but a few reasons among many for specifiers to have a thorough working knowledge of the standards they reference in their specifications. This becomes a monumental task, as the library required is monumental in size and it requires constant updating. While this article isn’t intended as a promotion of the use of a particular guide specification such as Masterspec, Spectext, or SpecLink, the producers of these and similar documents are better able to stay on top of the latest developments in consensus standards and use of these or similar products is a reasonable way to manage risk. Use of a good guide specification alone, however is not a substitute for knowledge on the part of the specifier.
Good library maintenance, continuing education, and CSI certification on the part of the specifier can help in the preparation of a quality specification which is clear, correct, complete, and concise. Participation in monthly CSI chapter meetings is a start in the right direction. The best way to gain information on this and other topics is to become an active member of CSI. Your career may depend on it!