Subaward vs. Subcontract: Choosing the Right Mechanism and Getting Budget Approval

Every multi-institutional grant proposal faces the same question before the budget spreadsheet is complete: does the partner organization receive a subaward or a subcontract? The answer determines how much indirect cost your institution can charge, what compliance obligations the partner must meet, whether the work counts toward your scope of work, and how the sponsoring agency evaluates the arrangement during review. Get it wrong and you face audit findings, budget disallowances, and the kind of post-award headaches that turn a successful grant into an administrative burden that outlasts the research.

The distinction is not intuitive. The two terms are used interchangeably in hallway conversations, on institutional websites, and sometimes even in agency guidance documents that should know better. But under the Uniform Guidance -- 2 CFR Part 200, the federal regulation that governs all federal awards -- they are legally distinct mechanisms with different definitions, different compliance requirements, and different financial consequences.

What 2 CFR 200 Actually Says

The Uniform Guidance draws a bright line between subawards and contracts (which in grant-speak become subcontracts when issued under a federal award). The definitions appear in 2 CFR 200.1, and the classification criteria in 2 CFR 200.331. The distinction turns on the nature of the relationship, not the dollar amount or the paperwork.

A subaward is an award provided by a pass-through entity to a subrecipient to carry out part of a federal award. The subrecipient has programmatic decision-making responsibility. They help design the work, they contribute intellectual leadership, they share in the objectives of the federal award. Their contribution is substantive and collaborative. In NIH terms, the subrecipient's PI is typically a co-investigator or key personnel on the application. In NSF terms, the subawardee is carrying out a portion of the scope of work described in the project description.

A subcontract (formally, a contract under a federal award) is an agreement for goods or services needed to carry out the project. The contractor provides a commercially available product or service. They do not have programmatic decision-making responsibility. They deliver a defined output -- sequencing services, survey administration, equipment fabrication, statistical analysis -- and their engagement ends when that output is delivered. They do not co-author publications. They do not attend investigator meetings to shape the direction of the research.

The critical phrase in the regulation is that the determination must reflect the substance of the relationship rather than the form of the agreement. A pass-through entity can call something a "subcontract" all day long, but if the other party is making programmatic decisions and its performance is measured against federal award objectives, the Uniform Guidance treats it as a subaward -- with all the compliance obligations that entails.

The Decision Framework: Five Questions That Determine the Answer

Grants offices use a checklist approach, but the underlying logic reduces to five questions. If most answers point toward "subaward," the mechanism is a subaward. If most point toward "subcontract," it is a contract. Mixed answers require judgment, documentation, and sometimes a conversation with the program officer.

1. Does the partner have programmatic decision-making responsibility?

This is the single most important factor. If the partner institution's PI is designing experiments, interpreting data, adjusting the research plan based on findings, and contributing to publications, that is a subrecipient relationship. If the partner is executing a defined protocol or delivering a specified product, that is a contractor relationship.

2. Is the partner's work a substantive portion of the project's scope?

A collaborating laboratory running a parallel aim of an R01 is performing a substantive portion of the scope. A company providing genotyping services on 500 samples at $12 per sample is providing a commercial service. The former is a subaward; the latter is a subcontract.

3. Does the partner bear responsibility for meeting federal award objectives?

Subrecipients share in the programmatic objectives and are accountable for using funds in accordance with federal requirements. Contractors are accountable for delivering the goods or services specified in the contract.

4. Does the partner determine who is eligible to receive the service?

This question, drawn directly from 2 CFR 200.331, helps distinguish entities that are carrying out a federal program from those providing commercial services. It primarily applies to social service and public health grants where eligibility determination is a core function.

5. Is the service commercially available from multiple sources?

If you could reasonably obtain the same service from several vendors through a competitive procurement process, the relationship is more likely a contract. If the collaboration depends on the specific expertise, facilities, or intellectual contribution of the partner institution, it is more likely a subaward.

The Uniform Guidance explicitly states that the substance of the relationship -- not its form -- determines classification. An institution cannot label a subaward as a contract simply to avoid the compliance burdens of the subrecipient monitoring requirements, nor can it label a contract as a subaward to shift audit responsibilities.

The MTDC Threshold: How Classification Affects Indirect Costs

Here is where the financial consequences become concrete. Under most federally negotiated indirect cost rate agreements, the pass-through entity (the prime awardee) can charge its full indirect cost rate on only a limited portion of each subaward issued under a federal award. The 2024 revision to the Uniform Guidance raised this threshold from $25,000 to $50,000 per subaward, though individual institutions cannot implement the new limit until it is reflected in their Negotiated Indirect Cost Rate Agreement (NICRA). Many institutions are still operating under the legacy $25,000 cap.

Here is what that means in dollars. If your institution's negotiated F&A rate is 55% and you have a $300,000 subaward, you recover indirect costs on only the first $25,000 (or $50,000, depending on your NICRA) -- yielding $13,750 to $27,500 in F&A. The remaining balance passes through without generating any indirect cost recovery for your institution.

Subcontracts, by contrast, are generally included in the Modified Total Direct Cost (MTDC) base in their entirety unless the institution's rate agreement specifically excludes them. A $300,000 contract for analytical services could generate $165,000 in indirect cost recovery at a 55% rate.

The institutional incentive is obvious: classify collaborative arrangements as contracts rather than subawards to inflate indirect cost recovery. It is also one of the most closely scrutinized aspects of federal grant budgets during both pre-award review and post-award audit. The Office of Inspector General at HHS, NSF, and other agencies has issued findings against institutions that misclassified subawards as contracts for exactly this reason. The consequences include repayment of disallowed costs, enhanced monitoring, and damage to the institution's reputation with the cognizant federal agency.

One timing note worth repeating: the MTDC subaward threshold applies per subaward per budget period, not as a lifetime cap. A five-year grant with a subaward that appears in each year's budget generates threshold-eligible MTDC costs per year -- so the cumulative indirect cost recovery over the project period is higher than a single year's threshold suggests.

Compliance Requirements by Mechanism

The compliance obligations attached to each mechanism are substantially different, and they fall primarily on the pass-through entity -- the institution that issues the subaward or subcontract.

For subawards, the pass-through entity must:

• Assess the subrecipient's risk of noncompliance (2 CFR 200.332(b)), including reviewing the subrecipient's audit history, evaluating their financial systems, and considering their prior experience with federal awards.
• Include specific federal award information in the subaward agreement: the CFDA number, federal award identification number (FAIN), award date, indirect cost rate information, and all applicable compliance requirements.
• Monitor the subrecipient's use of funds throughout the project period, including reviewing financial reports, verifying that costs are allowable, and confirming that the work is progressing according to the scope.
• Verify that subrecipients expending $750,000 or more in federal awards during their fiscal year have obtained a Single Audit in accordance with 2 CFR 200 Subpart F.
• Consider imposing specific subaward conditions if the risk assessment identifies concerns -- such as requiring more frequent reporting, limiting the subrecipient's authority to make budget transfers, or requiring prior approval for certain cost categories.

For subcontracts, the compliance framework is simpler. The pass-through entity must follow its own procurement standards (2 CFR 200.317-327), which typically means:

• Conducting the procurement in accordance with institutional policies (full and open competition for amounts above the simplified acquisition threshold, currently $250,000).
• Documenting the basis for contractor selection and the reasonableness of the price.
• Including required federal provisions in the contract (access to records, compliance with applicable regulations).
• Managing the contract to ensure deliverables are received and payment is appropriate.

The monitoring burden for subcontracts is lighter because the contractor is not a recipient of federal funds in the regulatory sense -- they are a vendor providing goods or services. They are not subject to Single Audit requirements based on the subcontract alone, though they may have their own federal awards that trigger audit requirements independently.

Five Misclassifications That Trigger Audit Findings

Misclassification is not hypothetical. It is one of the most common findings in federal grant audits, and it runs in both directions.

1. Calling a subrecipient a contractor to maximize F&A recovery. This is the most frequent and most consequential error. The collaborating institution is doing substantive programmatic work, but the pass-through entity classifies it as procurement to capture full indirect costs on the entire amount. Auditors test for this by examining the scope of work -- if it reads like a research plan rather than a purchase order, the classification is wrong. The marker they look for is straightforward: if the "contractor" has a PI listed as key personnel on the federal award, co-authors publications, or participates in investigator meetings, the arrangement is functionally a subaward regardless of what the paperwork calls it.

2. Calling a contractor a subrecipient to avoid procurement requirements. Less common but it creates its own problems. If the "subrecipient" is providing a standard commercial service, the pass-through entity has circumvented its own procurement standards. The institution should have competed the work or documented a sole-source justification. Audit findings for this error typically focus on procurement noncompliance rather than cost disallowance.

3. Using the same classification for every external partner. Some institutions default every outgoing agreement to one type -- usually subcontract -- regardless of the substance. This blanket approach guarantees misclassification in at least some cases and signals to auditors that no case-by-case analysis was performed.

4. Failing to reassess when the relationship changes. A vendor hired to provide routine testing services may evolve into a collaborator making programmatic decisions as the project matures. The classification should change when the substance does. Most institutions do not have a process for mid-award reclassification, which means the original determination persists even when it no longer reflects reality.

5. Relying on the partner's entity type as a proxy. The fact that a partner is a university does not make it a subrecipient, and the fact that a partner is a for-profit company does not make it a contractor. A commercial lab conducting original research under your award is a subrecipient. A university core facility providing routine analytical services at published rates is a contractor. Entity type is irrelevant; the work determines the classification.

How to Present Subawards and Subcontracts in Your Budget

The budget presentation differs by mechanism, and getting the format right signals competence to reviewers.

Subawards should be presented as a separate budget category, typically Line F.5 (Other Direct Costs -- Subawards/Consortium) on the SF-424(R&R) budget form or the equivalent line on the PHS 398 modular budget. Each subaward over $100,000 in total costs requires a separate detailed budget and budget justification from the subrecipient institution. The subrecipient's budget includes their own indirect costs calculated at their own negotiated rate. Your institution then includes the total subaward amount in your budget, with the first $25,000 (or $50,000) entering the MTDC base and the remainder excluded.

The budget justification for a subaward should explain three things: why this specific institution and investigator are essential to the project, what portion of the scope of work they will perform, and why the work cannot be performed at the prime institution. Reviewers want to see that the collaboration is scientifically justified, not just administratively convenient.

For modular NIH budgets (under $250,000 direct costs per year), you still need a consortium justification on the PHS 398 Modular Budget form. The justification should name the subrecipient institution, identify the sub-PI, describe their scope of work, and state the consortium's direct and F&A costs separately.

Subcontracts appear in the budget as consultant costs or other direct costs, depending on the nature of the service. They are presented with a description of the service, the basis for the cost estimate (vendor quote, catalog price, prior experience), and documentation of how the contractor was or will be selected. The full amount enters the MTDC base unless the institution's rate agreement specifies otherwise.

For NSF proposals, subaward budgets appear as a separate line in the prime budget with a budget justification of no more than three pages per subaward. NSF requires a statement of work, a detailed budget from the subrecipient, and a letter of commitment. The sub's budget justification counts against its own three-page limit, not the prime's.

For proposals with both subawards and subcontracts, clarity in the budget justification is essential. Explicitly state the mechanism for each external arrangement, explain why that mechanism was chosen, and ensure the indirect cost calculation reflects the correct treatment.

When the Line Gets Blurry

Some arrangements genuinely fall in a gray area. A biostatistics core at a partner university that will analyze your data using methods they helped develop for your project -- is that a service or a collaboration? A small business fabricating a custom instrument to your specifications and then helping optimize its performance in your laboratory -- vendor or collaborator?

In ambiguous cases, three strategies reduce risk:

Consult your sponsored programs office early. The determination should be made at the proposal stage, not after the award. Reclassifying a subaward as a contract (or vice versa) after the award has been issued requires agency approval, budget revisions, and explanations that nobody wants to write.

Document the analysis. Complete a determination form that addresses each factor in 2 CFR 200.331 and explain why the balance of factors supports your classification. If the case is genuinely close, say so -- and explain why you resolved it in the direction you did. The documentation itself can be the difference between a clean audit and a finding.

Ask the program officer. For federal awards, the program officer can provide guidance on how the agency expects the arrangement to be classified. This is particularly useful for large or unusual collaborations where the answer is not obvious. Getting the agency's view at the proposal stage avoids reclassification surprises during the Just-in-Time process or, worse, during a desk review three years into the award.

The subaward-versus-subcontract determination is one of those administrative decisions that reverberates through every stage of a grant -- from the proposal budget to the annual progress report to the final closeout. Getting it right at the beginning saves time, money, and audit exposure for every institution involved. For teams assembling multi-institutional proposals, tools like Granted can help structure budgets and justifications so that the classification is clear, the indirect cost math is correct, and the narrative aligns with the numbers from the first draft forward.