FAR 4.1705—Contract clauses.
Plain-English Summary
FAR 4.1705 tells contracting officers which service contract reporting clauses must be included in solicitations and contracts when the reporting thresholds in FAR 4.1703 are met. It covers two different clause prescriptions: the standard clause at 52.204-14 for non-indefinite-delivery service contracts, including construction, and the clause at 52.204-15 for solicitations and indefinite-delivery contracts where one or more orders are expected to meet the reporting threshold. The section also identifies three express exceptions where neither clause is required: actions entirely funded by DoD, contracts awarded with a generic entity identifier, and classified solicitations, contracts, or orders. In practice, this provision ensures the Government can collect service contract reporting data where required, while avoiding duplication or impractical reporting in certain DoD-funded, classified, or generic-identifier situations. For contracting officers, the key task is to determine the contract type, whether the threshold is met or expected to be met, and whether an exception applies before award. For contractors, the practical effect is that reporting obligations may be built into the contract through the required clause, so they must be prepared to comply when the clause is included.
Key Rules
Insert 52.204-14 for covered service contracts
For solicitations and contracts for services, including construction, that meet or exceed the threshold in FAR 4.1703, the contracting officer must insert clause 52.204-14. This applies to non-indefinite-delivery actions and is the standard reporting clause for covered service contracts.
Use 52.204-15 for IDIQ coverage
For solicitations and indefinite-delivery contracts for services, including construction, where one or more orders are expected to meet or exceed the FAR 4.1703 threshold, the contracting officer must insert clause 52.204-15. This clause is used when reporting is tied to future orders under an indefinite-delivery vehicle.
Threshold drives clause applicability
The reporting clauses are required only when the acquisition meets or is expected to meet the thresholds in FAR 4.1703. If the threshold is not met, these clauses are not required under this section.
DoD-funded actions are excepted
Neither clause is required for actions entirely funded by the Department of Defense. The exception applies even if the acquisition would otherwise fall within the reporting threshold.
Generic entity identifier exception
Neither clause is required for contracts awarded with a generic entity identifier. This exception recognizes that certain awards are not associated with a specific reporting entity in the normal way.
Classified acquisitions are excluded
Neither clause is required in classified solicitations, contracts, or orders. The rule avoids requiring service contract reporting in classified procurement contexts where disclosure or reporting may be inappropriate.
Responsibilities
Contracting Officer
Determine whether the acquisition is for services, including construction, and whether it meets or is expected to meet the FAR 4.1703 threshold. Insert the correct clause—52.204-14 for non-IDIQ actions or 52.204-15 for indefinite-delivery actions—unless one of the stated exceptions applies.
Contracting Activity
Structure solicitations and contracts so the required clause is included when applicable and ensure acquisition planning accounts for reporting obligations under the service contract reporting regime.
Contractor
If the applicable clause is included, comply with the contract’s service contract reporting requirements and be prepared to provide the information required by the clause and related contract terms.
Agency/Program Office
Provide acquisition and funding information needed to determine whether the action is entirely funded by DoD, whether the contract is classified, and whether the threshold is likely to be met for indefinite-delivery vehicles.
Practical Implications
Contracting officers must decide early whether the action is a standard service contract or an indefinite-delivery vehicle, because the clause choice depends on that distinction.
The threshold analysis matters: a contract below the FAR 4.1703 threshold does not trigger these clauses under this section, but an IDIQ can still require the clause if future orders are expected to cross the threshold.
The exceptions are important and easy to miss. If an action is entirely funded by DoD, classified, or awarded with a generic entity identifier, the clauses are not required even if the acquisition otherwise looks covered.
For IDIQs, the trigger is not the base contract value alone; the question is whether one or more orders are expected to meet the threshold, so planners should assess anticipated ordering patterns.
If the wrong clause is omitted or inserted, the contract may not properly capture reporting obligations, creating compliance issues for both the Government and the contractor.
Official Regulatory Text
(a) The contracting officer shall insert the clause at 52.204-14 , Service Contract Reporting Requirements, in solicitations and contracts for services (including construction) that meet or exceed the thresholds at 4.1703 , except for indefinite-delivery contracts. This clause is not required for actions entirely funded by DoD, contracts awarded with a generic entity identifier, or in classified solicitations, contracts, or orders. (b) The contracting officer shall insert the clause at 52.204-15 , Service Contract Reporting Requirements for Indefinite-Delivery Contracts, in solicitations and indefinite-delivery contracts for services (including construction) where one or more orders issued thereunder are expected to each meet or exceed the thresholds at 4.1703 . This clause is not required for actions entirely funded by DoD, contracts awarded with a generic entity identifier, or in classified solicitations, contracts, or orders.