FAR 34.005-2—Mission-oriented solicitation.
Plain-English Summary
FAR 34.005-2 addresses how a contracting officer should structure and distribute a mission-oriented solicitation for major systems or other acquisitions where the Government is focused on required mission capabilities rather than prescribing a specific solution. It covers advance notice of the acquisition, broad market outreach, presolicitation conferences and draft-solicitation comment opportunities, distribution of the final solicitation, the required content of that solicitation, the use of mission-capability language instead of system-specific descriptions, access to Government data, selection requirements tied to the acquisition strategy, freedom for offerors to propose alternative technical approaches and tradeoffs, mandatory Earned Value Management System (EVMS) requirements when applicable, and the general preference to avoid Government specifications and standards unless a subsystem or component is specifically mandated under agency procedures. In practice, this section is meant to encourage competition, innovation, and broader industry participation by telling the market what outcome the Government needs rather than dictating how to achieve it. It also helps reduce lock-in to a particular design or vendor solution and supports better acquisition planning by allowing industry to comment before the solicitation is finalized. For contractors, this means proposals can be more creative and solution-driven; for contracting officers, it means the solicitation must be carefully written to preserve flexibility while still giving offerors enough information to compete intelligently.
Key Rules
Broad advance notice
Before issuing the solicitation, the contracting officer should, when practicable and consistent with agency procedures, publicize the acquisition as widely as possible. This includes posting in the Governmentwide point of entry and reaching a broad mix of potential sources, especially small and newer firms, research institutions, and other nontraditional sources when appropriate.
Presolicitation input
If appropriate, the contracting officer should hold a presolicitation conference and/or distribute the proposed solicitation for comment. The solicitation may then be revised based on industry feedback, which helps improve clarity, realism, and competition.
Final solicitation to all offerors
The contracting officer must send the final solicitation to all prospective offerors. This ensures equal access to the same requirements and prevents selective distribution that could distort competition.
Mission-capability description
The solicitation must describe the need in terms of mission capabilities, not by naming a specific system or solution. The goal is to define what the Government needs to accomplish, not to preselect the technical answer.
State objectives and constraints
The solicitation must identify schedule, capability, and cost objectives, and explain any known acquisition constraints when appropriate. This gives offerors the framework needed to propose realistic solutions and tradeoffs.
Provide access to Government data
The solicitation must provide the Government data relevant to the acquisition or explain how offerors can obtain it. This is essential so offerors can prepare informed proposals and understand the operating environment, requirements, and assumptions.
Selection requirements tied to strategy
The solicitation must include selection requirements that are consistent with the acquisition strategy. Evaluation and source selection criteria should align with how the Government intends to buy, manage, and field the solution.
Allow alternative approaches
The solicitation must clearly state that each offeror may propose its own technical approach, major design features, subsystems, and alternatives to schedule, cost, and capability goals. This preserves competition on solutions rather than forcing compliance with a single prescribed design.
EVMS requirement when required
The solicitation must require an Earned Value Management System that complies with the current EIA-748 guidelines when EVMS is required. The solicitation should also point readers to FAR 34.201 for related EVMS and reporting requirements.
Avoid unnecessary specs and standards
To the extent practicable, the solicitation should not reference or mandate Government specifications or standards unless the agency is mandating a subsystem or component under approved agency procedures. This reduces unnecessary prescription and supports innovative solutions.
Responsibilities
Contracting Officer
Publicize the acquisition broadly before solicitation when practicable, consider presolicitation conferences and draft-solicitation comments, issue the final solicitation to all prospective offerors, and draft the solicitation to focus on mission capabilities, objectives, constraints, data access, selection requirements, EVMS requirements when applicable, and freedom to propose alternative solutions.
Agency
Maintain procedures governing when subsystems or components may be mandated, and ensure those mandates are approved under agency procedures before the solicitation references or requires them. The agency also supports acquisition planning and market outreach practices consistent with this section.
Prospective Offerors
Review the draft or final solicitation, provide comments when invited, and prepare proposals that address mission needs with their own technical approaches, design features, and tradeoff proposals within the stated objectives and constraints.
Government Program/Technical Personnel
Help define mission capabilities, identify relevant data, objectives, constraints, and selection requirements, and support presolicitation engagement so the solicitation reflects realistic needs and acquisition strategy.
Practical Implications
This section pushes the Government to buy outcomes, not preselected solutions, so contractors should expect more room to propose innovative designs and tradeoffs.
A common pitfall is writing a solicitation that quietly embeds a preferred system or overly detailed specification, which can undermine competition and conflict with the mission-oriented approach.
Another frequent issue is failing to give industry enough data or context; without access to relevant Government data, offerors may price risk too high or submit weak proposals.
Contracting officers should be careful that evaluation criteria, schedule, and cost objectives match the acquisition strategy; mismatches can create protests, confusion, or poor source selection decisions.
If EVMS is required, the solicitation must clearly state the requirement and tie it to the current EIA-748 standard and FAR 34.201, so offerors know the compliance burden up front.
Official Regulatory Text
(a) Before issuing the solicitation, whenever practicable and consistent with agency procedures, the contracting officer should take the actions outlined in paragraphs (a)(1) and (2): (1) Advance notification of the acquisition should be given the widest practicable dissemination, including publicizing through the Governmentwide point of entry (see subpart 5.2 ) and should be sent to as wide a selection of potential sources as practicable, including smaller and newer firms, Government laboratories, federally funded research and development centers, educational institutions and other not-for-profit organizations, and, if it would be beneficial and is not prohibited, foreign sources. (2) If appropriate, hold a presolicitation conference (see 15.201 ) and/or send copies of the proposed solicitation to all prospective offerors for their comments. After evaluation of these comments, the solicitation should be revised, if appropriate. (b) The contracting officer shall send the final solicitation to all prospective offerors. It shall- (1) Describe the nature of the need in terms of mission capabilities required, without reference to any specific systems to satisfy the need; (2) Indicate, and explain when appropriate, the schedule, capability, and cost objectives and any known constraints in the acquisition; (3) Provide, or indicate how access can be obtained to, all Government data related to the acquisition; (4) Include selection requirements consistent with the acquisition strategy; and (5) Clearly state that each offeror is free to propose its own technical approach, main design features, subsystems, and alternatives to schedule, cost, and capability goals. (6) Require the use of an Earned Value Management System that complies with the guidelines of Electronic Industries Alliance Standard 748 (EIA-748) (current version at time of solicitation). See 34.201 for earned value management systems and reporting requirements. (c) To the extent practicable, the solicitation shall not reference or mandate Government specifications or standards, unless the agency is mandating a subsystem or other component as approved under agency procedure.