Participant support costs look like ordinary travel and registration fees, but they follow their own rules. This article explains who counts as a participant under 2 CFR 200.1 and why the classification affects your indirect costs and your budget.
If your federal award pays for a training, a conference, or a community program, you're probably covering costs for the people who attend. On a ledger those costs look like ordinary travel and registration fees. Under 2 CFR Part 200, they follow their own rules.
Under 2 CFR 200.1, participant support costs are direct costs such as stipends, travel allowances, registration fees, temporary dependent care, and per diem paid to or on behalf of participants.
A participant is someone attending or taking part in program activities who isn't responsible for carrying out the award, such as students, community members, or conference attendees. Consultants, project staff, and employees who develop or deliver the program are not participants, even when they're at the same event.
It affects your award in three ways:
-
Indirect costs. Modified total direct cost (MTDC) excludes participant support costs, so if your rate uses an MTDC base, including the de minimis rate, these costs don't generate indirect recovery.
-
Budget flexibility. Under 2 CFR 200.308(f)(5), moving funds budgeted for participant support into another category requires prior written approval.
-
Consistency. Under 2 CFR 200.456, how you classify these costs must be documented in your written policies and applied the same way across all your federal awards.
Before the 2024 revisions took effect on October 1, 2024, participant support costs were allowable only with the agency's prior approval. The current rule replaces that with the documentation requirement above. Older awards may still carry the earlier terms, and some agencies add their own requirements, so check your notice of award.
Most mistakes come from treating everyone at an event the same way:
- Staff or trainer travel coded as participant travel
- Speaker fees recorded as participant support
- Shared meals for staff and attendees charged entirely to the participant line
- Leftover participant funds moved to another category without approval
A short policy section fixes most of this. Define who counts as a participant, name the costs you classify this way, explain how you split shared costs, and give these costs their own account code.
It also helps to make the call before the invoices arrive. When you set up an event, mark each person on the roster as either a participant or someone delivering the program, and keep that roster with the event's financial records. Whoever codes a travel or stipend payment can check the name instead of guessing from the receipt. If a monitor later asks why a cost landed on the participant line, the roster gives them the answer.
Most of the risk with participant support costs comes from not knowing which line a cost belongs on. This week, pick one active award that funds training or outreach and confirm that participant costs are coded separately from staff costs.
MyFedTrainer offers free resources to help you organize grant files and build practical compliance habits. Take a look when it is useful to you. 
