Construction Specifications Institute CDT Practice Test Questions Answers

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.

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

In CSI’s project delivery and documentation discussions, BIM is consistently defined as “Building Information Modeling.”

CSI describes BIM as:

A digital representation of the physical and functional characteristics of a facility.

A shared knowledge resource for information about a facility, forming a reliable basis for decisions during its life cycle.

A tool that supports coordination, clash detection, documentation, quantity takeoff, and communication between design and construction team members.

BIM models are used alongside, and coordinated with, drawings, specifications, and other contract documents, and they support communication and decision-making throughout design, construction, and sometimes operation.

The other options are not recognized industry meanings of BIM:

B. Business Information Manual – not a standard construction-industry term.

C. Building Interior Maintenance – does not match CSI or industry definitions of BIM.

D. Building Inspection Manual – again, not the accepted meaning of BIM in the AEC context.

Therefore, in the construction context, BIM stands for “Building Information Modeling” (Option A).

Key CSI References (titles only):

CSI Project Delivery Practice Guide – chapters addressing BIM and information management.

CSI Construction Specifications Practice Guide – discussions of model-based delivery and coordination with specifications.

CSI CDT Body of Knowledge – terminology and emerging practices including BIM.

CSI identifies several cost-control tools used in specifications and bidding documents:

Alternates – provide optional changes in scope or quality that can add or deduct cost.

Unit prices – establish prices for specific items or quantities where exact amounts may vary.

Contingencies – funds reserved by the owner (in the project budget) for unexpected conditions.

Allowances – specified amounts included in the contract sum for items whose exact product, quantity, or selection is not yet known at bid time.

When insufficient information is available to make final product decisions during design, CSI’s guidance is that the A/E can maintain control over construction cost by specifying allowances. An allowance:

Is clearly described in the specifications or Division 01.

Provides a defined monetary amount (or quantity and unit cost) for a future selection (for example, certain finishes, fixtures, or equipment).

Allows the project to proceed to bidding and contract award while preserving cost control, because bidders all carry the same allowance values in their bids.

Thus the best answer is D. Allowances.

Why the other options are less appropriate:

A. AlternatesAlternates help manage scope and options, but they do not directly solve the problem of not yet knowing which specific product will be chosen. They are more about “add or deduct” scenarios than uncertain product selection.

B. Unit pricesUnit prices are used when quantities are uncertain, not when product decisions themselves are unknown. They are tied to measurable units (e.g., cubic meters of rock excavation), not to undecided product choices.

C. ContingenciesContingencies are normally an owner’s budgeting tool, not written into the contract in the same way as allowances. They help the owner plan for unknowns but do not provide a structured way in the specifications to carry costs for undecided products.

Key CSI Reference Titles (no links):

CSI Project Delivery Practice Guide – sections on Cost Management and Design Phase cost-control tools.

CSI Construction Specifications Practice Guide – Division 01 provisions for Allowances, Alternates, and Unit Prices.

CSI CDT Body of Knowledge – “Methods of Specifying and Cost Control Provisions in the Project Manual.”

Top of Form

Bottom of Form

During the construction documents phase, CSI’s guidance emphasizes that coordination between the architect/engineer (A/E) and the various consulting disciplines (structural, mechanical, electrical, etc.) is essential to produce consistent, coordinated, and complete contract documents (drawings, specifications, and project manual). Part of that coordination is a shared quality assurance (QA) effort among the design team members.

In CSI’s practice guides and CDT body of knowledge, the following principles are stressed (paraphrased to respect copyright):

The prime design professional is responsible for overall coordination of the construction documents, but each consultant is responsible for the technical accuracy and coordination of their own portions.

Coordination includes review of cross-references, matching terminology, alignment of requirements between drawings and specifications, and resolving conflicts before bid/issue.

Quality assurance during this phase is not done in isolation; it is a team activity. Consultants and the lead design firm review each other’s work where it interfaces (e.g., architectural and mechanical coordination of ceilings and diffusers; structural and architectural coordination of openings, etc.).

Therefore, “Quality assurance tasks shared between design and consulting teams” (Option D) correctly describes a standard component of project design team coordination during the construction documents phase.

Why the other options are incorrect:

A. Duplication of important information by each disciplineCSI stresses “say it once, in the right place” as a fundamental principle. Information should not be unnecessarily duplicated because duplication increases the risk of conflict and inconsistency (for example, a requirement shown in both drawings and multiple spec sections but updated in only one location). Coordination aims to avoid duplication, not to promote it.

B. Ensuring drawing note terminology is differentiated from specification terminologyCSI emphasizes consistent terminology across drawings, specifications, and other documents. The same items (e.g., “gypsum board,” “reinforcing steel,” “membrane roofing”) should be described using the same terms in both drawings and specifications to reduce ambiguity. Coordination meetings often include checking that terminology is aligned, not intentionally differentiated.

C. Requiring the owner to hire a third-party to write the Division 01 specifications independentlyDivision 01 – General Requirements – is typically prepared or controlled by the lead design professional or specifier, in coordination with the owner. CSI materials do not identify it as a standard or required coordination practice for the owner to hire an independent third party to write Division 01 separately from the design team. That may occur on some projects, but it is not a defined component of team coordination in CSI’s CDT framework.

In summary, CSI-based construction documentation practice defines coordination during the construction documents phase as a shared responsibility among the architect/engineer and all consultants, including joint quality assurance reviews, consistency checks, and cross-discipline coordination. This aligns directly with Option D.

Key CSI References (no links):

CSI Project Delivery Practice Guide – chapters on Design Phase and Construction Documents coordination.

CSI Construction Specifications Practice Guide – sections on coordination between drawings and specifications and the role of Division 01.

CSI CDT Body of Knowledge – topics on roles and responsibilities of the design team and coordination of construction documents.

Within CSI’s project delivery framework, the Design stage (which includes schematic design and design development) is where the architect/engineer (A/E) works with the owner to evaluate options, select specific systems, and record decisions that will later be fully detailed in the construction documents.

CSI’s project-phase descriptions (as presented in the CSI Project Delivery Practice Guide and CDT study materials) explain the stages roughly as follows (paraphrased, not verbatim):

Project Conception: The owner defines a need or opportunity, explores whether a project is warranted, and considers general feasibility. The focus is on defining the reason for the project, not picking specific products or systems.

Programming: The owner’s requirements and objectives are documented—space needs, performance criteria, budget, schedule, and qualitative expectations. At this point, needs and performance requirements for systems (e.g., “energy-efficient HVAC,” “durable flooring”) are identified, but not necessarily specific named products or system configurations.

Design:

Schematic Design: General design concepts, overall configuration, and preliminary system approaches are developed; the owner begins making more concrete decisions.

Design Development: The A/E and consultants refine and confirm decisions about specific systems, materials, and assemblies, and these decisions are documented so they can be incorporated into specifications and drawings.

Construction Documents: The A/E takes those already-made decisions and fully documents them in coordinated drawings and specifications, but this phase is not usually where the majority of decisions about which specific products and systems to use are first obtained; instead, it formalizes and details what was already decided in Design.

CSI’s CDT content emphasizes that during Design Development, the A/E “confirms and documents owner decisions about materials, products, and systems” so that these can be translated into clear contract documents during the Construction Documents phase. That activity—obtaining and documenting the owner’s decisions about specific products and systems—is core to the Design stage, making Option B correct.

Why the other options are not correct under CSI’s framework:

A. Construction documentationIn the Construction Documents phase, the A/E develops the detailed drawings and specifications based on decisions made earlier. Changes and additional decisions can occur here, but CSI treats the primary “obtaining and documenting owner choices” as a Design-stage responsibility; the CD phase is about formalizing and coordinating them into contract documents.

C. Project conceptionAt conception, there often isn’t an A/E contracted yet, and the owner is still deciding whether to proceed at all. Product and system decisions would be far too early and poorly defined at this point.

D. ProgrammingProgramming focuses on what the facility must do, not on exactly how via specific products or named systems. It defines performance and functional requirements (e.g., acoustical needs, energy performance) but typically stops short of selecting specific manufacturers or detailed system configurations.

Key CSI-aligned references (no links):

CSI Project Delivery Practice Guide – chapters on project phases (Programming, Design, Construction Documents) and owner/A/E responsibilities.

CSI CDT Body of Knowledge – sections on the Design phase and decision-making responsibilities for products and systems.