Short answer
A subrecipient monitoring plan explains how your nonprofit will decide who is a subrecipient, assess risk, set reporting rules, review performance, follow up on findings, and close the subaward. Under 2 CFR 200.332, the pass-through entity stays responsible for monitoring the subrecipient.
Subrecipient monitoring is easy to underbuild because it starts as a relationship problem and ends as a compliance problem.
Your program team trusts the partner. Finance sees invoices. The grants manager sees reports. Everyone assumes someone else is checking the full file. Then the audit asks for risk review, reporting follow-up, and proof that problems were fixed.
A subrecipient monitoring plan closes that gap. It names what must happen before the subaward, during performance, and at closeout.
Start with the right determination
The first decision is whether the partner is a subrecipient or a contractor. This is not a label you choose for convenience. Under 2 CFR 200.331, the pass-through entity makes a case-by-case determination.
A subrecipient helps carry out part of the federal program. It may make program decisions, serve eligible participants, track performance outcomes, and follow federal program requirements. A contractor sells goods or services for your organization’s use.
Write the determination down before the agreement is signed. If the file does not explain why the partner is a subrecipient, every later monitoring step becomes harder to defend.
Do a pre-award risk review
2 CFR 200.332 requires the pass-through entity to evaluate each subrecipient’s risk of noncompliance. The point is not to create paperwork. The point is to decide how much monitoring the subrecipient needs.
Review:
- prior experience with similar awards
- prior audit findings
- staff capacity and turnover
- financial systems
- internal controls
- reporting history
- award complexity
- total dollar exposure
A new partner handling a large federal subaward needs more monitoring than a stable partner with clean audits and a small, familiar scope.
Put monitoring terms in the subaward
The subaward should say what the partner must submit. It should say when reports are due. It should also name the proof required. Do not leave reporting rules in email.
At minimum, define:
- performance report cadence
- financial report cadence
- invoice support required
- backup documentation rules
- prior approval triggers
- audit and records access
- corrective action deadlines
- closeout due dates
If the agreement is vague, staff will fill the gaps later. That is where inconsistency starts.
Review reports against both money and performance
Monitoring is not just invoice approval. The pass-through entity must review financial and performance reports. Those two views should line up.
If the subrecipient has spent 80 percent of the budget but completed 35 percent of the work, ask why. If performance looks strong but invoices are late or unsupported, ask why. If reports are timely but outcomes keep changing, document the reason.
GrantPipe can help here because it stores reporting dates, financial records, documents, and activity history in the same grant file. That does not replace judgment, but it keeps the monitoring trail from splitting across inboxes.
Follow up when something goes wrong
The plan should say what happens when a report is late. It should also cover unsupported costs, site visit problems, and audit findings.
Define the escalation path:
- staff request missing information
- subrecipient provides a written response
- owner reviews whether the response fixes the issue
- unresolved issues move to corrective action
- leadership decides whether to pause payments or modify the subaward
Corrective action should have a due date, owner, proof, and status. A call does not resolve a finding. The file must show what changed.
Verify audit requirements
If a subrecipient may meet the Single Audit threshold, check early. The pass-through entity must verify that audit rules are met. The federal threshold is $1,000,000 in federal spend for fiscal years ending on or after September 30, 2025.
Do not wait until closeout to ask. Build the check into the monitoring calendar.
Close the subaward cleanly
Closeout should confirm:
- final financial report received
- final performance report received
- invoices paid or rejected
- unspent funds resolved
- equipment or property issues addressed
- corrective actions closed or documented
- records retained under the award terms
Subrecipient closeout often has a shorter timeline than recipient closeout. Build backward from the prime award’s final report deadline. Your team needs time to review subrecipient materials before it files its own final report.
Use a one-page monitoring matrix
For each subrecipient, keep a matrix with these columns:
- subrecipient name
- award number
- risk level
- report cadence
- financial reviewer
- program reviewer
- next report due
- open issues
- corrective action status
- closeout status
This gives leadership a clear view without reading every file.
What to avoid
Do not copy a policy from the internet and call it a plan. A usable monitoring plan names the real staff roles. It names the report schedule, risk levels, and records for each subaward.
Also avoid watching only high-dollar subawards. Dollar size matters, but it is not the only risk. A smaller subaward can carry more risk. New staff, eligibility rules, or weak files can all raise that risk.
How GrantPipe fits
GrantPipe gives grants, finance, and program staff one place to track the subaward file. It can hold terms, report dates, documents, corrective action, and closeout status. That matters when program staff, finance staff, auditors, and leaders all need the same file.
Start with the subrecipient monitoring checklist, then decide which parts of the monitoring file need a shared system instead of a folder and spreadsheet.
Free resource
Get the Subrecipient Monitoring Checklist
A complete subrecipient monitoring checklist covering pre-award risk assessment, agreement requirements, ongoing monitoring, and documentation - organized for the pass-through entity. Delivered by email.
Looking for something else?
- Pass-through entity
- An entity that receives a federal award and passes part of it to a subrecipient to carry out part of the federal program.
DEFINITION
- Subrecipient
- An entity that receives a subaward to carry out part of a federal program. It is different from a contractor selling goods or services.
DEFINITION
- Corrective action
- The documented steps a subrecipient takes to fix a finding, reporting gap, late report, questioned cost, or other compliance issue.
DEFINITION
Q&A
What belongs in a subrecipient monitoring plan?
The plan should include subrecipient versus contractor determination, pre-award risk review, subaward terms, reporting schedule, invoice review, performance review, audit verification, corrective action follow-up, documentation rules, and closeout steps.
Q&A
Who owns subrecipient monitoring at a nonprofit?
Ownership usually spans grants, finance, and program staff. Grants staff manage award terms and reports. Finance checks costs and invoices. Program staff review performance. One named owner should coordinate the full file.
Frequently asked