CDT Construction Specifications Institute Construction Documents Technologist Free Practice Exam Questions (2026 Updated)

CSI uses the term value analysis or value engineering to describe a structured, function-oriented process that examines the relationship between:

The functions a building element or system must perform, and

The cost of achieving those functions

The objective is to improve value, which can mean:

Reducing initial cost without reducing required performance or quality

Reducing life-cycle cost (operation, maintenance, replacement)

Improving performance, quality, durability, or maintainability for a similar cost

Therefore, value analysis can be used:

“To enhance project value or reduce initial or long-term cost.” (Option B)

CSI stresses that value analysis is not simply “cheapening” the project; it is a disciplined decision-making process that balances cost and function to achieve the best overall value for the owner.

Why the other options are not correct in CSI terms:

A. To provide the owner with the lowest construction cost.The lowest first cost is not the sole or primary goal under CSI’s view. An excessively low first cost may sacrifice performance or significantly increase operation and maintenance costs. Value analysis focuses on best value, not just cheapest construction.

C. A phase for future work to allow higher quality items up front.Value analysis is a process or technique, not merely a “phase for future work.” It also does not inherently mean you always choose higher quality up front; sometimes it leads to lower initial cost, sometimes to better performance, sometimes a balance.

D. To change the perceived value by owner and stakeholder.While owner and stakeholder perception matters, CSI presents value analysis as a technical, function-and-cost-based method, not just a way to change perceptions. The goal is objective improvement of value, not merely altering how the project is perceived.

Key CSI-aligned references (no URLs):

CSI Project Delivery Practice Guide – sections on Value Analysis/Value Engineering in design and preconstruction phases.

CSI CDT Body of Knowledge – topics on cost, value, life-cycle thinking, and decision-making.

CSI-related discussions of life-cycle cost and value in project decision processes.

CSI’s project delivery and CDT materials distinguish clearly between public and private procurement:

Public work (funded and contracted by government entities) is typically governed by statutes and regulations that require:

Formal advertisement,

Clearly defined bidding procedures,

Sealed bids opened publicly at a specified time and place, and

Award to the lowest responsive and responsible bidder, except where law allows other defined selection methods.

Private work, by contrast, is not generally bound by these public procurement statutes. CSI explains that private owners have significantly more flexibility, including:

Not being required to publicly open bids,

Being able to negotiate with one or more bidders,

Rejecting any or all bids, and

Awarding the contract to any responsive and responsible bidder they choose, based on value, qualifications, schedule, or other criteria—not solely lowest price.

Because of this flexibility, CSI emphasizes that a private owner may select a bidder other than the lowest as long as the bidder is responsive (submits a bid per the requirements) and responsible (qualified, capable, and reliable). This matches Option D exactly.

Why the other options are incorrect or misleading:

A. A private owner may waive any informality in the bidding, except for the performance bond.While private owners often can waive bid informalities, CSI does not state any universal rule that the performance bond is a special exception in private bidding. Performance bonds are typically part of the contract requirements after award, not a fixed “unwaivable informality” in bid receipt; treatment of bonding is governed by the owner’s requirements and any applicable law, not a CSI rule unique to private work.

B. Private bids may be opened in private, but the results must be published in a reasonable time.Publication of bid results is a hallmark of public work (transparency and accountability). CSI does not require private owners to publish bid results; private owners may keep them confidential if they wish, unless other obligations apply (e.g., corporate policies).

C. The laws and regulations for private bidding are the same as for public bidding.CSI specifically distinguishes between public and private owners: public owners are constrained by statutes and regulations, whereas private owners have much more discretion. The laws governing public bidding and private bidding are not the same, and this is a key CDT concept.

Thus, the CSI-consistent distinction is that private owners are free to award the contract to a responsive and responsible bidder who is not the lowest, making Option D the correct choice.

Key CSI-aligned references (no links):

CSI Project Delivery Practice Guide – procurement and bidding chapters comparing public and private practice.

CSI CDT Body of Knowledge – sections on bidding requirements, “responsive and responsible bidder,” and differences between public and private construction procurement.

Good documentation of project decisions (typically in meeting minutes) is essential for traceability, accountability, and later dispute avoidance. CSI-oriented project management procedures and your uploaded construction management documents emphasize that minutes should record, at a minimum:

When the meeting occurred – date, time, location.

Who attended and whom they represent (owner, A/E, contractor, etc.).

What was decided and what remains unresolved.

Action items, assigned responsibilities, and due dates.

These elements are repeatedly included in the sample agendas and minutes procedures in your Construction Management Plan and Project Management Manual, which require minutes and action/open-items lists to be prepared and circulated after key meetings.

None of these procedures mention, or require, tracking how long each attendee spoke. That level of granularity does not contribute meaningfully to documenting decisions, responsibilities, or follow-up work. It adds administrative burden without improving clarity or accountability.

Thus:

A (date/time/location) – important context for the record.

B (attendees and representation) – critical to know who agreed to what.

D (action items, responsibilities, dates) – central to the decision-making trail.

C (length of time each attendee spoke) – least important and not standard practice in CSI-based documentation.

So the correct answer is Option C.

CSI-aligned references (no URLs):

CSI Project Delivery Practice Guide – sections on project meetings and documentation.

CSI CDT body of knowledge – “Documenting decisions and maintaining project records.”

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.

CSI’s project delivery and scheduling discussions describe network scheduling techniques such as the Critical Path Method (CPM) as tools for planning, sequencing, and controlling project time. CPM scheduling can be done either:

Forward, starting from a known start date and computing early and late completion dates, or

Backward, starting from a required completion/occupancy date and working backward to determine the latest allowable dates for preceding activities and milestones so that the final completion date is achieved.

This “working backward from a target completion or occupancy date to set milestone dates” is a classic application of the backward pass within the Critical Path Method. CSI’s project management materials emphasize that CPM is used to:

Establish logic relationships and durations,

Calculate early and late start/finish dates,

Identify the critical path, and

Adjust the schedule to meet a required completion or occupancy date by compressing or resequencing activities where possible.

Why the other options are not correct:

A. Methods technique – This is not a standard CSI or mainstream term for a recognized scheduling method.

C. Front end loading – In project management and cost engineering usage, this refers to investing significant effort early in project definition and planning; it is not specifically defined as the technique of back-scheduling from an occupancy date.

D. Schedule of values – This is a cost-allocation and payment document that breaks the contract sum into portions for progress payments. It is not a scheduling technique.

Because CPM scheduling explicitly supports setting a required completion date and then working backward to develop realistic milestone dates and activity sequencing, Option B – Critical path method is the best and CSI-consistent answer.

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.

CSI and the AIA A201–style general conditions define Substantial Completion as the stage in the progress of the work when the project (or a designated portion) is sufficiently complete in accordance with the contract documents so that the Owner can occupy or use it for its intended purpose.

In the typical Owner–Contractor Agreement, a clause or article states either:

A calendar date for substantial completion, or

A number of days from the date of commencement by which substantial completion must be achieved.

This is what establishes the duration of the work and the key date when the Owner can begin using the facility. Therefore, Option C – Date of substantial completion – correctly identifies the provision that defines the duration and occupancy milestone.

Why the others are incorrect:

A. Cutoff date – Not a standard CSI/AIA contract term.

B. Date of commencement of the work – This identifies the start, not the required completion/occupancy point.

D. Scope of work – Describes what is to be built, not when it must be complete or ready for use.

Relevant CSI references (no links):

CSI Project Delivery Practice Guide – sections on contract time, substantial completion, and final completion.

CSI CDT Study Materials – definitions of substantial completion, correction period, and related milestones.

Comprehensive and Detailed Explanation From Exact Extract (CSI-aligned, paraphrased)

CSI describes several techniques in the procurement documents to manage cost uncertainty. When the owner is concerned that the project may exceed the budget when bids are received, the most common tool to allow scope flexibility is the use of alternates.

Alternates (often called “bid alternates”):

Are defined variations in the work (additions or deletions) that bidders price separately from the base bid.

Can be additive (additional scope that can be accepted if the budget allows) or deductive (scope that can be removed to reduce cost if needed).

Give the owner the ability, after seeing the base bids, to accept or reject alternates to bring the project within the available budget without redesigning the entire project.

This fits the scenario in the question exactly: the owner anticipates that the budget may be tight and wants a mechanism to adjust the final contract amount if bids come in high.

Why the other options are not the primary CSI method for this budget-flexibility issue:

A. Cash allowanceAn allowance is a set amount included in the contract sum to cover a defined but not fully specified portion of the work (e.g., artwork, specialty items). It helps manage scope uncertainty, but it doesn’t systematically provide a way to reduce overall cost after bids in the same way alternates do.

B. Quantity allowanceThis is a form of allowance tied to a presumed quantity (e.g., rock excavation). It addresses uncertain quantities, not overall budget flexibility in the bidding process.

C. Unit pricingUnit prices provide fixed prices per unit (e.g., per cubic meter, per square meter) for work items whose final quantities are uncertain. They are useful for adjustments after contract award as quantities change, but they are not the primary tool for adjusting total scope to meet the owner’s budget at bid time.

Therefore, the CSI-aligned answer for allowing flexibility when bids may exceed the budget is:

D. Alternates

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

CSI Project Delivery Practice Guide – procurement and pricing strategies, including alternates and allowances.

CSI Construction Specifications Practice Guide – Division 01 sections on Alternates, Unit Prices, and Allowances.

CSI CDT Study Materials – explanations of bid alternates and their role in controlling project cost.

CSI and CDT principles stress that clear, timely, and documented communication is essential to avoid disputes and miscommunication during construction. Among the key tools for this are:

Written records of decisions, instructions, and clarifications

Formal meeting minutes that are distributed and retained as part of the project record

Consistent use of designated channels (e.g., RFIs, submittals, change documents)

In construction phase administration, progress meetings and other coordination meetings are routinely held. Best practice, as described in CSI guides and standard contract documents, is that:

One party (often the architect or construction manager) prepares written meeting minutes.

These minutes record attendance, topics discussed, decisions made, and action items (with responsible parties and due dates).

The minutes are then distributed to all attendees and other concerned parties, providing a shared, written understanding and an opportunity to correct any errors.

This practice directly addresses the question’s goal: avoiding miscommunication problems during construction. Therefore, the best answer is Option C.

Why the other options are weaker:

A. Develop a good working relationship for verbally addressing problems as they ariseA good working relationship is very important, but verbal-only communication is risky. CSI emphasizes that important decisions and directions must be documented in writing.

B. Mark emails and electronic communications as "Urgent!"This may get attention but does not ensure clarity, completeness, or shared understanding, and overuse can even reduce effectiveness.

D. Leave detailed voicemail messagesVoicemail is not a reliable or easily referenced project record. It is difficult to circulate, file, search, or confirm, and can easily be misunderstood or lost. CSI emphasizes written, project-file communication over voicemail.

Relevant CSI / CDT References (titles only, no links):

CSI Project Delivery Practice Guide – chapters on “Construction Phase” and communication and documentation.

CSI Construction Specifications Practice Guide – Division 01 sections on “Project Management and Coordination” and “Project Meetings,” including requirements for meeting minutes.

CDT Body of Knowledge – communication and documentation practices in construction administration.

Comprehensive and Detailed Explanation (CSI-aligned, paraphrased)

CSI’s description of the Design-Bid-Build (DBB) method highlights several characteristics:

The design professional completes the contract documents before bidding.

Contractors bid competitively based on a defined scope.

The owner’s construction cost is not known with certainty until bids are opened.

Among the commonly cited disadvantages of DBB in CSI-related materials are:

Cost risk at bid time – If the market is volatile, or if the design and scope outpace the budget, there is a real possibility that all bids may exceed the owner’s budget, forcing redesign, rebid, or scope reductions.

Longer overall project duration due to the sequential nature (design is completed before bidding, and bidding before construction).

Limited contractor input during design compared with more integrated methods (e.g., CM at Risk, Design-Build, IPD).

Given the answer choices, the one that matches a recognized, fundamental DBB disadvantage is:

B. All of the bids may exceed the owner’s budget

Why the other options are not accurate disadvantages in the CSI sense:

A. It attracts too many biddersHaving multiple bidders is generally considered a benefit of competitive bidding, promoting better pricing and selection, not a defined drawback.

C. It requires a higher level of bid document qualityAll methods benefit from high-quality documents. While DBB does rely heavily on complete and coordinated documents before bidding, CSI does not characterize this as a “primary disadvantage” but rather a professional obligation regardless of delivery method.

D. It reduces the owner’s control over the project during the construction phaseIn fact, in traditional DBB, the owner typically has significant control: separate contracts with A/E and contractor, direct role in changes, submittal review, etc. Compared with Design-Build, DBB often gives more direct owner oversight, not less.

Key CSI-Related References (titles only):

CSI Project Delivery Practice Guide – comparison tables of DBB, CM at Risk, Design-Build, and IPD, including advantages and disadvantages.

CSI CDT Study Materials – sections on project delivery methods and associated risk/allocation.

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.”

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.

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.

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

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.

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.

Under standard conditions of the contract used in CDT (e.g., AIA A201 as referenced by CSI), when hazardous materials or unsafe conditions are encountered:

The Contractor is required to stop work in the affected area and notify the Owner and Architect/Engineer.

The Contractor must not proceed until the hazardous condition has been evaluated and remedied by the Owner with qualified professionals.

CSI’s project delivery materials emphasize that the contractor is responsible for means, methods, and safety of construction operations. That includes the authority—indeed the obligation—to stop work where hazardous substances or conditions present an imminent danger to workers.

Why the others are incorrect:

A. Architect/engineer – The A/E can recommend suspension of work for nonconforming work or other reasons, but the specific duty and right to stop work because of hazardous conditions in the field lies with the Contractor under typical general conditions.

C. Stakeholders – This is a generic term, not a contract party with defined authority in CSI’s framework.

D. Facility manager – The facility manager may be involved if the existing facility is affected, but is not the contract party empowered in the construction contract to stop the contractor’s work.

Relevant CSI references (no links):

CSI Project Delivery Practice Guide – chapters on Construction Phase responsibilities and safety.

CSI CDT Body of Knowledge – discussion of contractor responsibilities and hazardous materials clauses in standard general conditions.

CSI and standard General Conditions define the architect/engineer’s submittal review purpose as confirming that submittals conform to the design intent shown and specified in the contract documents — not to approve means, methods, or to revise design.

The A/E’s review checks:

General compliance of the submittal with design intent.

Coordination among trades.

Any deviations that require clarification or change approval.

It is not for:

Designing or redesigning (Option A),

Supervising construction procedures (Option C), or

Evaluating formal substitution requests (Option D) — substitutions are separately submitted for approval under Division 01 procedures.

Therefore, the A/E reviews submittals to monitor design conformance, making Option B correct.

CSI Reference:

CSI Construction Specifications Practice Guide, “Submittal Procedures and Responsibilities”; Project Delivery Practice Guide, “Construction Phase — Submittal Review.”

Under CSI’s project delivery framework and the typical General Conditions of the Contract, the contractor has primary responsibility for:

The means, methods, techniques, sequences, and procedures of construction.

Job site safety and security, including protection of workers, the public, and the work itself.

Controlling access to the site, securing materials and equipment, and complying with safety laws and regulations.

CSI’s CDT materials summarize the allocation of responsibilities this way (paraphrased):

The owner is responsible for providing information, funding, and overall project requirements; the owner does not direct day-to-day site operations or security.

The architect/engineer is responsible for design and contract administration functions such as reviewing submittals, certifying payments, and evaluating change requests—not for job site security or safety control.

The contractor (or construction manager acting as contractor, where applicable) is the party who controls the site and is therefore responsible for job site safety and security.

Even when a construction manager is involved (Option D), CSI and standard general conditions distinguish between a CM as advisor (who advises the owner) and a CM as constructor (who is essentially the contractor). For the exam-style question as written, “contractor” is the single correct generic answer for who is responsible for job site security.

Why the other options are not correct:

A. Owner – The owner does not direct means and methods or daily site activities; shifting site security responsibility to the owner would contradict the usual conditions of the contract.

B. Architect/engineer – The A/E does not control the job site and is not responsible for job site safety/security; this is a repeated CDT exam emphasis to avoid misallocating liability.

D. Construction manager – Only in specific project delivery methods where the CM is also the constructor (CM-at-Risk) does this role overlap with the contractor. The question’s general form points to the contractor as the standard answer in CSI’s framework.

Therefore, in accordance with CSI’s explanation of roles and responsibilities under standard conditions of the contract, the contractor is responsible for job site security, making Option C correct.