8.5 Specifications and MasterFormat

Specifications and MasterFormat on the ExAC: the 1 sub-category you need to know

The official ExAC objectives place Specifications and MasterFormat under a single sub-category in Section 3's Final Project cluster. Sub-category 8.5 covers the connection between MasterFormat and the NMS, which NMS divisions are common or specific to each discipline, assigning a construction element to the right MasterFormat division, the components of a typical MasterFormat section, and the maxims of good specification writing. Two closely related objectives sit in 8.4 rather than 8.5: explaining how the construction documents relate to each other is 8.4.5, and explaining the different methods of specifying is 8.4.6. Questions appear across the item types the Framework Document names: multiple choice on division numbering and on choosing the right specification type, pairing or matching and ordering on SectionFormat structure, completion of sentences on the terminology, and a small number of short-answer items.

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. Common construction-contract language, quoted by CHOP, puts it this way: "Drawings and specifications are complementary and what is called for by one shall be as binding as if called for by both." CCDC 2 (2020) states the principle more broadly, at GC 1.1.2: "The Contract Documents are complementary, and what is required by one shall be as binding as if required by all."

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). The list the ExAC actually asks you to produce is a different one: objective 8.5.5 asks you to list the maxims which govern the writing of a good specification, and CHOP publishes that list under the heading "Specification Language". It is set out under sub-category 8.5 below.

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.

8.5 Understand the principles of specification writing

What sub-category 8.5 tests. Sub-category 8.5 of the official ExAC objectives is "Understand the principles of specification writing." Its five objectives are 8.5.1 explain the connection between MasterFormat and the National Master Specification; 8.5.2 distinguish which divisions of the NMS are common or specific to each discipline; 8.5.3 assign a construction element to the appropriate MasterFormat division; 8.5.4 describe the components of a typical MasterFormat specification section; and 8.5.5 list the maxims which govern the writing of a good specification. The 2026 Preparation Guide lists these objectives without citing any references, so the reference mapping used here is Examitect's own: CHING Appendix A.19, CHOP Chapter 2.5, and CHOP Chapter 6.4 as primary, with the Architectural Graphic Standards 12th Edition and the NMS RAIC table of contents as supplementary.

Questions here test your ability to apply the maxims of specification writing, recognize correct MasterFormat organization, match NMS divisions to disciplines, and understand the NMS as Canada's standard starting point. Choosing between methods of specifying is objective 8.4.6, and explaining how the construction documents relate to each other is 8.4.5, but both are examined alongside 8.5 material.

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.
• Handling means and methods carefully. CHOP says specifications define the general and trade contractors' responsibilities and obligations for products and materials used and for the procedures, general means and methods to be used in the execution of the work, and Part 3 Execution is exactly where those requirements belong. The narrower rule, from the NMS User's Guide, is that execution statements should describe what is required to achieve the quality of workmanship rather than describing how to construct, which could be misread as installation instructions.

The maxims of good specification writing (objective 8.5.5)

Objective 8.5.5 asks you to list the maxims which govern the writing of a good specification. CHOP sets them out under the heading "Specification Language":

• Be brief and clear.
• Use active imperative style. Avoid verb forms such as "shall be", "will be", "to be", "should", and "may be", and avoid the word "must".
• Address instructions to the contractor, but make materials and methods the subject of the sentence, not the contractor.
• Avoid repetition: say it once, in the appropriate place.
• Avoid specifying anything that is not to be enforced or is impossible to enforce.
• Avoid "or equal" phrases: "or equal", "approved as equal", "equal to", "or just as good".
• Avoid scope or scope of work paragraphs.
• Avoid weasel paragraphs and vague escape phrases such as "to the satisfaction of the architect", "as the architect may direct", or "acceptable to the architect".
• Use numbers for numeric quantities. Complete sentences are not required.

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.

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

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.

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

PageFormat: the paragraph hierarchy

Within each part, PageFormat defines the levels below the Part heading. Canadian sections written in NMS format number every level, and that is the convention the ExAC's Canadian references show:

1. Part: The top level. Example: "PART 1 - GENERAL"
2. Article: The level below the Part. Numbered 1.1, 1.2, 1.3 in NMS format. Example: "1.3 SUBMITTALS"
3. Paragraph: The level below the article. Numbered .1, .2, .3 in NMS format. Example: ".1 Submit product data for each product specified."
4. Sub-paragraph: The level below the paragraph. Numbered .1.1, .1.2 in NMS format, used for specific items under a paragraph.

The US CSI variant numbers articles 1.01, 1.02 and letters the paragraphs A, B, C. Recognize both, but write Canadian sections the way the NMS does.

Specification types and methods of specifying

CHOP keeps two classifications separate, and the ExAC expects you to do the same. The type of specification is prescriptive or performance, or a combination of both. The method of specifying is proprietary or generic, with reference standards incorporated into either. Every real specification is a combination of the two: a generic prescriptive section, a proprietary performance section, and so on. You choose based on the degree of control you need, the project delivery method, the product category, and the client's procurement policy.

Prescriptive specifications (type)

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 (type)

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 generic, non-proprietary systems where several manufacturers can achieve the same result, and where you want to keep competition open for pricing.

Proprietary method

Proprietary specifications identify products by trade name, preferably using the manufacturer's exact catalogue name and description to avoid ambiguity. 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: Names products as acceptable references for contractor selection and submittals. CHOP advises listing three to five true equivalents and qualifying the list with "or approved alternative" or similar wording tied to the Division 01 substitution procedure. Do not write "or equal", "approved as equal", "equal to", or "or just as good": CHOP lists all four among the phrases to avoid. Open lists are common on private-sector projects, where clients have more flexibility over method.
• 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 a plain open list of acceptable products, but still allows substitution.

Generic method

Generic specifications describe the requirements for a material, product, or system in terms of physical characteristics and properties or performance characteristics, without naming a trade name. Performance criteria may include appearance, strength, and durability. When a component is required to comply with a testing procedure, that is in effect a performance specification. Prescriptive generic specifications require in-depth research by the architect, and the criteria should be objective, field-testable against standardized test methods, and backed by evidence of compliance such as manufacturers' test results, calculations, samples, or mock-ups.

Reference standards

Reference standards are incorporated into either method. Specifications routinely cite standards from CSA, ULC, CGSB, and ASTM, and trade manuals from associations such as AWMAC, the CRCA, and the TTMAC. Using them cuts the volume of the specification considerably. Where a standard is cited, verify the number and the date of the latest issue, and confirm that any amendments have not changed criteria that affect the product or procedure.

Public-sector restrictions

Public sector clients such as Canada's federal government may require, as a matter of policy, that all specifications be of the prescriptive type, regardless of the type of work involved. On the method axis, policy or trade-agreement obligations may also require that all specifications be prepared using the generic method, whichever type is used, which compels those clients to disallow proprietary specifications except in narrow circumstances: only one specific material will fulfill the exact requirements of the project, materials are required to match existing materials, or the project has an unusual function or timing requirement such as emergency repairs. Private sector clients are usually more receptive to performance specifications, and have more flexibility to use either method or both in combination.

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

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.

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

NMS content is sold as a complete set and as libraries curated by discipline: Architectural, Performance, Building Services, Air Transportation, Conservation, Landscape Architectural, Structural, Interior Design, Heavy Civil, Mechanical, Electrical, and Engineering. The Architectural package covers Divisions 00 through 14 plus Divisions 31, 32, and 33, and also includes UniFormat content. The Building Services package covers Divisions 00, 01, 14, 21, 22, 23, 25, 26, 27, and 28 (there is no Division 24), plus parts of Divisions 02, 08, 10, 11, 33, 34, and 42. Division 00 and Division 01 are included in the Architectural, Building Services, Heavy Civil, Mechanical, Electrical, and Engineering packages; the Air Transportation, Conservation, Landscape Architectural, Structural, and Interior Design packages include selected sections only, with no full divisions. The UniFormat-based Performance package holds 55 sections for design-build and early-stage use.

How each reference fits the Specifications and MasterFormat sub-categories

The 2026 Preparation Guide lists objectives 8.5.1 to 8.5.5 without citing any references, so the mapping below is Examitect's own study plan. (The only reference list the guide publishes is the four primary documents on p.5: CHOP, the IAP, NBC 2020, and NECB 2020.) Each source contributes a different layer of knowledge. Use this table to understand which reference to turn to for each type of question.

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: Part, article, paragraph, and sub-paragraph. NMS-format Canadian sections number every level (PART 1 - GENERAL, article 1.1, paragraph .1, sub-paragraph .1.1); the US CSI variant numbers articles 1.01 and letters paragraphs A, B, C.

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 details the expected components and applicable reference standards for a material or system, and may offer pre-approved options. Gives the architect control over quality and execution but limits contractor flexibility. Independent of the method (proprietary or generic) used to describe the products.

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 method of specifying that names a specific manufacturer, product, or model. May be closed (sole-source, no substitution) or open (a list of acceptable products qualified by "or approved alternative" and tied to the Division 01 substitution procedure).

Or-equal clause

Language allowing the contractor to propose a substitute product that meets the specified requirements. CHOP tells specifiers to avoid the phrases "or equal", "approved as equal", "equal to", and "or just as good", and to qualify a list of named products with "or approved alternative" instead. 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. Specifications do set the contractor's obligations for procedures and general means and methods, and Part 3 Execution is where those requirements belong. The working rule, from the NMS User's Guide, is that an execution statement describes what is required to achieve the quality of workmanship rather than how to construct, which could be read as installation instructions.

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

The ExAC Framework Document names five item types: multiple choice, pairing or matching of components, ordering of elements, completion of sentences or fill in the blank, and short answers. The blueprint gives Section 3 as approximately 96 multiple-choice and approximately 6 short-answer questions, so most 8.5 items are multiple choice. A project situation or a term you have to recall is content inside those types, not a format of its own. The table below maps each type to the content it typically tests.

Common ExAC traps in Specifications and MasterFormat questions

1. Proprietary specifying on a public project. If the question involves a government or publicly funded project and one of the answers names a single product, that answer is almost certainly wrong. Public sector clients may be required by policy or trade agreement to use the generic method, disallowing proprietary specifications except where only one material will do, where materials must match existing materials, or where the project has an unusual function or emergency timing. Do not assume public clients prefer performance specifications either: CHOP notes the federal government may require all specifications to be of the prescriptive type.
2. 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.
3. Writing installation instructions instead of quality requirements. Part 3 Execution does specify means, methods, and procedures, so "never specify means and methods" is the wrong rule. The right rule, from the NMS User's Guide, is that an execution statement describes what is required to achieve the quality of workmanship, not how to construct. "Install masonry at a rate of no more than 1.2 metres per day" crosses that line unless there is a quality or safety reason for the limit.
4. 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.
5. 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.
6. Assuming drawings always take precedence. CCDC 2 (2020) GC 1.1.5 puts Division 01 above the technical Specifications, which rank above material and finishing schedules, which rank above the Drawings. 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

1. 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.
2. 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 general requirements for construction documents: clarity, readability, intelligibility of design solutions, constructability/feasibility, usability, and quality of graphic and written language. Then read Chapter 6.4 Appendix E for specification types, methods of specifying, MasterFormat, SectionFormat, and the maxims of specification language.
3. Hours 5 to 6: Read CHOP Chapter 2.5 (standards organizations, certification and testing agencies and trade associations). For CSC itself, read the short description in Chapter 2.3. Skim the NMS RAIC table of contents to understand what NMS packages exist and how sections are organized.
4. 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.
5. 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%.