Construction Specifications Institute CDT Exam With Confidence Using Practice Dumps

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

CSI’s Construction Specifications Practice Guide and CDT materials provide clear guidance on appropriate wording in specifications. They stress:

Use clear, specific, and enforceable language.

Avoid vague, subjective, or nontechnical terms that create ambiguity and open interpretation.

Among the answer choices, “Work” is the only word that is appropriate and standard in CSI-compliant specification text:

“Work” is a defined term in the General Conditions (and often Division 01), usually meaning the total construction and services required by the Contract Documents, including all labor, materials, equipment, and services necessary to complete the project.

Because it is defined and used consistently, “Work” is an acceptable and precise term for specification language. Example usage (conceptually): “Perform all Work in accordance with…”.

Why the other terms are inappropriate per CSI guidance:

A. AnyCSI recommends avoiding “any,” “either,” “etc.” and similar words because they are non-specific and create ambiguity. For example, “provide any fasteners as needed” does not clearly define what is required and can lead to disputes and inconsistent interpretation.

B. As perThe phrase “as per” is discouraged in CSI-style writing. It is considered informal and can be replaced by clearer, more direct phrasing such as “in accordance with,” “according to,” or “as indicated in.” CSI advocates for concise, plain, and unambiguous English in specs.

C. As requiredCSI strongly cautions against phrases like “as required” or “as necessary” when they are not tied to a clear condition or reference. They shift the decision to someone’s judgment later, instead of stating the requirement explicitly. If something is required, the specification should state what, when, and under what conditions, rather than simply saying “as required.”

Therefore, in a CSI-compliant specification, the term that is clearly appropriate from the options given is “Work” (Option D).

Relevant CSI references (no URLs):

CSI Construction Specifications Practice Guide – Chapters on language and writing style for specifications (clear, concise, complete, correct).

CSI Practice Guide for Principles & Formats of Specifications – Guidance on defined terms such as “Work.”

CSI CDT Body of Knowledge – Sections on specification-writing best practices and prohibited vague phrases.

In CSI-based project cost planning, contingency is defined as an amount added to an estimate or budget to cover uncertainties and unknowns that cannot yet be clearly defined at the current level of design development.

CSI’s practice guides and CDT materials explain (paraphrased):

In early design phases, such as schematic design, the design is only partially developed. Important elements are still undecided, and system configurations may change. Because of this, the cost estimate is inherently less precise.

A contingency line item is therefore included to cover:

Incomplete design information,

Potential scope refinement,

Normal estimating uncertainties, and

Other unknown factors at that stage.

As the project moves into design development and later into the construction documents phase, the design becomes more complete and the uncertainty decreases, so contingency percentages typically decrease.

By contrast, CSI differentiates contingency from other estimating tools:

Allowances: Specific sums in the contract for known-but-not-fully-defined items (e.g., “flooring allowance of X per m²”). These are identified items with placeholder values, not general unknowns.

Unit prices: Agreed rates for measuring work (e.g., $/m³ of rock excavation) used when quantities are uncertain, but scope categories are known and clearly described in the documents.

Alternates: Defined options requested by the owner (additive or deductive) for comparison and selection—again, specifically described items, not “unknowns.”

Because the question specifically references the schematic design phase and asks what the contingency line item covers, the CSI-aligned answer is “Unknown factors” – Option C.

Why the other options are incorrect:

A. Allowances – These are separate, explicit line items in the estimate or specifications and are not what contingency is intended to cover.

B. Unit prices – These deal with agreed rates for work whose quantities may vary, not with broad early-phase uncertainty.

D. Alternates – Alternates are specifically described choices requested for comparison; they are priced individually, not absorbed into contingency.

Key CSI-aligned references (no links):

CSI Project Delivery Practice Guide – sections on cost planning and contingencies by phase.

CSI CDT Body of Knowledge – definitions and uses of contingency, allowances, unit prices, and alternates in estimating.