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

In CSI/CDT terminology, “preconstruction submittals” are those required at (or very near) the start of the project, before actual construction work proceeds, to set up project administration, payment, and coordination. These submittals are usually specified in Division 01 – General Requirements of the Project Manual and are part of the contract requirements established by the specifications.

Typical examples of preconstruction submittals in CSI-aligned practice include:

Construction/progress schedule

Submittal schedule

Schedule of values

List of subcontractors and suppliers

Insurance and bonds

Temporary facilities and controls plans

Health & safety or site-specific plans (when required)

The schedule of values is expressly listed in standard Division 01 sections as a required early submittal that must be approved before progress payments can be properly evaluated and certified. It breaks down the contract sum into line items for payment and becomes the basis for reviewing the contractor’s pay applications throughout the project. Because it is required at the start of the construction phase and before regular work progress, it is a classic preconstruction submittal, matching Option C.

Why the other options are incorrect:

A. Product dataProduct data (cut sheets, catalog information, performance data, etc.) are action submittals for specific products and materials. Although some may be submitted early, they are typically required as needed before related work is installed, not universally at the very start of the job. They are not classified by CSI as “preconstruction submittals” in the same sense as the schedule of values or project schedule.

B. Shop drawingsShop drawings are also action submittals supporting fabrication and installation of specific work (e.g., structural steel, curtain wall systems, ductwork, etc.). They are provided during the construction phase in accordance with a submittal schedule, not as “preconstruction” administrative submittals that must be in place before construction administration and payments can be properly managed.

D. Warranty documentationsCorrected term: “warranty documentation.”Warranty documentation is typically part of closeout submittals—submitted near Substantial Completion or Final Completion, not at the beginning of the project. Division 01 and individual technical sections usually require warranties to be submitted as part of project closeout procedures, after the work is in place and accepted, not as a preconstruction submittal.

CSI / CDT-aligned references (no links):

CSI Construction Specifications Practice Guide – sections on Division 01, Submittals, and Requirements for Administrative Submittals (including preconstruction submittals).

CSI Project Delivery Practice Guide – chapters on Construction Phase and construction submittal processes.

CDT Exam Content Outline – topics on “Submittals,” “Division 01 – General Requirements,” and “Contract Administration documentation.”

CSI defines commissioning as a quality-focused process that verifies the facility and its systems meet the Owner’s Project Requirements (OPR). In the Project Delivery Practice Guide, commissioning is categorized into three broad types (paraphrased):

Systems and equipment commissioning – verifying that HVAC, electrical, plumbing, life safety, and other building systems perform as intended.

Building envelope commissioning – verifying performance of the exterior enclosure, including air/water infiltration, thermal performance, and durability.

Total project commissioning (also called whole-building or total building commissioning) – extending commissioning to the entire project, including design, construction, and operational aspects, integrating envelope, systems, and other building components.

Given that the question already lists “systems and equipment commissioning” and “building envelope commissioning,” the missing third category described by CSI is “total project commissioning”, which corresponds to Option D.

Why the other options are not correct:

A. Mechanical commissioning – This is a subset of systems and equipment commissioning (focused on HVAC/mechanical systems), not one of CSI’s three overarching categories.

B. Facility commissioning – While the term might be used informally, CSI’s categorized terminology in the CDT body of knowledge is “total project commissioning” rather than “facility commissioning.”

C. Process commissioning – This term is more common in industrial process industries and is not identified by CSI as one of the three principal commissioning categories for building projects.

CSI References (no links):

CSI Project Delivery Practice Guide – sections on commissioning types and scope (total project, systems and equipment, building envelope).

In CSI’s project delivery framework, the preconstruction meeting (often called the preconstruction conference) is a formal meeting held after award of the construction contract and before substantial field work begins. Its typical purposes match the stem of this question almost word-for-word:

Introduce the key members of the owner’s team, the design team, and the contractor’s team.

Review and establish communication protocols – who communicates with whom, in what format (letters, emails, RFIs, submittals), and through which channels (e.g., via the A/E as the owner’s representative).

Explain administrative procedures for submittals, RFIs, change orders, applications for payment, project meetings, record documents, and closeout requirements.

Clarify roles and responsibilities, lines of authority, and decision-making processes during construction.

Review the project schedule, major milestones, site logistics, and constraints so everyone begins the project with a common understanding.

These points are fully consistent with how CSI’s Project Delivery Practice Guide and typical Division 01 “Project Management and Coordination” sections describe the preconstruction conference: as the kickoff meeting for the construction phase, focused on communication, procedures, and administration—not bidding or detailed technical coordination.

Why the other options are not correct:

A. Mobilization meeting“Mobilization” refers to the contractor’s process of moving onto the site (bringing in equipment, setting up field offices, etc.). While a project might have discussions about mobilization, “mobilization meeting” is not the standard CSI project-delivery term for this formal kickoff. The structured, procedure-focused meeting described in the question is the preconstruction meeting.

C. Prebid meetingA prebid meeting (pre-bid conference) occurs during procurement, before bids are submitted. Its primary purposes are to familiarize prospective bidders with the project, review procurement requirements, visit the site, and answer questions that might affect bids. It does not introduce the already-selected construction team, nor does it establish the project’s communication and administrative procedures for contract execution. That occurs after award in the preconstruction meeting.

D. Coordination meetingCoordination meetings are typically recurring, working meetings during construction to resolve ongoing technical, scheduling, or coordination issues between trades (e.g., MEP coordination). They do not serve as the initial, formal kickoff to introduce teams and set overall administrative and communication “ground rules.”

Therefore, the meeting that introduces the design and construction teams, sets communication ground rules, and explains administrative processes is the Preconstruction meeting (Option B), as aligned with CSI project delivery and Division 01 practices.

Key CSI References (titles only, no links):

CSI Project Delivery Practice Guide – chapters on Construction Phase and Project Meetings (Preconstruction Conference).

CSI Construction Specifications Practice Guide – discussions of Division 01 “Project Management and Coordination” and required project meetings.

CSI CDT Body of Knowledge – topic area: “Construction Phase Services and Communication.”

CSI’s treatment of bidding and pricing mechanisms distinguishes between:

Alternates – for defined variations in scope or quality.

Allowances – for items not fully defined at bid time.

Unit prices – for work where quantities are uncertain or may change.

The question mentions:

Equal consideration and transparency during award

Flexibility while awarding

Managing cost during execution for undefined and unforeseen conditions

This language directly aligns with allowances and unit prices:

Allowances are used when the exact nature or selection of certain items (e.g., finishes, special equipment, or yet-to-be-selected products) is not fully defined at bid time. An allowance amount is stated in the documents so all bidders include the same amount, ensuring comparable bids and transparency. Actual cost is reconciled during construction.

Unit prices are used when work items have uncertain quantities (e.g., rock excavation, unsuitable soil replacement). The unit rate is bid up front, and final payment is based on actual measured quantities, which allows the owner to manage cost fairly during execution when unforeseen conditions arise.

Together, allowances and unit prices (Option C) ensure that:

All bidders base their bids on the same assumptions, supporting equal consideration and fairness.

The contract can adapt to undefined or unforeseen conditions without renegotiating basic pricing structures.

Why the others are not correct:

A. Bid security and substitutionBid security protects the owner if the bidder fails to execute the contract; substitution deals with product changes. These do not primarily address managing costs for undefined or unforeseen conditions nor set flexible price structures like allowances or unit prices.

B. Add and deduct alternativesAlternates provide flexibility in award (selecting add or deduct options), but they deal with defined scope options, not ongoing management of undefined or unforeseen conditions during execution.

D. Liquidated damages and combined bidsLiquidated damages relate to time and schedule risk, not unknown scope or quantities; combined bids are procedural. Neither is the primary mechanism CSI associates with managing cost for undefined/unforeseen work.

Relevant CSI-aligned references (no URLs):

CSI Project Delivery Practice Guide – sections on bidding, pricing, alternates, allowances, and unit prices.

CSI Construction Specifications Practice Guide – discussion of Division 01 provisions for allowances and unit prices.

CSI CDT Body of Knowledge – topics on bid forms, pricing mechanisms, and managing unknown quantities.

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

In Design-Bid-Build (DBB), CSI describes a clear, linear sequence of phases:

Programming and design

Procurement (bidding/negotiation and selection of contractor)

Award of the construction contract

Construction

At the end of the procurement phase, the owner has received and evaluated bids, determined the successful bidder, and is ready to award the contract. CSI’s project delivery guidance explains that the award step typically involves:

Issuing a Notice of Award or letter of intent to the successful bidder; and/or

Forwarding the owner–contractor agreement (and other contract forms) for execution.

Only after this step do the parties fully execute the contract and the owner issues a Notice to Proceed, marking the official start of the construction phase. This matches Option D:

The owner issues a letter of intent or forwards the owner-contractor agreement to the successful bidder.

Why the other options are incorrect:

A. The contractor begins negotiating agreements with subcontractors.Subcontractor negotiations and subcontracts typically occur after the contractor has been formally awarded and has a binding contract with the owner. This is not the immediate step that awards the contract for construction.

B. The owner forwards construction contract agreements to subcontractors.The owner’s contract is with the prime contractor, not with subcontractors. Subcontracts are between the prime contractor and subcontractors. The owner does not award contracts directly to subs in standard DBB.

C. The contractor and owner issue an amendment indicating the project is in the construction phase.There is normally no “amendment” to enter the construction phase. The project enters the construction phase upon execution of the owner–contractor agreement and issuance of the Notice to Proceed, not by amendment.

Key CSI References (titles only):

CSI Project Delivery Practice Guide – chapters on Design-Bid-Build and the Procurement and Contract Award processes.

CSI Construction Specifications Practice Guide – discussions on contract formation and Notice of Award/Notice to Proceed.

CSI CDT Body of Knowledge – “Project Delivery Methods” and “Procurement and Award of Contract.”

Under the typical CSI-aligned project delivery framework, additional time and money are generally justified when:

The owner (or A/E as owner’s agent) changes the work or otherwise causes delay (e.g., active interference, late decisions, design changes).

There are unforeseen conditions beyond the control of both owner and contractor, where the contract documents anticipated “normal” conditions instead.

Other compensable events defined in the Conditions of the Contract occur (e.g., certain force majeure events, if provided for).

However, the contractor is responsible for correcting defective or nonconforming work at no increase in contract sum or time (except where the defect is caused by others). CSI-based guidance on construction phase services and contract administration explains that:

Defective work (work not in accordance with the contract documents) must be removed, replaced, or corrected by the contractor at the contractor’s expense.

Any extra time and cost arising from correcting such defective work is not a valid basis for a change order or a claim for increased compensation or time extension.

If the contractor’s own documentation shows that the extra cost and time are due to defective work needing repair, the A/E has a clear basis—consistent with the Conditions of the Contract—to reject the claim. That aligns directly with Option D.

Why the other options do not support rejecting the claim:

A. Active interference by the owner – Owner-caused interference is typically a valid ground for a time and possibly cost adjustment, not grounds for rejection.

B. Conditions beyond the control of the contractor or owner – Unforeseen conditions are exactly the type of situation that may justify a claim, depending on the contract language.

C. The A/E modified the contract documents – A/E-issued changes (such as change orders or certain clarifications) often result in compensable changes if they add work or cause delay.

CSI-aligned references (no URLs):

CSI Project Delivery Practice Guide – Construction Phase and Claims/Changes discussions.

CSI Construction Specifications Practice Guide – responsibilities for defective work and changes.

CSI CDT Body of Knowledge – construction phase administration and evaluation of claims.

Per CSI’s Construction Specifications Practice Guide and Division 01 (General Requirements), the contractor is required to maintain record documents (as-built drawings, annotated specifications, and related data) at the jobsite.

CSI defines “record documents” as:

“A set of drawings, specifications, and other documents kept current during construction that show all changes and deviations from the original contract documents.”

Reasons:

They must be readily accessible to field supervisors, inspectors, and the A/E.

They serve as the source for preparation of final “as-built” documents submitted at project closeout.

Why others are incorrect:

A / B. Contractor’s office – does not satisfy accessibility requirements for site coordination.

C. Owner’s office – owner receives the final record documents at closeout, not during construction.

CSI Reference:

CSI Project Delivery Practice Guide, “Construction Phase Documentation”; Division 01 – 01 78 39 Project Record Documents.

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

CSI describes post-occupancy evaluation (POE) as a review of how the completed facility is performing for its users and operations staff, compared to the Owner’s Project Requirements (OPR). For the evaluation to be meaningful:

The facility must have been occupied long enough for systems and spaces to be used under normal operating conditions.

It should happen early enough that findings can inform warranty corrections, adjustments, and future projects.

CSI’s practice guidance indicates that POEs are typically performed several months after initial occupancy, often in the range of three to six months, when occupants have adjusted to the building and operational patterns are established but the project is still within the correction/warranty period. That aligns with Option B.

Why the others are less suitable:

A. At the end of the correction period and C. Just before the end of the warranty period – these are usually around one year; waiting this long reduces the time available to act on findings while warranties are in force.

D. One year after substantial completion – also generally coincides with warranty expiration; by then, significant issues may have already affected operations without being captured early.

Relevant CSI references:

CSI Project Delivery Practice Guide – sections on facility management, occupancy, and post-occupancy evaluation.

CSI CDT Body of Knowledge – material on owner and facility manager activities during occupancy.

In CSI’s description of the project conception and pre-design phases, the owner has a responsibility to determine whether a proposed project is feasible and appropriate before moving into full design. One of the key tools for this is a due diligence investigation.

CSI characterizes due diligence as including, for example:

Reviewing legal, zoning, and regulatory constraints.

Evaluating financial feasibility and the owner’s available resources or funding mechanisms.

Considering market conditions, potential users, and long-term operational costs.

Assessing social, environmental, and community impacts (traffic, neighborhood character, environmental effects, required approvals).

Through this activity, the owner can decide whether to:

Proceed with the project as envisioned,

Modify scope, location, or timing, or

Abandon the project if it is not viable.

This aligns directly with Option C – Due diligence investigation, which is about assessing viability, finances, and broader impacts.

Why the other options are less appropriate:

A. Schematic programmingCSI separates programming (defining needs and requirements) and schematic design (early design). The term “schematic programming” is not a standard CSI term. Programming helps define needs but is only one part; due diligence focuses more broadly on viability, finance, and external impacts.

B. Site selectionSite selection is important, but it is one component within a broader due diligence process. It does not, by itself, fully address financial feasibility or community impact; those are evaluated in the larger due diligence/feasibility effort.

D. Master planningMaster planning typically addresses long-range development of a site, campus, or area (phasing, land use, circulation, infrastructure). While it may touch community impacts, it is broader and more strategic. The question specifically targets an activity to assess viability, financial resources, and community impact for a specific project decision—that is due diligence.

Key CSI Reference Titles (no links):

CSI Project Delivery Practice Guide – Project Conception and Predesign, Owner’s due diligence and feasibility studies.

CSI Construction Specifications Practice Guide – Owner’s responsibilities prior to design and procurement.

CDT Body of Knowledge – “Owner’s Project Initiation, Feasibility, and Due Diligence.”

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.

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.

In CSI / CDT usage, quality assurance (QA) and quality control (QC) are distinct concepts:

Quality Assurance (QA) focuses on planning, processes, and preventive actions put in place before and during the work to help ensure the required quality will be achieved. It is about systems and procedures.

Quality Control (QC) focuses on inspection, testing, and verification to determine whether the constructed work conforms to the requirements of the Contract Documents.

Typical examples:

QA examples (process-oriented):

Developing and following a project-specific quality plan.

Coordinating scheduling and sequencing of the work so trades do not interfere with one another and work is done under appropriate conditions.

Prequalification of contractors, subcontractors, and testing agencies.

Establishing and enforcing submittal procedures and preinstallation meetings.

QC examples (inspection/testing):

Field testing (e.g., concrete cylinder tests, soil compaction tests).

Visual inspection of installed work.

Checking that installed products match submittals and specifications.

Looking at the options:

A. Performing compaction testing – This is a field test used to verify densities and is clearly quality control, not QA.

B. Field observations – These are performed by the A/E or others to observe and verify that work appears to be in general conformance; this is quality control.

C. Validating quantities for payment – This is a contract administration / cost control activity, not primarily a quality activity.

D. Scheduling and sequencing of the work – This is planning and coordination done in advance so the project can proceed efficiently, correctly, and without damaging completed work. Because it is a procedure-based, preventive activity, CSI places this type of planning under quality assurance.

Therefore, the example of quality assurance is “Scheduling and sequencing of the work” (Option D).

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

CSI Project Delivery Practice Guide – sections on “Quality in Project Delivery” and distinctions between QA and QC.

CSI Construction Specifications Practice Guide – discussions of quality requirements, testing, and inspection.

CDT Body of Knowledge – domain on “Construction Phase: Quality Assurance and Quality Control.”

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

Within CSI’s project delivery discussion, Integrated Project Delivery (IPD) is defined as a highly collaborative project delivery approach where key project participants—typically owner, architect/engineer, and contractor (and often major trades and key consultants)—work together as an integrated team from very early in the project.

Core characteristics of IPD in CSI-oriented material include:

Early involvement of key participants in planning, design, and sometimes even programming.

A single, collaborative team structure (rather than traditional silos of responsibility) focusing on shared project goals (cost, schedule, quality, performance).

Shared information and decision-making, often supported by digital tools (such as BIM) so that design, cost, constructability, and operations considerations are integrated.

A focus on joint problem-solving and collective risk and reward, rather than adversarial relationships.

That description aligns directly with Option A: “A collaborative, integrated, and productive team composed of key project participants.”

Why the other options are incorrect:

B. Traditional delivery methods and team relationships…IPD is specifically a departure from traditional team relationships (like those in conventional Design-Bid-Build), which are more linear and segmented. IPD emphasizes integrated rather than traditional or separated relationships.

C. Responsibility silos for greater efficiencies…“Responsibility silos” describe the opposite of IPD. IPD seeks to break down silos, fostering shared responsibility and integrated decision-making.

D. Segregat[ing] knowledge… with paper-based communications…IPD promotes continuous, transparent information sharing, often using digital platforms and models. Segregated, paper-based communications are characteristic of older, more fragmented approaches, not IPD.

Key CSI Reference Titles (no links):

CSI Project Delivery Practice Guide – sections on Integrated Project Delivery and collaborative team structures.

CSI CDT Body of Knowledge – “Project Delivery Methods” and comparison of IPD with traditional methods.

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

CSI uses the term “Procurement Documents” to describe the documents used to solicit and obtain offers (bids or proposals) from prospective contractors. In CSI and CDT terminology, these are more commonly referred to in everyday practice as “Bidding Documents.”

Per CSI’s Project Delivery Practice Guide:

Procurement (bidding) documents usually include:

Solicitation / invitation to bid or request for proposals,

Instructions to bidders,

Bid forms,

Procurement requirements, and

Often copies of the proposed Contract Documents (conditions, drawings, specifications) for information and pricing.

When CSI exam and study materials ask what is “commonly included as procurement documents,” they treat “bidding documents” as the proper term among choices like these. So the best answer is:

D. Bidding documents

Why the other options are not correct by themselves:

A. Project record documents – These are post-construction documents (record drawings, record specifications, record submittals) used for operations and maintenance, not for procurement.

B. Contract documents – While proposed contract documents are often included within the procurement package for pricing and review, the broader category name for the documents used in procurement is still “bidding (procurement) documents.”

C. Consensus documents – This refers to standard-form agreements produced by organizations (e.g., consensus-documents families), not the general CSI term for the set of documents used in the procurement phase.

Relevant CSI references (paraphrased):

CSI Project Delivery Practice Guide – chapters on Procurement Phase and “Procurement Documents (Bidding Documents).”

CSI CDT Study Materials – topics on document families used in procurement and contracting.