FAR and DFARS › FAR Part 39: Acquisition of Information Technology › Subpart 39.1
FAR 39.103 Modular contracting.
The codified text (eCFR, as of 2026-10-02). Under the Revolutionary FAR Overhaul ↗, agencies follow class deviations with new text for many parts while the formal rules go through the Federal Register: check the solicitation and your contract's clauses, which rule.
In plain English
This section encourages agencies to use modular contracting—dividing an information technology acquisition into smaller, independently useful increments—to reduce program risk and keep pace with changing technology. It explains what makes a good increment and how contracting officers should structure these acquisitions. For contractors, it signals that IT work may be bought in discrete pieces rather than one large contract.
Applies to: Agencies acquiring information technology systems, and contractors bidding on such work
What it requires
- Contracting officers shall choose an appropriate contracting technique for each increment that facilitates later increments.
- Contracting officers shall select the contract type and method appropriate to the circumstances.
- Contract(s) shall be structured so the Government is not required to procure additional increments.
- Each increment's information technology shall conform to the agency's master information technology architecture.
Key terms: modular contracting · major systems · increment · information technology architecture · contracting officer
Written by AI from this section's text. A guide, not legal advice: the text below rules.
The text
(a) This section implements 41 U.S.C. 2308. Modular contracting is intended to reduce program risk and to incentivize contractor performance while meeting the Governments need for timely access to rapidly changing technology. Consistent with the agency's information technology architecture, agencies should, to the maximum extent practicable, use modular contracting to acquire major systems (see 2.101) of information technology. Agencies may also use modular contracting to acquire non-major systems of information technology.
(b) When using modular contracting, an acquisition of a system of information technology may be divided into several smaller acquisition increments that—
(1) Are easier to manage individually than would be possible in one comprehensive acquisition;
(2) Address complex information technology objectives incrementally in order to enhance the likelihood of achieving workable systems or solutions for attainment of those objectives;
(3) Provide for delivery, implementation, and testing of workable systems or solutions in discrete increments, each of which comprises a system or solution that is not dependent on any subsequent increment in order to perform its principal functions;
(4) Provide an opportunity for subsequent increments to take advantage of any evolution in technology or needs that occur during implementation and use of the earlier increments; and
(5) Reduce risk of potential adverse consequences on the overall project by isolating and avoiding custom-designed components of the system.
(c) The characteristics of an increment may vary depending upon the type of information technology being acquired and the nature of the system being developed. The following factors may be considered:
(1) To promote compatibility, the information technology acquired through modular contracting for each increment should comply with common or commercially acceptable information technology standards when available and appropriate, and shall conform to the agency's master information technology architecture.
(2) The performance requirements of each increment should be consistent with the performance requirements of the completed, overall system within which the information technology will function and should address interface requirements with succeeding increments.
(d) For each increment, contracting officers shall choose an appropriate contracting technique that facilitates the acquisition of subsequent increments. Pursuant to parts 16 and 17 of the Federal Acquisition Regulations, contracting officers shall select the contract type and method appropriate to the circumstances (e.g., indefinite delivery, indefinite quantity contracts, single contract with options, successive contracts, multiple awards, task order contracts). Contract(s) shall be structured to ensure that the Government is not required to procure additional increments.
(e) To avoid obsolescence, a modular contract for information technology should, to the maximum extent practicable, be awarded within 180 days after the date on which the solicitation is issued. If award cannot be made within 180 days, agencies should consider cancellation of the solicitation in accordance with 48 CFR 14.209 or 15.206(e). To the maximum extent practicable, deliveries under the contract should be scheduled to occur within 18 months after issuance of the solicitation.
Sections it refers to
Sections that refer to it
- 16.505 Ordering.
← 39.102 Management of risk. · 39.104 Information technology services. →
Rule changes for FAR Part 39
- Federal Acquisition Regulation: Revolutionary Federal Acquisition Regulation Overhaul Parts 1, 2, 4, 33, 39, 40, and 53 ↗ · proposed 2026-06-23 · comments due 2026-07-23
- Federal Acquisition Regulation: Prohibition on Certain Semiconductor Products and Services ↗ · proposed 2026-02-17 · comments due 2026-04-20
- Federal Acquisition Regulation: Strengthening America's Cybersecurity Workforce ↗ · proposed 2025-01-03 · comments due 2025-03-04
- Federal Acquisition Regulation: Prohibition on Unmanned Aircraft Systems From Covered Foreign Entities ↗ · final rule 2024-12-30
- Federal Acquisition Regulation: Prohibition on Unmanned Aircraft Systems From Covered Foreign Entities ↗ · final rule 2024-11-12 · effective 2024-11-12
- Federal Acquisition Regulation; Technical Amendments ↗ · final rule 2024-04-22 · effective 2024-05-22
- Federal Acquisition Regulation: Sustainable Procurement ↗ · final rule 2024-04-22 · effective 2024-05-22
Source: eCFR, 48 CFR chapters 1 and 2 (GPO GovInfo bulk data) ↗. Plain words for the terms: glossary.