Within CSI’s project delivery and construction documents framework, quality control (QC) refers to activities that check and verify the accuracy and completeness of the work product itself —in this case, the drawings, specifications, and other parts of the project manual before they are issued for bidding or construction.

Peer reviews and internal reviews of completed documents are performed after the documents have been prepared, specifically to find and correct errors, omissions, conflicts, or lack of coordination.

These reviews examine the end product of the documentation process (the drawings and specifications), checking conformance with office standards, project requirements, code requirements, and coordination between disciplines.

CSI distinguishes this from quality assurance (QA), which focuses on the systems and procedures used to produce the documents (such as standard checklists, training, and office procedures). QC, by contrast, is concerned with reviewing the actual deliverables .

Therefore, activities like peer review of completed drawings and specifications, internal checking of finished sections, and coordination review of the project manual are classic examples of quality control tasks, not commissioning, QA-in-the-abstract, or construction administration.

Commissioning (B) focuses on verifying that systems and equipment are installed, tested, and performing according to the contract documents near project completion—not on checking design documents in the office.

Quality assurance (C) is the broader system of policies, procedures, and standards that aim to prevent errors , such as standard templates, firm-wide procedures, and training; the act of reviewing specific completed documents falls under QC.

Construction administration (D) includes responding to RFIs, reviewing submittals, processing change orders, and site visits during construction; it is not the term CSI uses for internal checking of design documents.

Key CSI-aligned references (no URLs):

CSI Project Delivery Practice Guide – chapters on Quality Management, Design Phase, and Construction Documents.

CSI Construction Specifications Practice Guide – content on quality assurance vs. quality control in construction documentation.

CSI CDT Body of Knowledge – sections on document coordination, reviews, and quality processes.

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.

CSI’s project delivery and ethical guidance (as reflected in CDT materials and standard practice) emphasize:

Known information that may affect cost, risk, or safety must be disclosed consistently and fairly to all bidders.

The design professional must act in a manner that is honest, transparent, and protective of public safety , even when data is incomplete.

The bid documents should not conceal information that could materially affect the work, even if its full extent is uncertain.

Applying those principles:

The design team has evidence (one contaminated boring) that contamination may exist onsite . Even if the extent is unknown, that fact is potentially material to bidders (cost of remediation, handling of contaminated soils, schedule impacts).

The best course is to disclose what is known and ensure all bidders have access to the same geotechnical information. This is exactly what Option B proposes:

Place a clear note or disclaimer in the contract documents stating that contaminants were encountered in at least one boring and may be present elsewhere.

Recommend that the owner make the geotechnical report available to all bidders , so every bidder can evaluate the risk and price accordingly.

Why the other options are inconsistent with CSI-aligned practice:

A. Withhold the information… – Concealing known contamination is unethical and undermines fair bidding. Even with unit prices for remediation, bidders would be pricing blindly without knowing that contamination has already been detected.

C. Insist the owner undertake additional investigation… – While the design team should recommend further investigation, it cannot “insist” beyond professional advice, especially where the owner has clearly stated financial constraints. Regardless, disclosure of existing data is still required.

D. Proceed with design as is… – Ignoring known contamination and calling it “statistically insignificant” is not defensible; even one contaminated boring is important information that must be shared.

So, the most appropriate and CSI-consistent choice is Option B : disclose the potential and share the geotechnical report so all bidders are equally informed.

CSI references (by name only, no links):

CSI Project Delivery Practice Guide – sections on procurement, fair competition, and disclosure of information

CDT ethics and professional conduct principles regarding risk disclosure to bidders

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 documentation In 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 conception At 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. Programming Programming 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.

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 (CSI-aligned, paraphrased)

CSI and commonly used general conditions define Substantial Completion as the stage in the progress of the Work when:

The Work, or a designated portion, is sufficiently complete in accordance with the Contract Documents so that the Owner can occupy or utilize it for its intended use .

Important implications in CSI/CDT context:

Substantial Completion is a functional milestone , not simply an administrative or paperwork milestone.

At Substantial Completion:

The Owner can begin using the facility for its intended purpose (e.g., occupy offices, treat patients, teach classes).

The warranty periods typically begin , unless otherwise specified.

The responsibility for utilities, security, and insurance often shifts in whole or in part to the Owner.

Final inspections, final payment, and complete closeout documentation generally occur after Substantial Completion.

So the correct definition is:

A. When the project is sufficiently complete to allow its intended use.

Why the other options are not correct:

B. When the project receives final inspections from the authorities having jurisdiction – AHJ inspections (for occupancy permits, etc.) are important and often coincide with or enable Substantial Completion, but they are regulatory milestones , not the contractual definition itself. Substantial Completion is determined under the contract, usually via certification by the A/E.

C. When the contractor’s final application for payment is approved – That is associated with Final Completion , which occurs after all work (including punch list) is done and all closeout requirements are met. Substantial Completion occurs before final payment.

D. When all of the close-out documents have been reviewed and approved – Closeout submittals (O & M manuals, warranties, as-builts) are typically prerequisites for final payment and Final Completion , not for Substantial Completion.

Key CSI-Related Reference Titles (no links):

CSI Project Delivery Practice Guide – sections on Construction Phase, Substantial Completion, and Final Completion.

CSI Construction Specifications Practice Guide – Division 01 “Closeout Procedures” and “Substantial Completion” articles.

CSI CDT Study Materials – definitions of Substantial and Final Completion.

CSI’s project delivery and CDT materials describe design as having a dual nature :

An aesthetic (or qualitative/artistic) side – concerned with form, appearance, spatial experience, and how the built environment is perceived and used.

A technical side – concerned with structural integrity, building systems, code compliance, constructability, performance, and cost.

In the broader project-management literature you’ve uploaded, the design and construction process is described as blending technical requirements with broader qualitative and organizational goals. For example, the project life cycle discussion notes that each stage involves both technical and managerial activities , reflecting the need to satisfy functional, performance, and experiential objectives simultaneously.

CSI’s CDT framework builds on this by emphasizing that:

The architect/engineer must respond to owner values (aesthetics, image, function) and

Technical constraints and criteria (codes, standards, performance, budget, schedule).

This is what is commonly summarized in CDT study materials as the “dual nature of design” – aesthetic and technical .

Why the other options do not match CSI’s phrasing:

A. Site and building – Both are important aspects of design, but CSI’s dual-nature concept is not expressed as site vs. building.

C. Programming and planning – These are phases or processes that precede or support design, not the two “natures” of design itself.

D. Innovation and authenticity – Desirable qualities, but not the canonical CSI pair.

Thus, the correct pair that matches CSI’s description of the dual nature of design is Option B – Aesthetic and technical .

CSI-aligned references (no URLs):

CSI Project Delivery Practice Guide – “The Design Stage” (discussion of design as both artistic/aesthetic and technical/problem-solving).

CSI CDT body of knowledge – conceptual overview of the designer’s responsibilities and

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

In CSI practice (as reflected in the CSI Construction Specifications Practice Guide and CDT study materials), warranties are treated as supplemental protection for the owner, not as a primary quality-control method. CSI emphasizes that the specifier should carefully research products, manufacturers, and performance history , and that the specifications should clearly define the required quality, performance criteria, and execution. A warranty cannot compensate for poor product selection or incomplete specification of performance and quality.

Because of this, relying on a warranty as a substitute for thorough investigation of a product and its manufacturer (Option D) is specifically contrary to CSI guidance. CSI’s approach is:

First: proper investigation and evaluation of the product and manufacturer (technical suitability, history, service, financial stability).

Second: clear, enforceable specifications stating performance and quality requirements.

Third: warranties as an additional contractual obligation, not a replacement for the first two.

That is exactly what Option D fails to do, so it is the practice that should be avoided.

Why the other options are acceptable in CSI terms:

Option A – Requiring or permitting a warranty that strengthens the owner’s rights CSI allows and often encourages warranties that provide greater protection than the default legal warranties, so long as they are realistic, coordinated with the contractor and manufacturer, and enforceable. Strengthening the owner’s rights through clear warranty language is consistent with CSI’s recommended practice, not something to avoid.

Option B – Requiring minimum warranty coverage available for a particular product It is normal in CSI-style specifications to state a minimum warranty duration or coverage (for example, “not less than 5 years” for roofing). This sets a clear baseline of expectations and is fully compatible with CSI guidance, provided it matches industry practice and project needs.

Option C – Including language to require warranties extending beyond the contractor’s one-year correction period CSI explicitly distinguishes between the contractor’s correction period (often one year, as described in the General Conditions) and longer manufacturer warranties (e.g., 5, 10, or 20 years). It is routine and appropriate for specifications to require manufacturer warranties that extend beyond the one-year correction period , especially for major building envelope or equipment systems. CSI materials show these longer warranties as normal practice, not something to avoid.

So, under CSI’s Construction Specifications Practice and CDT body of knowledge, the clearly incorrect—and therefore “to be avoided”—practice is Option D : counting on a warranty instead of doing the proper technical due diligence and specifying performance and quality requirements.

CSI reference concepts:

CSI Construction Specifications Practice Guide – chapters on warranties and product selection (discussing warranties as supplemental protection, not a substitute for proper specifying).

CSI CDT Study Materials – sections on Division 01, product selection, and quality assurance/quality control versus warranties.

In CSI/CDT programming and early project decision-making, the classic four primary project considerations are:

Function – What the facility must do; the operational and performance requirements.

Form – The physical configuration and appearance: size, shape, spatial relationships, and aesthetic character.

Economy – The financial aspects: project budget, life-cycle cost, operating costs, and economic constraints.

Time – Project and site timing: required completion date, phasing, and schedule constraints.

These four are used in programming and early planning (including site selection and site programming ) to structure owner–designer discussions and decisions. During site selection programming, the owner and design team evaluate how different sites support the project’s required function , allow appropriate form , meet economic constraints, and fit within time (schedule and phasing) limitations.

This four-part framework— Function, Form, Economy, Time —matches Option B exactly.

Why the other options are incorrect:

All three incorrect options are variations that re-label or partially capture the same ideas but do not use the standard terminology as defined in CSI/CDT references:

A. Use, space, funds, date

“Use” ≈ function

“Space” ≈ form

“Funds” ≈ economy

“Date” ≈ time While conceptually similar, CSI’s established terminology for programming and site selection is Function, Form, Economy, Time , not this wording.

C. Purpose, shape, cost, schedule Again, these loosely correspond to function, form, economy, and time, but CSI uses the more formal terms that appear in its programming discussions and CDT content: Function, Form, Economy, Time .

D. Goal, condition, budget, calendar These terms are more generic and do not match the recognized four-part framework used in CDI/CDT materials for programming and site selection.

CSI / CDT-aligned references (no links):

CSI Project Delivery Practice Guide – chapters on Programming and Planning, including the function–form–economy–time framework used in early decision-making and site selection.

CDT Body of Knowledge – owner’s project requirements and programming considerations.

According to CSI and standard General Conditions (such as AIA A201 and EJCDC C-700, both referenced in CSI’s CDT materials), the contractor has a duty to review the contract documents for coordination and constructability, and if any errors, inconsistencies, or code violations are discovered, the contractor must promptly notify the architect/engineer (A/E) in writing before proceeding.

This requirement exists because:

The A/E is responsible for design compliance with codes.

The contractor must not proceed with work known to be contrary to applicable laws or regulations without clarification.

The contractor’s written notice triggers the A/E’s responsibility to issue clarification, correction, or instruction to maintain compliance.

Therefore, the proper action is Option A — Notify the architect/engineer in writing.

Why others are incorrect:

B. Proceed with the work – would expose both the contractor and owner to risk of code violation; explicitly prohibited by standard conditions.

C. Request a variance – is not the contractor’s responsibility; this rests with the owner or A/E.

D. Stop all work – not authorized unless directed; the contractor must first notify the A/E.

CSI Reference:

CSI Project Delivery Practice Guide , “Construction Phase — Communications and Responsibilities”; Construction Specifications Practice Guide , “General Conditions Responsibilities — Compliance with Codes.”