The federal government will reimburse you for an enormous range of costs you incur to administer the programs it funds. Executive time, accounting infrastructure, compliance functions, technology, facilities, audit costs, board governance. The framework for what's allowable is broad, well-documented in 2 CFR 200, and considerably more generous than most organizations realize. The catch is that allowability is necessary but not sufficient. To recover a cost, you have to be able to defend it. And most organizations cannot.

Defense is where indirect cost recovery actually lives or dies. The cost has to be allowable, allocable, reasonable, and consistently treated. Those are the four tests, and each one requires documentation infrastructure that most organizations simply don't have. The cost can be entirely legitimate, fully recoverable under the federal framework, and the organization will still leave it on the table because it can't produce the documentation required to defend the inclusion if challenged. The federal cognizant agency doesn't have to disallow the cost. The organization disallows it preemptively, by building a rate proposal that excludes everything it can't defend.

This is one of the most expensive financial dynamics in the nonprofit and public sector, and almost no one talks about it directly. The conversation gets framed as compliance. Organizations build conservative rates because they're being compliant. The framing is wrong. They're building conservative rates because they don't have the documentation to support aggressive ones, and they don't have the documentation because they never built the infrastructure required to produce it.

Here's what defensible documentation actually requires, and why most organizations don't have it.

Time and effort tracking has to be real, not approximated. For costs that depend on personnel time, federal cost principles require documentation of how individual employees actually spent their time, in proportions that can be reconciled to payroll. Most organizations approximate this. They use rough percentages that get applied uniformly, or they have a time tracking system that captures hours worked but not the allocation of those hours across programs and funding sources. When the documentation gets examined, the approximation falls apart. So the rate proposal excludes the personnel time the organization can't precisely document, even though the time was really spent on activities the federal framework would reimburse.

Cost allocation methodology has to produce a clear, defensible mapping between shared costs and the programs that consume them. The methodology can't be a black box. The auditor or cognizant agency reviewer has to be able to follow the logic from cost to allocation to recovery. Most organizations have allocation methodologies that work for internal accounting purposes and don't survive structured external scrutiny. The methodology was set up years ago, has been adjusted in undocumented ways, and can't be cleanly reconstructed from the available records. So the rate proposal gets built on the portion of the allocation that can be defended cleanly, and the rest gets excluded, even when the underlying costs are genuinely indirect and genuinely allowable.

The relationship between costs and programs has to be documented, not assumed. Costs get classified as direct or indirect based on their relationship to specific programs. The classification has to be defensible against the operational reality. A cost that's classified as indirect but is actually consumed by a single program is misclassified, and a federal reviewer will find it. A cost that's classified as direct but actually supports the whole organization is misclassified in the other direction. Both errors create defense problems. Most organizations have classifications that have been in place for years, that don't reflect how the organization currently operates, and that can't be reconstructed from documented analysis.

Consistency of treatment has to be demonstrable across the organization. Federal cost principles require that costs be treated consistently across programs and funding sources. A cost that's treated as direct for one program and indirect for another, without a defensible basis for the difference, fails the consistency test. Most organizations have inconsistencies they don't even know about, accumulated over years of ad hoc decisions made by different people responding to different funder requirements. When the inconsistencies surface during audit or rate review, the organization either has to explain them or exclude the affected costs. Most explain poorly and exclude broadly.

The systems that produce the documentation have to support the level of granularity the framework requires. Most organizations are running financial and operational systems that were designed for general business management, not for the level of cost tracking that federal recovery defense requires. The systems produce summary-level data when defense requires transaction-level data. They produce monthly aggregations when defense requires the underlying daily activity. They produce reports designed for management use when defense requires reports designed to satisfy external review. Building defensible documentation on top of inadequate systems requires manual reconstruction, which is expensive, time-consuming, and never as clean as system-generated documentation.

The cumulative effect of these documentation gaps is that organizations leave significant recoverable cost unrecovered, year after year. The rate proposal gets built down to what the documentation supports, which is almost always less than what the cost reality would justify. The organization signs a rate agreement that under-recovers actual cost. The under-recovery compounds across the funding portfolio. Over five years, an organization with $20M in federal funding can leave $5M to $10M in defensible recovery on the table, not because the costs aren't real, but because the documentation infrastructure required to defend them was never built.

The strategic problem here is that most organizations don't see the documentation infrastructure as a financial investment. They see it as administrative overhead. The accounting team requests effort tracking, and program leaders resist because it feels burdensome. The CFO proposes investment in cost allocation systems, and the board declines because it doesn't tie cleanly to mission spending. The compliance function asks for better classification documentation, and operations pushes back because it slows things down. Each individual resistance is rational. The cumulative effect is that the organization preserves a documentation gap that costs millions of dollars annually in unrecovered cost.

The organizations that recover what they should are the ones that have built documentation infrastructure as a strategic asset. Real time tracking. Defensible allocation methodology. Clear classification rules. Consistent treatment across programs. Systems that produce the granularity federal review requires. The infrastructure costs money to build and maintain. It produces multiples of that cost in recovered indirect cost, year after year, for as long as the federal funding portfolio exists.

The argument against doing this work is always that the existing rate is acceptable, that the audit hasn't flagged anything material, and that the cost of building better documentation isn't justified. The argument inverts the actual math. The existing rate is acceptable only because the documentation can't support a stronger one. The audit isn't flagging anything because the rate has already been built down to what the documentation supports. The cost of better documentation is small relative to the recovery it would unlock. The organization is paying the cost of the documentation gap every year, in unrecovered cost. It just isn't paying it visibly, on a budget line that triggers leadership attention.

If your indirect cost rate is at or below the federal de minimis, or if you've never had a formal rate negotiation, your organization is almost certainly leaving substantial recoverable cost unrecovered. The cost isn't gone. It's been absorbed by your unrestricted dollars, paid for with funds that could have been deployed against mission. The defense gap is the reason. Closing the defense gap is the path to recovery.