FAR 11.1—Subpart 11.1

Order of precedence for requirements documents.

FAR 11.101 tells agencies how to choose, build, and prioritize the documents that define what they are buying. It covers the order of precedence among requirements documents, including documents mandated by law, performance-oriented documents such as performance work statements (PWSs) and statements of objectives (SOOs), detailed design-oriented documents, and certain Government-issued standards, specifications, and related publications used for non-repetitive acquisitions. It also addresses the separate requirement to use voluntary consensus standards under OMB Circular A-119 and the National Technology Transfer and Advancement Act, unless doing so would be inconsistent with law or impractical. In practice, this section pushes agencies toward clearer, more outcome-based requirements and away from unnecessary Government-unique specifications. For contractors, it affects how requirements are interpreted, how proposals are structured, and what technical approach will be judged acceptable. For contracting officers and acquisition teams, it is a key policy for drafting requirements documents, avoiding over-specification, and ensuring compliance with federal standards policy.

Standardization program.

FAR 11.102 explains how agencies are supposed to handle standardization when defining what they need. It tells agencies to use existing requirements documents when possible, or to develop new requirements documents when necessary, and it ties that process to the Federal Standardization Manual (FSPM-0001). It also points DoD components to DoD Manual 4120.24, Defense Standardization Program (DSP) Procedures, and directs agencies dealing with information technology standards and guidance to the Federal Information Processing Standards Publications (FIPS PUBS). In practical terms, this section is about avoiding unnecessary duplication, promoting consistency across government requirements, and making sure agencies use the correct government-wide or department-specific standardization guidance before creating new specifications. It also identifies where these reference documents can be obtained, which matters because contractors and contracting officers often need to know which standards framework controls a requirement and where to find the authoritative source.

Market acceptance.

FAR 11.103 explains when and how an agency may require offerors to prove that an offered item has already been accepted in the marketplace or has been satisfactorily supplied to the Government before award. It covers the statutory authority in 41 U.S.C. 3307(e), the kinds of situations where market acceptance is appropriate, and when it is not appropriate—especially where new or evolving items could satisfy the need. The section also sets out how contracting officers must develop solicitation criteria for demonstrating commercial market acceptance, including the need to tie the criteria to the agency’s minimum need, focus on performance and intended use rather than the offeror’s general capability, and support the criteria with market research. It further requires consideration of prior satisfactory Government supply, the full relevant commercial market including small businesses, and prohibits using market acceptance as the sole evaluation criterion. In practice, this section is meant to help agencies reduce performance risk for certain acquisitions while preventing overly restrictive requirements that could exclude innovative solutions or unduly limit competition.

Use of brand name or equal purchase descriptions.

FAR 11.104 explains when and how agencies may use a brand name or equal purchase description instead of a performance specification. It states the general policy preference for performance specifications because they encourage offerors to propose innovative solutions, but recognizes that brand name or equal descriptions can be useful in certain circumstances. The section also requires that any brand name or equal description identify the brand name item and describe the salient physical, functional, or performance characteristics that an “equal” product must meet to be acceptable for award. In practice, this section is about balancing competition and innovation against the need to define firm requirements clearly enough for vendors to know what they must match. It matters because poorly written brand name or equal descriptions can restrict competition, create ambiguity about what counts as “equal,” and lead to protests, evaluation disputes, or the purchase of items that do not actually satisfy the Government’s needs.

Items peculiar to one manufacturer.

FAR 11.105 limits the government’s ability to write requirements around a particular brand name, product, or product feature that is unique to one manufacturer when doing so would exclude other capable sources. The section is about avoiding unnecessary restrictive specifications and preserving competition, while still allowing a sole-brand or unique-feature requirement when it is truly essential to the Government’s needs. It ties that decision to market research, the proper competition or sole-source justification process, and the required documentation or approval path depending on the acquisition method. It also points readers to special rules for multiple-award schedule orders and orders under indefinite-quantity contracts, where the competition framework is governed by other FAR provisions. In practice, this section is a guardrail: agencies must be able to explain why a unique brand or feature is needed, show that alternatives will not satisfy the requirement, and place the required justification or documentation in the file and, when required, post it publicly.

Purchase descriptions for service contracts.

FAR 11.106 tells agencies how to write purchase descriptions for service contracts so they do not accidentally hand over inherently governmental functions to a contractor. It focuses on three specific drafting requirements: reserving final decision-making for Government officials, identifying contractor personnel in situations where they could be mistaken for Government employees or officials, and marking contractor-produced documents and reports appropriately. The section exists to protect the Government’s authority, avoid confusion about who is speaking or acting for the United States, and reduce the risk that contractor work will be treated as official Government action. In practice, this means the requiring activity must think carefully about the duties being described, the appearance of contractor personnel in meetings or on telephones, and how deliverables are labeled so there is no ambiguity about authorship or status. The rule is especially important in service acquisitions where contractors may work closely with Government staff and the line between support and official action can become blurred.

Solicitation provision.

FAR 11.107 tells contracting personnel when to include specific solicitation provisions tied to how the Government describes its needs. It covers two separate topics: the provision at 52.211-6, Brand Name or Equal, and the provision at 52.211-7, Alternatives to Government-Unique Standards. In practice, this section is about making sure offerors get the right instructions and that the solicitation matches the agency’s specification strategy. For brand name-or-equal buys, the provision must be included so offerors understand how to propose equivalent products. For solicitations using Government-unique standards, the rule depends on how the agency reports its use of voluntary consensus standards to NIST under OMB Circular A-119: agencies using the transaction-based reporting method must insert 52.211-7, while agencies using the categorical method may choose whether to use it. The section therefore links solicitation drafting to both competition requirements and agency standards-management/reporting practices.