CDT Exam Dumps - Construction Specifications Institute CDT Certification Questions and Answers

Comprehensive and Detailed Explanation (CSI-aligned, paraphrased)

In CSI’s project delivery guidance, constructability reviews are described as a structured way to have construction-experienced professionals—often contractors, CMs, or experienced field personnel—review the design during planning or design phases to determine:

Whether the design can be built efficiently and safely

How site conditions, constraints, and logistics will affect means and methods

Potential cost, schedule, and sequencing issues arising from unique or complex aspects of the project

Constructability reviews are especially valuable when:

The site is constrained (tight urban sites, limited access, nearby sensitive structures)

There are unusual ground, environmental, or logistical conditions

The work involves complex staging, phasing, or access issues

Option C. The site presents unusual challenges and constraints is therefore the clearest trigger for a constructability review, because it directly ties to the need to evaluate how the physical and logistical realities of the site affect construction feasibility, cost, and sequence.

Why the other options are less appropriate:

A. The client is unfamiliar with this type of project.This calls for more owner education, clearer communication, and perhaps additional planning or programming support—not specifically a constructability review. The core need is understanding, not constructability.

B. The project team consists of multiple new members.That suggests a need for team alignment, clarification of roles, and communication protocols. While new team members may benefit from constructability input, the main justification for a formal constructability review is project/site complexity, not simply team turnover.

D. The contractor is unable to commit to original schedule.This is a procurement or scheduling problem, often addressed through rescheduling, negotiation, or possibly re-bid. Constructability reviews are proactive during design; schedule commitment issues often arise later and are handled with different tools (e.g., schedule analysis, changes, resequencing).

Key CSI-Related References (titles only):

CSI Project Delivery Practice Guide – sections on constructability reviews and preconstruction services.

CSI CDT Study Materials – discussions of preconstruction evaluation, constructability, and risk identification.

CSI’s core principle is that contract documents describe the work results required, not the internal means, methods, or subcontracting arrangements of the contractor. The contractor (or construction manager) is responsible for:

Determining how the work will be divided among trades and subcontractors.

Coordinating different trades to achieve the required results shown on the drawings and described in the specifications.

Design professionals (architects and engineers):

Organize the documents by disciplines and work results (e.g., civil, architectural, electrical), not by subcontractor or trade contract structure.

Are not responsible for dictating which subcontractor performs which portion of the work; that is the contractor’s role.

Given that:

Site electrical work appears on civil drawings, but the electrical engineer has also prepared electrical documents for the building systems.

The intent of the contract documents is still to describe what must be installed and how it must perform, not which subcontractor does it.

The only option that aligns with CSI’s stated roles and responsibilities is:

D. The electrical engineer does not need to control how the work is to be assigned to subcontractors.

Why the other options are not the “intent” of the documents:

A. The civil contractor is to place the concrete bases and the electrical contractor is to install the site lighting.This presumes a specific trade split based on drawing origin. CSI emphasizes that the contractor determines trade assignments, not the drawings themselves.

B. The civil contractor is to place the concrete bases and the site lighting, with the electrical contractor making the final connections.Again, this dictates trade assignments. The documents may show coordination between civil and electrical work, but do not prescribe how contractors must divide their subcontracts.

C. The general contractor needs to coordinate the work and verify that the electrical subcontractor bids the site electrical.While coordination of work is indeed a contractor responsibility, the phrasing here implies that the documents intend to direct which subcontractor must price which work package. CSI’s standpoint is that the contractor is free to structure subcontract bids as they see fit, as long as the required work is provided in accordance with the contract.

Thus, the intent of the contract documents is to define the required end results, not to assign work scopes among subcontractors. Option D correctly reflects that intent and the design professional’s role.

Relevant CSI-aligned references (no URLs):

CSI Project Delivery Practice Guide – roles and responsibilities of owner, design professional, and contractor; explanation that contractor controls means, methods, and subcontracting.

CSI Construction Specifications Practice Guide – distinction between describing work results and assigning work trades.

CSI CDT Body of Knowledge – contract document intent vs. contractor’s responsibility for dividing the work.

Comprehensive and Detailed Explanation From Exact Extract (CSI-based)

In CSI’s project delivery model, the level of development of specifications increases as the project moves through the design phases:

Project Conception – programming, needs assessment, feasibility; little or no formal specifications.

Schematic Design (SD) – conceptual design, basic systems and relationships; CSI now emphasizes Preliminary Project Descriptions (PPDs) as early, performance-oriented spec tools at this stage.

Design Development (DD) – selection and refinement of specific systems and assemblies; this is where outline specifications or expanded PPDs are used as a structured checklist for developing detailed requirements.

Construction Documents (CD) – full, coordinated section-by-section specifications in MasterFormat order, fully detailed to support bidding and construction.

CSI’s Construction Specifications Practice and CDT materials explain that outline specifications (or expanded PPDs) in the Design Development phase play a key role as a checklist and coordination tool. They:

List major assemblies, systems, and products by specification section.

Identify key performance and quality requirements in a concise format.

Help ensure that nothing is overlooked when moving into full specification writing in the Construction Documents phase.

Support coordination between disciplines (architectural, structural, MEP, etc.) by providing a common list of systems and materials.

Therefore, the phase where “outline specifications are created in order to be used as a checklist for further development of the project documents” is the Design Development phase (Option C).

Why the others are not the best fit:

A. Project Conception phaseAt this early stage, work is focused on needs, scope, feasibility, and budgeting. Specifications are generally not yet developed to the “outline” level; instead, information is more conceptual and programmatic.

B. Schematic Design phaseCSI increasingly promotes Preliminary Project Descriptions (PPDs) during Schematic Design, which are even higher-level and more performance-based than traditional outline specs. While some offices may start outline specs during SD, CSI’s standardized view places the checklist-style outline specifications more firmly in Design Development, when system choices are better defined.

D. Construction Documents phaseBy this phase, specifications are typically developed into full, detailed sections (Part 1–General, Part 2–Products, Part 3–Execution) rather than simple outline checklists. The outline specs or expanded PPDs created earlier in DD have already served their purpose in guiding the development of these full specifications and coordinated drawings.

CSI reference concepts:

CSI Project Delivery Practice Guide – chapters describing the design phases and the evolution from PPDs/outline specifications to full specifications.

CSI Construction Specifications Practice Guide – sections on preliminary specifying, PPDFormat, and the role of outline specifications during the Design Development phase.

In the design-build project delivery method, the design-builder (a single entity or team under one contract) is responsible for both design and construction. Industry guidance consistent with CSI’s CDT framework explains that, unlike Design–Bid–Build (where the architect prepares construction documents and a separate contractor builds), design-build uses a single contract covering both the design and construction phases, with a “design builder” responsible for meeting contract requirements.

During the design phase of a design-build project:

The design-builder leads planning and design and, together with its architectural/engineering team, creates the detailed design needed to build the project.

Once design details are in place, this design is used to set prices and proceed into construction.

In CSI/CDT terms, the output of this design effort is the Construction Documents (drawings and specifications) that define the scope, quality, and requirements for the work and become part of the contract documents for the project.

Why the other options do not match the CDT/CSI role at this stage:

A. Submittals – Submittals (shop drawings, product data, samples) are primarily a construction-phase contractor responsibility, responding to the already-issued construction documents. They are not the primary deliverable of the design phase.

B. Record documents – Record documents (as-built drawings, O&M manuals, etc.) are post-construction deliverables, produced near the end of the project to show what was actually installed.

C. Geotechnical reports – In many project delivery methods, geotechnical investigations are owner-provided information or obtained early by the owner; the design-builder may coordinate or rely on them, but they are not the core design-phase deliverable the question is seeking.

Therefore, in a design-build delivery method, during design, the design-builder is responsible for producing and delivering Construction documents (Option D) to the owner.

Core CSI-aligned references for this question (no URLs):

CSI Project Delivery Practice Guide – sections on Design-Build roles and responsibilities (single point of responsibility for design and construction).

Industry explanations of design-build (single contract; design builder leads design and then construction).

In the standard organization of the contract documents as taught in CSI’s CDT materials and practice guides, the General Conditions establish the baseline contractual rights, responsibilities, and relationships among the owner, contractor, and architect/engineer (A/E).

CSI explains that whenever there is a need to change or add to the standard provisions of the General Conditions (for example, to address project-specific insurance limits, bonding, liquidated damages, or local legal requirements), those changes are made in the Supplementary Conditions. The Supplementary Conditions are expressly written to modify, delete, or add to the printed General Conditions, and they do so by direct reference to specific articles or paragraphs.

The General Conditions set the standard, overall rules of the contract.

The Supplementary Conditions are the only document whose primary purpose is to modify those General Conditions for the specific project.

Other documents (Agreement, Division 01) must be consistent with the Conditions of the Contract but are not the formal instrument intended to “directly modify” the General Conditions.

Why the other options are not correct:

A. Division 01, General Requirements – Division 01 coordinates administrative and procedural requirements for the work and bridges from the Conditions of the Contract to the technical specifications. It may elaborate how procedures are implemented but it is not the document that directly amends the General Conditions.

C. Agreement – The Agreement (e.g., AIA A101) identifies parties, contract sum, contract time, and incorporates the Conditions, drawings, and specifications by reference. It relies on the General and Supplementary Conditions; it does not systematically edit their language.

D. Instructions to Bidders – These govern the procurement phase only (how to submit bids, qualifications, bid security, etc.) and cease to have effect once the Contract is executed. They do not modify the General Conditions of the construction contract.

CSI’s Project Delivery and Construction Specifications Practice Guides describe this hierarchy and emphasize that Supplementary Conditions are the proper instrument for project-specific modifications to the General Conditions, which makes Option B the correct answer.

In CSI and CDT terminology, the process of reaching out to potential or prequalified bidders to obtain bids or proposals is called “solicitation.”

The procurement (bidding) phase includes preparing procurement documents and then soliciting bids or proposals from interested or qualified firms.

“Solicitation” covers all methods used to notify and invite participation: advertisements, invitations to bid, requests for proposals (RFPs), and notices to prequalified bidders.

CSI’s Project Delivery Practice Guide and CDT study materials describe the sequence in the procurement stage roughly as:

Preparation of procurement documents (including Instructions to Bidders/Offerors, bid forms, proposed contract forms, etc.).

Solicitation of bids or proposals – announcement or direct issuance to prospective bidders.

Receipt, opening, and evaluation of bids/proposals.

Recommendation and award of contract.

Within that structure, “solicitation” is clearly identified as the step where the owner/AE issues the invitation to bid or request for proposals. The other answer choices refer to documents or requests that are part of the process, but not the process itself:

B. Instructions for Procurement – The CDT/CSI terminology is usually “Instructions to Bidders” or “Instructions to Offerors,” which are sections within the procurement documents explaining how to submit bids (time, place, format, required forms, etc.). They are not the act of announcing or inviting; they are a part of the documents used once solicitation has begun.

C. Instructions to Bidders – This is a specific document or section that sets the rules for bidding (bid security, withdrawal of bids, opening procedures, etc.). It is not the overall process of broadcasting the opportunity; instead it governs bidder behavior after solicitation has occurred.

D. Request for Scope of Work – This is not a standard CSI/CDT term. Scope of work is normally defined in the drawings, specifications, and sometimes in a statement of work, but “request for scope of work” is not used as the formal label for the invitation stage.

Because the question asks specifically for “the process of notifying prospective or qualified bidders requesting proposals for a specific project or an invitation to bid,” the correct CSI-aligned term is “Solicitation” (Option A).

Relevant CSI references (no URLs):

CSI Project Delivery Practice Guide – Procurement phase and terminology for solicitation of bids/proposals.

CSI Construction Specifications Practice Guide – Sections on procurement and bidding documents.

CSI CDT Body of Knowledge – Topic: Procurement (solicitation and receipt of bids/proposals).

In CSI-based drawing conventions, a scaled view is one drawn at a stated scale so that actual dimensions can be measured directly from the drawing (e.g., 1:100, 1/4" = 1'-0"). CSI’s Uniform Drawing System (UDS) treats floor plans, roof plans, and foundation plans as primary orthographic views prepared at a defined scale for dimensioning and coordination between disciplines. These are the standard “working drawings” for construction.

Foundation plan (Option B)A foundation plan is an orthographic plan view drawn to a specific scale showing footings, slabs, and foundations with dimensions and notes. It is intended for measurement and layout, and CSI references it as one of the basic scaled plan views of the project drawings.

Why the other options are not correct:

A. Perspective – Perspectives are pictorial views used for visualization and presentation. CSI notes that such views are typically not used for taking dimensions and may not be drawn to a true working scale.

C. Riser diagram – Riser diagrams (for plumbing, fire protection, electrical, etc.) are diagrammatic, showing relationships and routing, not physical locations at scale. They are expressly identified as “not to scale” in most construction document standards.

D. Isometric – Isometric drawings are a type of pictorial/axonometric view used to show three-dimensional relationships. While they can sometimes be constructed proportionally, CSI’s guidance treats them as diagrammatic/pictorial views rather than the primary scaled working views used for dimensioning work in the field.

CSI References (no links):

CSI Uniform Drawing System (UDS) modules on drawing types and views (plan, elevation, section, diagrammatic views).

CSI Project Delivery Practice Guide – discussion of scaled plan views as part of the construction documents set.

CSI teaches that while project size, nature, and cost all influence the complexity and staffing of a project, the primary determinant of formal roles and responsibilities among owner, design professional, and constructor is the project delivery method.

For example:

In Design-Bid-Build (DBB), the A/E designs under a separate contract with the owner; the contractor is selected later and has no design responsibility (except limited design delegation).

In Design-Build (DB), the design-builder assumes both design and construction responsibilities under a single contract with the owner; the architect is typically under contract to the design-builder.

In Construction Manager at Risk (CMAR), the CM has both preconstruction services and then a construction contract with a Guaranteed Maximum Price.

In IPD, key participants share responsibilities collaboratively, often under multi-party agreements.

Because contracts and relationships change with the delivery method, the Project delivery type (Option D) is what determines how responsibilities are allocated in a formal, contractual sense.

Why the other options are not the best answer:

A. Size of the project – Larger projects may require more staff or additional roles (e.g., full-time construction administrator), but they do not fundamentally change who is contractually responsible for design, construction, and administration.

B. Nature of the project – A hospital vs. a warehouse may influence technical requirements and consultant types, but not the core allocation of responsibilities if the delivery method is the same.

C. Cost of construction – Budget level affects scope and possibly oversight intensity, but not the basic contractual roles of owner, A/E, and contractor.

Key CSI-Oriented References (titles only, no links):

CSI Project Delivery Practice Guide – chapters on Project Delivery Methods and team responsibilities.

CSI CDT Body of Knowledge – “Project Delivery Methods and Their Impact on Roles and Responsibilities.”

CSI defines three major, complementary organizing tools:

MasterFormat® – classifies work results and organizes specification sections into numbered divisions.

SectionFormat® – standardizes the internal arrangement and headings of text within each specification section (e.g., Part 1 – General, Part 2 – Products, Part 3 – Execution), making it easy to read and quickly reference.

UniFormat® – organizes information by systems and assemblies, often used in early design and cost planning rather than final spec sections.

The question specifically asks about a format that standardizes how the text is arranged on specification pages for easy reading and rapid reference. That is exactly the role of SectionFormat®: it defines the structure and order of information inside the section so that users know where to find general requirements, product information, and execution requirements, regardless of the project.

By contrast:

MasterFormat® (Option C) organizes which section information goes into (coding and naming of sections), not the layout of text within the section.

UniFormat® (Option D) structures information by building systems/elements, especially for programming and early design, not for final spec page layout.

PageFormat (Option B) is not one of CSI’s registered, widely recognized branded formats in the way the question is framed.

Therefore, the correct answer is Option A – SectionFormat®.

CSI-aligned references (no URLs):

CSI Construction Specifications Practice Guide – chapters on MasterFormat®, SectionFormat®, and UniFormat®.

CSI SectionFormat® & PageFormat™ standard (CSI publication).

CSI defines specifications (the spec sections in the project manual, typically organized by MasterFormat and SectionFormat) as the written requirements for:

Materials, products, and equipment

Systems and assemblies

Workmanship and installation

Quality, performance, and administrative/procedural requirements related to the work

In CSI’s traditional “drawings vs. specs” distinction:

Specifications primarily describe the qualitative requirements (what quality, what type, what standard, what performance, what procedures).

Drawings primarily show quantitative and dimensional information (how much, how big, where located, configurations and relationships).

Because of this, the correct choice is:

C. Qualitative requirements for products, materials, and workmanship.

Why the other options are incorrect, per CSI usage:

A. All written construction documentsThe project manual may also contain bidding requirements, contract forms, and conditions of the contract, but in CSI terminology, “Specifications” refers specifically to the spec sections, not every written document.

B. All written and drawn construction documentsSpecifications do not include drawings. Drawings are separate contract documents that complement specs; together they define the work, but the term “specifications” is not used to include drawings.

D. Quantitative requirements for products, materials, and workmanshipQuantitative information (dimensions, counts, locations, quantities) is primarily the role of drawings and related schedules, sometimes supported by quantity-related notes. Specifications may include some numbers, but their core function is qualitative and performance-based requirements, not serving as the main vehicle for quantities.

Key CSI-aligned references (no URLs):

CSI Construction Specifications Practice Guide – definitions of specifications and their relationship to drawings.

CSI Project Delivery Practice Guide – sections discussing contract documents and the role of the project manual.

CSI MasterFormat, SectionFormat + PageFormat documents – organize and describe written spec requirements.