Already have an account? Sign in instead.
You stay signed in for 30 days on this browser.
Continue with Google Continue with MicrosoftNo account yet? Create a free one.
We sent a six-digit code.
It expires in ten minutes, works once, and only in this browser. Five wrong tries void it. Send another code.
Your account is live and the Cloudflare checks are off for this browser.
11.101 Order of precedence for requirements documents.
(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).
Syfert holds no separate history line for this section. Where this code prints a source or history note, it appears with the text, usually at the end.
Edition shown: eCFR text as of Sept. 29, 2026. Syfert holds no earlier or later version of this section.