What Is a Subaward? Federal Grant Subawards Guide

This guide is for: Grant managers, finance directors, sponsored programs staff, and nonprofit leaders deciding whether a partner agreement is a subaward, a procurement contract, or a simpler referral relationship.

Full answer: What is a subaward? It is an award of federal grant funds from a pass-through entity, often called the prime recipient, to a subrecipient that carries out part of the funded project's work. Use 3 steps: classify the relationship under 2 CFR 200.331, write the required subaward terms, and monitor the subrecipient under 2 CFR 200.332. Defined in 2 CFR 200.1, subawards are distinct from procurement contracts.

If you're a grant manager setting up partnerships under a federal award, this guide explains what subawards are, how they differ from contracts, and what compliance rules apply.

What Is a Subaward in Federal Grants? Complete Guide (2026)

Data note: Subaward rules were checked on June 18, 2026 against 2 CFR 200.1, 2 CFR 200.331, 2 CFR 200.332, 2 CFR 200.414, SAM.gov subaward reporting guidance, NIH subaward policy, OJP subaward guidance, and Federal Audit Clearinghouse materials.

If your organization receives a federal grant and passes some of that funding to another organization to carry out part of the project, you've issued a subaward. That makes you a pass-through entity with a specific set of monitoring and reporting obligations under 2 CFR Part 200.

The subaward itself isn't complicated. What's complicated is the compliance framework around it: the distinction between subawards and procurement contracts, the monitoring requirements, the FFATA reporting, the risk assessments, and the audit implications. Getting any of these wrong can result in disallowed costs, audit findings, or worse.

This guide covers the regulatory framework, the subrecipient vs. contractor determination (the decision that sets which rules apply), pass-through entity responsibilities, and common compliance failures.

According to 2 CFR 200.331, recipients must decide whether each agreement creates a subrecipient or contractor relationship based on the substance of the relationship. According to 2 CFR 200.332, pass-through entities must verify exclusion status, identify subawards, evaluate risk, monitor subrecipients, and follow up on findings. According to SAM.gov, FSRS.gov was retired on March 8, 2025, and subaward reporting is now handled in SAM.gov. Our analysis is that subaward mistakes happen before the agreement is signed. For example, one college can create a monitoring problem by calling a program partner a vendor when that partner is actually selecting participants and carrying out federal program objectives.

Where official sources stop: Official subaward guidance tells you the legal test, but it does not rank the practical risk of each partner structure. Grantsights treats a proposed partner as high-risk when the partner controls participant eligibility, owns a program outcome, uses its own protocol or service model, and will invoice against a shared federal objective. That pattern is a stronger warning than the label on the draft agreement. The best application decision is to name the partner, budget the subaward correctly, and write the monitoring plan before submission. The bad-fit decision is to hide the partner in a vendor line, then solve classification after award. For example, a workforce nonprofit that asks a training college to select participants, deliver instruction, and report placement outcomes should model a subaward even if procurement staff prefer a contract template.

Where official sources stop: 2 CFR 200 gives the classification factors, but it does not tell a project team which partner setup will create the most monitoring risk in practice. Grantsights adds that risk screen by looking at who controls eligibility, outcomes, protocols, invoices, and federal reporting before the budget is locked.

Treat classification as a proposal-stage decision, not a contracting-stage cleanup. The later the team waits, the harder it is to fix the budget base, reporting owner, and monitoring plan.

Last updated: October 9, 2026

If you are comparing grant opportunities that require partners, search the Grantsights grant database before applying. A project with 3 subrecipients can be a much heavier compliance lift than a project with the same dollar amount and no pass-through structure.

June 2026 Source Check: Subaward Rules That Change the Budget

Related guides: pair this guide with subrecipient monitoring, federal grant compliance requirements, grant budget writing, SAM.gov registration, NOFO guidance, and live grant search before building a partner-heavy application.

Current Subaward Decision Table

---

Difference Between Prime Award and Subaward

For "difference between prime award and subaward," the clean distinction is who received money directly from the federal agency and who is carrying out a piece of that award under the prime recipient.

A prime award creates the direct legal relationship with the federal agency. A subaward creates a federal assistance relationship between the prime recipient and the subrecipient. A contractor relationship is different: it buys goods or services. Under 2 CFR 200.331, the substance of the relationship controls, even if the document is called a contract.

Subaward Definition: What the Regulation Actually Says

A subaward is an award provided by a pass-through entity to a subrecipient for the subrecipient to carry out part of a federal award received by the pass-through entity. Under 2 CFR 200.1, the definition explicitly excludes payments to contractors, beneficiaries, and participants.

A few points worth emphasizing:

A subaward can take any legal form. The regulation states that a subaward may be provided through any form of legal agreement, including an agreement the pass-through entity considers a contract. The substance of the relationship matters more than what you call the document. If you label an agreement a "contract" but the entity receiving funds is carrying out programmatic work with independent judgment, it's functionally a subaward regardless of the label.

Consortium agreements are subawards. This is explicitly stated in the definition. In NIH-funded research, consortium agreements where a collaborating institution receives funds to conduct part of the research are subawards, not procurement contracts. That distinction also matters for institutional training awards. If your graduate school or research office is mapping multi-campus training slots, search the Grantsights grant database for current NRSA T32 opportunities as examples of awards where consortium structure can shape compliance, budgeting, and monitoring.

The pass-through entity is the prime recipient. The organization that received the federal award directly from the agency and then issues the subaward is the pass-through entity. The organization receiving the subaward is the subrecipient.

---

Subaward vs. Subcontract: The Most Critical Distinction

Misclassifying a subaward as a procurement contract (or vice versa) is an easy mistake to make and an expensive one to fix after award. The classification determines which set of regulatory requirements applies, and the two sets are dramatically different.

What Makes It a Subaward (Subrecipient Relationship)

Under 2 CFR 200.331, a subrecipient relationship exists when the entity receiving funds:

• Determines who is eligible to receive services under the program
• Has its performance measured against whether the objectives of the federal program are met
• Has responsibility for programmatic decision-making
• Has responsibility for adherence to applicable federal program requirements in the subaward
• Uses the federal funds to carry out a program for a public purpose, as distinguished from providing goods or services for the benefit of the pass-through entity

Example: A university receives an NIH grant to study diabetes interventions in rural communities. It issues a subaward to a community health center to recruit participants, deliver the intervention, and collect data at its sites. The health center makes independent decisions about implementation, hires its own staff, and has its own IRB protocol. This is a subaward.

What Makes It a Procurement Contract (Contractor Relationship)

A contractor relationship exists when the entity receiving funds:

• Provides goods or services within its normal business operations
• Provides similar goods or services to many different purchasers
• Normally operates in a competitive environment
• Provides goods or services ancillary to the operation of the federal program
• Is not subject to the compliance requirements of the federal program as a result of the agreement

Example: The same university hires a data analytics company to clean and analyze the dataset collected by the community health center. The analytics company performs this service for many clients, doesn't make programmatic decisions about the research, and delivers a defined product (a clean dataset and statistical analysis). This is a procurement contract.

The Decision Flowchart

When you're unsure how to classify a relationship, work through these questions in order:

1. Does the entity carry out a substantive portion of the federal program's objectives? Yes = leans subaward. No = leans procurement.

2. Does the entity make independent programmatic decisions about how to accomplish the work? Yes = leans subaward. No = leans procurement.

3. Does the entity provide goods or services that it also provides to other non-federal customers as part of its regular business? Yes = leans procurement. No = leans subaward.

4. Is the entity's performance measured against program objectives, or against delivery of a specific product or service? Program objectives = subaward. Specific deliverable = procurement.

5. Does the entity determine eligibility of beneficiaries or participants? Yes = subaward. No = could be either, use other factors.

If the answers are mixed, 2 CFR 200.331(c) says to use judgment and consider the substance of the relationship, not the form of the agreement. Document your reasoning. Auditors will ask for it.

For example, a college that uses its standard vendor template for a partner who selects participants, delivers the federally funded training model, and reports employment outcomes would likely be looking at a subrecipient relationship under the 2 CFR 200.331 factors, whatever the template says. Fixing that after the award starts can mean rewriting the agreement, adding FFATA reporting, completing a risk review, and documenting monitoring late.

For related compliance decisions, use this page with the subrecipient monitoring guide and the federal grant compliance requirements guide.

Why Getting This Wrong Matters

If you classify a subrecipient as a contractor:

• You skip the required risk assessment and monitoring under 2 CFR 200.332
• You skip FFATA reporting
• You may not pass through required federal terms and conditions
• You may not ensure the subrecipient has a Single Audit
• An auditor will likely flag this as a finding

If you classify a contractor as a subrecipient:

• You impose unnecessary compliance requirements on a vendor
• You may not follow competitive procurement procedures required under 2 CFR 200.318-327
• You add administrative burden without corresponding benefit
• An auditor may still flag this if the procurement rules weren't followed

---

Pass-Through Entity Responsibilities Under 2 CFR 200.332

According to 2 CFR 200.332, pass-through entities have nine lettered requirements, (a) through (i): check exclusion status, identify the subaward, evaluate risk, consider specific conditions, monitor, use monitoring tools matched to risk, verify audits, adjust records when needed, and consider enforcement. The sections below group the main ones. When your organization issues a subaward, you become a pass-through entity with specific obligations. These aren't suggestions.

1. Clearly Identify the Subaward

Every subaward must include specific information so the subrecipient knows the funding source and applicable requirements. Required elements include:

• Federal award identification (FAIN)
• Federal award date and period of performance
• Total amount of the federal award and the subaward amount
• Name of the federal awarding agency, pass-through entity, and contact information
• CFDA (now called ALN, Assistance Listing Number) title and number
• Whether the award is R&D
• Indirect cost rate (the subrecipient's federally negotiated rate; if none exists, either a rate negotiated between the pass-through entity and the subrecipient or the 15% de minimis rate, per 2 CFR 200.332(b)(4))
• All applicable compliance requirements

Missing any of these elements is a common audit finding. Create a subaward template that includes all required fields so nothing gets skipped.

2. Assess Subrecipient Risk

Before issuing the subaward, you must evaluate the subrecipient's risk of noncompliance. The regulation doesn't prescribe a specific methodology, but factors to consider include:

• The subrecipient's prior experience with federal awards
• Results of previous audits (check the Federal Audit Clearinghouse, which moved from Census to GSA at fac.gov)
• Whether the subrecipient has new personnel or new or substantially changed systems
• The extent and results of federal awarding agency monitoring

Document your risk assessment. A simple risk matrix (low, medium, high) with supporting rationale for each factor is sufficient. The level of monitoring you perform should correspond to the assessed risk level.

3. Monitor Subrecipient Activities

Monitoring is the ongoing obligation that continues throughout the subaward period. Required monitoring activities include:

• Reviewing financial reports: Verify that the subrecipient's expenditures are allowable and within the approved budget
• Reviewing performance reports: Confirm that the subrecipient is making adequate progress toward its scope of work
• Following up on audit findings: If the subrecipient's Single Audit identifies findings related to your subaward, you must ensure corrective action
• Issuing management decisions on audit findings: You must issue a management decision within 6 months of receiving the audit report
• Considering imposing additional conditions: For high-risk subrecipients, you may require more frequent reporting, additional documentation, or pre-approval of expenditures

The level of monitoring should match the risk assessment. A large research university with a clean audit history warrants less intensive oversight than a small community organization receiving its first federal subaward.

4. Verify Single Audit Compliance

According to OMB's 2024 Uniform Guidance revisions, a subrecipient that spends $1 million or more in federal awards during its fiscal year must have a Single Audit performed. As the pass-through entity, you must:

• Verify whether the subrecipient met the audit threshold
• Obtain and review the subrecipient's audit report (available on the Federal Audit Clearinghouse)
• Follow up on any findings related to your subaward

If the subrecipient is below the threshold and doesn't require a Single Audit, consider alternative monitoring approaches: desk reviews, site visits, or agreed-upon procedures engagements.

5. Enforce Remedies for Noncompliance

If a subrecipient fails to comply with federal requirements, you must consider taking enforcement action. Available remedies include:

• Temporarily withholding cash payments
• Disallowing costs
• Wholly or partially suspending or terminating the subaward
• Initiating suspension or debarment proceedings
• Withholding further awards
• Taking other remedies that may be legally available

These are serious steps. Most issues get resolved through communication and corrective action plans before reaching enforcement. But you need to document that you identified problems and took action. Ignoring subrecipient noncompliance doesn't protect you. It creates a finding against your organization.

For a broader overview of these compliance obligations, see our federal grant compliance requirements guide.

---

FFATA Reporting: The $30,000 Threshold

The Federal Funding Accountability and Transparency Act (FFATA) requires pass-through entities to report subaward data for public transparency. Here's what you need to know.

What Triggers Reporting

You must report any subaward with a cumulative value of $30,000 or more. This is a cumulative threshold: if your initial subaward is $20,000 and you later amend it to $35,000, reporting is triggered when the total crosses $30,000.

Do not split a subaward into smaller increments to avoid the reporting threshold. This is explicitly prohibited, and auditors check for it.

Where to Report

According to SAM.gov, subaward reporting moved from the previous FFATA Subaward Reporting System into SAM.gov in March 2025. The reporting module is integrated into SAM.gov's entity management interface.

Reporting Timeline

Reports are due by the end of the month following the month the subaward obligation was made. If you issue a subaward on October 15, the report is due no later than November 30.

Required Data Elements

• Subrecipient name and UEI (Unique Entity Identifier)
• Subrecipient address
• Subaward amount
• Subaward obligation/action date
• Subaward project description (using the same language as the federal award's project description in FFATA)
• Subrecipient principal place of performance
• Subrecipient executive compensation data (if applicable, based on revenue and federal award thresholds)

Consequences of Non-Reporting

Failure to submit FFATA reports can result in special award conditions on your federal awards, reduced funding, or designation as a high-risk grantee. Some agencies conduct FFATA compliance reviews as part of their site visit protocols.

---

What to Include in a Subaward Agreement

The subaward agreement is the legal document governing the relationship between the pass-through entity and the subrecipient. Beyond the required information listed in 2 CFR 200.332, a complete subaward agreement should include:

Scope of Work

A detailed description of the work the subrecipient will perform, including specific objectives, activities, deliverables, and timelines. This should be detailed enough that both parties (and an auditor) can determine whether the subrecipient fulfilled its obligations.

Budget

An itemized budget showing how the subaward funds will be spent, organized by the same categories used in the prime award (personnel, fringe, travel, supplies, contractual, indirect, etc.). Include the subrecipient's indirect cost rate and basis.

Period of Performance

Start and end dates, which typically fall within the prime award's period of performance. If the subaward period extends beyond the prime award period (which sometimes happens with no-cost extensions), address that explicitly.

Reporting Requirements

Specify the frequency and format of financial and programmatic reports the subrecipient must submit. Quarterly financial reports and semi-annual progress reports are common. Align reporting schedules so you receive subrecipient data in time to include it in your own reports to the federal agency.

Flow-Down Provisions

All applicable terms and conditions from the prime award that apply to the subrecipient's work must be included. This includes federal program requirements, cost principles (2 CFR 200 Subpart E), and any agency-specific terms. This is called "flowing down" the requirements.

Common flow-down provisions include:

• Allowable cost restrictions
• Equipment management requirements
• Record retention requirements (typically 3 years after final report submission)
• Access to records for audit purposes
• Non-discrimination and civil rights requirements
• Intellectual property and data sharing terms

Termination Provisions

Conditions under which either party can terminate the subaward, required notice periods, and how wind-down costs will be handled.

---

Indirect Costs on Subawards: The $50,000 Rule

How indirect costs interact with subawards trips up many grant managers, even experienced ones.

The Pass-Through Entity's Indirect Costs

When calculating your organization's indirect costs on the prime award, subaward costs are included in your modified total direct cost (MTDC) base only up to the first $50,000 of each subaward (raised from $25,000 in the 2024 Uniform Guidance revision). The amount above $50,000 is excluded.

This means if you issue a $200,000 subaward, you charge your indirect cost rate on $50,000 of that subaward, not the full $200,000. The remaining $150,000 is excluded from your MTDC base.

Important: the $50,000 threshold applies to the total subaward across the entire project period, not per year. A 3-year subaward totaling $150,000 ($50,000 per year) still only generates $50,000 in MTDC base for your indirect cost calculation, total.

The Subrecipient's Indirect Costs

The subrecipient charges their own indirect costs on their portion of the work, using their own federally negotiated rate. If the subrecipient doesn't have a negotiated rate, they can use the 15% de minimis rate established in 2 CFR 200.414(f) (raised from 10% in the 2024 Uniform Guidance revision).

The subrecipient's indirect costs are a direct cost to your prime award. They show up in your budget under the subaward line item.

For more on how indirect cost rates work across awards, see our guide on how to calculate your indirect cost rate.

---

Risk Assessment: A Practical Framework

The regulation requires a risk assessment but doesn't prescribe a format. Here's a practical approach.

Risk Factors to Evaluate

Monitoring Levels Based on Risk

Low risk: Standard monitoring. Quarterly financial reports, semi-annual progress reports, annual desk review of Single Audit.

Medium risk: Enhanced monitoring. Monthly financial reports, quarterly progress reports, annual desk review of Single Audit, at least one site visit during the project period.

High risk: Intensive monitoring. Monthly financial reports with supporting documentation, quarterly progress reports, pre-approval of expenditures above a threshold, annual site visit, possible agreed-upon procedures engagement. Consider imposing specific award conditions (withholding payments pending report review, requiring additional documentation).

Document your risk assessment before the subaward starts and update it annually or when circumstances change (e.g., the subrecipient has an audit finding or experiences staff turnover).

---

7 Common Subaward Compliance Failures

1. Misclassifying the Relationship

As discussed above, calling a subrecipient a contractor (or vice versa) is one of the most consequential errors. Use the 2 CFR 200.331 criteria, document your analysis, and get it right before the agreement is executed.

2. Missing Required Subaward Agreement Elements

Subaward agreements that omit the FAIN, the ALN number, the indirect cost rate, or other required data elements from 2 CFR 200.332 are incomplete. Auditors check for this. Build a checklist from the regulation and verify every element before both parties sign.

3. No Risk Assessment on File

You assessed the risk informally in your head. That's not documentation. Write it down, sign it, date it, and file it with the subaward records. The risk assessment doesn't need to be elaborate, but it needs to exist.

4. Inadequate Monitoring

The subaward was issued, the subrecipient submitted financial reports, and nobody reviewed them. Or the subrecipient didn't submit reports at all and nobody followed up. Monitoring isn't passive. It requires active review, documented follow-up, and timely action on problems.

5. Late or Missing FFATA Reports

FFATA reporting falls through the cracks when it's not assigned to a specific person with a specific deadline. Assign responsibility, set calendar reminders, and verify submissions in SAM.gov.

6. Not Following Up on Subrecipient Audit Findings

Your subrecipient's Single Audit identifies a finding related to your subaward. The regulation requires you to issue a management decision within 6 months. If you never check the Federal Audit Clearinghouse and never review the subrecipient's audit, you've failed this requirement.

7. Applying Your Indirect Rate to the Full Subaward Amount

Charging indirect costs on the full subaward amount instead of only the first $50,000 is a budgeting error that becomes a compliance finding if it results in overcharging the federal award. Calculate MTDC correctly and ensure your budget reflects the $50,000 cap.

---

When You Don't Need Prior Approval for a Subaward

Some grant managers assume every subaward needs prior approval from the federal agency. That's not always the case.

If the subrecipient and their scope of work were identified in your original application and approved budget, many agencies consider that sufficient approval. NIH, for example, generally allows subawards that were part of the approved application without additional prior approval.

However, you do need prior approval in these situations:

• Adding a new subrecipient not identified in the original application
• Significantly changing the scope of an existing subaward
• Transferring a substantial portion of the work to a subrecipient (this can trigger 2 CFR 200.308 prior approval requirements for budget changes)
• Your award terms specifically require prior approval for all subawards (common with DOJ/OJP awards)

When in doubt, ask your federal program officer. Getting confirmation before issuing a subaward takes a few days. Getting a disallowed cost finding can take years to resolve.

For step-by-step guidance on the initial application process where subawards should be identified, see our guide to applying for federal grants.

---

What Federal Audit Findings Doesn't Tell You

Single Audit reports, including findings on subrecipient monitoring, are public on the Federal Audit Clearinghouse, so you can read a partner's past findings before you sign. What the regulation doesn't spell out is how labels in your own financial system can work against you. For example, an organization that issues several subawards but records some of them as "contracts" in its accounting system could end up with no risk review or monitoring file for those partners, and an auditor could question the related costs. Check that the label in the agreement, the budget, and the accounting system all match the 2 CFR 200.331 determination.

Pass-through entities must monitor subrecipients even when the subaward is small. There's no dollar threshold below which monitoring is optional. A $15,000 subaward to a community partner requires the same risk assessment and monitoring framework as a $500,000 subaward, though the intensity of monitoring can be scaled.

Subrecipient audit requirements changed with the 2024 Uniform Guidance revision. The single audit threshold is now $1,000,000 in federal expenditures (up from $750,000). This means fewer of your subrecipients will need their own single audit, but your monitoring obligations as a pass-through don't decrease.

Related Guides

• Federal Grants for Nonprofits
• State Grants for Nonprofits
• Subrecipient Monitoring for Federal Grants
• Grant Budget Guide
• SAM.gov Registration Guide
• What Is a NOFO

Grantsights Trust Check: Apply or Skip This Path

Use this page as a decision screen before your team spends writing time. Apply the guidance when the applicant type, deadline, budget size, required evidence, and official submission path all match the source record. Skip or pause when the fit is only thematic, the applicant cannot document eligibility, the deadline leaves no time for review, or the official source points to a different route.

Sources

• 2 CFR 200.1: Definitions (including Subaward)
• 2 CFR 200.331: Subrecipient and Contractor Determinations
• 2 CFR 200.332: Requirements for Pass-Through Entities
• Grants.gov Blog: What Is a Subaward and a Subrecipient?
• NIH Subawards Policy
• OJP Subawards Guide Sheet