The DoD Source Selection Process: How the Government Chooses Its Contractors

Source selection is the process through which the DoD evaluates competing contractor proposals and picks a winner. It's also the process where billion-dollar decisions get protested, programs get delayed, and contracting officers lose sleep. Whether you're writing a proposal, evaluating one, or trying to understand why you lost, you need to understand how this process actually works.

This is the deep dive. For the foundational overview (including contract types, the FAR framework, and the COR role), see our Federal Contracting 101 guide.

A note on section numbers: this guide uses the traditional FAR citations most people still know. Since early 2026, DoD has used the rewritten FAR text from the Revolutionary FAR Overhaul, which reorganized Part 15. Evaluation factors now sit at 15.104, the competitive range at 15.204-1, preaward debriefings at 15.206-2, and postaward debriefings at 15.301 (FAR overhaul Part 15). The concepts below carry over.

Phase 1: Pre-Solicitation: Building the Foundation

Source selection doesn't start when the RFP drops. It starts months (sometimes years) earlier with acquisition planning. A weak pre-solicitation phase creates ambiguous requirements, poorly crafted evaluation criteria, and vulnerable award decisions. A strong one creates clarity for offerors and a defensible record for the government.

The Acquisition Plan (AP)

FAR 7.1 requires an Acquisition Plan for most significant acquisitions. The AP documents the acquisition strategy: contract type, competition approach, schedule, funding, and source selection methodology. For ACAT I and II programs, the AP goes through senior leadership review. This is where the decision to use Best Value Tradeoff vs. LPTA is first made, and it should be made deliberately, not by default.

Market Research

FAR 10.001 requires market research before developing requirements. This isn't just a compliance checkbox. It's how the government learns what's commercially available, who can do the work, whether competition is realistic, and what fair market prices look like. Inadequate market research leads to requirements written for one vendor, unrealistic performance standards, or a cost estimate that doesn't reflect reality.

Drafting the Requirements

The Statement of Work (SOW), Statement of Objectives (SOO), or Performance Work Statement (PWS) defines what the contractor must do. The choice matters:

• SOW: Government prescribes how the work must be done (specific tasks, methods, deliverables). Maximum government control; limits contractor innovation.
• PWS: Government defines outcomes (measurable performance standards, acceptable quality levels). Contractor determines how to achieve them. Preferred for services; enables best-value competition on approach.
• SOO: Government states high-level objectives; offerors propose the SOW/PWS as part of their proposal. Maximum offeror innovation; requires strong technical evaluation capability.

Industry Engagement

Pre-solicitation engagement (market surveys, Requests for Information (RFIs), industry days, and one-on-one meetings) is legal and encouraged. FAR 15.201 (15.101 in the overhauled text) says exchanges of information with industry are encouraged from the earliest identification of a requirement through receipt of proposals. Well-run industry days reduce ambiguity in proposals and improve competition quality. Contractors who skip industry days and one-on-ones do so at their peril. That's where the real requirements picture often emerges.

Phase 2: The RFP: Section L and Section M Are Everything

The Request for Proposals (RFP) is the government's formal offer to receive competing proposals. For complex acquisitions, the RFP is organized into sections (traditionally A through M, though formats vary). Two sections dominate every competitive source selection:

Section L: Instructions to Offerors

Section L tells offerors how to structure and submit their proposal. Page limits by volume. Required content and format for each section. Proposal classification requirements. Submission deadlines and methods. A contractor that violates Section L requirements (submits too many pages, omits a required certification, uses the wrong font size) can have its proposal rejected or evaluated unfavorably.

Read Section L first, then read it again. Build your proposal outline directly from Section L headings. Evaluators score what's in the RFP, not what you think should be there.

Section M: Evaluation Factors for Award

Section M is the most important section in the RFP. It lists the evaluation factors (e.g., Technical Approach, Management Approach, Past Performance, Price/Cost), states their relative order of importance, and describes how they'll be evaluated. FAR 15.304 (15.104 in the overhauled text) requires the RFP to state the significant factors and subfactors and their relative importance, and to say whether the non-price factors combined are significantly more important than, approximately equal to, or significantly less important than price.

A sample Section M hierarchy might be:

• Technical Approach (most important)
• Past Performance (second)
• Price (least important, but must be evaluated)

Phase 3: The Source Selection Team: Who Does What

Source Selection Authority (SSA)

The SSA is the individual with the authority and accountability to make the final award decision. The FAR makes the contracting officer the SSA unless the agency head appoints someone else. In DoD, for acquisitions with a total estimated value of $100 million or more (including options), the agency head must appoint, in writing, someone other than the Procuring Contracting Officer (PCO) as the SSA (DoD Source Selection Procedures). The SSA reviews the SSEB and SSAC reports, makes the best-value determination, and signs the Source Selection Decision Document (SSDD).

The SSA is not required to adopt the SSAC's recommendation, but if the SSA departs from it, the SSDD must explain why. The SSA's decision is the one that matters, and it's the one that gets scrutinized in a protest.

Source Selection Evaluation Board (SSEB)

The SSEB is the working-level evaluation team. It's typically divided into functional groups: a Technical Evaluation Team, a Management Evaluation Team, a Past Performance Evaluation Team, and a Cost/Price Team. Each team evaluates proposals against the Section M criteria in their domain and produces an SSEB Report with narrative ratings and supporting documentation.

SSEB members must be independent. They cannot have organizational conflicts of interest, and they must treat all offerors' proprietary information with strict confidentiality.

Source Selection Advisory Council (SSAC)

Required for acquisitions with a total estimated value of $100 million or more unless a waiver is approved (per DoD's Source Selection Procedures). The SSAC is made up of government personnel from the functional areas where the SSA needs expertise. They review the SSEB's work and produce a written comparative analysis and recommendation to the SSA. The SSAC recommendation is advisory; the SSA makes the final call.

Note: DoD's procedures say no SSAC report is prepared for an LPTA source selection. LPTA evaluations are binary (pass/fail on technical requirements, then price ranking), so there's no tradeoff for the SSAC to analyze.

The Procuring Contracting Officer (PCO)

The PCO manages the mechanics of the source selection: issuing the RFP and amendments, receiving and safeguarding proposals, managing the Q&A process, coordinating with the SSEB, conducting discussions, and ultimately executing the contract award. The PCO has independent legal authority to bind the government and is personally responsible for the integrity of the process.

Phase 4: Proposal Evaluation: How Proposals Are Scored

Once proposals are received, the SSEB evaluates them against Section M criteria. Each factor is typically assessed using an adjectival rating system. DoD's Source Selection Procedures provide a standard rating scale:

• Technical/Management Ratings: Outstanding, Good, Acceptable, Marginal, Unacceptable
• Past Performance Ratings: Substantial Confidence, Satisfactory Confidence, Neutral Confidence (for offerors with no relevant past performance record), Limited Confidence, No Confidence
• Risk Ratings: Low, Moderate, High, Unacceptable (technical risk: how likely the offeror's approach is to cause schedule disruption, higher cost, or degraded performance)

DoD's procedures bar numerical or percentage weighting of evaluation factors, and the ratings are adjectival, backed by narrative findings rather than point totals. A proposal rated Outstanding in technical should have specific documentation of why it exceeds requirements and how that exceedance benefits the government.

Cost/Price Evaluation

For FFP competitions, the government evaluates price (what you'll charge). For cost-reimbursement competitions, the government evaluates cost realism: whether your proposed cost reflects a realistic assessment of what the work will actually cost. An unrealistically low cost proposal on a CPFF competition is a red flag, not a win; it suggests the offeror doesn't understand the scope.

Phase 5: Competitive Range and Discussions

After the initial evaluation, the CO may establish a competitive range (FAR 15.306): the group of offerors whose proposals are most highly rated and stand a reasonable chance of award. Offerors outside the competitive range are eliminated and notified. They can get a preaward debriefing if they ask in writing within 3 days.

Within the competitive range, the government may conduct discussions: formal written or oral exchanges intended to allow offerors to address deficiencies, significant weaknesses, and ambiguities. Discussions are optional (the government can award without them), but once discussions open, the CO must engage all offerors in the competitive range and treat them fairly.

Discussions cannot reveal one offeror's price or technical approach to another (FAR 15.306(e)), so the CO can't tell you the number you need to beat, though the CO can tell you your own price looks too high or too low. After discussions close, the CO issues a call for Final Proposal Revisions (FPRs). Offerors get one last chance to revise their proposals.

Phase 6: Best Value Determination and Award

The SSA receives the SSEB Report, the SSAC Report (if applicable), and makes the best-value determination. This is where the rubber meets the road.

Best Value Tradeoff

The SSA must weigh technical merit and past performance against price and determine whether any premium over the lowest-priced technically acceptable offer is worth paying. The tradeoff must be documented in the SSDD with specific reasoning: "Offeror A's Outstanding technical rating for System Integration, specifically its proposed approach, provides a meaningful benefit that justifies the premium over Offeror B's Acceptable-rated proposal."

Generic statements like "the technical superiority justifies the higher price" are protest bait. The SSDD must connect specific technical differentiators to specific government benefits.

LPTA: Simplest Route to Award

Under LPTA, once a proposal passes all technical acceptability criteria (it's either acceptable or unacceptable, no gradient), the lowest priced technically acceptable proposal wins. No tradeoff required. The government cannot pay more for a better technical solution because the process doesn't allow for it.

Congress has increasingly restricted LPTA use for DoD. The FY2018 NDAA prohibited LPTA for Engineering and Manufacturing Development (EMD) on major defense acquisition programs (section 832) and for auditing contracts (section 1002), and both bans now sit in DFARS 215.101-2-70. DoD policy further restricts it: LPTA is not appropriate where requirements are not well-defined, where there is meaningful risk of unsuccessful performance, or where paying for technical superiority would benefit the government.

Best Value vs. LPTA: When to Use Each

Factor	Best Value Tradeoff	LPTA
Requirements definition	Can be partially defined; technical approach matters	Must be clearly and completely defined upfront
Performance risk	Appropriate when risk of failure is meaningful	Only when performance risk is minimal
Value of technical superiority	Government willing and able to pay for better	No value to technical superiority beyond threshold
Contractor innovation	Rewards innovative technical approaches	Discourages innovation (no reward beyond pass/fail)
Administrative burden	Higher: SSA must document tradeoff rationale	Lower: binary evaluation, no tradeoff required
Protest risk	Higher (tradeoff rationale can be challenged)	Lower (but technical acceptability determination can be challenged)
Prohibited for	N/A: appropriate across the spectrum	EMD on major defense acquisition programs; auditing contracts; personal protective equipment and aviation critical safety items where poor quality could cause combat casualties
Typical use cases	Complex system development, professional services, IT solutions	Commodities, well-defined services (janitorial, food service, basic IT support)

Phase 7: Award, Debriefs, and Protests

Award and Notification

After the SSA signs the SSDD, the CO executes the award. Unsuccessful offerors in the competitive range are notified and can get a post-award debriefing if they ask in writing within 3 days of the award notice (FAR 15.506). Offerors outside the competitive range can request a preaward debriefing (FAR 15.505).

Debriefings

Debriefings are important, both for the government and for contractors. The government must provide: the agency's evaluation of the significant weak or deficient factors in the offeror's proposal, the overall evaluated cost/price and technical rating of the winner, and the rationale for award decision. Contractors should use debriefings to understand why they lost and what to fix for next time.

DoD adds its own enhanced debriefing rule, first issued as a class deviation in 2018 and made permanent in March 2022 (DFARS 215.506-70). After a required postaward debriefing, offerors can submit additional written questions within 2 business days, the government must answer within 5 business days, and the debriefing isn't concluded until it does.

Protests

Unsuccessful offerors who believe the government violated procurement law or regulation have the right to protest. The three protest forums are:

• Agency-level protests: Filed with the contracting agency. Fast and low-cost, but the agency is reviewing its own decision. Must generally be filed before award or within 10 days of learning the basis of protest.
• GAO (Government Accountability Office): Most common forum. Must generally be filed within 10 days after you know (or should have known) the basis for protest, or within 10 days after a required debriefing; problems with the solicitation itself must be raised before proposals are due (4 CFR 21.2). GAO has 100 days to issue a decision. A timely GAO protest triggers an automatic stay of award or performance unless the agency overrides it (for urgent and compelling circumstances, or after award, when continuing is in the best interests of the United States). In FY2025 GAO sustained 14% of the protests it decided on the merits, and protesters got some form of relief, through a sustain or voluntary corrective action, in 52% of cases (GAO FY2025 report).
• Court of Federal Claims (COFC): Formal federal court. More expensive, more formal, no automatic stay. Used for larger dollar protests or when the legal issues require judicial resolution.

Frequently Asked Questions

What is the Source Selection Decision Document (SSDD) and why does it matter?

The SSDD is the formal document signed by the Source Selection Authority that records the best-value determination and the rationale for the award decision. It must document the SSA's comparative assessment of all offerors in the competitive range, including the specific technical, past performance, and cost/price tradeoffs that led to the award. The SSDD is the primary document reviewed in a protest. If the rationale isn't there, the award doesn't survive.

Can an offeror see a competitor's proposal?

No. Competitor proposals are proprietary and protected. The government will not share another offeror's technical approach, pricing, or business data during the source selection. In a debriefing, the government can tell you the winner's overall evaluated rating and price but cannot reveal proprietary details. In a protest proceeding at GAO, redacted versions of protest-relevant documents may be produced under a protective order that limits access to counsel and authorized representatives.

What is competitive range and what happens if you're excluded?

The competitive range is the set of offerors whose proposals are most highly rated and are considered for award after initial evaluation. If your proposal is excluded from the competitive range, you're out of the competition, but you're entitled to a preaward debriefing. You can also file an agency-level protest or a GAO protest challenging the competitive range determination, but you must act quickly (within 10 days of learning the basis of protest).

How long does a DoD source selection typically take?

It varies enormously by program complexity. Simple acquisitions under the SAT can be awarded in weeks. Major system source selections (ACAT I programs, large IDIQ vehicle competitions) can take a year or more from RFP release to award. Government capacity constraints, amendment cycles, protest delays, and Congressional notification requirements all add time. Contractors should plan their BD and capture timelines accordingly. If you're not engaged 12-plus months before RFP release on a large program, you're already behind.

What does "technically acceptable" mean in an LPTA evaluation?

In an LPTA source selection, proposals are evaluated as either Acceptable or Unacceptable on each technical factor. There is no gradation. An Acceptable rating means the proposal meets the minimum requirements for that factor. An Unacceptable rating means it does not. An offeror with any Unacceptable factor rating cannot be selected for award, regardless of price. The government's job is to set the acceptability thresholds clearly in Section M so that the pass/fail determination is objective and auditable.