FAR and DFARS › FAR Part 11: Describing Agency Needs › Subpart 11.1
FAR 11.101 Order of precedence for requirements documents.
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 tells agencies the order of precedence they must follow when choosing or creating requirements documents. It also directs agencies to use voluntary consensus standards instead of Government-unique standards when those voluntary standards exist, unless that would conflict with law or be impractical. For contractors, this matters because it shapes which kinds of requirements documents and standards an agency may rely on in a solicitation.
Applies to: Agencies selecting, modifying, combining, or creating requirements documents
What it requires
- Follow the stated order of precedence when selecting or creating requirements documents
- Use voluntary consensus standards, when they exist, in lieu of Government-unique standards, except where inconsistent with law or otherwise impractical
Key terms: requirements documents · order of precedence · performance-oriented documents · PWS · SOO
Written by AI from this section's text. A guide, not legal advice: the text below rules.
The text
(a) Agencies may select from existing requirements documents, modify or combine existing requirements documents, or create new requirements documents to meet agency needs, consistent with the following order of precedence:
(1) Documents mandated for use by law.
(2) Performance-oriented documents (e.g., a PWS or SOO). (See 2.101.)
(3) Detailed design-oriented documents.
(4) Standards, specifications and related publications issued by the Government outside the Defense or Federal series for the non-repetitive acquisition of items.
(b) In accordance with OMB Circular A-119, “Federal Participation in the Development and Use of Voluntary Consensus Standards and in Conformity Assessment Activities,” and Section 12(d) of the National Technology Transfer and Advancement Act of 1995, Pub. L. 104-113 (15 U.S.C. 272 note), agencies must use voluntary consensus standards, when they exist, in lieu of Government-unique standards, except where inconsistent with law or otherwise impractical. The private sector manages and administers voluntary consensus standards. Such standards are not mandated by law (e.g., industry standards such as ISO 9000, and IEEE 1680).
Sections it refers to
- 2.101 Definitions.
← 11.002 Policy. · 11.102 Standardization program. →
Rule changes for FAR Part 11
- Federal Acquisition Regulation: Ending Procurement and Forced Use of Paper Straws ↗ · proposed 2025-07-21 · comments due 2025-09-19
- Federal Acquisition Regulation: Preventing Organizational Conflicts of Interest in Federal Acquisition ↗ · proposed 2025-01-15 · comments due 2025-03-17
- Federal Acquisition Regulation: Controlled Unclassified Information ↗ · proposed 2025-01-15 · comments due 2025-03-17
- Federal Acquisition Regulation: Strengthening America's Cybersecurity Workforce ↗ · proposed 2025-01-03 · comments due 2025-03-04
- Federal Acquisition Regulation; Technical Amendments ↗ · final rule 2024-07-30 · effective 2024-08-29
- 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.