Specifications and MasterFormat on the ExAC: the 1 sub-category you need to know
Examitect's ExAC study plan places Specifications and MasterFormat under a single sub-category in Section 3's Final Project cluster. Sub-category 8.5 covers everything from spec writing principles to MasterFormat organization, SectionFormat structure, the NMS, and how specs coordinate with drawings. Questions appear across multiple formats: multiple choice on division numbering, scenario-based on choosing the right spec type, and short-answer on SectionFormat structure.
What specifications are, and what they produce
Specifications are the written part of construction documents. They describe the quality, materials, products, workmanship standards, and execution requirements for every item of work on a project. Drawings show where and how much; specifications describe what quality and how.
Together, drawings and specifications form the construction documents. When combined with the contract form, supplementary conditions, and general conditions, they become the full set of contract documents. CCDC 2 states that "drawings and specifications are complementary and what is called for by one shall be as binding as if called for by both."
What a good specification does
A well-written specification is clear (no ambiguity the contractor can exploit), coordinated (no conflicts with drawings or consultant specs), and accurate (technically correct for the products and methods specified). These three qualities are the standard against which spec quality is judged on the ExAC.
The project manual
Specifications form the core of the project manual. The project manual typically includes Division 00 (procurement and contracting requirements such as bidding instructions, bid forms, and the contract form) and Divisions 01 to 49 (the specifications themselves). Not all divisions appear in every project manual: you include only the divisions that apply to the specific project's scope of work.
Key distinction
Drawings describe scope and geometry. Specifications describe quality and execution. If a conflict exists between them, Division 01 typically takes precedence over technical specifications, and technical specifications take precedence over drawings. The order of precedence is stated in the contract conditions (e.g., CCDC 2 Clause 1.1.7).
8.5 Understand the principles of specification writing
What sub-category 8.5 tests. Sub-category 8.5 of Examitect's ExAC study plan, taken from the CACB blueprint, is "Understand the principles of specification writing." The primary references are CHING Appendix A.19, CHOP Chapter 2.5, and CHOP Chapter 6.4. The supplementary references are the Architectural Graphic Standards 12th Edition and the NMS RAIC table of contents.
Questions in this sub-category test your ability to apply specification writing principles, select the appropriate specification method for a given situation, recognize correct MasterFormat organization, and understand the NMS as Canada's standard starting point.
Core principles of specification writing
- Clarity. Each requirement must be unambiguous. Avoid vague language such as "acceptable" or "adequate" without defining the standard. Use imperative mood: "Install according to manufacturer's written instructions."
- Coordination. Specifications must align with drawings and consultant documents. The spec writer reviews structural, mechanical, and electrical specs as well as architectural drawings before finalizing any section. Gaps and overlaps both create liability and cost money.
- Accuracy. Technical content must be correct: product standards, installation requirements, testing methods. An inaccurate spec that references the wrong CSA standard can invalidate a product substitution review.
- Completeness. Every product and process that appears on the drawings must have a corresponding specification section. Items not covered by specs tend to become change order territory.
- Avoiding means and methods. Unless safety is involved, do not specify how the contractor must perform the work. Specifying means and methods can transfer liability from the contractor to the architect.
Who writes specs, and when
The architect is responsible for architectural specification sections and for coordinating all consultant spec sections into a single project manual. Spec writing begins during design development with an outline specification describing materials and systems in general terms. Full specification sections are completed during the construction documents phase, after design decisions are locked.
How to spot an 8.5 question
The question describes a project situation and asks which specification method is correct, which division a product falls under, or how to structure a section. Watch for scenario stems like "The architect is writing the spec for a roofing system on a federal project" or "A contractor requests a substitution for the specified product."
MasterFormat: the 50-division system
MasterFormat is a master list of numbers and titles developed jointly by the Construction Specifications Institute (CSI) and Construction Specifications Canada (CSC). Its purpose is to standardize the organization of construction information so that architects, contractors, estimators, and suppliers can all navigate specifications the same way.
Six-digit numbering
The 2004 edition moved from a five-digit to a six-digit numbering system, written as XX XX XX. The first pair of digits is the division (level one). The second pair is the level-two grouping within that division. The third pair is the level-three section. When a fourth level is needed, an additional pair of digits follows a dot: 04 21 13.13 is Brick Veneer Masonry.
Two major groups
MasterFormat has two top-level groups:
- Procurement and Contracting Requirements Group: Division 00 only. Covers solicitation documents, instructions for procurement, bid forms, contract forms, project forms, general conditions, and revisions.
- Specifications Group: Divisions 01 through 49, subdivided into five subgroups.
The five Specifications subgroups
| Subgroup | Divisions | What it covers |
| General Requirements | 01 | Project-wide administrative procedures (submittals, meetings, quality, closeout) |
| Facility Construction | 02 to 19 | Existing conditions, concrete, masonry, metals, wood, thermal and moisture protection, openings, finishes, specialties, equipment, furnishings, special construction, conveying equipment |
| Facility Services | 20 to 29 | Fire suppression, plumbing, HVAC, integrated automation, electrical, communications, electronic safety and security |
| Site and Infrastructure | 30 to 39 | Earthwork, exterior improvements, utilities, transportation, waterway and marine construction |
| Process Equipment | 40 to 49 | Process interconnections, material handling, heating/cooling/drying equipment, pollution control, power generation |
Some divisions within each subgroup are reserved for future use or unassigned. The total is 50 level-one titles (divisions 00 to 49). MasterFormat has been updated in 2010, 2012, 2016, 2018, and 2020 to reflect new construction types and technologies.
Division numbers to know for the ExAC
Division 00 (Procurement/Contracting), Division 01 (General Requirements), Division 03 (Concrete), Division 04 (Masonry), Division 05 (Metals), Division 06 (Wood, Plastics, and Composites), Division 07 (Thermal and Moisture Protection), Division 08 (Openings), Division 09 (Finishes), Division 22 (Plumbing), Division 23 (HVAC), Division 26 (Electrical), Division 31 (Earthwork), Division 32 (Exterior Improvements). You don't need to memorize every section title, but you do need to know which division a scope of work belongs to.
SectionFormat and PageFormat: how a spec section is structured
SectionFormat is the companion to MasterFormat. While MasterFormat defines what division and section number a topic belongs to, SectionFormat defines how the text within each section is organized. SectionFormat is also developed by CSI and CSC and is the standard used by the NMS and all well-written Canadian specifications.
The three-part SectionFormat
| Part | Name | What it contains |
| Part 1 | General | Administrative and quality requirements for this section: references to applicable standards, submittals required (shop drawings, product data, samples), quality assurance requirements, warranty requirements, delivery/storage/handling, and project conditions. |
| Part 2 | Products | Materials, manufactured products, equipment, fabrication requirements, mixes, and finishes. This is where you name the product or performance standard. Acceptable manufacturers or products are listed here. |
| Part 3 | Execution | Installation requirements, application methods, field quality control (testing and inspection), adjusting, cleaning, demonstration, and project-closeout requirements specific to this section. |
PageFormat: the paragraph hierarchy
Within each part, PageFormat defines three levels of paragraphs:
- Article: The top level within a Part. Numbered .01, .02, .03. Example: "1.01 SUBMITTALS"
- Paragraph: The second level. Lettered A, B, C. Example: "A. Submit product data for each product specified."
- Sub-paragraph: The third level. Numbered 1, 2, 3 (then lettered a, b, c at the fourth level). Used for specific items under a paragraph.
SectionFormat vs. MasterFormat
MasterFormat tells you which division and section number your content belongs to. SectionFormat tells you how to organize the text inside that section. A question might show you a spec section out of order and ask which part (General, Products, or Execution) a particular paragraph belongs in.
Types of specifications: prescriptive, performance, and proprietary
You choose a specification method based on the degree of control you need, the project type, the product category, and whether the owner has restrictions on sole-source procurement.
Prescriptive specifications
Prescriptive specs describe the exact materials and methods the contractor must use. You define the product standard (e.g., "ASTM C90, hollow load-bearing concrete masonry units"), the physical properties (minimum compressive strength, dimension tolerances), and the installation method. The contractor has little discretion. Use prescriptive specs when you need precise control over quality and execution, for example: custom concrete mixes with specific air-entrainment targets, waterproofing membranes with defined application thickness and testing requirements.
Performance specifications
Performance specs state the required outcome but leave the means to the contractor. You define what the assembly must achieve: a curtain wall must achieve a specific air infiltration rate, a structural floor must carry a defined load at a defined deflection limit. The contractor proposes a product or system and proves it meets the criteria through testing, engineering calculations, or manufacturer's certified test data. Performance specs work well for proprietary systems where multiple manufacturers can achieve the same result, and where you want to keep competition open for pricing.
Proprietary specifications
Proprietary specs name a specific manufacturer, product, or catalogue number. They come in three forms:
- Closed proprietary (sole-source): Names one product only, no substitutions. Used when only one product meets the design intent. Requires justification on public projects and may require an exemption from competitive procurement rules.
- Open proprietary (or-equal): Names one or more products followed by "or equal" or "or approved alternate." The contractor may propose a substitute, but you review it against the named product's specifications. This is the most common proprietary method on private-sector projects.
- Basis-of-design: Names one product as the design basis for dimensions, performance, and aesthetics, and requires that any substitute match all characteristics of the named product. Stronger than "or equal" but allows substitution.
Public-sector restrictions
Public (government) projects in Canada typically prohibit closed proprietary specifications unless there is a documented justification. Open proprietary with or-equal language is acceptable. Performance specifications are often preferred for publicly funded work because they keep the market open for competitive bidding.
Choosing the right method
If the question says "public sector" or "government project," be cautious about proprietary or sole-source specs. If the stem says "the architect wants maximum control over installation," think prescriptive. If it says "the architect wants the contractor to prove the system works," think performance.
Division 01: General Requirements
Division 01 is the administrative backbone of the project manual. It covers procedures and requirements that apply to all sections of the specifications, not to any single product or trade. Anything you write in Division 01 binds the entire contract.
What goes in Division 01
| Section group | Contents |
| 01 10 00 Summary | Project description, contractor's use of premises, work covered by the contract, phasing |
| 01 20 00 Price and Payment | Allowances, alternates, unit prices, applications for payment, schedule of values |
| 01 30 00 Administrative | Project coordination, project meetings, submittals (general procedure), requests for information, document control |
| 01 40 00 Quality | Quality control, quality assurance, testing and inspecting services, references (standards and codes) |
| 01 50 00 Temporary Facilities | Temporary utilities, construction facilities, barriers, construction aids, hoarding |
| 01 60 00 Product Requirements | Product delivery and storage, substitutions procedure, owner-furnished products |
| 01 70 00 Execution and Closeout | Closeout procedures, project record documents, demonstrations and training, warranties |
The key rule for Division 01
Do not put generic requirements in technical sections (Divisions 02 to 49). If a submittal procedure applies to all sections, it goes in Division 01. If a quality requirement applies only to masonry work, it goes in Division 04. This separation keeps the project manual easy to navigate and avoids conflicting requirements between sections.
Division 01 on the ExAC
Questions often ask whether a specific requirement belongs in Division 01 or in a technical section. If the requirement applies project-wide (all submittals, all meetings, project closeout), it goes in Division 01. If it's trade-specific (how to install masonry ties), it goes in the technical section.
The National Master Specification (NMS)
The National Master Specification is Canada's master text base for construction specifications. It contains pre-written text for most MasterFormat sections, covering every procedure, product, or method likely to be specified on a Canadian construction project.
Who publishes it and how it's maintained
The NRC (National Research Council) publishes the NMS and coordinates continuous review of all sections with the design and construction industry. The NRC ensures the NMS stays current and is available in both English and French. NRC is also working to "green" all sections so they include environmentally responsible material and work practices. The NMS has been available to the Canadian construction industry for over 35 years.
How architects access and use it
Architects purchase the NMS through the RAIC from NBS (which acquired Innovative Technology Inc. in 2020). Three product formats are available:
- NBS Chorus: Cloud-based specification software pre-loaded with all NMS content in English and French. Compatible with Mac, Windows, tablets, and phones.
- SPECedit: Software for editing Word documents (note: SPECedit is no longer supported after December 31, 2023).
- Word document libraries: Curated NMS content in Word format with free specification cleanup macros.
Regardless of format, the workflow is the same: you start with the NMS master text for the section, delete the options and alternatives that don't apply, fill in project-specific values, add project-specific requirements, and produce the project specification section.
Specialty NMS packages
The NMS is sold in themed packages: a General package (all architectural divisions), a Building Services package (Division 14, 21 to 28), a Structural package, an Interior Design package, a Heavy Civil package, a Landscape Architectural package, and others. Each package includes Division 00 and 01 plus the relevant technical divisions. The UniFormat-based Performance package is available for design-build and early-stage use.
NMS on the ExAC
Know that the NMS is a starting point, not a finished spec. You always edit it to suit the project. Know that it's Canadian-specific (not an American document). Know that it's published by the NRC and distributed through RAIC/NBS, not by CSI or CSC directly (though CSC is involved in reviewing content).
How each reference fits the Specifications and MasterFormat sub-categories
Each source listed in Examitect's ExAC study plan for sub-category 8.5 contributes a different layer of knowledge. Use this table to understand which reference to turn to for each type of question.
| Reference | Scope relevant to 8.5 | Sub-category |
| CHING Appendix A.19 | Full MasterFormat division listing from Division 00 to Division 49 with level-two titles; explains the six-digit numbering system and the two major groups | 8.5 |
| CHOP Chapter 2.5 | Standards organizations (CSA, CGSB, ULC, ISO, SCC); role of standards in specifications; CSC and its role in MasterFormat and SectionFormat development; certification and testing agencies | 8.5 |
| CHOP Chapter 6.4 | Construction documents: how specs and drawings are complementary; order of precedence; quality criteria for construction documents (clarity, readability, intelligibility, constructability); coordination between disciplines | 8.5 |
| Architectural Graphic Standards 12th Ed. | MasterFormat, SectionFormat, UniFormat, and OmniClass as the four classification systems; how MasterFormat is used for keynotes and drawing references; BIM and specification tools | 8.5 |
| NMS RAIC Table of Contents | Overview of NMS products, packages, and section coverage; how the NMS is purchased and maintained by NRC; Canadian specificity of NMS content | 8.5 |
Key Specifications and MasterFormat terms (glossary)
- MasterFormat
- A master list of numbers and titles developed by CSI and CSC to standardize the organization of construction specifications, cost data, and drawing keynotes. 50 divisions, six-digit numbering.
- SectionFormat
- A companion standard to MasterFormat developed by CSI and CSC that defines how text within each specification section is organized: Part 1 General, Part 2 Products, Part 3 Execution.
- PageFormat
- The paragraph hierarchy within a SectionFormat section: articles (numbered .01), paragraphs (lettered A, B, C), and sub-paragraphs (numbered 1, 2, 3).
- UniFormat
- A classification system for construction information organized by functional building element (foundations, shell, interiors, services, equipment). Used for schematic design and preliminary cost estimating. Complements, not replaces, MasterFormat.
- OmniClass
- A classification system for the entire built environment, covering many tables including construction entities, work results, properties, and phases. Provides a broader framework than MasterFormat alone.
- National Master Specification (NMS)
- Canada's master text base of pre-written specification sections, published by NRC and distributed through RAIC/NBS. Used by architects as a starting point that is edited to suit each project.
- Project manual
- The bound document containing the specifications, bidding requirements, contract forms, and conditions of the contract. Specs form the core; the manual also includes Division 00 procurement documents.
- Construction documents
- The working drawings and the specifications. When combined with the contract form and conditions, they become the contract documents. (CHOP Chapter 6.4 definition.)
- Prescriptive specification
- A specification type that describes exact materials and methods. Gives the architect maximum control over quality and execution but limits contractor flexibility.
- Performance specification
- A specification type that states the required outcome (strength, air infiltration rate, acoustic performance) and allows the contractor to choose the means to achieve it.
- Proprietary specification
- A specification type that names a specific manufacturer, product, or model. May be closed (sole-source, no substitution) or open (with "or equal" language allowing substitutes).
- Or-equal clause
- Language added to an open proprietary specification allowing the contractor to propose a substitute product that meets the specified requirements. The architect reviews and accepts or rejects substitution proposals.
- Basis-of-design
- A specification approach that names one product as the design reference for dimensions, performance, and aesthetics, and requires that any approved substitute match all characteristics of the named product.
- Division 01
- General Requirements. The MasterFormat division covering project-wide administrative procedures: summary of work, payment procedures, submittals, quality requirements, temporary facilities, product requirements, and closeout. Applies to all sections of the specifications.
- Submittal
- A document or sample provided by the contractor for review by the architect before an item is ordered, fabricated, or installed. Types include shop drawings, product data (catalogue cuts), samples, and mock-ups.
- CSI
- Construction Specifications Institute (U.S.). Co-developed MasterFormat, SectionFormat, and UniFormat with CSC.
- CSC
- Construction Specifications Canada (Canadian). Co-developed MasterFormat, SectionFormat, and UniFormat with CSI. Has chapters across Canada.
- NRC
- National Research Council Canada. Publishes and maintains the NMS.
- Means and methods
- How the contractor physically constructs the work. Architects generally should not specify means and methods (how to do it) unless safety is involved; this avoids transferring construction liability from the contractor to the architect.
- Outline specification
- A preliminary specification prepared during design development that describes proposed materials and systems in general terms. It informs the full specification sections written in the construction documents phase.
How Specifications and MasterFormat questions are asked on the ExAC
Sub-category 8.5 produces questions in several formats. The table below maps format to the type of content typically tested.
| Question format | Typical 8.5 wording |
| Multiple choice | "Which MasterFormat division covers waterproofing and air barriers?" / "A specification that states 'Provide a curtain wall system achieving maximum 0.3 L/s/m2 air infiltration' is an example of which specification type?" |
| Multi-select | "Which of the following belong in Division 01 of the project manual? Select all that apply." / "Which of the following are part of SectionFormat's Part 3 Execution?" |
| Scenario-based | "The owner of a government building requests that a specific manufacturer's product be used without allowing substitutions. The architect should..." / "A contractor's submittal proposes a substitute for the specified roofing membrane. The architect's first step is to..." |
| Definition | "What is the NMS?" / "What distinguishes a prescriptive specification from a performance specification?" |
| Ordering | "Place the following SectionFormat paragraph types in the correct hierarchy from highest to lowest level: Article, Sub-paragraph, Paragraph." |
| Short answer (paid) | "Describe three situations in which a performance specification is preferred over a prescriptive specification." / "Explain the role of Division 01 in a project manual." |
Reading questions carefully
Watch for questions that mix up MasterFormat and SectionFormat. MasterFormat = which division and section number. SectionFormat = how the text inside a section is organized (Part 1, Part 2, Part 3). These are two separate and distinct standards. Also watch for questions that confuse UniFormat (elemental classification for early cost estimating) with MasterFormat (product-based classification for specs and detailed cost data).
Common ExAC traps in Specifications and MasterFormat questions
- Sole-source on a public project. If the question involves a government or publicly funded project and one of the answers is "write a closed proprietary spec naming one product," that answer is almost certainly wrong. Public procurement rules typically prohibit sole-source specifications without documented justification.
- Putting trade-specific requirements in Division 01. Division 01 covers requirements that apply to all sections. A test on plaster installation quality belongs in Division 09, not in Division 01's quality requirements article.
- Specifying means and methods unnecessarily. "Install masonry at a rate of no more than 1.2 metres per day" is a means-and-methods restriction. Unless there is a safety or quality reason, specs should say what to achieve, not how fast to achieve it.
- Confusing the NMS with MasterFormat. MasterFormat is the numbering and organizational system. The NMS is the actual text content. The NMS uses MasterFormat numbers and SectionFormat structure, but the two are separate. The NRC publishes the NMS; CSI/CSC developed MasterFormat.
- Mixing up or-equal and sole-source. Or-equal specifications name a product but allow substitutions. Sole-source names a product and prohibits substitutions. These have very different procurement implications.
- Assuming drawings always take precedence. CCDC 2 puts Division 01 above technical specs, which are above drawings in the order of precedence. Many candidates assume drawings win conflicts. Check the contract conditions before answering.
Tips for Intern Architects studying Specifications and MasterFormat
- Read the CHING appendix actively. Go through the 50-division list once with a project in mind and ask yourself which division each scope of work in that project falls under. Active reading beats passive memorization.
- Write a practice spec section. Take the NMS template for a product you know (e.g., gypsum board, resilient flooring) and edit it for a fictional project. You'll see SectionFormat and the three-part structure in context.
- Map Division 01 to your office's standard spec. If your office has a master specification, compare its Division 01 sections to the MasterFormat groupings. This builds pattern recognition for the exam.
- Know the four classification systems. MasterFormat (by work result), UniFormat (by building element), OmniClass (broader taxonomy), SectionFormat (internal section structure). These appear in the AGS and are often tested together.
- Practise "which type" questions. For any spec scenario, ask: does this control quality and means (prescriptive), require a result only (performance), or name a product (proprietary)? Run through 20 scenarios until the distinction is automatic.
How to study Specifications and MasterFormat in 8 to 12 hours
- Hours 1 to 2: Read CHING Appendix A.19 (MasterFormat division listing). Sketch the five Specifications subgroups from memory. Review AGS pages on MasterFormat, SectionFormat, and UniFormat.
- Hours 3 to 4: Read CHOP Chapter 6.4 (construction documents). Focus on the complementarity of drawings and specs, the order of precedence, and the clarity/coordination/accuracy criteria.
- Hours 5 to 6: Read CHOP Chapter 2.5 (standards organizations). Note CSC's role. Skim the NMS RAIC table of contents to understand what NMS packages exist and how sections are organized.
- Hours 7 to 8: Practise specification type scenarios: prescriptive vs. performance vs. proprietary. Work through Division 01 content: know what each major section group covers and why Division 01 is separate from technical divisions.
- Hours 9 to 12: Do Examitect practice questions for sub-category 8.5. Review wrong answers against the source references. Repeat any question format where you scored below 70%.
One-line summary
Specifications describe quality; drawings describe scope. MasterFormat organizes them by work result into 50 divisions; SectionFormat organizes each section into Part 1 (General), Part 2 (Products), and Part 3 (Execution). The NMS gives you a Canadian starting point for each section, and you edit it for the project.