A school district may know exactly which product it wants for a federally funded project. That preference does not, by itself, establish that only one supplier can meet the requirement. Before issuing a purchase order without competition, the business office needs to identify a permitted federal exception, test the market, explain the price, and preserve the decision.
This guide addresses single-source procurement under 2 CFR 200.320(c)(2) for a U.S. public K–12 district spending a federal award. It is a transaction-level workflow, not a substitute for the district’s written procedures, state purchasing law, grant terms, or pass-through agency conditions. Those may require a competitive process or approvals even when a federal exception is available.
Start with the actual purchasing requirement
Define the function the grant project needs before naming a product or vendor. An IT request might require a device to exchange specified data securely with an existing system by a particular date. It should distinguish indispensable technical features from convenient preferences. Record the project, federal award, estimated total transaction value, proposed contract period, and any options or related purchases. This makes the decision reviewable against the procurement methods in 2 CFR 200.320 and the district’s own thresholds.
Check the applicable state and local rules and the federal award before selecting a method. The federal regulation allows recipients and subrecipients to set lower thresholds for informal purchasing. State law may add advertising, board approval, or emergency procedures. An award or pass-through entity may add conditions. A purchase should not be divided into smaller orders to make it appear eligible for a less demanding method; assess the aggregate procurement transaction.
If ordinary competition can meet the need, use it. For example, multiple authorized resellers may offer the same proprietary item, or a functionally equivalent product may satisfy the documented requirements. A limited manufacturer list is not proof that only one contractor can fulfill the transaction. The competition rule in 2 CFR 200.319 identifies unnecessary qualifications, organizational conflicts, and brand-only specifications as potential restrictions. It allows a carefully defined “brand name or equivalent” description when the required features are stated.
Identify the correct noncompetitive exception
2 CFR 200.320(c) permits a noncompetitive method only in five listed circumstances: a transaction at or below the applicable micro-purchase threshold; a requirement that only one source can fulfill; a public exigency or emergency that cannot tolerate delay for public notice; a written request followed by written federal agency or pass-through approval; or inadequate competition after several sources have been solicited. The first circumstance also has micro-purchase price-reasonableness documentation requirements in paragraph (a)(1).
Do not label all five paths “sole source.” An urgent project is not automatically single source, and a vendor’s claim of exclusivity is not a written agency approval. State which specific paragraph supports the method and explain the facts that meet it. For a true single-source purchase under paragraph (c)(2), the key question is whether this transaction, with its necessary requirements, can only be fulfilled by one source. If the evidence shows several capable sellers, use a competitive method unless another permitted exception independently applies.
Evidence that makes a single-source claim testable
A one-page memo can summarize the decision, but it needs attachments. Ask the requesting department to describe the technical requirement and why substitutes do not work. Procurement staff should independently look for compatible products and authorized sellers, record the search terms, dates, suppliers contacted, and responses, and retain relevant specifications. A manufacturer letter may help establish distribution rights or compatibility; it does not replace the district’s own market check. If the conclusion depends on a product’s integration with an existing system, document the interface or licensing constraint rather than merely saying “standardization.”
Write down why a reasonable alternative would fail, what it would cost or delay to make it work, and whether the requirement could be competitively described as performance specifications. A preferred relationship, incumbent convenience, or an employee’s familiarity with a product is weak evidence of a single source. The reviewer should be able to see both the options considered and the reason they were rejected.
Build the price basis before the order
Even when competition is excused, the district still needs a defensible price. 2 CFR 200.318(i) requires procurement records to include the basis for the contract price. A useful file can compare the quoted price with a current catalog or published schedule, recent comparable purchases, an independent estimate, component costs, or a documented negotiation. Adjust comparisons for installation, maintenance, quantity, term, and scope. Note any material differences instead of presenting unlike numbers as equal.
For a procurement transaction, including a modification, in excess of the simplified acquisition threshold, 2 CFR 200.324(a) requires a cost or price analysis and an independent estimate before bids or proposals are received. The method and depth depend on the transaction. Below that threshold, the separate record-of-price-basis requirement still applies. The regulation also prohibits cost-plus-a-percentage-of-cost and percentage-of-construction-cost contracting methods. Check the applicable threshold and current district policy at the time of the purchase; do not copy a dollar limit from an old template.
A hypothetical $48,000 technology purchase
Suppose a district plans to buy a specialized $48,000 interface module for a grant-funded student support system. The program manager says only the current system manufacturer can provide the module. Procurement first documents the required data exchange and asks whether an open interface or another compatible module would work. It finds two resellers advertising the manufacturer’s module. In that case, the claim that the transaction has only one source is not established merely because the product has one manufacturer. The district can seek quotations from the resellers under the appropriate competitive procedure.
Now assume the manufacturer confirms in writing that it sells and installs the licensed interface directly, no reseller may provide the required installation, and the district’s documented technical review finds no compatible equivalent. Procurement records that market check, the vendor’s written terms, and a $45,000 independent estimate based on comparable functionality and labor. It asks the vendor to explain the $3,000 difference and negotiates a $46,500 fixed price with installation included. The file would show the original $48,000 quote, the estimate, the explanation, the revised $46,500 offer, and the approver’s conclusion. Those facts could support a single-source rationale if the district’s reviewer confirms the exception and all other applicable rules. The numbers and market outcome are illustrative, not a finding about any actual vendor.
Approve the decision before commitment
Route the file through the district’s required procurement, grants, legal, and board approvals before issuing a purchase order or signing a contract. The approver should verify the exception citation, market evidence, grant allowability and budget, price basis, and contract terms. 2 CFR 200.318(a), (c), and (h) also require documented procedures, written conflict-of-interest standards, and award to a responsible contractor. A staff member or board member with a real or apparent conflict must not participate in selection, award, or administration of the federally supported contract.
Where the district relies on 2 CFR 200.320(c)(4), preserve both the district’s written request and the federal agency’s or pass-through entity’s written approval. Do not assume that written approval is a universal federal precondition for every other paragraph (c) exception; review the award and local rules for any additional approval requirement. Record who authorized the actual purchase, the date, and the version of the quote or contract approved.
After award, tie the purchase order and contract to the approved memo. Confirm that delivery, installation, and invoicing match the agreed scope. The district’s three-way matching process can support payment review, while the broader internal-control process addresses separation of duties and exception monitoring. The purchase file should remain linked to the grant ledger entry so a reviewer can trace the charge from approval through payment.
Keep one audit-ready procurement history
The minimum history named in 2 CFR 200.318(i) covers the rationale for the method, contract type, contractor selection or rejection, and price basis. A practical electronic folder should also contain the requirement and independent estimate, market searches and vendor responses, the exception memo, any required written agency approval, conflict review, signed contract or order, receiving evidence, invoices, and change orders. Index it by grant and purchase order rather than scattering the pieces across personal email accounts.
Apply the retention clock carefully. Under 2 CFR 200.334, federal award records generally must be kept for three years from submission of the final financial report, with different starting points for awards renewed quarterly or annually and specified exceptions, including unresolved audit findings or litigation. State law and district policy may require longer retention. Keep contract amendments with the original file; a later increase in scope may require its own procurement and price review.
Common mistakes and a closeout checklist
- “We already use this brand.” Test whether equivalent products or multiple sellers can meet the actual requirement.
- “The project is urgent.” Document the emergency facts and the delay a solicitation would cause; do not mislabel urgency as proof of one source.
- “The vendor set the price.” Retain an independent basis, comparison, or negotiation record.
- “The grant manager approved it verbally.” Preserve the approvals required by the district, award, and applicable paragraph of the regulation.
- “The invoice is the entire file.” An invoice cannot show why competition was omitted or how the price was judged.
- Define the grant-funded need, total transaction value, and applicable federal, state, local, and award rules.
- Check whether a competitive specification and qualified sources are available.
- If not, identify the exact 2 CFR 200.320(c) exception and collect dated evidence for it.
- Document price reasonableness and perform the required cost or price analysis when the threshold is exceeded.
- Check conflicts, vendor responsibility, budget, and grant eligibility; obtain required approvals before commitment.
- Link the memo, order, contract, receipt, invoice, amendments, and payment to the grant record.
- Retain the file for the applicable federal and state period and review exceptions periodically.
A defensible single-source file explains why one supplier was necessary for a defined grant purchase and why the agreed price was reasonable. It gives the next reviewer enough evidence to reconstruct the decision without relying on the requester’s memory. For the wider purchasing cycle, see InsightCleanHub’s K–12 procurement overview; apply the current regulations and the district’s own policy to the particular award.