Capability promise
The garden should still work when you are not there.
After completing this guide, you should be able to inspect a garden's operating system, assign critical responsibilities, separate rules from procedures, review basic finances, manage maintenance and neglected plots, choose the right conflict path, preserve records, run an annual health audit and prepare a leadership handoff.
Govern fairly
Make authority, membership, rules and consequences understandable before conflict begins.
Account for money
Know what came in, what went out, who approved it and what the garden can actually afford.
Maintain systems
Inspect water, hoses, tools, paths, gates, storage and other shared infrastructure before small failures become garden-wide problems.
Transfer leadership
Keep the garden's records, access and know-how with the organization rather than inside one founder's head.
The five-minute answer
Run the garden as a small civic institution.
NC State Extension's current community-garden guidance is direct: management does not end after opening day. Gardeners should increasingly share day-to-day responsibility, while rules, membership, dues, waiting lists, tools, workdays and leadership remain transparent and documented.
Control 1
Authority
Someone can answer routine questions and make routine decisions. Critical roles have backups.
Control 2
Expectations
Rules, plot agreements and operating procedures agree with one another and are easy to find.
Control 3
Maintenance
Water, tools, paths, common areas and neglected plots are inspected on a predictable rhythm.
Control 4
Continuity
Money, contacts, records, passwords, agreements and procedures survive leadership turnover.
The leadership test
If the coordinator became unavailable tonight, could another responsible person identify the current gardeners, plot assignments, water shutoff, land agreement, insurance contact, account balance, next workday and unresolved problems tomorrow morning? If not, the garden has a continuity problem even if every bed looks good.
The document stack
Do not make one document carry the whole garden.
The live page previously treated bylaws and the plot agreement as if they carried nearly every operating rule. A more usable system separates four kinds of information. A tiny garden may keep each document short, but the functions should remain distinct.
Governance document
Defines who has authority, how leaders are selected, how decisions are made, who may approve spending, how records are kept, and how the governance document itself is changed. Depending on the sponsor, this may be bylaws, a committee charter, municipal program rules or another formal document.
Garden rules
States practical expectations: plot maintenance, common areas, workdays, water, tools, structures, weeds, pesticide or fertilizer restrictions, behavior, guests, harvest boundaries and the process for violations. NC State recommends keeping rules simple, visible and understandable.
Seasonal plot agreement
Records the gardener, plot, season, fee or waiver if applicable, current contact information, acknowledgement of the rules, required common work and any sponsor-specific forms. It creates a dated record of what the gardener agreed to for that season.
Operating procedures
Explains repeatable tasks: opening and closing water, handling a leak, checking out tools, inspecting paths, documenting a neglected plot, running a workday, recording an incident, onboarding a new gardener and handing off leadership.
Keep the hierarchy clear
If the garden is part of a city, school, nonprofit, church, synagogue, housing authority, HOA or other sponsor, the sponsor's governing documents and policies may control. Do not create garden rules that conflict with the land agreement, insurance requirements, sponsor policy or applicable law.
Step 1
Define authority, responsibility and backup.
NC State notes that successful gardens usually have someone empowered to answer questions and coordinate resources, but also encourages gardeners to take increasing responsibility. The goal is neither founder control nor leaderless ambiguity.
| Function | Primary responsibility | Backup requirement | Record that proves it |
|---|---|---|---|
| Routine coordination | Questions, schedules, sponsor contact, problem routing | Another person knows current issues and contacts | Issue list + contact sheet |
| Membership | Applications, plot map, agreements, renewals, waitlist | Records are accessible to an authorized backup | Current roster + plot map |
| Money | Budget, deposits, expenses, receipts, reporting | A second responsible person reviews activity | Ledger + statements + receipts |
| Infrastructure | Water, tools, paths, storage, gates, repairs | Another person can shut off water and locate repair contacts | Inspection and repair log |
| Communication | Notices, meeting records, rule updates, emergency information | Distribution list and account access are organizational | Communication log + account inventory |
Name the decision rights
What can the coordinator decide alone? What requires committee review? What requires the sponsor or landowner? A list of decision rights prevents both paralysis and overreach.
Name the records owner
Every critical record needs a responsible keeper and an organizational storage location. Personal inboxes should not be the only archive.
Name the backup
At least one other authorized person should know how to perform each critical function. The test is operational access, not a ceremonial title.
Step 2
Run a transparent membership cycle.
Plot assignment should not depend on who knows the coordinator. NC State describes first-come systems, lotteries and eligibility rules as possible selection methods and cautions against letting persistent applicants bypass a waitlist. Whatever method you use, publish it before assigning plots.
1 · Application
Collect only what you need
Eligibility, contact method, household or accessibility information only when it serves a legitimate garden need, and any sponsor-required information.
2 · Selection
Publish the method
First-come, lottery, geographic eligibility or another defensible method. Keep the waitlist current and apply the method consistently.
3 · Orientation
Meet at the plot
Confirm plot boundaries, water, tools, common work, rules, contacts and what happens if the gardener needs temporary help.
4 · Agreement
Sign the current season
Record the plot, season, responsibilities, fees if any, current contact information and acknowledgement of the current rules.
5 · Renewal
Decide before the rush
Set the renewal process and deadline before new applicants are promised openings. Keep gardeners informed about changes in rules or fees.
6 · Exit or reassignment
Close the record
Document voluntary exits, reassigned plots and any cleanup responsibility. Update the plot map and waitlist promptly.
Privacy rule: A coordinator may need gardeners' contact information, but that does not mean the entire roster should be publicly distributed. Obtain consent before publishing personal phone numbers, addresses or other private information. Use the sponsor's privacy practices where applicable.
Step 3
Make the rules enforceable in practice.
Rules fail when they are vague, invisible, contradictory or too complicated to enforce. NC State recommends discussing drafts with gardeners, keeping rules straightforward, posting them and revising them when experience reveals a problem.
Define observable expectations
Replace “keep your plot nice” with specific expectations about weeds, pathways, harvest, structures, end-of-season cleanup and notification during an absence.
Use the Garden Resilience guide for extended-absence coverage, water disruption, heat and flood continuity.Define the consequence before the violation
State what happens after a missed responsibility: reminder, documented notice, opportunity to correct, reassignment or another action. The exact sequence belongs to your garden and sponsor. Do not invent a universal number of days.
Apply rules equitably
Similar situations should receive similar treatment. Record reasons when a reasonable accommodation, health issue or unusual circumstance changes the response.
Separate preference from safety
Aesthetic disagreements should not be treated like unsafe tool use, prohibited pesticide use, threats or blocked access. Match the response to the actual risk.
| Issue | Better rule language asks | Evidence to keep |
|---|---|---|
| Plot maintenance | What condition triggers contact? What is the gardener expected to do? | Dated inspection note or photo when appropriate |
| Common work | What counts? How are accommodations handled? How are missed obligations addressed? | Workday or task log |
| Pesticides | What does the garden permit or prohibit in addition to label requirements? | Current policy + incident note if needed |
| Structures | What size, location or materials require approval? | Plot map or approval note |
| Behavior | What conduct is incompatible with a safe shared space? | Incident record handled with appropriate privacy |
Step 4
Make garden money boring and visible.
NC State recommends a simple realistic budget covering continuing costs such as water, compost, mulch, tools, repairs and rent where applicable. If the garden is an independent nonprofit, basic internal controls become particularly important. The National Council of Nonprofits recommends clarity about account access and spending authority and notes that a second person reviewing bank statements is a simple control even small organizations can use.
Budget
Start the year with expected income, normal operating costs and known projects. Update when conditions change.
Authorization
Write down who may commit garden funds, spending limits if used, and what requires broader approval.
Documentation
Retain receipts, invoices, deposits, grant restrictions and reimbursement records in the sponsor's or garden's system.
Review
Regularly compare cash on hand with the ledger and bank or sponsor records. Share a concise report with the responsible group.
The minimum monthly finance review
- Opening balance
- Income received
- Expenses paid
- Closing balance
- Unpaid obligations
- Restricted grant or donation balances
- Expected water and repair needs
- Reserve available for failures or replacement
Stop condition: missing or disputed money
If balances cannot be reconciled, receipts are missing for material expenses, or unauthorized transactions are suspected, pause nonessential spending, preserve records and involve the garden's sponsor, board, fiscal agent, accountant or other responsible authority. Do not solve a financial-control problem by quietly rewriting the ledger.
Step 5
Inspect the systems everyone depends on.
NC State's management guidance calls out paths, water taps, hoses, plot markers, shared tools, storage, gathering areas, children's areas, recycling and trash as continuing maintenance responsibilities. The garden needs an inspection rhythm, not a heroic repair day after failure.
| System | Inspect for | Know before failure |
|---|---|---|
| Water | Leaks, damaged taps, hose failures, poor drainage, winter exposure | Master shutoff, utility/landowner contact, repair parts and who may perform repairs |
| Tools | Loose heads, cracked handles, rust, dull edges, missing tools | Checkout/storage method and maintenance responsibility |
| Paths | Weeds, erosion, mud, obstructions, trip hazards, narrowing vegetation | Maintenance standard and accessible-route requirements where applicable |
| Storage | Locks, moisture, pests, chemical incompatibility, clutter | Who has keys and what may be stored there |
| Compost/waste | Contamination, overflow, pests, trash, unmanaged weeds | Accepted materials and removal route |
| Fence/gates/signage | Damage, blocked access, stale contact information | Repair authority and emergency access |
Tool rule
NC State recommends cleaning tools after use, keeping them sharp, tightening loose hardware, smoothing rough handles and storing them dry. A community tool shed should make these practices easier, not turn shared tools into anonymous consumables.
Go deeper: Shared Garden Tools: Selection, Safety, Maintenance and StorageAccessibility rule
If an accessible route is required, it must remain usable. U.S. Access Board guidance emphasizes firm, stable, slip-resistant surfaces and maintaining accessible features in working order. Do not let mulch drift, hoses, weeds, stored materials or broken gates slowly erase access.
Go deeper: Accessible Community Garden Design and ParticipationStep 6
Workdays should solve defined maintenance problems.
Workdays are not a ritual attendance test. They are a way to distribute maintenance, teach skills and build new leaders. Schedule them from actual seasonal needs, provide tasks with different physical demands, and record what was completed and what remains.
Before
- List specific jobs and materials.
- Assign a task lead.
- Check weather, heat and severe-weather risk.
- Provide lower-exertion or seated tasks where possible.
- Confirm water, shade/rest and first-aid access appropriate to the event.
During
- Brief workers on the task and tools.
- Keep children with age-appropriate supervision and tools.
- Encourage water and cooling breaks in hot conditions.
- Stop unsafe tool use or unsafe weather exposure.
- Do not pressure a member to perform a task beyond their ability.
After
- Return and inspect tools.
- Record repairs still needed.
- Update maintenance logs.
- Thank contributors without turning volunteer hours into status.
- Identify one person who learned a new leadership or maintenance skill.
Stop condition: unsafe outdoor work
CDC/NIOSH recommends reducing heat exposure, providing access to cool potable water, increasing rest and recovery in hot conditions, and rescheduling nonessential work when conditions become extreme. Severe weather, lightning, dangerous heat or an unsafe task is a reason to change the plan, not proof of commitment.
Step 7
Treat a neglected plot as an operating problem first.
NC State recommends clear expectations, reliable contact information, early contact and a fair reassignment process. It also urges coordinators to determine whether a gardener needs help because of health or personal circumstances. The goal is to protect the shared garden while treating people consistently and reasonably.
Observe
Use the written maintenance standard, not personal taste.
Contact
Ask what happened and whether temporary help is needed.
Document
Record the condition, contact and next expected action.
Follow policy
Use the garden's existing correction and reassignment process.
Close
Update the plot map, records and waitlist after resolution.
Do not confuse accommodation with favoritism
A gardener recovering from surgery may reasonably need temporary help or a modified task. Another may simply have abandoned the plot. The response can differ while the process remains fair if the garden documents the reason and applies its policies consistently.
Step 8
Match conflict resolution to the kind of conflict.
The current live guide requires direct conversation first for every conflict. That is too broad. Direct conversation can be excellent for low-risk misunderstandings. It is not an appropriate mandatory first step for threats, harassment, violence, suspected crimes or other conditions where safety or sponsor policy requires escalation.
| Problem type | Examples | First route | Record |
|---|---|---|---|
| Ordinary interpersonal | Hose placement, accidental shading, noise, minor misunderstanding | Respectful direct conversation when both parties are comfortable | Usually none unless repeated |
| Rule dispute | Plot maintenance, structures, common-work expectations | Coordinator or designated reviewer applies written rule | Dated issue and decision |
| Technical/safety | Water damage, unsafe tools, pesticide use, blocked access | Stop or correct the hazard; involve sponsor or qualified help as needed | Incident/repair record |
| Threat/harassment/serious conduct | Threats, intimidation, violence, discriminatory harassment, suspected crime | Use sponsor, landowner, safety or appropriate legal/emergency process | Restricted incident record |
A defensible decision note answers five questions
- What happened?
- Which written rule or responsibility applies?
- What evidence was considered?
- What action was taken and why?
- What follow-up date or condition closes the matter?
Step 9
Keep the records that let the garden remember.
The garden should not need an archaeological dig through a former coordinator's email to understand its own history. NC State specifically calls for accurate membership, waitlist and dues records. Extend that discipline to the rest of the operating system.
People and plots
Current roster, plot map, signed agreements, waitlist, renewal status, emergency/sponsor contacts where legitimately needed.
Governance
Current governance document, rules, version dates, meeting decisions, officer or committee list.
Money
Budget, ledger or sponsor reports, receipts, statements, grant restrictions, donor commitments and reserve plan.
Land and risk
Land agreement, renewal dates, insurance documentation, owner/sponsor contacts, approvals and material restrictions.
Infrastructure
Water shutoff information, maintenance inspections, tool inventory, repairs, warranties and vendor contacts.
Continuity
Organizational email and file access, website/domain access where applicable, procedure list, annual calendar and leadership handoff notes.
Step 10
Build succession before someone resigns.
NC State describes a healthy garden as one that becomes increasingly self-sustaining and develops leadership among gardeners. Succession is therefore not a farewell task. It is an ordinary operating discipline.
The founder-dependency test
- Is a critical account tied to one person's private email?
- Does only one person know the water system?
- Does only one person know the landowner or insurer?
- Can only one person access the money?
- Are unresolved conflicts known only to one leader?
- Would meetings stop if one person stopped scheduling them?
The handoff packet
- Role description and annual calendar
- Current roster, plot map and waitlist
- Open issues and next decisions
- Financial status and obligations
- Land, insurance and sponsor contacts
- Infrastructure problems and seasonal maintenance
- Organizational account/access inventory
- Thirty-day transition meeting with outgoing and incoming leaders when possible
Annual garden health audit
Inspect the institution, not just the beds.
At least once each year, review the garden's operating condition. Do not reduce the audit to a score. The useful outcome is a short corrective-action list with owners and deadlines.
| Domain | Healthy evidence | Watch signal | Corrective action |
|---|---|---|---|
| Membership | Current agreements, accurate plot map, fair assignment | Stale waitlist, unclear renewals | Reconcile records before next assignment cycle |
| Maintenance | Common areas and plots addressed early | Repeated neglected areas, unclear responsibility | Assign owner and maintenance rhythm |
| Water/tools | Known shutoff, repair log, usable tools | Leaks, missing tools, no repair owner | Repair, inventory and document |
| Finances | Budget, records and balances agree | Late reports, unexplained transactions | Reconcile and strengthen review controls |
| Land/risk | Current land authorization and insurance answer | Renewal approaching, unclear responsibility | Open renewal/insurance review early |
| Accessibility/safety | Routes and shared areas remain usable | Blocked routes, unsafe surfaces, damaged gates | Remove obstruction or repair promptly |
| Leadership | Backups exist and records are organizational | One person controls critical knowledge or access | Train backup and build handoff packet |
Decision table
Know when to proceed, correct, or stop.
| Finding | Meaning | Action |
|---|---|---|
| Rules are old but generally workable | Routine governance maintenance | Review with gardeners, revise, date and redistribute |
| No one besides the coordinator can access records or accounts | Founder-dependency risk | Create authorized backup access and handoff documentation now |
| A few plots are neglected after a gardener reports a temporary hardship | Maintenance issue with possible accommodation need | Use the written process, offer reasonable temporary help where appropriate and document the plan |
| Account records do not reconcile | Financial control failure | Pause nonessential spending, preserve records and involve responsible financial oversight |
| Land agreement or required insurance has expired | Operating authority/risk uncertainty | Do not make new commitments or major investments until the responsible parties resolve the status |
| Threats, violence or serious harassment are reported | Safety issue, not an ordinary garden disagreement | Use sponsor, landowner, safety or appropriate emergency/legal procedures; do not require direct mediation first |
Failure diagnostics
Why a garden can look alive while the organization is weakening.
Founder bottleneck
Symptom: every decision, password and relationship runs through one person. Response: document decision rights, assign backups and transfer organizational access. Prevention: build deputy roles before burnout.
Rule drift
Symptom: gardeners describe different rules depending on whom they ask. Response: reconcile the current rule set, date it and distribute one authoritative version. Prevention: keep a version history.
Workday resentment
Symptom: the same few people do every heavy task while others feel judged or excluded. Response: define real maintenance needs, offer varied tasks and record contribution without status competition. Prevention: assign recurring responsibilities instead of depending only on big workdays.
Abandonment spiral
Symptom: neglected plots spread weeds, pests and frustration. Response: contact gardeners early, use the existing policy and reassign confirmed vacancies promptly. Prevention: inspect regularly and keep the waitlist accurate.
Invisible money
Symptom: no one can state the current balance or explain recent expenses. Response: reconcile records and establish routine reporting. Prevention: budget, receipts, defined authorization and second-person review.
Access erosion
Symptom: paths narrow, surfaces degrade, hoses block routes or gates stop working. Response: remove obstructions and repair the route. Prevention: include accessibility in the regular maintenance inspection.
Stop conditions
Some problems are not solved by another meeting.
Verify this locally
Governance lives inside a real institution and jurisdiction.
Decision authority, land agreement, required forms, insurance, keys, public access and conduct policy.
Coverage, volunteer status, waivers/forms, events, tools, structures and incident reporting.
Permits, structures, water, composting, public access and other local operational rules when applicable.
Horticulture, IPM, soil, plant health, tool and seasonal maintenance practices.
Recordkeeping, tax, grant and internal-control requirements for the garden's actual legal/fiscal structure.
Applicable access requirements for public, governmental, housing, school or other covered sites. Do not assume one raised bed makes the site compliant.
Do this yourself
Run a 60-minute operations audit.
Do not begin by rewriting the bylaws. Walk the garden and gather the evidence first.
Records
Locate current rules, roster, plot map, land agreement, insurance answer and latest financial report.
Infrastructure
Walk water, hoses, tools, paths, gate, storage, compost and shared spaces. Record three repair or maintenance needs.
Continuity
Ask who could perform five critical functions if each current leader disappeared for a month.
Corrective list
Choose the three highest-consequence weaknesses, assign an owner and a realistic completion date.
Prove it
A Level 5 garden leader can show the system.
Common questions
Questions that keep governance practical.
Does a community garden need bylaws?
A small garden may be able to use a simple governance document rather than elaborate bylaws, depending on its sponsor and legal structure. What matters operationally is that authority, decisions, money, membership and leadership selection are clear and documented.
What should every community gardener sign?
A current seasonal plot or membership agreement should acknowledge the garden's rules, responsibilities, timelines and consequences. The exact form depends on the garden's sponsor, insurer and local requirements.
How should a garden handle an abandoned or neglected plot?
Define maintenance expectations in advance, contact the gardener early, determine whether short-term help is appropriate, document the communication and use the garden's stated reassignment process consistently. Do not invent a punishment timeline after the problem begins.
How should a community garden manage money?
Use a written annual budget, record income and expenses, retain receipts, make account access and spending authority clear, ensure more than one responsible person can review financial activity, and report the garden's financial position regularly.
How should community garden conflicts be resolved?
Match the process to the problem. Ordinary low-risk disagreements may begin with respectful direct conversation. Persistent rule disputes may require mediation or leadership review. Threats, harassment, suspected crimes or safety issues should move directly to the appropriate sponsor or safety process.
How does a community garden survive a founder leaving?
Give critical functions backups, keep organizational records and account access outside one person's private systems, write repeatable procedures, and complete a documented leadership handoff before the outgoing leader leaves.
Sources and method
Operating advice should be traceable and adaptable.
This guide was rebuilt in September 2026 from current NC State Extension community-garden guidance, current federal pesticide and heat-safety guidance, U.S. Access Board accessibility guidance, and nonprofit financial-control guidance. It does not prescribe a universal legal structure, notice period, waiver, fee, workday quota or insurance policy.
NC State Extension · How to Organize a Community Garden
Current 2026 guidance on management structure, rules, agreements, dues, tools, workdays, budgeting, insurance and conflict.
NC State Extension · Organization
Roles, leadership, committees, plot selection, agreements, waiting lists, communications and records.
NC State Extension · Management
Paths, water taps and hoses, shared tools, common areas, seasonal maintenance and gardener meetings.
NC State Extension · Troubleshooting
Neglected plots, neighbor complaints, disputes and other recurring garden-management failures.
NC State Extension · Garden Tools
Cleaning, sharpening, tightening, handle care and dry storage for shared garden tools.
National Council of Nonprofits · Internal Controls
Checks and balances, account access, spending authority, documentation and second-person financial review for nonprofit organizations.
CDC/NIOSH · Heat Stress Recommendations
Planning hot outdoor work, hydration, recovery time, acclimatization and rescheduling when conditions become unsafe.
U.S. Access Board · Accessible Routes
Accessible-route clearances, surfaces and the requirement to maintain accessible features in working order where applicable.
U.S. EPA · Introduction to Pesticide Labels
Why pesticide label directions are legally enforceable and govern safe, legal product use.
Prepared by: New World Survival · Reviewed: September 4, 2026 · Scope: U.S. general operations guidance · Verify locally: legal structure, sponsor authority, land agreement, insurance, waivers/forms, financial/tax obligations, privacy, accessibility, volunteer requirements, pesticide restrictions, water and local operating rules.
Next skills
Keep the sequence connected.
Prerequisite
Start the Garden
Land, water, site safety, approvals, design and opening procedures should already be established.
How to Start a Community GardenGardener perspective
Manage a Plot
Leaders should understand the real maintenance burden placed on individual gardeners.
How to Plan and Grow a Community Garden PlotNext calibration page
School Gardens
Institutional gardens add supervision, food safety, summer maintenance and school-year succession requirements.
Current School Gardens guideLeadership continuity
Do not let the garden become one person's operating system.
Roles, records, financial access, landowner relationships, recurring deadlines and digital accounts should survive leadership turnover. Use the specialist to run the founder-dependency test and build emergency and planned transition procedures.
Leadership Succession and Preventing Founder BurnoutAnnual operating cycle
Put recurring governance and maintenance work on one owned calendar.
Back-plan applications, agreements, dues, meetings, workdays, water startup/shutdown, inspections, renewals, budgets, records and year-end review. Separate hard deadlines from local seasonal anchors and trigger events.
The Annual Community Garden Operating CalendarAnnual health review
Audit whether the operating system is healthy enough for another year.
Review land, authority, leadership depth, participation, finances, water, infrastructure, accessibility, safety, records, maintenance capacity and partner relationships. Keep serious defects visible instead of averaging them into a score.
How to Conduct an Annual Garden Health Audit