The J&A is the CO's document — but you supply the raw material
A sole source award under FAR 6.302-5 requires a Justification and Approval (J&A) from the contracting officer. The contractor doesn't write the J&A — the CO does, and the CO's name goes on the document. But the CO can only write a defensible J&A when the contractor has supplied the raw material: evidence of capability, evidence of fair pricing, and evidence that the requirement fits within the sole source authority being invoked. Most SDVOSBs understand the authority exists. Few understand what the CO actually needs to use it.
The discipline is the same as any capture work: the contractor's job is to make the agency's job easy. A J&A that is hard to write — because the supporting evidence is incomplete, the pricing is unsupported, or the capability claims are vague — does not get written, regardless of how much the agency wants the award to happen. A J&A that writes itself, because every element is documented, gets written and gets approved.
What the J&A must establish
The CO's J&A has to defend the award against later scrutiny — protests, IG review, GAO inquiry, oversight. Every J&A establishes the same set of elements:
- The requirement is identified and well-defined
- The contractor can perform the work — demonstrated, not claimed
- The award price is fair and reasonable, supported by market research
- The contractor is the only known source that can perform at that price within the threshold
- The applicable FAR authority (6.302-5 for SDVOSBs) is correctly invoked
Each element requires evidence, not assertions. The CO documents — the contractor supplies the material to document with. Capability statements without contract numbers, pricing claims without benchmark sources, and "we can do it" assertions without past performance evidence are not material the CO can use.
What makes a J&A defensible vs. protestable
Strong J&As share patterns. They cite past performance on the same NAICS code with specific contract numbers and dollar values. They reference pricing benchmarked to CALC+ rates or BLS wage data. They establish that the requirement was communicated through a sources sought notice that received limited or no qualified responses. They document the absence of other qualified SDVOSBs through a specific market research effort, not a generic claim.
Weak J&As — the ones that get protested — share their own patterns. They rely on the contractor's self-assessment of capability. They lack pricing evidence and depend on the CO's discretion. They skip or abbreviate the market research step. They invoke the wrong FAR authority for the requirement, or invoke the right authority without the supporting evidence.
Protestable J&As usually fail on market research. The CO did not establish that only one SDVOSB could perform the work, or the pricing rationale was unsupported, or the sources sought process was not run. The protest grounds are almost always the same — and almost always preventable when the contractor supplies the right evidence at the right time.
The contractor's role in making the J&A easy
The contractor controls more of the J&A's strength than is commonly recognized. Five categories of evidence make the difference:
Past performance citations in the required NAICS codes. Not capability statements — contract numbers, periods of performance, and dollar values that map to the requirement. Three relevant past performance entries are worth more than ten generic ones.
Pricing transparency. Labor rates benchmarked against CALC+ or BLS data with a clear basis of estimate. A wrap rate calculation tied to specific overheads and G&A. The CO needs a number they can defend in the price reasonableness section, not a number they have to take on faith.
Capability documentation. Technical certifications, key personnel resumes, relevant clearances, facility certifications. The artifacts that prove capability rather than claim it.
Prior work samples. Releasable, unclassified work product that demonstrates the quality of past performance. A redacted final deliverable from a similar engagement is more persuasive than a paragraph describing it.
Compliance with the SDVOSB authority. SBA verification, ownership documentation, and confirmation that the firm meets the 6.302-5 criteria. The authority does not work without the underlying eligibility evidence.
The goal at every step is to make the CO's job easy. The easier the J&A is to write, the more likely it gets written and the more defensible it is once written.
The relationship that precedes the award
Sole source awards are won months before the J&A is written. The agency relationship is built through patient, consistent engagement:
- Sources sought responses that demonstrate SDVOSB qualification and fit
- Industry day attendance that signals domain expertise to the program office
- Engagement with the agency's Office of Small and Disadvantaged Business Utilization (OSDBU), whose mandate is to connect small businesses with requirements
- RFI responses that shape the requirement in ways that align with your capabilities — both the formal RFI and the informal pre-RFI conversations
- Capability briefings to program managers and contracting offices that introduce the firm before any specific opportunity is on the table
The discipline is patience and consistency, not one-shot outreach. A firm that has been in front of an agency office for two years, has responded to three sources sought notices, and has a documented relationship with the OSDBU is in a structurally different position than a firm submitting a capability statement for the first time when the J&A is being drafted.
Sole source intelligence delivered
Prime Recon Labs delivers sole source intelligence as part of the retainer — agency-level scoring based on sole source spending patterns, expiring contract timelines, and small business office contacts. The agency intelligence package includes draft J&A citations with FAR 6.302-5 references, contracting officer contact information, and recent agency sole source award history. The capture work behind a sole source award is information-intensive and relationship-intensive; the information part is what we deliver.