Most foundations have a stated commitment to serving underinvested communities. Far fewer have examined whether their application processes, reporting requirements, and due diligence frameworks actively disadvantage the very communities they intend to reach. After two decades of working on both sides of the grantmaking table, I've seen how well-intentioned processes can create barriers that contradict institutional intent.
The gap between what organizations intend and what their processes actually produce is not a failure of commitment — it's a failure of design. And design failures can be fixed.
The Hidden Architecture of Exclusion
Consider the standard grant application. It typically requires audited financials, a board with specific composition, evidence of prior grants from institutional funders, and a theory of change articulated in the language of the funding community. Each of these requirements, reasonable on its own, compounds into a system that systematically favors organizations with existing access to resources and networks.
The question isn't whether your grantmaking criteria are defensible in isolation — it's whether the cumulative effect of all your criteria produces the outcomes you say you want.
Community-based organizations led by and for the populations most affected by inequity are often the least likely to meet traditional funder requirements — not because they lack effectiveness, but because the requirements were designed without them in mind.
Three Questions Worth Asking
Before redesigning your entire process, start with honest answers to three questions. First, who isn't applying — and why? If your applicant pool doesn't reflect the communities you've committed to serving, the application itself may be the barrier.
Second, what does your reporting actually measure? Reporting requirements often measure what's easy to count rather than what matters. If your grantees spend more time on compliance paperwork than on program delivery, you've created a system that optimizes for accountability theater rather than community outcomes.
Third, whose expertise counts? Review panels staffed exclusively by funders and academics will evaluate proposals differently than panels that include practitioners and community members. Lived experience is expertise. If it's absent from your decision-making process, your decisions will reflect that absence.
Moving from Language to Architecture
Equity statements are a starting point, not a destination. The real work is in the architecture — the policies, processes, and power structures that determine who gets funded, how much, and under what conditions. That architecture either produces equitable outcomes or it doesn't, regardless of what the mission statement says.
The organizations I've seen make genuine progress are the ones willing to audit their own processes with the same rigor they apply to their grantees. It's uncomfortable work. It's also the only kind that produces lasting change.