What Does a Major Source Selection Actually Look Like?

The Air Force organizes major acquisition programs under Program Executive Officers - typically general officers (one-star or two-star) or senior civilian executives who are responsible for a portfolio of programs. Think of the PEO as the executive owner of the program. They report up through the acquisition chain to SAF/AQ - the Secretary of the Air Force's acquisition office, which is the top acquisition authority for Air Force programs. For a program this size, the Secretary of the Air Force's acquisition executive has personal interest in how it goes.

Under the PEO sits the Program Manager - typically a Colonel or a senior civilian (GS-15 or Senior Executive Service level). The PM runs the day-to-day program. They own the schedule, the technical performance, and the budget. They are accountable for everything. The contracting officer works very closely with the PM and is a key member of the Integrated Product Team (IPT) - the cross-functional group of engineers, logisticians, financial managers, and legal staff that manages the program together.

At this stage the contracting officer is not buying anything yet. They are learning the program, understanding what will eventually need to be procured, building relationships with the program office, and starting to think about acquisition strategy. For a major development program, the lead contracting officer is typically a senior civilian or military officer with significant systems acquisition experience - this is not a job for a brand-new CO.

The first major document the contracting officer owns on a large program is the Acquisition Plan (AP). This is required by FAR Part 7 for most significant acquisitions. It documents everything about how the government intends to buy this program - the competition strategy, the contract type, how requirements will be structured, small business considerations, how the government will evaluate proposals, and dozens of other decisions. It forces the entire team to think through the whole acquisition before committing to a path.

Before the acquisition strategy is finalized, it goes before an Acquisition Strategy Panel. This is a review panel of senior Air Force leadership - program executive officers, senior acquisition officials, and others - who review and approve the acquisition strategy. Think of it as a mandatory leadership check: senior officials hear the plan, ask hard questions, and either approve it or send the team back to rethink. Getting through the ASP with a clean approval is a significant milestone.

A decision this consequential is: how many contractors will compete, and at what stage? For a major development program, the government often runs a competitive Technology Maturation phase with two or three contractors, then down-selects to one winner for the full development contract (called the Engineering and Manufacturing Development contract). Each competition is its own source selection. The competition strategy has enormous cost implications - more competition costs more in the short term but typically produces better outcomes and lower prices over the life of the program.

The government does not just accept what a contractor says the program will cost. Two parallel efforts happen: an Independent Cost Estimate (ICE) is developed by the Cost Assessment and Program Evaluation office (CAPE) - they run their own model of what the program should cost, completely independent of the contractor or the program office. Simultaneously, the program office runs a Should-Cost analysis - an internal challenge to find inefficiencies and cost drivers. Both products become inputs to the government's negotiation position and pricing strategy.

For the full development contract (after the technology maturation phase), another major DoD milestone decision gates the program. Milestone B is when the Under Secretary of Defense formally authorizes Engineering and Manufacturing Development - the phase where the contractor actually builds and tests the system. This milestone requires dozens of certifications from program leadership and is a formal legal and policy gate. The government cannot award the main development contract until Milestone B is approved.

The first public signal that this acquisition is coming is a Sources Sought Notice posted on SAM.gov (the government's public contract opportunity website). This is not a solicitation - it is a market research tool. The government is asking: who out there is capable of doing this work? Responses help the program office understand the industrial base, assess small business opportunities, and determine the right competition strategy. There is no obligation on either side at this point.

The government hosts one or more Industry Day events where all interested contractors attend together. The program office presents what they are trying to accomplish and answers questions. Everyone hears the same information at the same time - this protects the integrity of the competition. Industry Days can run for a full day or even multiple days for a complex program, and often include classified sessions for programs with sensitive requirements. Attendance is typically very high - major defense contractors take these seriously.

The government may issue a formal Request for Information - a structured questionnaire asking contractors specific questions about their capabilities, their approach to key technical challenges, and their views on how the solicitation should be structured. An RFI is still not a solicitation and still obligates nothing. But the responses are extremely valuable - they tell the government what the market can actually deliver and often shape how the requirements and evaluation criteria are written.

Before the final solicitation goes out, the government releases a Draft Request for Proposals (Draft RFP) to industry for comment. Contractors review the draft instructions, the evaluation criteria, and the technical requirements, and submit written comments. The government reviews every comment and either adopts it, partially adopts it, or explains why it is not being adopted. This process typically runs 30 to 60 days and often results in significant changes. It is far better to fix a problem in the draft than after proposals are submitted.

A large source selection has a layered evaluation structure. Three groups are established and play distinct roles:

Source Selection Evaluation Board (SSEB): The working-level team that actually reads and scores the proposals. They are organized into technical, past performance, and cost/price teams. For a major fighter program this board could have dozens of people from engineering, logistics, financial management, and contracting.

Source Selection Advisory Council (SSAC): A senior review body above the SSEB. They review the SSEB's findings and make a recommendation to the final decision-maker. They provide an independent check on the evaluation.

Source Selection Authority (SSA): The single person who makes the final award decision. For a program of this magnitude this is typically a general officer or a very senior civilian - someone with the authority and seniority to make a multi-billion dollar decision and defend it in court. The SSA does not evaluate proposals directly - they rely on the SSEB and SSAC - but the decision is theirs alone.

The two most important sections of any competitive solicitation under FAR Part 15 are Section L (Instructions to Offerors - what contractors must submit) and Section M (Evaluation Criteria - how the government will judge what they submit). These two sections must align perfectly with each other. If Section M says the government will evaluate past performance on similar efforts, Section L must tell contractors exactly what to submit about their past performance. Inconsistencies between L and M are a common source of protests. These sections go through extensive legal and competition review.

The rest of the solicitation package takes shape: the Statement of Work (what the contractor must do), the Contract Data Requirements List (every report, test result, drawing, and document the contractor must deliver over the life of the program), the contract terms and conditions, the contract type (likely a Cost-Plus-Incentive-Fee contract for development, where the government pays actual costs plus an incentive profit tied to performance), and the Independent Government Cost Estimate (the government's own internal estimate of what it should cost).

Before a major solicitation goes out the door, it goes through multiple layers of review. The contracting office's legal counsel (typically Judge Advocate officers or civilian attorneys) reviews every word for legal sufficiency. The Competition Advocate - an official required by law whose job is to promote competition and challenge unnecessary restrictions on who can compete - reviews the strategy. For a program this large these reviews are thorough and often result in changes.

The final RFP is published on SAM.gov after a public presolicitation notice (required at least 15 days in advance by FAR). For a development contract of this complexity, the response period is typically 90 to 180 days - contractors need that long to write a credible proposal. Pre-proposal conferences are held, written questions come in, and the government issues formal amendments answering them. Every amendment restarts or extends the timeline for everyone equally.

While the government waits, major defense contractors are running proposal war rooms. For a fighter aircraft program, a proposal team can be hundreds of people working around the clock. The technical volume alone might be thousands of pages. The cost volume includes detailed estimates for every element of work - labor categories, hours, materials, overhead rates. These proposals cost contractors millions of dollars to prepare. That is a real barrier to entry, and one reason only a handful of companies ever compete on programs like this.

Proposals must be received by the exact date and time stated in the RFP. Late proposals are almost always rejected with no exceptions - FAR 15.208 governs this strictly and for good reason. Late proposal acceptance rules exist to prevent contractors from using extra time to improve their proposals while others had to meet the deadline. For classified programs, proposals may be hand-delivered to a secure facility. The contracting office logs every proposal received, tracks the page counts, and begins the compliance review.

Before anyone reads a word of the technical proposal, the contracting office checks that each proposal is administratively compliant - did the contractor follow all the instructions? Did they include every required section? Are the certifications complete? Proposals that fail a mandatory pass/fail requirement may be eliminated at this stage without any substantive evaluation. The contracting officer documents every compliance finding in writing.

The Source Selection Evaluation Board assigns each proposal an adjectival rating - typically Outstanding, Good, Acceptable, Marginal, or Unacceptable - for each evaluation factor. Every strength, weakness, significant weakness, and deficiency in every proposal is documented in writing with direct references to the proposal pages that led to the finding. This documentation has to be airtight - it will potentially be reviewed by the Government Accountability Office (a federal watchdog that handles contract protests) or even a federal court if a losing contractor challenges the award.

A separate team evaluates each contractor's track record on prior government contracts. They send past performance questionnaires to government customers who previously worked with each contractor, review contractor performance reports in the government's database (the Contractor Performance Assessment Reporting System, known as CPARS), and assess relevance of prior work to this program. A contractor who has built aircraft before gets more credit than one who has not. Past performance is rated on confidence - how confident is the government that this contractor will perform successfully based on their history?

The cost/price evaluation is its own major undertaking. For a cost-reimbursement development contract, the government does not just look at the bottom line - it performs a cost realism analysis to determine whether each contractor's proposed costs are realistic for what they are promising. An unrealistically low cost proposal is actually a risk, not a benefit - it suggests the contractor either does not understand the work or plans to come back for more money later.

The Defense Contract Audit Agency (DCAA) - an independent government agency that audits defense contractor finances - may be requested to perform an assist audit of the contractor's proposed costs, labor rates, and overhead rates. A DCAA audit on a major program can itself take 6 to 12 months. The cost team uses the audit results, DCAA's established billing rate agreements with the contractors, and their own analysis to build the government's assessment of what each offer will actually cost.

After the initial evaluation, the contracting officer - advised by the SSEB - makes a competitive range determination. The competitive range includes all offerors who have a reasonable chance of receiving award after discussions. Proposals so deficient that no amount of discussion could make them competitive may be excluded at this stage. Excluded offerors are notified promptly (FAR 15.306(c)) and may request a pre-award debriefing to understand why they were cut. Exclusion decisions are one of the most protest-prone moments in a source selection.

Once the competitive range is set, the government opens discussions with each offeror. This is one of the most technically demanding parts of the CO's job. The government must communicate every significant weakness or deficiency in each proposal - the contractor has a right to know what the government found and a chance to address it. Discussion letters (sometimes called Evaluation Notices) are sent to each contractor.

There are strict rules: you cannot tell Contractor A what Contractor B proposed. You cannot tell anyone the ratings. You cannot engage in "auction techniques" - telling a contractor they need to lower their price to a specific number to win. Every written exchange goes through legal review. The CO is managing simultaneous discussions with multiple sophisticated contractors, each of which has teams of attorneys and proposal specialists pushing hard.

When discussions are complete, the contracting officer sends a Final Proposal Revision request to every offeror still in the competitive range. This is the contractors' last chance to improve their proposals. They have a set deadline - typically 30 to 60 days - to revise any part of their proposal. The SSEB then performs a final evaluation of the revised proposals. After FPRs are submitted, discussions are closed. There is no going back.

The Source Selection Evaluation Board compiles its final report - a comprehensive document covering every factor, every offeror, every rating, every finding. This document is the foundation of the entire source selection record. It must be complete, accurate, and defensible. Every conclusion must be tied back to the proposal pages that support it. The report goes to the Source Selection Advisory Council for review.

The SSAC reviews the SSEB's findings independently and prepares its own recommendation to the Source Selection Authority. The SSAC may agree with the SSEB, raise concerns, or recommend a different offeror. Their job is to provide the SSA with a senior-level assessment - are the findings sound? Is the record complete? Does the recommended award make sense? The SSAC recommendation is advisory, not binding. The SSA can accept or reject it, but must document why.

The SSA conducts a best-value tradeoff analysis. For a best-value competition, the SSA is not required to pick the lowest price or even the highest-rated technical proposal. They must make an integrated judgment: is the technical superiority of Contractor A worth the additional cost compared to Contractor B? Is past performance confidence strong enough to matter at this price differential? This judgment must be documented thoroughly in the Source Selection Decision Document (SSDD) - a written narrative of the SSA's reasoning that will survive legal scrutiny.

For a multi-billion dollar fighter program, this decision is made by a general officer or senior civilian with the full weight of that responsibility. It will be reviewed by lawyers, questioned by Congress, and potentially challenged in federal proceedings by the losing contractors.

Before any award announcement, the SSDD and the entire source selection record goes through a final legal sufficiency review. Attorneys review the documentation to ensure the process was followed correctly, the record supports the decision, and there are no obvious legal vulnerabilities. For a program this large, this review is extensive. The attorneys are essentially stress-testing the record against every known protest ground.

For a contract of this magnitude, Congress must be notified before award. This is a statutory requirement - the government cannot sign the contract until the required notification period has passed. The relevant committees are notified of the intended award, the selected contractor, and the contract value. Congressional oversight of major defense programs is real and active. If members of Congress have concerns, this is when they raise them.

All offerors who did not win are notified promptly after award. FAR 15.503 requires written notification including the number of offerors, the name of the awardee, and the contract value. Losing a competition of this scale is a significant business event for a defense contractor. Their response is immediate: they call their attorneys and ask for a debriefing.

Each unsuccessful offeror has the right to request a debriefing - a meeting where the government explains why they did not win. FAR 15.506 governs these in detail. The government must provide the evaluation of the offeror's proposal, their ratings, the overall rankings, and the rationale for the award decision. What the government cannot provide is another offeror's proprietary information.

Debriefings are high-stakes. The contracting officer, source selection officials, and legal counsel prepare extensively. Losing contractors send senior executives and attorneys. The clock on the protest period typically starts running from the debriefing date.

An unsuccessful offeror generally has 10 days after their debriefing to file a protest with the Government Accountability Office (GAO) - the federal watchdog that adjudicates most contract protests. When a protest is filed on a program of this size, the contract may be automatically stayed (stopped) while the protest is pending - typically 100 days. The government must file an Agency Report defending every aspect of the source selection. GAO attorneys review the entire record. If GAO finds the government made a mistake, they can recommend re-evaluation, a new competition, or other remedies.

Assuming no protest, or after a protest is resolved in the government's favor, the contract is signed, a program kickoff meeting is held, and the work begins. After years of planning, evaluating, and deciding - the aircraft development program is now underway. The contracting officer's work shifts from acquisition to contract administration - managing a multibillion dollar development relationship with a defense contractor that will likely span 10 to 15 more years before the aircraft ever reaches an operational squadron.