What best describes a specification in project documents?

• A. A Narrative About Design Intent
• B. A Set Of Requirements And Procedures To Determine Compliance
• C. A List Of Equipment Vendors
• D. A Schedule Of Construction Milestones

Answer: (B)

A specification is the set of requirements and procedures used to determine whether the project meets the defined design, codes, and contract expectations. It lays out exactly what must be achieved, including performance criteria, materials, installation methods, quality standards, and the tests or inspections needed to verify compliance. This makes it a tool for both design intent and verification—it tells you not only what is required, but how you confirm that those requirements are met.

For example, a specification might state that an air handling unit must achieve a specific cooling capacity at a given outside temperature, limit air leakage to a defined rate, and use materials that meet a particular standard. It would also describe the testing and commissioning procedures, such as functional performance tests and the acceptance criteria (pass/fail thresholds). This contrasts with a narrative about design intent, which describes goals without detailing verification steps; or with a procurement list of equipment vendors, which focuses on source and selection rather than how compliance is demonstrated; or with a schedule of milestones, which outlines timing rather than technical requirements.