A school district chooses a vendor for a federally funded service and is ready to issue the purchase order. The bid file shows a fair price and proper approvals, but no one has documented whether the proposed contractor is excluded from federal awards. That missing check can turn an otherwise sound procurement into a grant-compliance problem. The business office needs to identify when a contract is a covered transaction, verify the party’s eligibility before award, and keep evidence that another reviewer can reproduce.
This guide addresses U.S. K–12 districts that spend federal grant funds directly or through a state education agency. The starting rule is 2 CFR 200.214, which applies the governmentwide nonprocurement suspension and debarment system to recipients and subrecipients. The detailed transaction and verification rules are in 2 CFR part 180. Award terms, federal agency rules, and state or local purchasing policies may require additional steps, so keep those documents with the procurement file.
First decide whether the planned contract is covered
Do not treat every purchase order, every grant subaward, and every federal direct contract as the same transaction. For district goods and services contracts awarded under a covered nonprocurement federal award, 2 CFR 180.220 generally makes a contract covered when its expected amount is at least $25,000. A contract that needs the consent of a federal agency official is covered regardless of amount, as is a contract for federally required audit services. The regulation also describes when certain lower-tier subcontracts are covered. Review the actual award chain and contract value; do not assume that a district’s micro-purchase or bidding threshold is the debarment threshold.
Record the federal award, assistance listing or grant identifier, pass-through agency, funding source, expected full contract amount, and why the transaction falls inside or outside the covered category. If a contemplated arrangement gives another organization programmatic responsibility rather than simply buying its services, it may be a subaward and needs a different classification analysis. Our subrecipient-versus-contractor guide explains that decision. This article focuses on vendor contracts after that classification is made.
The $25,000 rule should not become a loophole in the district’s controls. A lower-value purchase can still be covered under the federal-consent or audit-service provisions, and grant conditions or local policy can require screening more broadly. Conversely, a vendor’s lack of a public SAM entity registration is not, by itself, proof of an exclusion. SAM.gov displays entity registrations and exclusions as different record types; the compliance question here is whether the intended party is excluded or disqualified from this transaction.
Choose a permitted verification method before award
For a covered lower-tier transaction, 2 CFR 180.300 requires the district to verify that the intended party is not excluded or disqualified. It permits three methods: checking SAM.gov Exclusions, obtaining the party’s certification, or adding an appropriate clause or condition to the covered transaction. The federal rule does not say that a SAM search is the only acceptable method. A specific agency, pass-through award, or district policy may require a particular method or extra evidence; follow the stricter applicable requirement.
A documented SAM search is often the easiest way for a reviewer to see what was checked at the time of award. Search the Exclusions area of SAM.gov using the vendor’s exact legal name and, when available, its Unique Entity ID or other reliable identifier. Save the date and time, search terms, results, and the legal name on the proposed contract. If the vendor operates under a trade name, obtain the contracting entity’s legal identity before clearing the file. A screenshot of a generic entity-registration page does not show the same thing as an exclusion search.
A same-name result is a lead to investigate, not automatic proof that the bidder is excluded. Compare identifiers, address, exclusion status, and the named party. SAM.gov’s exclusion-record guidance says similar names can belong to different parties and points users to the excluding agency for confirmation of a potential match. Hold the award while procurement and grants staff resolve a genuine ambiguity; retain the resolution in the file.
Work a $38,000 school-district example
Assume a district receives a covered federal education grant through its state education agency and plans a $38,000 contract for after-school tutoring services. The approved budget allocates 60% of the contract, or $22,800, to the federal grant and the remaining $15,200 to local funds. For the 2 CFR 180.220 contract test, the expected contract amount is $38,000; looking only at the $22,800 federal charge would misclassify the transaction. On these facts the contract exceeds the $25,000 covered-transaction threshold.
The buyer completes the normal competition and responsibility review, then identifies the selected company’s exact legal name from its bid and draft agreement. Before signing or issuing the award, the grants reviewer checks SAM.gov Exclusions using that name and its available identifier, records a dated no-match result, and signs the district’s eligibility checklist. The contracting officer then places the search record, bid evaluation, award approval, purchase order, and applicable flow-down language together. The $22,800 federal and $15,200 local funding split is documented separately in the accounting distribution. A clean exclusion search does not replace the bid analysis, price reasonableness, conflict-of-interest review, or grant allowability test.
Suppose the search instead returns a similar name with a different Unique Entity ID and address. The reviewer does not delete the hit or reject the bidder without investigation. They compare the record with the contractor’s legal documents, seek clarification from the excluding agency if needed, and document why the hit is or is not the same party. If the proposed party really is excluded, 2 CFR 180.305 generally bars the covered transaction unless the responsible federal agency grants an exception under the regulation. Escalate that issue before award; a local manager’s approval alone is not the federal exception.
Carry the control through contract changes
Debarment review is a pre-award gate, but the file cannot be forgotten after signature. Before a renewal, extension, or material change, procurement should revisit the award terms, expected amount, and current eligibility evidence. 2 CFR 180.310 treats an already-existing transaction differently from a new renewal or extension when a party is later excluded: an existing covered transaction may continue after a careful review, but renewal or extension generally cannot proceed without a federal exception, other than a no-cost time extension. Do not automatically cancel a live contract or automatically renew it; involve the grant officer and counsel.
For covered lower-tier work, 2 CFR 180.330 requires passing the subpart’s compliance condition to the next-tier participant and requiring that participant to pass it further down when applicable. Put this obligation in the contract file and make the vendor understand it. The district should also have a process to route notice of a later exclusion or an ownership/name change to grants and procurement rather than leaving the information in one employee’s inbox.
Keep this control alongside the ordinary procurement process. Our school purchasing overview covers method selection and approvals, while the sole-source grant-purchase guide addresses documenting the narrow noncompetitive exception. Eligibility screening is a separate gate even when a purchase has been competitively bid or a single-source justification is valid.
Design a reviewable district control
Build the gate into the procurement system before a grant-funded purchase order or contract can be released. The requisitioner identifies federal funding and attaches the grant code. Procurement classifies the transaction and records the expected full contract amount. The grants reviewer performs the required eligibility verification using the method allowed by the award and records the evidence. A second approver checks that the legal name, search date, amount, and contract all match before signature. If the vendor is changed after bidding, repeat the eligibility review for the actual awardee.
Maintain a compact checklist with the award identifier, vendor legal name, identifier used, contract value, covered-transaction rationale, verification method, result, reviewer, date, and any escalated hit. Save the underlying dated search output, certification, or executed clause—not just a checked box. For renewals and amendments, link the new review to the original file. Periodically sample purchase orders charged to federal grants to find covered contracts that bypassed the gate. This makes the control useful to both the grants manager and an auditor.
Common mistakes and a pre-award checklist
- Testing only the federal share. For the 2 CFR 180.220 amount test, use the expected contract amount under the covered award.
- Treating all small purchases as exempt. Federal-consent and federally required audit contracts can be covered regardless of amount; other requirements may be broader.
- Confusing registration with exclusions. Search the right SAM record type and match the legal contracting party.
- Declaring a same-name hit conclusive. Check identifiers and contact the excluding agency when a potential match cannot be resolved.
- Assuming a clean search proves the whole procurement compliant. Maintain the separate competition, price, conflict, and allowability records.
- Forgetting changes and lower tiers. Reassess renewals and pass down the covered-transaction condition as required.
- Identify the federal award and whether the arrangement is a contract or subaward.
- Apply 2 CFR 180.220 and any stricter agency, pass-through, state, or district rule.
- Confirm the selected vendor’s exact legal name and reliable identifier.
- Use the required or chosen 2 CFR 180.300 verification method before award.
- Resolve possible matches and stop an excluded-party award absent a proper federal exception.
- Save dated evidence, signoff, contract terms, and lower-tier flow-down language.
- Recheck the decision at renewal, extension, or other relevant change.
A good debarment control is brief but timed correctly: classify the transaction, verify the actual awardee, resolve any hit, and retain the evidence before committing grant funds. That sequence protects the district without confusing vendor eligibility with the many other procurement decisions it must also document.