The subaward vs subcontract question is not answered by the title typed at the top of the agreement. Federal rules put the decision — and the liability — on the organization passing the money down. Under 2 CFR 200.331, the pass-through entity must classify every disbursement of federal program funds as either a subaward to a subrecipient or a procurement contract, and the regulation is blunt about how: “the substance of the relationship is more important than the form of the agreement.” With a sweeping rewrite of the federal grants rulebook proposed to take effect October 1, 2026, an undocumented or wrong call is about to get considerably more expensive.

Why the Label on the Agreement Means Nothing

Start with a vocabulary problem that trips up even experienced administrators: the word “subcontract” does not appear anywhere in 2 CFR Part 200, the regulation governing federal grants and cooperative agreements. In the grants regime, the two downstream roles are subrecipient (receiving a subaward) and contractor (receiving a procurement contract — the category regulators called “vendor” before 2014). “Subcontract” is procurement vocabulary that formally belongs to FAR Part 44, which governs what happens beneath a federal contract, not a grant. In everyday usage the terms blur — the NTIA’s own broadband program guide is titled Subrecipient vs. Subcontractor 101 — but the compliance regimes behind them do not.

That is why the label means nothing. Under 2 CFR 200.331, an entity may concurrently hold federal funds as a recipient, a subrecipient, and a contractor across different agreements. The pass-through entity — the organization that received the prime award and is disbursing part of it — must make a case-by-case determination for each agreement. No single factor decides the outcome, characteristics from both categories can be present at once, and the regulation instructs the pass-through to use judgment. The federal agency has no direct legal relationship with your downstream partners; what it monitors is your oversight of them. When a reviewer looks at a mislabeled agreement, the question is never “what did you call it?” It is “what did the entity actually do, and can you show the reasoning behind your classification?”

The Subaward vs Subcontract Test: Six Sorting Questions

The regulation lists five characteristics for each category. Collapsed into practical form, the subaward vs subcontract determination comes down to six sorting questions you can answer for any agreement:

1. Who decides eligibility? If the entity determines who qualifies for assistance under the program, that is a defining subrecipient trait. A contractor serves clients after eligibility has already been decided.
2. What is performance measured against? Subrecipients are measured on whether federal program objectives were met. Contractors are measured against contract deliverables and specifications.
3. Who makes programmatic decisions? Independent judgment about how to accomplish program objectives points to a subaward. Working at the recipient’s direction points to a contract.
4. Do federal award terms flow down? A subrecipient is responsible for adhering to the federal program requirements in the award. A contractor is bound by contract terms, not program compliance.
5. Is the work the program, or ancillary to it? Carrying out a portion of the program for a public purpose is subaward territory. Supplying goods or services the recipient needs for its own performance is procurement.
6. Is this the entity’s normal commercial business? An organization selling similar services to many purchasers in a competitive market looks like a contractor — especially if it was selected through a bid process and earns a margin.

The Department of Transportation’s determination guidance offers a useful shorthand: if you chose the entity because it had the best widgets or service for the price through a competitive process, it is a contractor; if you chose it because it was already delivering services within the program’s guidelines and wants to partner to expand that delivery — perhaps contributing its own match, and typically without profit — it is likely a subrecipient. Hard cases exist. A consulting firm that commercially sells program design services but ends up making eligibility and delivery decisions for your federally funded intervention is functioning as a subrecipient no matter what its marketing materials say. When indicators point both ways, the two questions that control are programmatic decision-making and what performance is measured against.

What Each Classification Costs You After Signing

The determination is not academic — it selects which compliance regime you must run for the life of the agreement.

Classify the entity as a subrecipient and 2 CFR 200.332 hands you a standing job: identify the agreement as a subaward with fourteen required data elements, evaluate the subrecipient’s risk of noncompliance before money moves, monitor its performance, review its reports, and follow up on findings. You must verify whether the subrecipient crossed the Single Audit threshold — $1 million in federal awards expended in its fiscal year under the current rules, a trigger unpacked in our single audit requirements breakdown — and review the results. Transparency reporting stacks on top: subawards of $30,000 or more must be reported under the FFATA framework, now filed through SAM.gov since the FSRS system was retired in 2025. There are budget-math consequences too. Only the first $50,000 of each subaward counts toward your modified total direct cost base when calculating indirect cost recovery, and a subrecipient’s budget should reflect actual costs — profit is not part of the deal.

Classify the entity as a contractor and the obligations shift to procurement standards at 2 CFR 200.317 through 200.327: documented competition, cost or price analysis at the right thresholds, required contract clauses. The entity itself faces no Single Audit exposure through your agreement, and a commercial margin in its price is expected and allowable.

Misclassification is where organizations bleed money. Call a genuine subrecipient a “contractor” and you have skipped required risk assessment and monitoring, failed to flow down award terms, and possibly let the entity dodge a Single Audit it owed. When a federal reviewer or auditor catches it, the standard consequence ladder runs from disallowed costs to formal findings to, in serious cases, repayment of the federal funds. The reverse error — dressing a simple vendor up as a subrecipient — will not usually cost you the award, but it burns administrative hours and imposes compliance burdens on an organization that just sold you a product. Anyone managing federal grants with partners downstream should treat the classification decision as a budget line, not a formality.

The October 1 Rewrite Raises the Price of a Wrong Call

On May 29, 2026, the Office of Management and Budget published a proposed rule in the Federal Register — the Regulation for Federal Financial Assistance — that would rename the Uniform Guidance the “Uniform Grants Regulation” and give it direct regulatory effect. Analysts at BDO call it one of the most significant reconsiderations of federal grants administration since the framework was created. The comment period closed July 13, 2026, and OMB is targeting an effective date of October 1, 2026. Three proposed changes land directly on the subaward-versus-contract decision.

First, fixed-amount subawards would be eliminated. That instrument has been the pragmatic middle ground for small partner agreements — a defined payment for defined milestones without line-item cost tracking. Remove it, and nearly every subaward defaults to the cost-reimbursement model, with the cash-flow and documentation burdens we detailed in our piece on how cost reimbursement grants actually pay. Second, SAM.gov subaward reporting would expand, with pass-through entities required to confirm in performance reports that their reported subaward records match executed agreements — turning a back-office filing task into a recurring certification. Third, the pass-through duties in 200.332 would tighten, with risk assessments documented in a form that can be produced on request and monitoring activity recorded against defined schedules. We mapped the broader proposal in our rundown of the October 1 federal grant rules rewrite. The direction of travel is unmistakable: every subaward becomes more visible to regulators, which means every classification decision becomes more testable.

How to Write a Determination That Survives an Audit

The protection is a determination memo — short, dated, and written before the proposal budget locks. For each downstream agreement, record your answers to the six sorting questions, note any indicators that point the other way, and state which factors controlled your conclusion. Where the call is close, say so, and anchor the decision in the two controlling questions: does the entity make decisions about how program objectives are achieved, and is its performance measured against program goals rather than a commercial deliverable? A paragraph per question is plenty. What auditors want, years later, is evidence that a reasonable judgment was made at the time — not a perfect one.

Three habits keep the memo honest. Classify per agreement, not per organization: the same university can be your subrecipient on one award and your contractor on another, and each file needs its own determination. Revisit the classification when an amendment changes the scope — a vendor relationship that quietly absorbs programmatic decision-making has become a subaward whether or not the paperwork noticed. And keep the memo with the award file alongside the budget justification, because the classification drives both the compliance plan and the indirect-cost math. Organizations building partner-heavy proposals — common across nonprofit grant programs — should make the memo a standard proposal-stage artifact rather than a post-award scramble.

Frequently Asked Questions

Is “subcontract” the wrong word under a federal grant?

Q: Is “subcontract” the wrong word under a federal grant?
A: Technically, yes. The term “subcontract” belongs to FAR Part 44, which governs work performed beneath federal procurement contracts. Under a grant or cooperative agreement, 2 CFR 200 recognizes only subrecipients and contractors. The usage persists out of habit — some university offices are still named “Subcontracts Office” — but calling a subaward a subcontract can create real confusion about which compliance regime applies, and it will not change how an auditor classifies the relationship.

Does the dollar amount decide subaward vs subcontract?

Q: Does the dollar amount decide subaward vs subcontract?
A: No. 2 CFR 200.331 contains no dollar-value factor — classification turns entirely on the substance of the relationship. The dollar thresholds you hear about serve other purposes: $30,000 triggers FFATA subaward reporting through SAM.gov, only the first $50,000 of each subaward counts toward your modified total direct cost base, and $1 million in federal awards expended triggers a subrecipient’s Single Audit. None of those figures makes an agreement a subaward or a contract.

Can the same organization be both a subrecipient and a contractor?

Q: Can the same organization be both a subrecipient and a contractor?
A: Yes. The regulation expressly contemplates that an entity may concurrently receive federal funds as a recipient, a subrecipient, and a contractor. The determination is made agreement by agreement, not organization by organization. A community health nonprofit might be your subrecipient for program delivery under one award and a straightforward contractor providing translation services under another — each agreement gets its own documented determination.

Who is liable if a subrecipient is misclassified as a contractor?

Q: Who is liable if a subrecipient is misclassified as a contractor?
A: The pass-through entity. Classification is your determination to make and to document, and the consequences of getting it wrong — skipped monitoring, missing flow-down terms, a bypassed Single Audit — land in your findings, not the partner’s. Typical outcomes include disallowed costs and mandatory corrective action, and in serious cases repayment of federal funds. A written determination memo prepared at signing is the strongest evidence that your judgment was reasonable.

Bottom Line: Classify Before the Budget Locks

The subaward vs subcontract call is the rare compliance decision that is entirely within your control. The regulation hands pass-through entities the judgment, the factors, and the responsibility — and from October 1, 2026, if the proposed Uniform Grants Regulation takes effect on schedule, it also hands them expanded reporting duties and fewer instruments to soften the load. The organizations that will absorb the change cheaply are the ones whose award files already contain a dated determination memo for every downstream agreement.

Do two things this quarter. First, inventory your current agreements and confirm each one has a written classification with reasoning — re-paper the ones that do not before the new rules arrive. Second, make the six-question memo a standard step in proposal development, so the classification, the monitoring budget, and the indirect-cost math are settled before signatures. If your team is structuring partner budgets or needs a second set of eyes on a determination that could swing your compliance burden, OpenGrants’ grant writing services can pressure-test the classification and the budget behind it before you commit.