What Communities Keep: Governed Knowledge and the Afterlife of Health Projects

The project ends. What remains?

Picture a familiar arc. A university and a community partner win a grant. Over three years they build something genuinely useful: a screening tool, a dashboard, a set of trusted relationships, a body of local knowledge about what works in this particular place. The project is celebrated. Then the grant ends. The faculty lead moves to a new study, the data sits on a server no one maintains, the tool loses its updates, and the relationships, built on the presence of people who have now moved on, quietly dissolve. A year later, a new project arrives to solve the same problem, starting from zero.

This primer is about that arc and how to break it. The argument is that the recurring failure of community health work is not a failure of effort or insight but a failure of stewardship, and that the remedy is to design, in advance, for what the community keeps after the project ends. I call this governed knowledge infrastructure, and health is where its absence does the most visible harm.

The pattern of loss

Academic-community and civic health partnerships are unusually good at producing applied knowledge and unusually bad at keeping it. The reasons are structural, not personal. Grant funding is time-bounded and rarely pays for maintenance. Academic incentives reward the next publication and the next grant, not the long stewardship of the last one. The people who hold the relationships and the institutional memory are often temporary to the project. And the community that helped create the knowledge usually has no formal control over what happens to it once the partnership dissolves.

So the knowledge scatters. Tools lose maintenance and decay. Dashboards break and are not fixed. The hard-won understanding of a neighborhood's specific needs fades as the people who held it disperse. And the community is left, again, without practical control over something it helped build. This is not a rare misfortune. It is the default outcome, and it repeats because nothing in the standard arrangement is designed to prevent it.

Why health makes the stakes vivid

Every domain loses knowledge this way, but health makes the cost legible. When a community health worker program ends, the trust it built does not transfer to a database; it leaves with the workers. When a screening initiative ends, the understanding of which families are at risk and why does not persist; it has to be rebuilt, asking vulnerable people the same intrusive questions a second and third time. When a community data effort ends, the residents who shared sensitive information about their housing or their food security lose any say over what becomes of it.

Each restart is not neutral. It spends the community's patience, asks people to disclose again what they already disclosed, and teaches a hard lesson: that the help is temporary and the burden of starting over falls on them. The churn itself becomes a determinant of health, eroding the trust on which all community health work depends.

What governed knowledge infrastructure means

The remedy is to treat the applied knowledge a partnership produces as infrastructure that needs governance, designed before the spotlight arrives rather than improvised after it leaves. In practice this means deciding, at the outset, a small set of questions that projects usually defer until it is too late. Who stewards the tools, the data, and the relationships after the funding ends? Who is accountable to the people whose information and effort created them? What gets preserved, who may access it, and under what rules? Who maintains the technology, and how is that paid for?

These are not technical questions. They are governance questions, and answering them in advance is what lets applied knowledge stay alive, governed, and accountable across cohorts, grants, and administrations. The principle underneath is simple and, I think, just: communities deserve to keep what they helped create. A partnership that builds something valuable and lets it dissolve has, in a real sense, taken something from the community even as it tried to give.

What this means for community health infrastructure

The practical shift is to change what counts as success. A community health project should be judged not only by what it delivers while funded but by what survives it: the tools still maintained, the relationships still intact, the knowledge still governed and usable, the community still in control of what it built. Designing for that afterlife is harder than running a pilot, and it is the difference between a field that keeps relearning the same lessons and one that compounds them.

This is the Foundation's foundational concern, and health is where I find it clearest. The measure of a community health effort is what the community keeps. Build for that from the beginning, settle the stewardship before the work starts, and the benefits hold. Defer it, and the knowledge scatters on schedule, as it almost always has.

References

1. Editorial: Maximizing local government impact on community health initiatives. PMC. Community engagement enhances the relevance, effectiveness, and sustainability of public health interventions and fosters trust. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC12358446/

2. Actualising power sharing in community-led initiatives: insights from community-based organisation leaders in Chicago. PMC. The need for system-wide investment in an infrastructure for community-led public health; lessons from trust-based philanthropy. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC11283759/

3. City planning policies to support health and sustainability. The Lancet Global Health (2022). Integrated planning across levels of government and sectors as a condition for durable health gains. https://www.thelancet.com/journals/langlo/article/PIIS2214-109X(22)00069-9/fulltext

4. Standardizing social determinants of health data: a proposal for a comprehensive screening tool. Health Affairs Scholar (2024). Repeated, non-standardized screening burdens and the value of persistent, governed data. https://academic.oup.com/healthaffairsscholar/article/2/12/qxae151/7900047