
SAM.gov Is Where Subaward Reporting Lives Now, and the Affiliate Loophole Just Closed
Subaward reporting consolidates on SAM.gov, and for the first time, transfers to affiliates and subsidiaries count as subawards. Here's how to tell what counts, and how to build a reporting system that doesn't fall apart under volume.
What actually counts as a subaward, and where the gray area has been. A subaward is federal money you pass to another organization to carry out part of your award's scope of work, as opposed to a vendor payment for goods or services on the open market. The test isn't the paperwork you used, it's the substance of the relationship: does the recipient have discretion over how to use the funds to accomplish a program objective, or are they simply delivering a good or service you specified? Under the old framework, transfers to affiliates, subsidiaries, or fiscally sponsored partners often fell into a gray area and went unreported as subawards, especially when the relationship felt internal rather than external. That gray area closes now. If federal dollars leave your organization and a related entity uses them to carry out part of the program, it's a subaward, reported the same way an external subrecipient relationship would be.
Here's how the reporting mechanism actually changes. Subaward reporting moves onto SAM.gov as the single system of record, replacing the patchwork of agency-specific and FSRS-based reporting that existed before. For each subaward, you'll need the subrecipient's entity information current in SAM.gov, the award amount and period of performance, and a description of the funded activity, reported on the cadence your award terms specify. The mechanical change is consolidation onto one platform. The substantive change is the affiliate and subsidiary rule, which likely adds subawards to your reporting count that were never counted before.
A quick way to check your exposure. List every organization, including internal affiliates, chapters, and fiscally sponsored partners, that received federal dollars from your organization in the last year to carry out part of a funded program. Anything on that list you haven't been reporting as a subaward is the gap this rule closes.
For State Agencies: The Volume Problem Needs a Standing System
For state agencies passing funds through to counties and municipalities, the volume problem is the real challenge, and the fix is a standing system, not a reporting sprint. A state agency with subawards to dozens of counties can't treat SAM.gov reporting as something staff reconstruct each time a report is due. Build a subaward inventory that's a living record, not an annual spreadsheet: every subaward's entity information, amount, period of performance, and reporting status in one place, updated as subawards are issued or amended rather than assembled retroactively before a deadline. Assign one staff member as the named owner of that inventory and its reporting cadence. The agencies that struggle here aren't the ones with the most subawards, they're the ones without a single source of truth for what those subawards are.
For Nonprofit Primes: Map the Affiliate Provision Before It's a Deadline
For nonprofit primes, the affiliate provision is the piece most likely to catch you by surprise, so map it before it's a reporting deadline. If your organization funnels federal dollars to a state chapter, a fiscally sponsored project, or a related entity, that relationship needs the same monitoring file an external subrecipient would get: an agreement, a scope of work, and now, SAM.gov reporting. Start by listing every affiliate relationship that touches federal funds, then confirm each one either already has subaward-level documentation or needs it built before your next reporting cycle. Where the relationship has operated informally for years, expect this to take real time to formalize, so start now rather than in September.
For Local Governments: Vendor or Subaward?
For local governments, the question to ask is whether a "vendor" relationship is actually a subaward relationship. A city that contracts with a local nonprofit to deliver part of a federally funded program, say, running a youth services component under a broader grant, may have been treating that partner as a vendor when the substance of the relationship, programmatic discretion, not just service delivery, makes it a subrecipient. Review any contracted partner under a federal award against that test now, since the reporting obligation follows the actual relationship, not the label on the agreement.
For Nonprofit Subrecipients: Keep Your Own Records Current
For nonprofit subrecipients, expect more detailed documentation requests from your pass-through, and the fastest way through them is having your own records current. As primes and state agencies tighten their SAM.gov reporting, they'll ask you for the underlying data behind your subaward: your entity information, your award period, your performance details. Keeping your own SAM.gov registration current and your program records organized means you're the subrecipient who turns that request around in a day, not the one who holds up the prime's entire report.
Prepare Now
- Build a living subaward inventory, not a point-in-time spreadsheet, with a named owner responsible for keeping it current
- List every affiliate, subsidiary, or fiscally sponsored relationship that receives federal dollars, and confirm each has subaward-level documentation
- Review any vendor or contractor relationships under a federal award to confirm they aren't actually subaward relationships
- Confirm your SAM.gov registration is active and your entity information is current, whether you report or are reported on
Your first move toward getting ahead of the new compliance requirements. Get the 2026 Uniform Guidance Transition Checklist.
