FAR 11.000—Scope of part.
Plain-English Summary
FAR 11.000 is the scope statement for FAR Part 11, and it tells readers that this part sets the policies and procedures for describing agency needs. In practice, that means Part 11 governs how the Government states what it wants before it buys supplies or services, including the way requirements are written and communicated to industry. Although this section is very short, it is important because the quality of the requirement description drives competition, pricing, evaluation, contract performance, and the ability to obtain the right product or service. It also signals that the rest of Part 11 is the place to look for the rules on defining needs in a way that supports effective acquisition planning and solicitation development. For contracting officers, program offices, and acquisition teams, this section is the gateway to the broader requirement-description framework used throughout federal procurement.
Key Rules
Part 11 covers need descriptions
This part applies to policies and procedures for describing agency needs. It is the FAR location for rules on how the Government defines what it is buying, rather than how it will administer the contract after award.
Requirement wording matters
The scope statement makes clear that the focus is on the content and structure of the Government’s need statement. In practice, this affects statements of work, specifications, performance requirements, and other acquisition documents that communicate the requirement to offerors.
Foundation for later Part 11 rules
Section 11.000 does not itself impose detailed drafting requirements, but it establishes the subject matter for the rest of Part 11. Users should read it as the entry point to the FAR’s rules on describing needs, including the standards and preferences that follow in the part.
Responsibilities
Contracting Officer
Use Part 11 as the governing source when shaping and reviewing how the agency’s needs are described in solicitations and related acquisition documents.
Program/Requirement Office
Provide a clear, accurate description of the agency’s actual need so the contracting team can translate it into acquisition language consistent with Part 11.
Acquisition Team
Coordinate to ensure the requirement is described in a way that supports competition, evaluation, and successful performance.
Offerors/Contractors
Review the Government’s stated needs as described under Part 11 to understand the requirement and prepare responsive proposals or quotes.
Practical Implications
This section is brief, but it tells you where to look when the core issue is how to describe what the Government needs.
A common pitfall is treating requirement description as a purely administrative task; in reality, poor drafting can distort competition and lead to performance problems.
Contracting officers should use Part 11 early in acquisition planning, not just at solicitation release, because requirement wording affects the entire procurement strategy.
Program offices should avoid vague, overly broad, or internally inconsistent need statements, since those often create evaluation disputes and contract changes later.
Because this section is only a scope statement, users must consult the rest of Part 11 for the actual substantive rules and preferences that apply to specific acquisitions.
Official Regulatory Text
This part prescribes policies and procedures for describing agency needs.