Sole Source Justification for EdTech: State Rules, the Four Tests, and a Template

Estimated reading time: 11 minutes

Most district staff meet the form before they meet the standard. A purchase is agreed, procurement asks for a justification, and someone writes a paragraph explaining that this is the product the team wants. That paragraph fails. A defensible sole source justification example does something narrower and harder: it establishes that the district’s requirement can be met by one source only, and that the requirement itself was set for programmatic reasons rather than written around a preferred vendor. This guide covers the four tests reviewers apply, what each section of the document has to say, a worked example for an EdTech purchase, and a template districts can reuse.

Executive Summary

A sole source justification is the written record explaining why a purchase was made without competition. What obliges a district to write one is state procurement law and board policy, triggered when a purchase crosses the state competitive bidding threshold: $50,000 in aggregate over twelve months in Texas under Education Code 44.031, $119,100 for 2026 in California under Public Contract Code 20111. Federal rules are a second layer that applies only when federal money pays part of the purchase, and the stricter of the two governs. The document is judged on whether the district established a genuine requirement first and then found only one source able to meet it. Most rejected justifications fail in the reverse direction: they describe a chosen product and work backwards to a requirement only that product satisfies. For K-12 EdTech there is usually a better path than sole source at all, because a cooperative purchase satisfies competition without the paperwork.

Key Takeaways

• A sole source justification documents why only one source can meet a requirement, not why a product was preferred.
• State law is the trigger, not federal rules: $50,000 aggregate in Texas, $119,100 in California for 2026.
• State grounds are often narrower than federal ones. Texas excludes data-processing equipment above $15,000 from the exception entirely.
• Federal rules at 2 CFR 200.320(c) apply only when federal funds are involved, as a second layer.
• Reviewers apply four tests: genuine need, true uniqueness, price reasonableness, and absence of vendor-written specifications.
• “Only one vendor responded” is not sole source. Neither is “the teachers already know it.”
• For most EdTech, a cooperative purchase is cleaner and faster than a sole source claim.
• Districts that template the document cut it from hours to minutes and get more consistent approvals.

What a Sole Source Justification Actually Is

Quick answer: a sole source justification is a written determination that a required good or service is available from only one responsible source, which is why the purchase proceeded without competition. It is a record created for the procurement file and read later by an auditor, not a persuasive memo written for an internal approver.

The distinction that matters is between sole source and single source, and districts use the terms interchangeably at their own risk. A sole source purchase means only one supplier exists that can meet the requirement. A single source purchase means several suppliers could meet it, but the district selected one for a specific, documented reason. Many states and many district policies treat these as different categories with different approval paths. Check which word your own board policy uses before writing anything, because the standard of proof is not the same.

Start With the State Threshold, Not the Federal Rule

Districts routinely reach for the federal framing first, and it is the wrong starting point. Nothing obliges a district to justify a noncompetitive purchase until that purchase crosses the competitive procurement threshold set by state law. Below it, board policy governs and most districts need no formal justification at all.

Quick answer: a district writes a sole source justification because its state statute requires competition above a dollar threshold, not because of federal rules. Check the threshold first, then check whether your state even recognizes a sole source ground. In roughly half the states surveyed below, it does not.

Two conclusions follow, and both matter more than the paperwork.

In seven of these fifteen states there is no general sole source ground to claim. A district in Michigan, Minnesota or Colorado that finds a genuinely unique product cannot write its way to a noncompetitive award, because the statute offers no such route. The workable path there is cooperative purchasing, which satisfies competition rather than avoiding it. Writing a sole source justification in those states is not merely unnecessary, it asserts an authority the district does not have.

In several states technology is exempt from competitive procurement outright. Nevada exempts computer hardware, software and support at any dollar amount. Ohio exempts instructional hardware and software. Illinois exempts data processing and telecom entirely. Florida allows direct negotiation for IT. Minnesota exempts software but not hardware. In those states an educational technology purchase never reaches the sole source question at all, and a district drafting a justification is doing work its own statute does not ask for.

The Texas position is the opposite and deserves particular attention. Education Code 44.031(k) excludes mainframe data-processing equipment and peripherals with a single-item price above $15,000 from the sole source exceptions. A Texas district relying on a sole source claim for technology should confirm with counsel whether that exclusion reaches its purchase. Note also that the Texas threshold rose from $50,000 to $100,000 effective September 2025; TEA’s own procurement handbook has not been updated and still shows the old figure.

State grounds are also frequently narrower than the federal ones, which produces the failure mode districts do not see coming: a purchase can satisfy 2 CFR 200.320(c) and still be unlawful under state law.

The Federal Layer: What 2 CFR Part 200 Adds

When federal money pays for any part of a purchase, the procurement standards in the Uniform Guidance (2 CFR Part 200) apply in addition to state law and local board policy, and the stricter of the two governs. The default is full and open competition. Noncompetitive procurement is an exception permitted only in specific circumstances, which include: the item is available from a single source; a public exigency or emergency will not permit delay; the federal awarding agency or pass-through entity expressly authorizes it; or competition was solicited and found inadequate.

Two consequences follow, and both are routinely missed.

First, the burden of proof sits with the district, not the vendor. A vendor letter asserting that its product is unique is evidence a district may cite, but it is not the determination. The district makes the determination and signs it.

Second, the exception is read narrowly. “We prefer this product” is not one of the four circumstances. “This is the only product our staff has been trained on” is not either, because training is a district choice rather than a market fact.

The Four Tests a Reviewer Applies

Whether the reviewer is a state program monitor, an independent auditor under the Single Audit, or a district’s own internal audit function, the questions are consistent.

Test three is the one districts forget most often. Removing competition does not remove the obligation to establish that the price is reasonable. Acceptable evidence includes published cooperative contract pricing, prices paid by comparable districts, the vendor’s public price list against its state or national contract rate, or a documented negotiation that reduced the initial quote.

What Does Not Qualify, and Why Districts Get This Wrong

1. “Only one vendor responded to our solicitation.” That is a competitive procurement with one responsive bidder, which is a different and generally simpler situation. Document it as such.
2. “Our staff are already trained on it.” Switching costs are real and can support a single source rationale under some policies, but they do not make a product the only one in the market.
3. “It integrates with our student information system.” Usually true of several products. If integration is genuinely a requirement, state the technical requirement and show which products fail it.
4. “The grant named this vendor.” Rare, and if true, cite the grant language directly. Program officers can authorize noncompetitive purchases; district assumptions cannot.
5. “There is no time to run an RFP.” Urgency created by the district’s own planning is not a public exigency. This is the most commonly rejected argument in the K-12 context.

A Worked Sole Source Justification Example

Here is what the substance looks like for an EdTech purchase, in the order a reviewer reads it. The example concerns a district seeking individualized spoken English practice for English Learners, which is a useful case because it shows both a defensible and an indefensible version of the same purchase.

The version that fails

“The district wishes to purchase [Product] for our English Learner program. Our EL Director evaluated several options and found [Product] to be the best fit for our needs. It is well regarded and our teachers are enthusiastic. We request approval to purchase without competitive bidding.”

This fails all four tests at once. It describes a preference, admits alternatives exist, offers no price analysis, and never states a requirement.

The version that holds

A defensible document states the requirement in measurable terms, then demonstrates the market gap.

The honest test to apply before signing: if a competitor read this document, could they credibly write to the superintendent arguing that their product also meets the stated requirement? If yes, the requirement is not written tightly enough or the purchase is not actually sole source.

The Distinction Most Justifications Miss: Unique Vendor Versus Unique Need

Reviewers reject sole source claims because the writer tried to prove the vendor is special. The stronger and more honest argument is usually that the requirement is unusual, and that the market has thinned around it.

Individualized spoken practice is a clean illustration. A district can buy reading software, writing feedback, assessment analytics and lesson generation from many suppliers, because those needs are met by producing or evaluating text, which scales cheaply. Responsive spoken interaction with a single student does not scale the same way, which is why far fewer products attempt it and why staffing cannot substitute. A justification that documents that structural gap, with the district’s own evidence of which suppliers were examined and where each fell short, is arguing about a market rather than praising a brand. That is the argument that survives review.

Before You Write One: Check Whether You Need It At All

A sole source justification is a defensible instrument and also a burdensome one. For most K-12 EdTech purchases there is a shorter path.

Cooperative purchasing satisfies the competition requirement because the cooperative already ran a competitive solicitation on behalf of its members. The Uniform Guidance encourages this explicitly: 2 CFR 200.318(e) directs entities to consider intergovernmental and inter-entity agreements for the procurement of common goods and services. A district buying against a cooperative award is buying against competition that has already occurred, so no sole source claim is needed and no uniqueness has to be proven.

The practical sequence is therefore: check whether the product is on a cooperative you already belong to; if it is, buy that way and write nothing. Reserve the sole source justification for purchases with no cooperative pathway. Details of how the cooperative route works are in our guide to TIPS cooperative purchasing.

Funding Options and What Each One Adds

The last row is worth noticing. If a purchase is paid entirely from local funds, the federal procurement standards do not apply and only board policy governs. Districts sometimes write a full federal-standard justification for a locally funded purchase out of habit, and sometimes apply the local standard to a federally funded one, which is the costly direction of the mistake.

District Benchmark: The Cost of Writing Each One From Scratch

The burden of sole source documentation is invisible because it never appears in a budget line. It appears in director-hours.

A mid-size district processes on the order of thirty to fifty noncompetitive purchases a year across all departments. Reconstructing each justification from a blank page, gathering market research after the fact, and chasing a price comparison typically takes a director or coordinator around three hours. Working from an established template with the four tests as headings, the same document takes about twenty minutes because the thinking is already structured and only the evidence changes.

At forty purchases a year, that difference is roughly 110 director-hours annually, which is close to three working weeks of senior program staff spent formatting rather than deciding. The template is not a convenience. It is the difference between a document written while the reasoning is fresh and one reconstructed months later under audit pressure, which is also why templated justifications survive review more often.

Why the Requirement Is Hard to Write for Speaking

The Speaking Time Gap is the shortfall between the responsive spoken practice an English Learner needs and what one teacher can supply across a full class. It shows up in procurement in a way that catches districts out.

The arithmetic, expressed in purchasing terms. A district that wants to close the gap through staffing must price the alternative honestly, because “could this requirement be met another way” is the first question a reviewer asks. Supplying each of 900 English Learners fifteen minutes of individual spoken practice three times a week is 675 staff-hours per week. At any realistic loaded hourly rate, that is a recurring commitment far beyond what Title III allocations support, and the calculation is worth putting in the file: it converts “we chose a product” into “we compared the requirement against the staffing alternative and documented why the alternative is not available to us.”

That comparison is not a sales argument. It is the market research section doing its job. Reviewers accept a justification more readily when the district shows it priced the obvious non-purchase alternative and recorded the result.

Common Mistakes District Leaders Make

1. Writing the justification after the purchase order. The determination must predate the commitment. A backdated file is worse than a weak one.
2. Naming no alternatives. A document that examines nothing looks like it sought nothing.
3. Skipping price reasonableness because there was no competition to compare against. That is precisely when it is required.
4. Copying vendor language into the requirement, which fails the independence test on inspection.
5. Using sole source when a cooperative award exists, taking on audit exposure for no reason.
6. Applying the federal standard to locally funded purchases, or worse, the reverse.

Recommended Actions

Immediate (this month): Adopt one template for the whole district with the four tests as fixed headings, and require the signature date to precede the purchase order date.

Medium-term (this year): Before any noncompetitive purchase, check the cooperatives the district already belongs to. Most EdTech purchases should never reach a sole source claim.

Long-term (strategy): Keep requirements in program documents such as the Title III plan or LCAP, written before vendor conversations begin. A requirement that predates the market scan is the single strongest fact in any justification.

Questions District Leaders Should Ask

• Does our board policy distinguish sole source from single source, and which are we claiming?
• Was the requirement documented before we spoke to any vendor?
• Which alternatives did we examine, and on which specific requirement did each fail?
• What evidence establishes that the price is reasonable?
• Is this product available on a cooperative we already belong to?
• Does the signature date precede the purchase order date?

Frequently Asked Questions

What does a sole source justification example look like?

A defensible one has six parts in order: the measurable requirement, the market research showing which sources were examined and how each fell short, the specific attribute only one source provides, the evidence that the price is reasonable, the funding source and allowability statement, and a signature dated before the purchase order. A version that opens by naming a preferred product and explaining why staff like it fails on inspection.

Is there a standard sole source justification template?

There is no single national form. Most districts and states publish their own, and the required fields vary. What does not vary is the substance a reviewer looks for, so a template organized around the four tests (need, uniqueness, price reasonableness, independence) will satisfy essentially any local form.

What is the difference between sole source and single source?

Sole source means only one supplier can meet the requirement. Single source means several could, but the district selected one for a documented reason. Many board policies treat them as separate categories with different approval thresholds, so use the term your own policy uses.

Can we use a sole source justification with federal funds?

Yes, within limits. The Uniform Guidance at 2 CFR Part 200 permits noncompetitive procurement in defined circumstances, including when an item is available from only one source. The exception is read narrowly and the district carries the burden of documenting it.

Who signs a sole source justification?

The official with delegated procurement authority, which in most districts is the purchasing director, business official or superintendent depending on the dollar threshold. The requesting program administrator supplies the requirement and market research but is generally not the approving signature.

Do we need a sole source justification if we buy through a cooperative?

No. A cooperative purchase relies on the competition the cooperative already conducted, so there is no noncompetitive determination to justify. You document membership, the vendor’s current award, and that the award category covers what you are buying.

How do we show the price is reasonable without competition?

Acceptable evidence includes cooperative contract pricing for the same product, prices paid by comparable districts, the vendor’s published or state-contract rate, or documentation of a negotiation that reduced the quoted price. Some comparison must be on file; the absence of competition does not remove the obligation.

Related Resources

• TIPS Cooperative Purchasing: How Districts Buy Without an RFP
• Complete Guide to Title III Funding
• What Can Title III Funds Be Used For?
• FERPA and AI: What Districts Must Verify
• Complete Guide to English Learners in U.S. Schools

Conclusion

A sole source justification is a determination, not an argument. It works when the district can show it defined a requirement, searched the market, found one source able to meet it, and satisfied itself the price was fair, in that order and with dates that prove the order. It fails when it starts from a product. For most EdTech purchases the better answer is not to write one at all, because a cooperative award already carries the competition the rule is asking for. Keep the instrument for the purchases that genuinely have no other path, and template it so the reasoning is captured while it is still fresh.

Sources: Uniform Administrative Requirements, 2 CFR Part 200; U.S. Department of Education, Title III, Part A.

When the Market Is Thin, Not the Vendor Special

The justifications that hold up are the ones that describe a market accurately. A district that writes “this vendor is the best” has written an opinion. A district that writes “we required individually responsive spoken practice for every English Learner three times a week, we examined these five suppliers, and these are the specific points at which four of them do not attempt it” has written a finding.

That distinction matters more in speaking than in any other domain, because the constraint is structural. Producing text at scale is cheap, and many suppliers do it. Holding a responsive spoken exchange with one student at a time does not get cheaper with volume, which is why the category is thin and why adding staff is rarely the affordable alternative.

Telo AI sits in that category, and the useful thing for a district writing a justification is not the brand but the shape of the requirement: individual spoken practice, standards-aligned, with per-student evidence a program administrator can put in a file.

See what the requirement looks like in practice: https://mytelo.ai/how-telo-works/

Written that way, the document stops being a hurdle and becomes what the rule intended: a record of a decision a district can still defend three years later, when the person who made it has moved on and only the file remains.