Federal grant procurement for school districts: a 7-step compliance checklist

A purchase funded in whole or in part by a federal award must satisfy more than an ordinary budget check. School districts need to align the transaction with their own written procedures, applicable state and local requirements, the award terms, and the federal procurement standards in 2 CFR Part 200. A cooperative contract may support that process, but it does not replace the district's review.

The most reliable approach is to create the compliance record while the purchase moves through approval. The seven controls below give purchasing, grants, finance, and program staff a shared sequence to follow before an order is issued.

Start by recording the federal award, Assistance Listing number when available, grant period, approved budget category, and the share of the purchase charged to the award. Staff should also confirm whether the grantor or pass-through entity added conditions beyond the Uniform Guidance.

This first step matters because a purchase that looks routine in the operating budget may require a different review when federal dollars are involved. Marking the funding source on the requisition gives every approver the same context and reduces the risk of discovering a grant condition after a commitment has been made.

Section 200.320 separates procurement methods into informal methods for micro-purchases and simplified acquisitions, formal methods using sealed bids or proposals, and limited noncompetitive methods. The district is responsible for documenting the thresholds it uses, and those thresholds must also be permitted by state and local rules.

Do not choose a method from the expected invoice amount alone. Evaluate the aggregate procurement transaction and guard against dividing one requirement into smaller purchases to avoid a more demanding procedure. The requisition should state the method selected, the controlling threshold, and why that method fits the transaction.

Federal rules require procurement transactions under an award to provide full and open competition. Specifications should describe the district's actual performance and technical needs without creating an unnecessary barrier. If a brand name is used because a requirement cannot be described practically in another way, the solicitation should allow an equivalent and identify the essential features that an equivalent must meet.

The competition file should also show the evaluation factors that suppliers were expected to satisfy. Avoid allowing a potential bidder to draft the specifications or statement of work and then compete for the same purchase; the rule treats that participation as an unfair competitive advantage.

When a district plans to use a cooperative contract, reviewers should match the proposed goods or services to the awarded scope, verify that the contract is active, and confirm that the district is eligible to use it. The quote should follow the contract's pricing structure and identify any items, labor, freight, or optional services clearly enough for reviewers to compare them with the award documents.

Keep the cooperative solicitation, evaluation, award, executed contract, amendments, and purchase-specific quote together. That record helps the district demonstrate what competition occurred and whether the resulting order stayed within the awarded scope.

A contract vehicle does not eliminate the need to evaluate the purchase price. For a micro-purchase, Section 200.320 permits an award without competitive quotes when the district considers the price reasonable and keeps support for that conclusion. Simplified acquisitions require price or rate quotations from an adequate number of qualified sources.

For transactions above the district's simplified acquisition threshold, Section 200.324 requires a cost or price analysis, including for contract modifications. The method and depth depend on the facts, but the district must make an independent estimate before receiving bids or proposals. Preserve the estimate, comparisons, analysis, and approval in the purchase file.

The federal rule allows noncompetitive procurement only in specified circumstances: a transaction within the micro-purchase threshold, a true single source, an emergency or public exigency that will not permit delay, written approval from the federal agency or pass-through entity, or inadequate competition after soliciting several sources.

A preferred supplier, an expiring budget, or a tight internal schedule does not create a separate exception. The file should identify the applicable basis, explain the facts, include required approval, and document price reasonableness. If the district relies on an emergency, the record should connect the urgency to the time available for competition.

Before issuing the purchase order, assemble the funding confirmation, procurement-method rationale, solicitation or cooperative documents, quotes, responsibility review, conflict disclosures, cost or price support, award decision, and all required district approvals. The record should make clear who requested the purchase, who reviewed it, who approved it, and which contract governs it.

Retain the file under the federal record-retention rule, the award terms, and any longer state or local requirement that applies. A connected requisition process makes that discipline easier: the documents and approval history travel with the transaction instead of being reconstructed from inboxes during monitoring or audit.

A grant-funded purchase is ready to move when the team can answer each of these questions with a document, not only a verbal assurance.