Sole Source Justification: What It Is and How to Write One

A sole source justification is a written document that explains why a contract should be awarded to one vendor without competition. It names the legal authority for the noncompetitive award, describes the capability only that supplier offers, records the market research performed, and establishes that the price is fair and reasonable.

Buyers write it. Vendors live with the consequences of it. A weak justification is the most common reason a planned noncompetitive award collapses back into a competitive solicitation, which is why both sides of the table need to understand what the document has to prove. In federal contracting, FAR 6.302 lists the statutory authorities that permit contracting without full and open competition, and FAR 6.303 sets the requirements for the justification that supports them.

Sole source vs single source vs limited competition

These terms get used interchangeably in procurement conversations and they are not the same thing. The difference determines how much documentation the buyer owes and how exposed the award is to challenge.

The practical test is whether an alternative exists. A sole source award says no alternative can meet the requirement. A single source award says alternatives exist and the buyer chose not to use them. The second is far harder to defend, and it is where most challenges land.

The legal authority behind a sole source justification

Every sole source justification has to point at a rule. Which rule applies depends on whose money is being spent.

Federal contracts

FAR 6.302 provides seven authorities: only one responsible source and no other supplies or services will satisfy agency requirements; unusual and compelling urgency; industrial mobilization, engineering, developmental, or research capability, or expert services; international agreement; authorized or required by statute; national security; and public interest. The first is the classic sole source case. The others are narrower, and the justification that supports any of them has to be approved at a level that rises with the value of the action.

Federal grant and award recipients

States, local governments, universities, and nonprofits spending federal award dollars follow 2 CFR 200.320. Its noncompetitive method is available in five circumstances: the transaction does not exceed the micro-purchase threshold; only a single source can fulfill it; a public exigency or emergency will not permit the delay of a competitive solicitation; the federal agency or pass-through entity gives written approval after a written request; or competition is determined inadequate after several sources were solicited.

State, local, and commercial buyers

State statutes, municipal codes, and corporate procurement policies rarely mirror the federal language, but they almost always require the same four things: a named exception, evidence of market research, a demonstration of price reasonableness, and an approval signature above the requester's level. Commercial buyers tend to call it a competitive bid waiver or a single source request. The burden of proof is the same.

How to write a sole source justification

The form varies by agency and by company. The reasoning does not. Work through these six elements in order and the document mostly writes itself.

1. State the requirement, not the vendor. Describe the capability the organization needs and why it needs it. A justification that opens with a product name has already lost, because it reads as though the conclusion came first.
2. Cite the specific authority. Name the regulation, statute, or policy clause you are relying on. A general appeal to convenience or timing is not an authority.
3. Document the market research. List the sources considered, how you identified them, and the specific reason each one cannot meet the requirement. A blanket statement that no alternatives exist invites challenge.
4. Prove the uniqueness is real. Proprietary technology, exclusive distribution rights, sole possession of required data, and certifications no competitor holds are defensible. Familiarity, incumbency, and staff preference are not.
5. Establish price reasonableness. Without competition there is no market check, so substitute one: historical pricing, published rate schedules, comparable contracts at other organizations, or an independent cost estimate.
6. Address future competition. Describe what the organization will do so the next purchase can be competed, whether that means acquiring data rights, rewriting the requirement in performance terms, or qualifying a second source.

Where a sole source justification falls apart

Reviewers see the same failures repeatedly. Each one is cheap to fix before submission and expensive to fix after.

• The requirement was written around one vendor's specifications, which turns the justification into circular reasoning.
• Urgency is claimed for a need the organization has known about for months. A lack of advance planning is not a valid basis for avoiding competition.
• Market research consists of a single conversation with the incumbent.
• The uniqueness claim describes a preference, such as staff already being trained on a particular interface, rather than a genuine capability gap.
• Price reasonableness is asserted rather than demonstrated.

What vendors should do when a sole source justification is in play

If a buyer is considering a noncompetitive award to you, your job is to make their justification easy to write and hard to overturn. That means supplying, in writing and without being chased, the specific technical differentiators no competitor can match, the certifications and accreditations you hold, the intellectual property or data rights that block substitution, and current pricing that can be benchmarked against something. Buyers rarely ask for these as a tidy package. The vendors who provide one anyway tend to survive the review.

If a buyer is considering a noncompetitive award to a competitor, the counter is factual and narrow: show that you can meet the stated requirement. Vague capability claims will not reopen a competition. A point-by-point response against the published requirement sometimes will, and it is worth studying how RFP evaluation criteria are framed for the moment the requirement does go competitive.

Both moves depend on evidence that is already written, already approved, and already current. Teams that treat their approved answers as an institutional knowledge base rather than a folder of last year's proposals answer these requests in hours instead of weeks. The Consortium for Service Innovation formalized that pattern in its Knowledge-Centered Success methodology: capture knowledge as a byproduct of doing the work, reuse it inside the workflow, and improve it in place rather than rewriting it. A maintained content library applies the same discipline to capability statements, certifications, and past performance.

A sole source justification example, in structure

A useful example is a skeleton, not a filled-in template, because the facts have to be yours. The document should read in this order: requirement description; estimated value and period of performance; the authority cited; the market research conducted and the sources ruled out, with reasons; the unique capability and the evidence supporting it; the basis for price reasonableness; the plan to enable future competition; and the approval signatures. Anything that cannot be evidenced should be cut before a reviewer sees it, because one unsupported claim tends to discredit the claims around it.

Sole source awards are the exception. Most revenue still moves through the competitive bidding process, and the same evidence that supports a buyer's justification is the evidence that wins competitive bids. RocketDocs keeps it approved, current, and one search away. Book a demo to see how.