Sole source justification for software: building a defensible record

Reference article · 5 min read

Nearly every state and local purchasing code allows a noncompetitive award in narrow circumstances, and nearly every one puts the burden of proof on the agency. A sole source justification is the record that carries it. It has to show why competition was not available, not why one product is attractive, and it will be read by a purchasing officer, sometimes a governing body, and often an auditor.

Most rejected justifications fail the same way: they say why staff prefer a product rather than establish that no other product can meet the requirement. Terminology varies too. Some jurisdictions distinguish sole source, where only one supplier exists, from single source, where the agency chose one supplier among several for a documented reason. Rules and forms differ by jurisdiction and change, so confirm specifics with your purchasing office and counsel.

What the justification has to establish

Whatever the form, it asks for the same things.

The requirement, stated functionally. What the software must do, in capabilities and constraints, not a brand name.
Why only one supplier can meet it. The technical, legal, or proprietary condition that excludes others, traced to a document rather than staff opinion.
What market research was done. Who was considered, how, and what was found.
Why the price is reasonable. A basis that does not depend on competing offers.
What happens otherwise. The operational consequence of buying something else, stated plainly.

Add the approver's name and authority, the date, and where the record is retained; unsigned or undated justifications are an audit finding by themselves.

Only supplier, or strong preference

A useful test is whether the constraint lives in the product or in the agency's own configuration. If a competing product could meet the need provided staff accepted a different workflow, that is a preference. Preferences are legitimate, but they belong in the evaluation criteria of a competitive solicitation, not in a uniqueness claim.

Common fact patterns and the evidence each needs

Proprietary integration with an incumbent system. Document the dependency itself: interface specifications, license terms restricting third-party integration, and a dated written answer from the publisher on whether the interface is licensed to others. That an integration would be difficult is not a dependency.
Exclusive reseller or distribution rights. A dated manufacturer letter naming the product and the territory. Read it closely: calling a firm an authorized or preferred reseller establishes authorization, not exclusivity, and manufacturers often name several partners in one region.
Continuation of a pilot. Show the authority the pilot was awarded under, that the continuation stays within the scope already competed, and the configuration and data invested. Include a date by which the long-term award will be competed, since this pattern weakens when a noncompetitive pilot quietly becomes permanent.
Emergency replacement. State what failed, when, the operational or public safety consequence, and why the timeline does not permit even an abbreviated competition. Keep the scope to restoring service: emergency authority carries its own approvals and reporting, and using it to buy a full replacement platform is where these awards get challenged.

Market research that holds up

The record should show sources consulted, firms contacted, what each was asked, what each said, and dates. Sending the same functional requirement to several firms and keeping their replies is more persuasive than an assertion that staff looked around.

A notice of intent to sole source, posted publicly for a stated period with a way to respond, is among the strongest evidence available: if no capable firm objects, the record shows a market given a chance to speak, and if one responds, the agency learns it before the award rather than after.

Price reasonableness without competition

Auditors question this element as often as uniqueness, and it is easier to fix. Usual bases include the published price list compared against the discount offered, the same product's price on a state or cooperative schedule, prices paid by comparable agencies adjusted for quantity and term, the agency's own purchase history, or a cost breakdown of license metric, implementation hours, rates, and support tier. Record the analysis and the conclusion, not just the quote. A sole source award does not mean accepting list price, and the negotiation record is itself evidence.

What weakens a justification

A deadline as the reason. An expiring grant, a fiscal year end, or no time to run a solicitation generally does not create a sole source. Lack of advance planning is a recognized non-reason in most purchasing codes, and saying it invites rejection.
Brand-locked specifications. Requirements copied from one vendor's materials manufacture the uniqueness they claim to prove.
Vendor-drafted justifications. A uniqueness letter written by the firm that benefits is not independent evidence.
Scope that grows. A noncompetitive award expanded by amendment into a full system.
Conclusory language. "The only vendor able to meet our needs," with nothing behind it.

How to start, and what to require in the contract

Write the functional requirement before naming a product, then ask purchasing which authority applies and what approval the amount triggers. Do the research and the price analysis before drafting the memo, so it reports findings rather than defends a decision already made.

In the contract, limit the term, avoid automatic perpetual renewal, cap renewal escalation, require data export in a documented usable format, address ownership of configuration and custom work, secure rights to interfaces and documentation, and reserve the right to compete later phases. Each reduces the chance that today's justified award becomes next cycle's unavoidable one.

HQT works with state and local agencies on software development, integration, and technology advisory work, including the technical documentation behind a procurement record.

Frequently asked questions

What is the difference between a sole source and a single source purchase?

In jurisdictions that separate the terms, a sole source means only one supplier can furnish the product or service at all, while a single source means several suppliers exist but the agency selected one for a documented reason such as standardization or a technical dependency. The evidence burden is usually heavier for a sole source claim, since the agency is asserting that the market has no alternative. Not every purchasing code uses both terms, so check which one your policy recognizes and what approval each requires.

Can a tight deadline or an expiring grant justify a sole source award?

Generally no. Most purchasing codes treat lack of advance planning as an invalid basis for avoiding competition, and stating the deadline as the reason in the memo often draws the rejection directly. If the schedule is genuinely compressed, ask purchasing about abbreviated competitive routes, cooperative contracts, or existing schedules before reaching for a noncompetitive award.

How do we show price reasonableness when we have only one quote?

Use a basis that does not depend on competing offers: the publisher's published price list compared against the discount offered, the same product's price on a state or cooperative schedule, prices paid by comparable agencies adjusted for quantity and term, the agency's own purchase history, or a cost breakdown showing license metric, implementation hours, rates, and support tier. Write down the comparison and the conclusion, not just the quote. Negotiating and recording the result strengthens the file, because a sole source award does not obligate the agency to accept list price.

Is a letter from the manufacturer enough to prove a vendor is the only source?

Only if it actually says so. Many manufacturer letters confirm that a firm is an authorized or preferred reseller, which establishes authorization rather than exclusivity, and the same manufacturer may name several partners in one region. Look for a dated letter that names the specific product and the specific territory and states that no other firm may supply it there, and pair it with the agency's own market research.

Our sole source justification was rejected. What should we fix first?

Start with the uniqueness element, since that is where most rejections originate. Rewrite the requirement in functional terms with no brand names, then attach documents that show the exclusion is technical, legal, or proprietary rather than a matter of preference, such as interface specifications or license terms. Then strengthen the market research record with named firms, dates, and what each said, and add a price reasonableness analysis if the file only contains a quote.