HomeCommunityCommunity gardensHouses of worship

Community gardens · School and institutional gardens

Garden Programs for Houses of Worship

The garden should belong to the institution, not disappear with one ministry leader.

Churches, synagogues, mosques, temples and other houses of worship may have land, kitchens, food pantries, volunteers, youth programs and strong community relationships. Those are real assets. They also create institutional responsibilities: property authority, insurance, weekday access, money handling, safeguarding, garden rules, food distribution, grounds coordination and leadership succession. A durable garden program makes those responsibilities explicit before the first bed is built.

General U.S. guidance. Property authority, denominational or organizational policy, insurance, youth safeguarding, public access, food distribution, permits and tax/accounting treatment vary by institution and jurisdiction.

The five-minute answer

First decide what kind of garden the institution is actually sponsoring.

NC State describes faith communities as sponsors that may provide land, money, leadership or organizational support. Its faith-community training emphasizes leadership teams, secure permission, insurance review, garden management rules, shared responsibility and integration with the congregation's broader life. The first institutional decision is therefore not what to plant. It is what the garden exists to do and who has authority to operate it.

Allotment garden

Individuals or families manage assigned plots, with shared rules, common-area duties and clear eligibility/access.

Communal donation garden

Volunteers grow together and route most or all harvest to a pantry, meal program or outside recipient.

Mixed model

Personal plots plus shared donation, teaching, pollinator or community beds.

Partner-hosted garden

The institution supplies land or facilities while another nonprofit or organized group operates part of the program under written authority.

Put the model in writing.

Purpose, eligibility, authority, money, access, shared work, harvest destination and leadership succession should not be left to oral tradition.

Capability promise

After this guide, a congregation or host organization should be able to operate the garden as a real program rather than an informal side project.

Identify the governing body or authorized leader that can approve land use, spending and long-term commitments.
Choose an allotment, communal, mixed or partner-hosted model and write its participant rules.
Verify insurance, permits, utilities, facilities coordination and public-access boundaries.
Create volunteer and youth/safeguarding controls appropriate to the host institution.
Keep garden money inside the host's authorized financial controls and records.
Build a donation or pantry relationship around recipient needs rather than surplus dumping.
Schedule recurring steward coverage between workdays and services/events.
Create a succession packet that survives clergy, staff, board, committee and ministry-leader turnover.

The institutional distinction

Hosting land is not the same as operating the garden.

A house of worship may be the property owner, program sponsor, financial custodian, insurer, food-pantry operator, youth-program host and public-facing organization all at once. Or it may do only one of those things. Write the relationships down so volunteers know which decisions belong to the garden team and which require the institution.

QuestionGarden team may handleInstitution should control or formally delegate
Crop plan / ordinary garden workUsually, within written rulesRestrictions involving property, pesticide/IPM, facilities or mission policy
New fence, shed, trench, irrigation or electrical workRecommend / scopeProperty approval, permits, utilities, contractor authority and budget
Garden fees and donationsTrack garden purpose / approved budgetReceipt, deposit, spending authority and accounting system
Youth / vulnerable-person participationPlan appropriate tasksSafeguarding, screening, supervision and incident procedures
Public / neighbor accessRecommend hours and garden etiquetteProperty-access policy, keys/gates, security, liability and event rules
Pantry / meal distributionGrow, harvest and record under approved processRecipient acceptance, food handling, kitchen/pantry rules and institutional partner agreement

The procedure

A twelve-step house-of-worship garden program.

Name the purpose without making the garden carry every ministry goal.

A garden can support congregational fellowship, practical education, neighborhood relationships, individual plots, food donation, youth learning or stewardship of property. NC State's faith-community training recommends connecting the garden to the host's values and mission. Translate that into operating goals. If the garden tries to be a pantry farm, children's program, neighborhood allotment, meditation space and fundraising event simultaneously, responsibilities become unclear.

Identify the real authorizing body.

Do not assume the clergy leader, facilities chair or volunteer gardener can unilaterally commit institutional land or money. Houses of worship have different governance structures. Record who can approve property use, budget, insurance, construction, outside partnerships, public access and program policies. On institution-owned land, an external lease may not be needed, but internal authorization still should be documented.

Form a garden team that includes gardeners and institutional stakeholders.

NC State's faith-community training recommends actual gardeners, people with varied skills, clergy/lay leadership, grounds volunteers and youth leaders where relevant. Include someone who understands facilities and someone who understands the host's financial/administrative system. Avoid a committee made entirely of people who support the idea but will not maintain it.

Choose the participation and harvest model.

Decide whether plots are for members, neighborhood residents, a defined service population or a broader public application pool; whether the garden is communal; whether personal plots may donate voluntarily; and which beds are dedicated to pantry/meal partners. If nonmembers may participate, state access hours, fees, expectations and whether religious-program participation is separate from garden eligibility so prospective gardeners understand the arrangement before joining.

Approve the site, insurance and facilities interface.

Use the standard site-history, soil, water, accessibility and utility procedures. NC State's faith-community training specifically advises checking whether the institution's insurance covers garden activity and checking local permits. Coordinate mowing, spraying, snow removal, parking, funerals/weddings/services, maintenance access and special events so the garden does not conflict with normal property operations.

Write garden rules and institutional boundaries.

For allotments, use written plot agreements covering use, maintenance, common work, water/tools, end-of-season cleanup, permitted materials, behavior and consequences. For communal gardens, write the shared-maintenance and harvest system. Avoid copying another congregation's rule about fees, attendance or volunteer hours without asking whether it fits your participants, access goals and host policy.

Put money through the institution, not a volunteer's pocket.

Garden fees, designated gifts, grants and purchases should follow the house of worship's authorized receiving, depositing, spending and recordkeeping process. IRS guidance says tax-exempt organizations, including churches and religious organizations, must maintain records needed to support activities, receipts and expenditures even though many churches are excepted from the annual Form 990 filing requirement. Use the host's finance system and checks/balances rather than a personal payment account.

Separate workdays from routine stewardship.

NC State's faith-community model uses larger collaborative workdays plus rotating stewards for ordinary watering, pest checks and harvest between them. That is a strong institutional pattern: worship-week announcements may recruit a crowd for a Saturday workday, but recurring maintenance still needs named weekday coverage and handoff notes.

Use the host's safeguarding rules for children and youth.

A garden activity does not suspend existing youth-ministry or volunteer policies. NC State notes that youth programs sponsored by churches and other organizations may require volunteer registration or background checks. Use the institution's actual supervision, screening, permission, transportation, restroom, photography and incident-reporting requirements rather than inventing a separate garden system.

Build the food pathway around the recipient.

NC State reports that faith-community gardens often pair naturally with food pantries and can use congregation volunteer bases effectively. Its examples also show why coordination matters: ask pantries what produce they want, harvest near distribution time, package in useful amounts and coordinate among recipients to reduce waste. Use Produce Donation Systems rather than treating the pantry as a place to unload whatever became surplus.

Place the garden on the institutional calendar.

Schedule opening/renewal, water startup, workdays, steward rotation, youth activities, pantry harvesting, budget review, insurance/land review, seasonal cleanup and leadership handoff around the host's actual worship, holiday, building-use and fiscal calendars. Avoid assuming Sunday or another weekly gathering is automatically the best maintenance day. The garden is a seven-day physical system even when the institution gathers less often.

Build succession beyond clergy and ministry turnover.

Record land authorization, insurer/contact, facilities decisions, account/budget location, keys/access, water shutoff, garden roster, pantry partners, recurring vendors, rules and annual calendar where authorized leaders can retrieve them. Use co-leaders and practiced backups. The garden should survive a pastor, rabbi, imam, staff member, committee chair or founding volunteer transition without reconstructing the program from personal email and memory.

Participation design

“Community garden” should tell people what community means here.

Faith-community gardens range from member-only ministry gardens to neighborhood allotments and interfaith donation projects. Penn State Extension has documented interfaith groups working together to grow produce for hunger-relief programs. There is no single correct participation model. There should be a clear one.

ModelWrite down
Congregation-onlyWho qualifies, how plots/roles are assigned, guest policy, fees, work and harvest rules.
Congregation + neighborsApplication/priority rules, access when office/building is closed, communication, fees/waivers and public behavior expectations.
Communal donationSteward rotation, crop plan, harvest authority, recipient schedule, food-safety and donation records.
Interfaith / multi-organizationHost authority, partner roles, shared decisions, money/assets, schedule conflicts, volunteer/child-safety rules and communications.
Outside operator on host landWritten land/use agreement, insurance, utilities, keys, improvements, restoration, public access, termination and asset ownership.

Money and donations

A ministry designation does not replace ordinary financial control.

One budget home

Identify the institutional account, fund or cost center used for water, tools, soil, repairs, insurance-related costs, food-safety supplies and approved purchases.

Authorized spending

National Council of Nonprofits recommends clarity about who has account access and spending authority and basic checks and balances. Apply the host's existing policy rather than a garden-created shortcut.

Fees and accessibility

If plots have fees to offset water or supplies, define the amount, purpose, collection method, refund/renewal rule and any host-approved waiver process. Do not let an informal fee become unrecorded cash.

Restricted gifts / grants

Record donor/grant restrictions, reporting and asset ownership. A donated shed, irrigation system or grant-funded coordinator can create future maintenance obligations after the gift period ends.

Food pantry and meal programs

Grow for the recipient, not for the photo.

NC State's faith-based garden examples emphasize contacting pantries before production, learning what they want, coordinating harvest with distribution and packaging produce in useful amounts. Those are operational skills, not merely charitable intent.

  1. Choose the recipient before dedicating major production.
  2. Ask what crops, varieties, sizes and quantities are actually useful.
  3. Confirm receiving days/times, refrigeration or storage limits and closure dates.
  4. Define who may harvest and how produce is handled.
  5. Schedule harvest close enough to distribution to preserve quality where practical.
  6. Use small, practical units if that matches the pantry/meal program.
  7. Record quantities and rejected/unusable produce.
  8. Ask recipients at season end what to change next year.

Failure diagnostics

Institutional gardens fail when goodwill substitutes for operating ownership.

The clergy leader approved it verbally, but the facilities board objects later.

Likely cause: wrong authority or incomplete internal approval. Response: stop new infrastructure and document who actually controls property decisions.

Sunday workdays are crowded, but the garden is neglected by Thursday.

Likely cause: event participation replaced routine stewardship. Response: assign rotating stewards and handoff notes between group workdays.

Neighbors thought plots were public; members thought they were reserved.

Likely cause: “community” was never operationally defined. Response: publish eligibility, priority, hours and application rules before assignments.

Pantry receives boxes of produce it cannot distribute.

Likely cause: donation goal was defined by grower surplus rather than recipient need. Response: establish recipient crop/quantity/timing feedback before next planting.

A volunteer pays for everything and gets reimbursed informally.

Likely cause: garden finance bypassed institutional controls. Response: establish approved budget, purchase/reimbursement route and records.

The garden collapses after a staff or ministry-chair transition.

Likely cause: contacts, keys, rules, finances and partner knowledge lived with one person. Response: rebuild shared records and practiced backups before expansion.

Stop conditions

Good intentions do not override property, safety or safeguarding controls.

Do not build permanent or expensive infrastructure until the institution's actual property authority has approved the project and local permit/utility questions are resolved.
Do not assume the host's normal insurance automatically covers garden plots, outside gardeners, volunteers, events or off-site activity. Verify coverage with the institution.
Do not give public or after-hours access without an approved key/gate/security and property-access policy.
Do not run youth garden activity outside the institution's safeguarding, screening, supervision and incident procedures.
Do not collect or spend garden money through a volunteer's personal account when the program belongs to the institution.
Do not distribute food through a pantry, kitchen or outside partner without confirming what it accepts and how produce must be handled.
Do not let volunteers apply pesticides, herbicides or landscape treatments outside the host's approved property/IPM process.
Do not treat a charismatic founder, clergy sponsor or ministry chair as the succession plan. Build shared authority, records and backups.

What varies locally

The host's governance is part of the garden environment.

Who legally owns property and which board, council, trustees, staff or other body may authorize use.
Denominational, congregational or organizational policy for property, volunteers, funds and ministries.
Insurance, permits, zoning, utilities, accessibility and construction approvals.
Garden eligibility, fees, public access, parking, keys and hours.
Youth safeguarding, vulnerable-person policies, background checks and supervision.
Pantry, kitchen, meal-service and outside donation procedures.
Financial account, designated-gift and grant reporting rules.
Religious-calendar events, grounds maintenance, weddings/funerals/services and other competing property uses.

Do this yourself

Run the institutional-ownership drill before building the next bed.

  1. Write the garden's primary purpose in one sentence.
  2. Name the institutional body/person that can authorize land use and capital improvements.
  3. Choose allotment, communal donation, mixed or partner-hosted operation.
  4. Write who may participate and exactly how access works when the main building is closed.
  5. Locate the insurance contact and record whether garden activities were reviewed.
  6. Identify the grounds/facilities contact and the rules for mowing, spraying, utilities and deliveries.
  7. Trace one garden fee or donation from receipt through deposit, spending approval and record.
  8. Review the host's youth/volunteer safeguarding procedure and decide whether minors will participate.
  9. Name the pantry/meal recipient and ask what produce it wants and when it can accept it.
  10. Build the next four weeks of routine steward coverage between group workdays.
  11. Give the backup leader the keys/records needed to run one week without the founder.
  12. Put insurance review, budget, season opening, cleanup, donation review and succession check on the Annual Operating Calendar.

Prove it

A durable program can explain who owns every important decision.

☐ I can name the institutional authority that approved land use and major improvements.
☐ I can explain our garden model, participant eligibility, access hours and harvest rules.
☐ I can locate the insurance review, site/soil/water records and facilities contact.
☐ I can trace garden money through the host's authorized financial system.
☐ I can show the routine steward roster between group workdays.
☐ I know which youth/safeguarding rules apply to garden activities.
☐ I can explain what our pantry or recipient wants and when it accepts produce.
☐ I can show that keys, water, rules, partner contacts and the annual calendar are shared with a backup.
☐ I can distinguish a congregational event from recurring garden operations.
☐ The program can survive the departure of its founding clergy sponsor, staff member or volunteer leader.

Sources and method

Extension supplies the faith-community garden model. Institutional governance sources define the boundaries.

Prepared September 5, 2026 from NC State Extension community-garden and faith-community training resources, current NC State organizer guidance, Penn State Extension interfaith/community examples, current IRS church/religious-organization recordkeeping guidance, and current nonprofit internal-control guidance. No particular religious tradition is assumed.

NC Cooperative Extension / NC Council of Churches · Community Gardening 101 for Faith Communities

Leadership, mission, land authority, insurance review, garden models, rules, shared stewardship, roles, accessibility, funding and institutional integration.

NC State Extension · How to Organize a Community Garden

Current 2026 community-garden planning, site, management, insurance, budget, water, workday and organizer fundamentals.

NC State Extension · Community/Home Gardens and Food Banks

Faith-based garden donation models, pantry coordination, harvest timing, useful package sizes and regional coordination.

NC State Extension · Youth and Community Gardening

Community-of-faith cooperative gardens, youth-garden sponsorship and the need to follow host volunteer/screening requirements.

Penn State Extension · Interfaith Community Garden Example

Documented multi-faith volunteer collaboration growing produce for hunger-relief organizations, illustrating that host/partner models can extend beyond one congregation.

IRS · Exempt Organization Recordkeeping

Activities, receipts and expenditures require adequate supporting records even where annual filing rules vary.

IRS · Churches and Religious Organizations

Current federal tax-exemption context; many churches are not required to apply for recognition or file annual Form 990, but that does not eliminate garden-program recordkeeping needs.

National Council of Nonprofits · Internal Controls

Clarity about account access, spending authority and checks/balances. Use the host organization's own governing policy where applicable.

Prepared by: New World Survival · Reviewed: September 5, 2026 · Verify locally: property authority, insurer, permits, public access, youth safeguarding, finances, food distribution, institutional policy and denominational/organizational requirements.

Common questions

Questions that reveal whether the program is institutionally real.

Does a garden on congregation-owned land need a lease?

Not necessarily between the congregation and its own ministry, but internal land-use authority should still be documented. If another organization operates the garden or the garden uses outside land, use an appropriate written agreement and verify local legal/insurance needs.

Should the garden be open to nonmembers?

That is a host-governance and mission decision, not a universal rule. Decide explicitly and publish eligibility, priority, hours, access and expectations so people understand the program before joining.

Should every member be required to volunteer?

Do not impose one national hour requirement. Define the common work needed, offer varied participation roles and create a fair rule appropriate to the model. Avoid equating physical labor hours with moral worth.

Can garden fees go into a separate volunteer account?

If the garden is an institutional program, money should ordinarily move through the host's authorized financial system. Ask the treasurer/administrator how funds must be received, deposited, designated and spent.

Is a Sunday workday enough?

Usually not for a productive communal garden. NC State's faith-community model combines collaborative workdays with rotating stewards between events.

Should we plant first and find a pantry later?

No for a donation-focused program. Ask recipients what they want, when they distribute and how they can handle fresh produce before dedicating large beds to donation production.

Next skills

The next institutional garden has a different ownership problem: residents share housing, but they usually do not control the land individually.

Operations

How to Run a Community Garden

Use the governance guide for rules, money, plot management, enforcement and records.

Open How to Run a Community Garden

Donation pathway

Produce Donation Systems

Use the donation specialist when the program grows for a pantry, meal program or outside recipient.

Open Produce Donation Systems

Next roadmap guide

Community Gardens for Apartments and HOAs

Move to multifamily land, where lease/association authority, resident eligibility, common-property rules, turnover and utility costs shape the garden.

Open Community Gardens for Apartments and HOAs