If you took the indirect cost rates of a hundred grant-funded organizations and examined them with rigor, you'd find that the vast majority are wrong. Not wrong in the sense of fraud or noncompliance. Wrong in the sense of mathematically indefensible, structurally outdated, or systematically understated. The rates were calculated, accepted, and have been in use for years. They're producing recovery numbers every month. And they don't reflect what the organization actually spends to operate the programs the rate is supposed to cover.

This isn't a fringe issue. It's the default condition. The exception is the organization with a rate that's been built recently, defensibly, and against current cost reality. Most organizations are operating on rates that were calculated under conditions that no longer exist, using methodologies that were defensible when they were built and aren't anymore, recovering at levels that bear only a loose relationship to actual cost consumption.

The reason this is so widespread is that indirect cost rate calculation sits in a structural blind spot. The rate is a federal requirement, so organizations build it. The rate gets accepted by the federal cognizant agency, so organizations treat it as approved and final. The rate produces a recovery number every month, so organizations move on. What almost never happens is a rigorous re-examination of whether the rate still represents the cost reality of the organization. The rate was correct when it was built. It got grandfathered into ongoing use. The organization changed underneath it. The rate didn't.

Here's what's actually wrong with most rates, broken into the patterns I see most often.

The cost pool is incomplete. The rate is calculated by dividing allowable indirect costs by an appropriate direct cost base. Most organizations underbuild the indirect cost pool because they don't fully understand what's allowable. Costs that legitimately belong in the pool get excluded because the original methodology was built conservatively, because nobody questioned the exclusions, or because the documentation infrastructure required to defend the inclusion was never built. Executive compensation, board-related costs, certain compliance functions, certain technology costs, certain shared services. All of these are partially or fully allowable under the right conditions. Most rate calculations leave money in the pool that should be in the rate.

The base is wrong. The denominator of the rate calculation matters as much as the numerator. The base determines what the rate gets applied to, which determines the recovery. Modified Total Direct Costs is the most common base, but the definition of what's included and excluded varies. Subawards above and below specific thresholds, equipment, capital expenditures, participant support costs, all have specific treatment. Most organizations use a base that was set up years ago and hasn't been re-examined as funding patterns evolved. A base that was appropriate when the organization had three subawards is wrong when the organization has thirty. A base that worked under one funding portfolio is wrong under a different one.

The cost allocation methodology underneath the rate is structurally weak. The rate calculation rolls up to one number, but underneath it sits a methodology for allocating shared costs between direct and indirect categories. That methodology determines whether costs are properly classified. Most methodologies use proxies that are easy to administer and operationally inaccurate. Square footage, headcount, percentage of payroll. These produce defensible-looking calculations that don't reflect actual consumption. A program that consumes a disproportionate share of CFO time, IT support, or compliance attention should bear a proportionate share of those costs. Most allocation methodologies smooth that consumption out across all programs in a way that distorts both the direct cost and the indirect cost pool.

The rate is built at the wrong level. Some organizations need a single indirect cost rate. Others need separate rates for different functional areas, different facilities, different programs, or different funding streams. The structure of the rate has to match the structure of the organization. Most organizations default to a single rate because it's simpler, even when the operational reality requires multiple rates to capture cost consumption accurately. The simplification produces a rate that's not wrong in any single direction, but understated in some areas and overstated in others, with the net effect almost always being under-recovery.

The rate hasn't been renegotiated when it should have been. Federal indirect cost rates can be renegotiated. Most organizations don't, because the renegotiation process feels burdensome and the existing rate is already approved. Meanwhile, the organization's cost structure is shifting, the funding portfolio is changing, the operational footprint is evolving, and the rate that was defensible three years ago is no longer reflecting current reality. The organization keeps using the old rate because changing it requires effort. The cost of not changing it is millions of dollars in unrecovered cost over time.

The documentation infrastructure can't defend the rate that the organization should have. Some organizations could build a much stronger rate if they had the documentation to support it. They don't, because the systems for tracking effort, allocating shared resources, and documenting cost consumption were never built to the level federal cost principles require for an aggressive rate. The result is that the rate gets built down to what the documentation can support, rather than the documentation getting built up to what the rate should justify. This is a self-imposed ceiling that most organizations don't even recognize they're operating under.

Underneath all of these specific problems sits a deeper structural issue. The indirect cost rate is treated as an accounting calculation when it should be treated as a strategic asset. Accounting calculations get done correctly within the constraints of existing methodology. Strategic assets get optimized. The difference is whether the organization is asking "did we calculate the rate properly?" or "did we build the strongest defensible rate the cost data and federal framework will support?" The first question produces a compliant rate. The second produces a rate that captures what the organization is actually entitled to recover.

The financial impact of getting this right is substantial and durable. An organization that moves from a fifteen percent rate to a defensible twenty-five percent rate on $20M of federal funding recovers an additional $2M annually. That's not a one-time gain. It compounds for as long as the rate is in effect, and it doesn't require finding new funding, winning new grants, or expanding programs. It requires examining the rate that's already in place and rebuilding it to what the cost reality and the federal framework will support.

Most organizations won't do this work because the rate they have is producing a number, the audit isn't flagging it, and there's no acute pressure to change it. The absence of pressure is exactly why the rate is wrong. Pressure surfaces problems. The absence of pressure allows structural problems to persist for years. Indirect cost rates are one of the cleanest examples of a financial structure that quietly underperforms in the absence of someone willing to do the rigorous work of re-examining it.

If your rate hasn't been rebuilt in the last three years, against current cost reality, with full attention to the methodology, the base, the allocation infrastructure, and the documentation, then your rate is almost certainly wrong. Not in a way that creates compliance risk. In a way that costs your organization money every single month.