Subgrant Management: What You Take On

A state agency sets aside two million dollars for grassroots organizations. The application opens in March. By September, nearly half of it has not moved, and the reason is not that nobody applied. It is that several organizations that scored well could not produce an audited financial statement, two could not accept a wire, and one withdrew when it learned it would be paid in arrears.

Nothing in that sequence was unreasonable on its own. Together they describe a program that was designed for organizations other than the ones it was written for.

A pass-through is a fiduciary role

An entity that receives funds under one set of terms and re-grants them is not simply moving money. It carries the obligations attached to the original award and answers for how its subrecipients spend, long after the transfer clears.

That is the whole of what subgrant administration covers, and it begins before the application opens rather than when the first payment clears.

That has a practical consequence worth stating plainly: anything the subgrant agreement leaves out cannot be enforced later, however clearly it bound the original award. The terms flow down through that document or they do not flow down at all.

• Period of performance, and whether costs incurred before the start date are allowable.
• The approved budget, and what size of change needs prior written approval.
• Allowable and unallowable cost categories, stated plainly rather than by citation alone.
• Reporting obligations, with dates and the form each report takes.
• Record retention, including how long and in whose custody.
• Audit and site visit rights, and the notice given before they are exercised.
• Conditions for suspension, repayment, and termination.

Write the rubric before the application

Decide how you will score, then write the questions that let an applicant earn those points. Done in the other order, applications arrive full of material nobody scores, and the questions that would have separated a strong applicant from a weak one were never asked.

Then record the basis for every award and every denial at the time the decision is made. If a disappointed applicant asks, or a review follows, contemporaneous notes are the record. Reasoning reconstructed afterward is not, and the people reading it can tell the difference.

The requirements that quietly exclude

Most exclusion in a subgrant program is inadvertent. It lives in the application requirements, and it removes the organizations the program was created to reach.

• Audited financial statements, requested from organizations below the threshold where an audit is required.
• Portal-only submission with no alternative, where the applicant has no reliable connectivity.
• A two-week open period, which favors organizations with staff free to drop other work.
• Data requests that presume a case management system the applicant does not own.
• Match requirements that assume reserves a grassroots organization does not hold.
• Narrative limits generous enough to reward whoever can afford a professional grant writer.

For each requirement, ask which organizations it excludes and whether that exclusion is the point. Some are load-bearing. A program with a statutory eligibility boundary has to check it. Most are inherited from larger programs and were never examined against this applicant pool.

Reimbursement is a working capital requirement

This is the one that catches programs by surprise. Paying in arrears asks a subrecipient to spend first and recover later, which is a requirement to hold cash. An organization making payroll on a thin margin cannot do it, and will either withdraw or quietly go into debt to participate.

There is usually a safer structure available.

• Advance payment against an approved budget, with tighter and more frequent reporting.
• A first installment on execution, with later tranches released against submitted reports.
• Milestone payments where the work has natural checkpoints.
• Smaller, more frequent disbursements to a first-time subrecipient rather than one large one.

Monitoring is not report collection

A program that reads its reports at closeout has a reporting function. Monitoring means looking while there is still time to act, and concentrating attention where the risk actually is. A first-time subrecipient with one bookkeeper warrants more contact than an experienced one with a finance department, and treating them identically wastes effort on one and misses problems in the other.

It also matters who you talk to. A quarterly call with the executive director tells you how the program is going. A call with the person who keeps the books tells you whether the general ledger exists.

When something is wrong, a finding is a diagnosis rather than a verdict. A subrecipient that cannot produce a general ledger needs help building one. Recording the failure and moving on guarantees the same finding next period, and eventually a repayment demand that helps nobody.

Closeout is the last time anyone looks

The administrative close is the part everyone plans for: final financial report, reconciliation against the approved budget, return or reallocation of unspent funds, final programmatic report, confirmation of where records now sit, and written closure of any outstanding corrective action.

The part usually skipped is the one that makes the program defensible a year later. Build the audit file as the work happens. Scoring notes, agreements, reports, and correspondence filed at the time cost almost nothing to keep and are the whole of the defense. A file assembled under deadline afterward is visibly assembled afterward.

When not to become a pass-through

This is worth saying because the answer is sometimes no. Acting as a fiscal pass-through means accepting liability for how other organizations spend money, with the staff time, accounting capacity, and insurance that implies. An organization taking it on because the funding is available, rather than because it can carry the obligation, has added a risk to its balance sheet in exchange for administrative overhead.

If that is the position, the honest routes are to partner with an entity that already does this, to subcontract the administration, or to let the funder disburse directly and contribute what you are actually good at.

What good looks like

The money moved on schedule. Every organization that scored well was able to accept it. Problems surfaced in month four rather than month eleven, and were fixed. The file supports every decision without anyone having to remember anything.

None of that is visible while a program is running well, which is why it tends to be funded only after a program has run badly.