FAR 15.6 explained: a contractor's guide to unsolicited proposals

You log into SAM.gov on a Tuesday morning, staring at a feed of freshly dropped RFPs. As you scan the solicitations, a familiar sinking feeling sets in. The requirements are hyper-specific, the timelines are brutally short, and the evaluation criteria seem practically hardwired for an incumbent or a competitor who helped shape the acquisition strategy months ago.

If your business development team is solely relying on published solicitations, you are constantly reacting. You are competing in crowded, commoditized arenas where the lowest price technically acceptable (LPTA) often wins out over genuine innovation.

But there is another way to engage with the federal government—a proactive strategy that allows you to bypass the RFP bloodbath, introduce your proprietary technology, and potentially secure a sole-source contract before an agency even formalizes a requirement.

This strategy is built entirely around far 15.6 unsolicited proposals. Rather than waiting for the government to tell you what they need, you tell the government how your unique solution solves a critical mission challenge they haven't yet figured out how to tackle. It requires precision, deep agency knowledge, and strict adherence to federal acquisition regulations, but mastering this approach fundamentally changes how you win government business.

What Is FAR 15.6 and How Does It Benefit Federal Contractors?

FAR 15.6 is the specific subpart of the Federal Acquisition Regulation (FAR) that establishes policies and procedures for the submission, receipt, evaluation, and acceptance or rejection of unsolicited proposals.

While the majority of federal contracting operates on a competitive, solicited basis—where an agency identifies a need, publishes a Request for Proposal (RFP), and evaluates bids—FAR 15.6 opens a backdoor for genuine innovation. It allows contractors to pitch unique methods, approaches, or ideas that the government did not request.

To truly understand the value of this regulation, you have to contrast the unsolicited approach with the traditional bidding cycle.

For BD professionals, the strategic benefits of mastering FAR 15.6 are enormous. You are no longer constrained by the rigid boundaries of a published Performance Work Statement (PWS). You have the freedom to define the problem and present your proprietary technology as the definitive solution.

By introducing your capabilities to federal agencies before a formal requirement exists, you position your firm as a thought leader and trusted advisor. Even if the unsolicited proposal does not immediately result in a sole-source award, it often heavily influences future solicitations, ensuring that when an RFP finally does drop, the requirements align perfectly with your technical strengths.

Furthermore, this approach allows you to deploy your BD resources more efficiently. Instead of burning countless hours on losing proposals in highly saturated markets, you invest that time in targeted, high-impact pitches that leverage your organization's unique intellectual property.

Essential Criteria for a Valid Unsolicited Proposal

Agencies do not want their inboxes flooded with generic sales brochures, and FAR 15.6 is specifically designed to filter out marketing fluff. If your submission does not meet a very rigid set of criteria, the agency coordinator will reject it outright without ever passing it to a technical evaluator.

Understanding what qualifies—and what disqualifies—your submission is the most important step in this entire process.

Mandatory Requirements Under FAR 15.603

According to FAR 15.603(c), a valid unsolicited proposal must check several non-negotiable boxes. If any of these elements are missing, the document is legally categorized as something else (usually marketing material) and dismissed.

1. It must be innovative and unique.

Your proposal cannot simply offer a better version of something the government already buys. It must present a novel concept, an unproven but highly promising technology, or a completely new approach to solving a known mission challenge.

2. It must be independently originated.

You must have developed the idea entirely on your own. If your proposal was drafted under the supervision of a government official, or if an agency explicitly asked you to write it down and send it to them after a meeting, it is not an unsolicited proposal. It is a solicited document and must be treated as such.

3. It must include sufficient detail.

A mere conceptual outline is not enough. The proposal must contain detailed technical information, a methodology, and a realistic cost estimate to allow a contracting officer and a technical team to determine if the idea is viable and beneficial to the agency's mission.

4. It cannot be an advance proposal for a known requirement.

If an agency has already published an RFI, a Sources Sought notice, or an RFP for a specific need, you cannot bypass that competitive process by submitting an unsolicited proposal for the same requirement. You must wait and bid competitively.

What Disqualifies an Unsolicited Proposal?

Many contractors waste valuable time trying to shoehorn standard offerings into the FAR 15.6 framework. To avoid instant rejection, understand that the following submissions will never be evaluated as unsolicited proposals:

• Commercial Off-The-Shelf (COTS) Products: Standard software licenses, typical hardware, or commercially available goods that can be procured via GSA schedules.
• Routine Services: Standard IT support, janitorial services, or basic staff augmentation.
• Marketing Materials: Brochures, generic capabilities statements (cap statements), or white papers that lack technical methodology and cost data.
• Responses to Published Needs: Any submission that attempts to answer a published agency requirement, even if the RFP is still in the draft phase.

Required Proposal Contents

FAR 15.605 explicitly mandates what must be included in the submission package. Omit any of these, and you fail the compliance gate. Keep your descriptions brief, tight, and professional.

• Basic Information: The cover page must include the contractor's name, address, and the names of both technical and business points of contact. You must also include the date of submission and a clear, concise title.
• Technical Information: This is the core narrative. It must include a concise title, an abstract (executive summary), the proposed statement of work, the specific method of approach, and a detailed explanation of the innovation. You must also name the key personnel involved and provide their qualifications.
• Supporting Cost Data: You cannot just throw out a ballpark figure. You must include a rough order of magnitude (ROM) or detailed cost estimate, proposed duration of the project, and a brief description of the facilities or equipment required to perform the work.

How to Submit an Unsolicited Proposal Under FAR 15.6

The submission phase is where process hygiene matters most. You are asking a federal agency to allocate unscheduled time and resources to evaluate your idea. If you make it difficult for them to process your document, they simply won't do it.

Before you send anything, you need a highly regimented workflow. The government dictates how they want to receive these documents, and attempting to bypass the designated channels is a surefire way to get your proposal ignored.

1. Identify the Correct Agency Contact

Do not send your unsolicited proposal directly to an agency director, a program manager you met at an industry day, or a military commander. Under FAR 15.604, each agency is required to establish a centralized point of contact to coordinate the receipt and handling of unsolicited proposals.

This person is usually called the Unsolicited Proposal Coordinator, and they sit within the agency's procurement or acquisition office. If you send the proposal to a technical contact, they are legally required to forward it to the coordinator anyway, but doing so makes you look unfamiliar with federal acquisition rules. Find the coordinator's details on the agency's official website or by querying their main contracting office.

2. Follow a Step-by-Step Submission Checklist

To ensure your submission doesn't get snagged on administrative technicalities, follow this step-by-step approach before finalizing your package.

3. The Critical Importance of Marking Proprietary Data

When you submit an unsolicited proposal, you are handing over your most valuable intellectual property to the federal government. If you fail to mark this data correctly, it becomes highly vulnerable to Freedom of Information Act (FOIA) requests from your competitors.

FAR 15.609 dictates the exact restrictive legends you must place on the title page and on every single page containing trade secrets, proprietary formulas, or confidential financial data.

You must verbatim include the restrictive legend outlined in FAR 15.609(a) on the title page. Furthermore, on every subsequent page that contains protected data, you must include a header or footer stating: “Use or disclosure of data contained on this page is subject to the restriction on the title page of this proposal.” Do not try to write your own non-disclosure statement; the government will only recognize the specific language mandated by the FAR.

The Agency Evaluation Process: What to Expect

Once you press send, your proposal enters a highly structured, two-phase government review process. Understanding this workflow helps your BD team manage internal expectations and prepare for inevitable agency follow-ups.

The timeline is never fast. Agencies evaluate these submissions alongside their existing, funded procurement workloads.

The Initial Review Phase (Gatekeeping)

Before any technical evaluation occurs, the Unsolicited Proposal Coordinator conducts an initial compliance review under FAR 15.606-1. They are essentially looking for reasons to throw the document out.

They will verify that the submission includes all mandatory contents (from FAR 15.605), that it meets the definition of an unsolicited proposal (from FAR 15.603), and that it has been properly marked. They will also verify that the proposed concept does not closely resemble a pending competitive acquisition. If your proposal passes this administrative gate, the coordinator officially accepts it and routes it to the appropriate technical personnel.

Assessing Technical Merit and Mission Relevance

Once in the hands of technical evaluators (often program managers, chief technology officers, or subject matter experts), the proposal is scrutinized for its scientific, technical, and socioeconomic merits.

The technical team will evaluate whether your proposed innovation actually solves a painful problem for their department. They will dissect your methodology to see if it is scientifically sound and operationally viable. They aren't just looking for a cool idea; they want to see a clear path to execution that minimizes disruption to their current operations.

Evaluating Cost Realism and Value

Simultaneously, the contracting and finance offices will look at your pricing data. They need to determine cost realism—is your estimate accurate based on the technical approach, or are you lowballing to get a foot in the door?

Because this is not a competitive environment, the evaluators must determine if the cost represents an exceptional value to the government. They will also quietly investigate whether they even have the discretionary budget to fund the initiative, which is often the biggest hurdle to a successful award.

Gauging Overall Mission Benefit

Finally, the agency consolidates the technical and financial feedback to gauge the overall mission benefit. Does the unique nature of your proposal justify bypassing full and open competition?

If the answer is yes, the evaluation phase concludes with a highly favorable outcome. The contracting officer may draft a Justification and Approval (J&A) document under FAR 6.302-1, citing that only one responsible source (your company) can provide the required supplies or services. This paves the way for a sole-source contract award. If the agency likes the idea but lacks funding, they may request clarifications or keep the concept in mind for a future, competitively bid requirement.

Common Mistakes to Avoid When Drafting Unsolicited Proposals

Despite the high upside, the failure rate for unsolicited proposals is notoriously high. This is rarely because the contractor's technology is flawed; rather, it is because BD teams make unforced errors during the drafting and submission phases.

Avoid these common traps to dramatically increase your chances of surviving the agency's initial review.

Submitting Generic Marketing Materials

The single most common mistake contractors make is treating FAR 15.6 like a cold-email marketing campaign. They slap a cover page on an existing capabilities statement, attach a glossy PDF of their software features, and send it to an agency coordinator.

This triggers an immediate rejection. An unsolicited proposal is a formal acquisition document, not a sales brochure. It must contain granular technical methodologies, personnel qualifications, and detailed cost breakdowns. If an evaluator reads your submission and feels like they are being pitched rather than educated, you have lost the engagement.

Failing to Align with Agency Mission and Budgets

Your innovation might be brilliant, but if it doesn't solve a specific, high-priority problem for the target agency, they will not fund it. Contractors often make the mistake of developing a proposal in a vacuum, focusing entirely on how great their technology is, rather than on the agency's pain points.

You must deeply understand the target agency's strategic plan, their recent GAO audit reports, and their budget constraints. If you pitch a $10 million AI modernization platform to an agency that just had its IT budget slashed by Congress, your proposal will die in committee, regardless of its technical merit.

Ignoring Strict Formatting Requirements

Federal contracting officers are sticklers for the rules. FAR 15.6 outlines very specific requirements for cover pages, data markings, and content structure.

Contractors who try to get creative with formatting or ignore the mandatory data points listed in FAR 15.605 will see their proposals returned without a technical evaluation. To ensure compliance, create an internal review process where a separate proposal manager grades the document against the FAR guidelines before it is finalized. Never let an excited technical lead hit send without a compliance check.

Frequently Asked Questions About FAR 15.6 Unsolicited Proposals

To help your BD team navigate this complex landscape, we’ve compiled the most common questions contractors have when structuring a proactive bidding strategy.

Does an unsolicited proposal guarantee a sole-source contract?

Absolutely not. While a successful FAR 15.6 submission can lead to a sole-source award, the agency must still legally justify bypassing competition under FAR 6.302-1 (Only one responsible source). If the agency determines that your idea is great but other vendors could potentially execute it, they will likely use your concept to draft an RFP and open it up to full competition.

Can we submit the same unsolicited proposal to multiple agencies?

Yes, but you must be entirely transparent about it. FAR 15.605 requires you to explicitly state in your submission whether the proposal has been submitted to other government agencies or departments. Be aware that agencies may communicate with one another, so your pricing and technical narrative should be consistent, though the mission alignment sections should be uniquely tailored to each specific agency.

How long does the FAR 15.6 evaluation process take?

You must set realistic expectations for your business development team. Because unsolicited proposals are evaluated outside the normal rhythm of scheduled procurements, the timeline can be excruciatingly slow. Expect the initial compliance review to take a few weeks, while a full technical and financial evaluation can take anywhere from three to twelve months, depending on the agency's workload and budget cycle.

Can a small business submit an unsolicited proposal?

Yes. FAR 15.6 applies equally to businesses of all sizes. In fact, small businesses with highly specialized, niche intellectual property often find great success with unsolicited proposals, as it allows them to demonstrate unique value without getting crushed by large systems integrators in a standard LPTA RFP environment.

What happens if the agency likes the proposal but has no current funding?

This is a common outcome. The technical evaluators may praise the innovation, but the contracting officer simply lacks the discretionary budget to execute an award. In these cases, the agency will formally reject the proposal due to lack of funds, but they will often incorporate the concepts into their budget requests for the next fiscal year. Your BD team must maintain the relationship and track future forecasts for when the funding finally materializes.

Streamline Your Federal Bidding Strategy With Craxy AI

Executing a proactive strategy based on far 15.6 unsolicited proposals requires immense internal coordination. You are managing highly sensitive proprietary data, building complex technical volumes from scratch, and coordinating pricing models without the safety net of government-provided templates.

When you are simultaneously tracking multiple unsolicited submissions alongside your standard RFP workload, version control and compliance tracking become a nightmare. A fragmented approach using disparate Word documents, email threads, and localized spreadsheets inevitably leads to compliance errors, missed data markings, and leaked intellectual property.

Craxy AI transforms this chaotic process into a streamlined, centralized workflow.

Our proposal-management platform allows your BD team to securely organize proprietary data libraries, ensuring that your core innovations are perfectly documented and easily accessible. When drafting a FAR 15.6 submission, Craxy AI helps you map your narrative directly against the mandatory compliance criteria, ensuring you never miss a required field on your cover page or a critical IP data marking.

By unifying collaboration across your technical, pricing, and compliance teams, Craxy AI ensures your proactive pitches are as rigorously constructed as your most critical RFP responses.

---

Ready to Stop Leaving Revenue on the Table?