Chapter 31: Grant Writing for Community Development — Funding That Builds Places and Power

Part V closes with community development — the work of building stronger, healthier, safer, more prosperous communities and places: revitalizing neighborhoods, developing affordable housing, fostering local economic opportunity, improving the physical and social environment, addressing environmental injustice, and building the capacity of communities to shape their own futures. It is work done in and for places — a neighborhood, a town, a rural region — and, the field has increasingly recognized, work that must be done by the people of those places to succeed and to last. Community development draws together many threads of this book — the localization principle of international funding (Chapter 21), the authentic equity and power-sharing of Chapter 25, the coalitions of Chapter 23, the place-based and community-rooted work we've glimpsed through RYCC and Lighthouse — into a distinctive funding world. This chapter is grant-writing for that distinctive world.

The organizing insight is the chapter's threshold concept: community proposals are written with the community, not about it. Community development is, by definition, work done by and for a community — so a proposal about a community, written by outsiders who studied it and designed solutions for it, fundamentally misunderstands the work and, increasingly, fails. The proposal that succeeds is one genuinely shaped by the residents and organizations of the community — written with them — carrying the legitimacy, the local knowledge, and the power that community development requires and that funders increasingly demand. This "with, not about" principle is the authentic-equity threshold of Chapter 25 and the localization threshold of Chapter 21, brought home to domestic place-based work: the community isn't the object of the development (something done to a place by outsiders) but its author and owner.

In this chapter we'll map the community-development funding ecosystem, develop the "with, not about" principle, ground proposals in a resident-led and asset-based community needs assessment, structure coalition and partnership proposals for place-based work, confront the distinctive sustainability challenge where there's no tax base, and address the dual goal of building both places and community power. Our anchors are community-based organizations doing place-based work — Lighthouse (whose reentry work is community development in the human sense, helping returning citizens rebuild lives and, through them, strengthening the neighborhoods they return to) and RYCC (rooted in its under-resourced neighborhood, serving its young people) — alongside a new composite, the Northside Community Coalition, a neighborhood coalition of residents and community organizations pursuing revitalization on its own terms. (As always, community-development funding varies by place, program, and time; verify specifics with your funders.)

31.1 The Community-Development Funding Ecosystem

Community development draws on a distinctive ecosystem heavy with public place-based funding and community-rooted philanthropy. Orienting to it reveals the landscape.

Federal place-based programs. Several federal programs fund community and economic development, often flowing through states and localities (Chapter 19's pass-through structure). The Community Development Block Grant (CDBG) program is a cornerstone — federal funds distributed to states and localities for community development, housing, and economic-development activities benefiting low- and moderate-income communities. HUD funds housing and community development broadly; USDA Rural Development funds community and economic development in rural areas; the EPA funds environmental justice work (addressing the disproportionate environmental burdens on marginalized communities); and various federal programs fund economic development, infrastructure, and community capacity. Much of this money is administered locally, so — as Chapter 19 stressed — you watch your state and local governments, not only federal sites.

🎓 Going Deeper — how CDBG actually reaches a community: The Community Development Block Grant is worth understanding in some detail, because it's the cornerstone of place-based public funding and its structure shapes how community organizations access it. CDBG is a federal program, but the money flows to states and localities: larger cities and urban counties receive CDBG funds directly as "entitlement" communities, while smaller places receive funds through their state's CDBG program (the pass-through structure of Chapter 19). The locality or state then decides how to use its CDBG money — and crucially, those decisions are made through a local planning process that typically requires citizen participation. This means a community organization's path to CDBG funding often runs through local government: the city or county allocates its CDBG funds to activities and sometimes subgrants to community organizations, guided by a consolidated plan developed with public input. The practical implications are significant. First, engage your local government's CDBG process — attend the public hearings, get on the planning radar, understand the local priorities, because that's where CDBG allocation decisions are made. Second, CDBG funds must benefit low- and moderate-income communities (a core requirement) and meet national objectives, so your project must fit those parameters. Third, because the decisions are local and participatory, the "with, not about" principle and resident voice matter at the local-government level too — organized residents shaping the local CDBG plan is community power in action. Understanding that CDBG is federal money allocated through a local, participatory process tells you where to engage (local government), what's required (benefit to low/moderate-income communities), and why community voice matters at every level.

Community development financial institutions (CDFIs). A distinctive feature of this sector: CDFIs are specialized institutions that provide loans and financial services to underserved communities, supporting community and economic development through financing (not only grants). For community-development organizations, CDFIs are part of the capital ecosystem.

Community foundations and place-based philanthropy. Community foundations (Chapter 18) are central to community development — they exist to strengthen specific places and often anchor local community-development funding. Place-based philanthropy — funders who concentrate their giving on a particular place and its long-term flourishing — is increasingly important, and these funders often deeply value resident leadership and the "with, not about" principle.

Local government and anchor institutions. Cities, counties, and local anchor institutions (hospitals, universities, and large employers) fund and partner on community development in their own areas, increasingly recognizing a stake in the health of the communities around them.

📊 From the Field: Environmental justice is a fast-growing and instructive corner of community-development funding, and it sharply illustrates the chapter's themes. Environmental justice addresses the reality that environmental burdens — pollution, contamination, lack of green space, climate vulnerability — fall disproportionately on low-income communities and communities of color, often as a direct legacy of discriminatory decisions (where highways, industrial facilities, and waste sites were sited). Funders, including the EPA and many foundations, increasingly support community-led environmental-justice work — and the operative word is community-led. An environmental-justice proposal exemplifies "with, not about": the affected residents, who live the environmental burden and often know its sources and effects better than any outside expert, must lead the analysis and the response, both because their knowledge is essential and because the harm came precisely from decisions made about them without their voice. So environmental-justice funding tends to reward proposals where the community's own residents and organizations identify the environmental problems they face, shape the response, and hold leadership — the asset-based, resident-led, community-authored approach this chapter describes, applied to environmental harm. For a community-development organization, environmental justice is a growing funding area that rewards exactly the community-led practices the threshold concept demands — a reminder that across community development's many sub-areas (housing, economic development, environment, health), the constant is the community as author and leader of work done with it, not to it.

🧩 Productive Struggle: Before reading on, consider why community-development funding, more than almost any other kind in this book, has moved toward demanding resident leadership and community voice — why funders increasingly insist that the community shape the work rather than have it designed for them. Jot your thinking. The resolution, which is this chapter's core, is that community development has learned, often painfully, that work done to communities by outsiders frequently fails or harms — top-down revitalization that displaces residents, "solutions" that don't fit local realities, projects that collapse when the outside funder leaves because the community never owned them. The field's hard-won lesson (echoing the localization reckoning of Chapter 21 and the authentic-equity insight of Chapter 25) is that lasting community development must be led by and owned by the community — so funders increasingly demand the resident voice and community ownership that the "with, not about" threshold describes. The history of failed top-down development is exactly why this principle now governs the field.

31.2 Written With the Community, Not About It

Now the threshold concept, the heart of community-development grant-writing. Because community development is work by and for a community, the proposal must genuinely be of the community — written with residents and community organizations, not about the community by outsiders.

🚪 Threshold Concept: Community proposals are written with the community, not about it. A proposal written about a community — by an outside organization, consultant, or institution that studied the community and designed solutions for it — fundamentally misunderstands community development, which is by definition community-led work. Such a proposal lacks the legitimacy (the community didn't author it), the knowledge (outsiders miss what residents know), the ownership (the community won't sustain what it doesn't own), and increasingly the fundability (funders demand resident voice). A proposal written with the community — genuinely shaped by residents and local organizations who identified the needs, designed the approach, and hold real roles and power in the work — carries all of these. Cross this threshold and you stop asking "how do I write a good proposal about this community's problems?" and start asking "how do we, with the community, write a proposal that the community authors and owns?" The shift from about to with — from community-as-object to community-as-author — is the defining move of community-development grant-writing, and it is the authentic-equity (Chapter 25) and localization (Chapter 21) thresholds applied to domestic place-based work.

What does "with, not about" look like in practice? It means residents and community organizations are genuinely involved in identifying the needs (the resident-led needs assessment, Section 31.3), designing the approach (the community shapes the solution, not just receives it), holding roles and power in the work (residents and local organizations lead and deliver, not just participate), and authoring the proposal itself (the proposal reflects the community's voice, priorities, and language, not an outsider's framing). The Northside Community Coalition's revitalization proposal, done right, is shaped throughout by Northside residents — their priorities, their knowledge of the neighborhood, their leadership — not written by a distant consultant who interviewed a few people and designed a plan. The community is the author; the proposal is theirs.

📜 How We Got Here: The "with, not about" principle is the field's response to a long, often painful history of community development done to communities by outsiders — a history worth knowing because it explains why funders now insist on community leadership. Much twentieth-century "development" was top-down: urban renewal that demolished functioning (if poor) neighborhoods and displaced their residents; outside experts designing "solutions" disconnected from local realities; well-intentioned programs that treated communities as passive recipients and collapsed when the outside resources left, because the community never owned them. The damage — displacement, broken trust, failed projects, the disempowerment of communities treated as problems rather than partners — taught the field a hard lesson: development imposed on a community, however expert or well-meaning, frequently fails and sometimes harms, while development led and owned by a community endures and empowers. Out of this reckoning grew the principles of this chapter — resident leadership, asset-based community development, community ownership, "with, not about" — and the movements (community organizing, the resident-leadership and community-power movements, the equity and localization reckonings of Chapters 21 and 25) that insist communities author their own futures. Understanding this history reframes the "with, not about" principle from a fashionable preference into a hard-earned lesson: it's how the field corrected for decades of damage done by development done to people. Funders demand community leadership now because the alternative has been tried, at great cost, and found wanting.

Contrast two versions of the Northside revitalization proposal to see the difference concretely (composite). The "about" version: a large regional development institution, seeing Northside's disinvestment, commissions a study, hires a consultant who interviews a few residents, and designs a revitalization plan — new mixed-use development, a commercial corridor strategy, infrastructure improvements. The plan is polished and expert. But it was written about Northside by outsiders; residents were consulted, not leading; the priorities reflect the institution's assumptions (and its development interests) more than residents' actual concerns (which, it turns out, center on displacement fears the plan ignores); and Northside's residents have no ownership of a plan that will be done to their neighborhood. The "with" version: the Northside Community Coalition — anchored by community-rooted organizations like RYCC and Lighthouse and led by resident leaders — conducts a resident-led needs assessment (Section 31.3), surfaces the community's own priorities (anti-displacement protections, local jobs, youth opportunity, a community-owned space), designs an approach residents shaped, holds residents in genuine leadership of the work, and authors a proposal in the community's own voice. It's less polished, perhaps — but it's Northside's, carrying the legitimacy, local knowledge, and ownership the institution's plan lacks. A localization-minded funder funds the second, because the field has learned that the first kind, however expert, is done to a community that never owned it and collapses when the institution moves on. The difference isn't polish; it's authorship.

🪞 Learning Check-In: This is the place to examine your own position honestly, especially if you come from an outside organization, institution, or consultancy that works "in" communities. Notice any habit of seeing the community as the subject of your work — people to be studied, helped, developed — rather than as the authors and owners of their own development. The "with, not about" principle asks you to genuinely cede authorship and power to the community, which can be uncomfortable for organizations used to driving the work. But the discomfort is the point: community development done to people, however well-meaning, is exactly what the field has learned doesn't last and often harms. If you find your proposal is really about a community you've studied rather than with a community that authored it, that's the signal to do the harder, realer work of genuine resident leadership — not because funders demand it (though they increasingly do), but because it's what makes community development actually work. The community's flourishing is theirs to author.

31.3 The Community Needs Assessment: Resident-Led and Asset-Based

The foundation of a community-development proposal is the community needs assessment — the understanding of the community's needs, conditions, and priorities that grounds the work. But how it's done embodies the threshold concept, and what it looks for shapes everything.

Resident-led. A genuine community needs assessment is led by and conducted with residents, not done to them by outside experts. Residents identify what they see as the community's needs and priorities — which often differ from what outsiders assume — through processes the community shapes (community meetings, resident surveys residents help design, listening sessions, participatory mapping). This resident-led assessment is both more accurate (residents know their community) and more legitimate (the community owns the analysis), and it's the practical embodiment of "with, not about" (Section 31.2).

Asset-based, not only deficit-based. A crucial discipline: a strong community needs assessment is asset-based — it identifies the community's strengths, assets, resources, and capacities, not only its deficits and problems. This is the asset-based community development (ABCD) principle: communities are not merely bundles of problems to be fixed but possess real assets — skilled residents, local organizations, cultural strengths, relationships, institutions — that development should build on. A purely deficit-based assessment (the community as nothing but problems) reproduces the savior narrative (Chapter 25) and misses the assets that make development possible; an asset-based assessment sees the community's strengths alongside its real challenges (often externally imposed), and designs development that builds on those assets. The Northside assessment, done right, documents Northside's assets — its engaged residents, its existing organizations (like RYCC and Lighthouse), its cultural strengths, its relationships — alongside the real barriers, and designs revitalization that builds on them.

💡 Key Insight: The asset-based approach isn't just more respectful — it's more effective and more sustainable, because development that builds on a community's existing assets and capacities is development the community can own and sustain, while development that treats the community as an empty problem to be solved by outside resources collapses when those resources leave. When the Northside Coalition's plan builds on Northside's existing organizations, leaders, and strengths, it creates something rooted that can endure; when an outside plan imports solutions disconnected from local assets, it creates dependency that ends with the grant. So the asset-based lens (seeing and building on community strengths) and the "with, not about" principle (community authorship) work together toward the same end: development that the community owns, drives, and sustains. Find and build on the assets, and you build something that lasts; ignore them and import solutions, and you build something that ends.

🔄 Check Your Understanding: An outside organization conducts a community needs assessment for a disinvested neighborhood by gathering statistics on poverty, crime, unemployment, vacancy, and health disparities — producing a thorough, data-rich portrait of the neighborhood's problems. Why might this assessment, despite its rigor, undermine genuine community development, and what's missing?

Answer

The assessment is purely deficit-based and done about rather than with the community — and both are problems. By portraying the neighborhood as nothing but a collection of problems (poverty, crime, vacancy), it reproduces the savior narrative (Chapter 25): the community as a bundle of deficits awaiting outside rescue, stripped of its strengths and agency. What's missing is the asset-based lens (ABCD, Section 31.3) — the neighborhood's real assets (engaged residents, existing organizations, cultural strengths, relationships, local institutions) that development must build on to be sustainable — and the resident-led process that would surface the community's own priorities (which often differ from what the statistics suggest) and give the community ownership of the analysis. A development effort built on this deficit-only, outsider-conducted assessment will likely import solutions disconnected from local assets and priorities, creating dependency that collapses when the outsiders leave. The fix: a resident-led assessment that documents the community's assets alongside its real (often externally-imposed) challenges, owned by the community — the operational form of "with, not about" and the foundation of development the community can sustain.

📐 Project Checkpoint — Draft a resident-engagement plan: For a community-development project (real or imagined), draft a resident-engagement plan that embodies "with, not about." (1) How residents will lead the needs assessment — the processes (meetings, resident-designed surveys, listening sessions) through which residents identify their own priorities, conducted with them, not done to them. (2) An asset-based lens — how you'll identify and build on the community's strengths, assets, and existing organizations, not just its deficits (avoiding the savior narrative, Chapter 25). (3) Resident roles and power in the work — how residents and local organizations will hold genuine leadership and decision-making roles, not just participate. (4) How the community authors the proposal — how its voice, priorities, and language shape the proposal itself. Save it in your "My Proposal" document. The resident-engagement plan is the operational form of the threshold concept — and increasingly, what community-development funders most want to see.

31.4 Coalition and Partnership Proposals

Place-based community development almost always requires many organizations working together, because no single organization addresses everything a community needs — so community-development proposals are frequently coalition or partnership proposals, bringing together the multiple actors a place-based effort requires (the collaboration craft of Chapter 23, place-based).

A community's challenges are interconnected — housing, jobs, education, health, safety, environment — and addressing them requires the coalition of organizations that collectively serve the community: the housing organization, the workforce program (like Lighthouse), the youth program (like RYCC), the health center, the resident association, the local government, the anchor institutions. A community-development proposal often knits these together into a coordinated effort, with the coalition as the applicant or a lead organization coordinating partners (Chapter 23's structures).

This makes the coalition craft of Chapter 23 central: justify each partner by the necessary capability they bring; structure the coalition with clear leadership and coordination; document partnerships with MOUs (memoranda of understanding) and commitment letters; and — the threshold concept — ensure the coalition genuinely includes and is led by community organizations and residents, not just large institutions. A community-development coalition that is really a few big institutions with residents as window-dressing fails the "with, not about" test; one genuinely led by and including community-rooted organizations and residents embodies it. The strongest community-development coalitions are of the community — anchored by the community-based organizations and resident leaders who know and represent the place — with larger institutions adding specific capabilities in genuine partnership (the localization-style power-sharing of Chapter 21, domestically).

✅ Best Practice: Put residents and community-based organizations in genuine leadership of the coalition — with real authority, real budget, and real decision-making roles — and resource their participation, just as the equity chapter urged (Chapter 25). A frequent failure of community-development coalitions is that large institutions (a university, a hospital, a regional nonprofit) hold the lead role, the money, and the decisions, while the community-based organizations and residents are subcontracted to "do outreach" or "engage the community" — the decorative-partnership failure that funders increasingly penalize. The strong version inverts this: community-rooted organizations and resident leaders hold genuine coalition leadership (perhaps a community organization as the lead applicant, or residents on the governing body with real authority), the budget genuinely flows to community organizations and compensates resident leaders for their time and expertise, and the larger institutions contribute specific capabilities (fiscal capacity, technical expertise, connections) in service of the community's leadership rather than controlling it. When you build a community-development coalition, ask the localization questions (Chapter 21): who leads, who decides, who holds the money, whose knowledge shapes the work? If the honest answers put the community at the center — leading, deciding, resourced, authoring — you have a genuine community-led coalition; if they put outside institutions at the center with the community as junior partners, you have the done-to arrangement the field has learned to distrust. Resource and empower the community's leadership of the coalition; don't just invite the community to participate in someone else's.

🗣️ From the Review Panel: (A community-development funder reflects.) I fund places, and I've learned to read a proposal for one thing above all: is this genuinely community-led, or is it being done to a community by people who don't live there? The tells are clear. A community-led proposal reflects residents' actual priorities (not an outsider's assumptions), is anchored by organizations rooted in the community, shows residents in real leadership and decision-making roles, and builds on the community's assets, not just its deficits. A done-to proposal reads as an outside institution's plan for a community it studied — residents consulted but not leading, a needs assessment full of deficits and no assets, a coalition of big institutions with a token community partner. I fund the first kind, because the field has taught us the hard way that the second kind doesn't last — it collapses when we leave, because the community never owned it. Show me the community authoring and leading its own development, building on its own strengths, and I'll invest; show me a plan about a community, and I won't.

31.5 The Sustainability Challenge Where There's No Tax Base

Community development faces a distinctive sustainability challenge (Chapter 14, place-based): the communities that most need development are often those with the least local resources — no strong tax base, limited local wealth, few earned-revenue opportunities — which makes the "what happens after the grant?" question especially acute.

A nonprofit can sometimes build earned revenue or diversify donors (Chapter 28); a community-development effort in a disinvested neighborhood may have far fewer such options, because the community's economic weakness is precisely the problem being addressed. So community-development sustainability often must be reconceived. Building capacity and power, not just projects (Section 31.6) — development that strengthens the community's own organizations, leaders, and capacity creates a lasting foundation even where a tax base doesn't. Leveraging multiple and ongoing public sources — place-based public funding (CDBG and others) is often ongoing, so a community-development effort may sustain through continued public funding rather than becoming self-sufficient. Building assets that generate value — some community development creates lasting assets (affordable housing that generates rents, community-owned enterprises that earn revenue, a community land trust that holds property permanently affordable, a CDFI's revolving loans that recycle capital) that generate ongoing value and reduce dependence on future grants. These asset-building strategies are especially powerful because the assets stay in and benefit the community over the long term. Systems and policy change — sometimes the most sustainable outcome is changed systems or policies that continue benefiting the community without ongoing project funding. And honestly, community development sometimes requires sustained external investment — addressing deep, structural disinvestment may legitimately require ongoing support rather than a quick path to self-sufficiency, and the honest sustainability case acknowledges this rather than promising an unrealistic exit.

🔍 Why Does This Work?: Why is "building the community's own capacity and power" often the most realistic sustainability answer where there's no tax base, rather than the usual nonprofit path of earned revenue or diversified donors? Because in a deeply disinvested community, the absence of local economic resources is the very problem being addressed — so expecting the community-development effort to quickly become financially self-sufficient from local sources is often unrealistic, even contradictory (if the community had the resources to sustain it, it might not need the development). What development can durably build, even where money is scarce, is the community's own capacity and power: stronger community organizations, developed local leaders, residents organized to advocate for their own interests, systems and relationships that persist. This capacity and power continue working for the community after a specific grant ends — securing the next resources, sustaining the organizations, advancing the community's interests — even if the community can't simply fund itself from a local tax base. So reframing sustainability as building lasting community capacity and power (rather than narrow financial self-sufficiency) is both more honest and more achievable in disinvested places — and it connects to the chapter's deeper point: community development builds not just places, but the power to keep building them.

31.6 Building Places and Power

This brings us to the chapter's deepest theme, captured in its subtitle: community development funds work that builds both places and power. The physical and economic development — housing, businesses, infrastructure, services — is the visible work. But the most lasting community development also builds the community's power and capacity — its ability to organize, advocate, lead, and shape its own future.

The two are connected. Physical development without community power can be done to a community and can even harm it (top-down revitalization that displaces residents). Community power without resources can't build the physical places. The strongest community development builds both: it develops the places and strengthens the community's capacity to drive its own development — the organizations, the leaders, the organized residents who will continue shaping the community long after any grant. This is why "with, not about" matters so deeply: a proposal written with the community doesn't just produce a better plan; it builds the community's power in the act of authoring and leading the work. The process is part of the outcome.

For the grant writer, this means framing community-development proposals around both the tangible place-based outcomes (the housing built, the jobs created, the neighborhood improved) and the community-capacity outcomes (the leaders developed, the organizations strengthened, the residents organized, the power built). Funders increasingly value both — and the most sophisticated community-development proposals show how the work builds the community's lasting capacity to shape its own future, not just a one-time physical improvement. Building places and power is the full ambition of community development, and the proposal that captures both — tangible improvements that also strengthen community capacity, authored by the community itself — is the one that embodies the field at its best.

📊 From the Field: The "places and power" framing resolves a tension community-development organizations often feel. Funders want tangible outcomes (units of housing, jobs created, measurable improvements) — but the deepest community-development work is the harder-to-measure building of community capacity and power, which doesn't fit neatly into output counts. The resolution isn't to abandon either, but to show how they connect: the tangible outcomes (the housing, the jobs) are real and worth funding, and they're achieved through a process that builds lasting community capacity (residents who led the housing effort are now organized to lead the next one; the coalition built to create jobs is now a durable community institution). The strongest proposals present the tangible places-outcomes that funders can count and the power-outcomes that make the work last — showing they reinforce each other. So when you write a community-development proposal, capture both: the countable improvements to the place, and the lasting strengthening of the community's capacity to keep improving it. The places give funders the concrete results they need; the power gives the work its durability and its deepest value. Together, they are community development at its fullest.

31.7 Strategy: Author With the Community, Build Places and Power

Pull the threads together into community-development strategy, closing Part V. Orient to the ecosystem (CDBG and place-based public funding, HUD/USDA/EPA programs, CDFIs, community foundations, place-based philanthropy — much administered locally); above all, write with the community, not about it — genuine resident leadership and community authorship throughout; ground the proposal in a resident-led, asset-based community needs assessment; structure coalition proposals genuinely led by community-rooted organizations and residents; address the distinctive sustainability challenge honestly (building capacity and power, leveraging ongoing public sources, creating lasting assets, sometimes acknowledging the need for sustained investment); and frame the work around building both places and power. Above all, hold the threshold concept: community proposals are written with the community, not about it.

Community development is the fullest convergence of Part V's and the book's deepest themes:

What unifies them is the community as author and owner. The community-development grant writer who internalizes that the work is the community's own — authored with residents, built on the community's assets, led by community-rooted organizations, building both places and lasting power — has the frame that makes this work both fundable and genuinely transformative. The deepest community development isn't done to a place by outsiders; it's the community building its own future, with grants as one resource the community marshals toward a flourishing it authors and owns. That is community development at its best, and the grant writer's role is to help the community make its own case — with it, never merely about it. This reframes the grant writer's very identity in community development: not the expert who writes for a community, but a skilled ally who helps the community articulate and fund the future it authors — putting their craft in service of community leadership rather than substituting for it. The best community-development grant writers are often those most willing to cede the authorial role, to amplify rather than replace community voice, and to measure their success by how much the community owns the work, not by how impressive their own writing is.

This also brings Part V to its close. Across five sectors — academic researchers, nonprofits, K-12 educators, artists, and now community developers — you've seen the universal craft of Parts I–IV adapted to each world's distinctive realities. The threshold concepts varied (fund a program; diversify the stool; start small and build; make the vision reviewable; write with the community), but beneath them ran a constant: grant-writing always serves something larger than the individual proposal — a research program, a healthy organization, a student's future, a creative vision, a community's flourishing. Part VI now synthesizes the whole book into a toolkit, a sustainable funding strategy, a capstone, and a view of the grant writer's career.

🔄 Check Your Understanding: Two organizations seek funding for the same neighborhood's revitalization. An outside institution submits a polished, expert-designed plan; a community coalition submits a less polished plan genuinely authored by residents. A localization-minded community-development funder favors the coalition. Name two reasons, from this chapter, why.

Answer

Several are valid. Two clear ones: (1) "With, not about" / community authorship and ownership — the coalition's plan is genuinely authored and led by the residents and community-rooted organizations of the neighborhood (carrying the legitimacy, local knowledge, and ownership that make community development last), while the outside institution's plan, however polished, is written about the community by people who don't live there and won't be sustained because the community never owned it — the threshold concept, and the field's hard-learned lesson that done-to development collapses when the outsiders leave. (2) Building power, and asset-based development — the community-authored plan builds the community's own capacity and power in the act of authoring and leading it (developing leaders, strengthening organizations, organizing residents) and builds on the community's existing assets, while the expert plan delivers a physical project without building the community's lasting capacity and may treat the community as a bundle of deficits to be fixed by outside expertise — missing both the power-building and the asset-based foundation that make development durable. Both reflect the threshold: community development is the community's own work, authored with it, building places and power — not an outside plan imposed about a place. (Also acceptable: the resident-led, asset-based needs assessment vs. an expert deficit analysis; a coalition of community organizations vs. an outside institution; honest place-based sustainability through capacity vs. a project that ends with the grant.)

Spaced Review

Retrieve these from earlier chapters without looking back, then check against the collapsed answers.

1. (From Chapter 21) How is the "with, not about" principle of community development the domestic expression of the localization / local-leadership threshold of international funding?
2. (From Chapter 25) How does asset-based community development (ABCD) connect to Chapter 25's asset-based, agency-centered framing and the rejection of the savior narrative?
3. (From Chapter 23) How does the coalition craft (Chapter 23) apply to community-development proposals, and what does the threshold concept add to it?

Answers

1. Localization (Chapter 21) insists that power, money, and leadership shift toward the local communities affected by international development, rather than work being done for them by outside intermediaries who keep control; "with, not about" is exactly this principle applied to domestic place-based work — the community authors and leads its own development rather than having it designed and controlled by outside institutions, so both reject development done to a community in favor of development led and owned by it. 2. ABCD's insistence on identifying and building on a community's assets and strengths (not only its deficits and problems) is the same move as Chapter 25's asset-based, agency-centered framing that rejects the savior narrative: both refuse to see a community as nothing but problems to be fixed by outsiders, instead recognizing its real strengths, capacities, and agency — and both produce more respectful, more accurate, and more sustainable work, because development that builds on community assets (like a proposal that centers community agency) creates something the community owns rather than depends on. 3. Chapter 23's coalition craft (justify each partner by necessary capability, clear leadership and coordination, MOUs, evidence of working together) applies directly, since place-based work requires the coalition of organizations a community needs; the threshold concept adds that the coalition must genuinely be of and led by the community — anchored by community-rooted organizations and residents, not big institutions with token community partners — so a community-development coalition isn't just any working team but one that embodies "with, not about" through genuine community leadership of the coalition itself.

Chapter Summary

Key Takeaways

• Community development builds stronger places — neighborhoods, towns, regions — and increasingly is done by the people of those places. It converges localization, authentic equity, coalitions, and place-based work.
• Threshold concept: community proposals are written with the community, not about it. A proposal about a community (designed by outsiders) misses the point and increasingly fails; one written with the community (genuinely authored and led by residents and community organizations) carries the legitimacy, knowledge, ownership, and fundability community development requires.
• The ecosystem is place-based and public-heavy: CDBG, HUD, USDA Rural Development, EPA environmental justice, CDFIs, community foundations, and place-based philanthropy — much administered locally (watch state/local governments).
• Ground the proposal in a resident-led, asset-based community needs assessment — residents identify their own priorities, and the assessment builds on the community's assets (ABCD), not just deficits (avoiding the savior narrative).
• Structure coalition proposals (Chapter 23) genuinely led by community-rooted organizations and residents, not big institutions with token community partners.
• Address the distinctive sustainability challenge where there's no tax base — build capacity and power, leverage ongoing public sources, create lasting assets, and honestly acknowledge when sustained investment is needed.
• Build both places and power — tangible place-based outcomes and the community's lasting capacity to shape its own future; the process (authoring with the community) is part of the outcome.

Action Items

1. Write with the community — genuine resident leadership and community authorship throughout, not a plan about a community.
2. Conduct a resident-led, asset-based needs assessment — residents identify priorities; build on community assets, not just deficits.
3. Structure a community-led coalition — anchored by community-rooted organizations and residents; document with MOUs.
4. Address sustainability honestly — capacity and power, ongoing public sources, lasting assets; acknowledge needed investment.
5. Frame around places and power — tangible outcomes and lasting community capacity.

Common Mistakes

• Writing about a community — an outside-designed plan with residents consulted but not leading (the threshold failure).
• A purely deficit-based needs assessment (the savior narrative) instead of an asset-based one.
• A coalition of big institutions with a token community partner, rather than one genuinely community-led.
• Promising unrealistic financial self-sufficiency where there's no tax base, instead of an honest capacity-and-power sustainability case.
• Funding only places (physical outcomes) while ignoring power (community capacity) — building things to a community rather than its capacity to build for itself.

Decision Framework — "Is this genuinely community development?"

1. Is it written with the community, not about it? → Residents and community organizations authoring and leading, not consulted window-dressing?
2. Is the needs assessment resident-led and asset-based? → Community identifying its own priorities; building on assets, not just deficits?
3. Is the coalition genuinely community-led? → Anchored by community-rooted organizations and residents, with institutions in genuine partnership?
4. Is the sustainability case honest? → Capacity and power, ongoing sources, lasting assets — not unrealistic self-sufficiency?
5. Does it build places and power? → Tangible outcomes and lasting community capacity to shape its own future?

🔁 Carry this forward: Community development closes Part V, and with it the sector tour. Across five sectors you've seen the universal craft adapted to each world's realities, beneath which ran one constant: grant-writing serves something larger than any proposal. Part VI now synthesizes the whole book — the grant writer's toolkit (Chapter 32), building a sustainable funding strategy (Chapter 33), the capstone where you complete your own proposal (Chapter 34), and the grant writer's career (Chapter 35). The journey turns from learning the craft to building a life and practice with it.