The Shared World Project
Story Pillar guide May 23, 2026

The First 90 Days of a Community Garden

A clear first-season plan for starting a community garden with site checks, water access, soil work, volunteers, and shared records.

Sections

Quick answer

Use the first 90 days to prove the site can be cared for: confirm permission, water, sunlight, access, soil safety, volunteer roles, and harvest routing before planting too much. A smaller garden with records and a care rhythm beats a large launch that nobody can maintain.

A community garden can look simple from the sidewalk. Beds, soil, water, seeds, and people. The hard part is the order. A garden that skips the first checks can spend the whole season fixing problems that should have been solved before planting.

The first 90 days should prove that the site can be cared for. It should also teach the group how decisions will be made when the weather is hot, a hose breaks, a volunteer misses a shift, or harvest arrives faster than expected.

Days 1 to 30: confirm the site

Start with permission, water, sunlight, and access. Who owns the land? Who can open it? Where does water come from? How many hours of sun reach the growing area? Can volunteers reach the site without unsafe crossings or blocked sidewalks?

Put the answers in writing. A garden does not need a thick legal file to start learning, but it does need a clear agreement about who may use the land, what can be built, and who can make site decisions.

Soil testing belongs in this first month. Do not guess about soil near old buildings, parking lots, rail lines, or industrial corridors. If the soil is questionable, raised beds and clean imported soil may be the right starting point.

Days 31 to 60: build the care system

Planting is easier than maintenance. Before seedlings go in, decide who waters, who opens the site, who handles compost, who records volunteer hours, and who gets called when something breaks.

A shared calendar matters. So does a simple task board. People should know what needs doing without waiting for one organizer to answer every message.

Minimum care roles:

  • Site lead: makes day-to-day calls and knows the agreement.
  • Water lead: checks the watering plan during hot weeks.
  • Supply lead: tracks soil, mulch, gloves, tools, seeds, and repairs.
  • Volunteer lead: handles check-in, task fit, and service records.
  • Harvest lead: decides how food leaves the site.

One person can hold more than one role at first. The point is that the role exists.

Days 61 to 90: plant with restraint

Choose crops the team can actually tend. Herbs, greens, beans, peppers, okra, and sweet potatoes may fit a first season better than a complicated mix of fragile plants.

Avoid planting the whole dream at once. A first season should answer practical questions:

  • How fast does the soil dry out?
  • Which volunteers return without being chased?
  • Which tools are missing every week?
  • Where do people naturally gather?
  • How will harvest move from bed to table?

The first harvest should teach the group how food moves. Will it be shared during a workday? Donated through a pantry partner? Given to nearby households? Decide before harvest day arrives.

Keep records from the beginning

Records do not need to be fancy. Track volunteer names, hours, tasks, harvest notes, supply needs, and repair issues. These notes help the next crew understand what happened.

For volunteers using service hours, records also protect the value of their work. Shared World service letters should connect hours to real tasks, not vague attendance.

A basic garden log should include:

  • Date and weather conditions
  • People present and hours worked
  • Tasks completed
  • Crops planted, harvested, or removed
  • Watering and compost notes
  • Safety issues or repairs
  • Materials needed before the next workday

Let the garden become a local habit

A garden survives when neighbors know when people will be there. A steady Saturday morning can do more than a large launch event.

Make the rhythm visible. Post the weekly care window. Keep the tool area clean. Make the next task obvious. Thank people with specifics, not empty praise. “You watered the new beds during the hardest week” means more than “thanks for coming.”

Use the Community Gardens program page to connect a site, request support, or prepare a garden need that can be listed for local help.

Write the land agreement before the first build day

A garden needs permission that survives enthusiasm. A handshake can start a conversation, but it should not carry donated materials, volunteer hours, or public expectations by itself.

The agreement can be simple, but it should answer:

  • Who owns or controls the land
  • Who is allowed to garden there
  • What structures, beds, signs, compost, and storage are allowed
  • Who carries insurance or liability responsibility
  • How water access will be billed or managed
  • What happens if the land use changes
  • How much notice the garden gets before removal
  • Who can speak for the project

If the garden is on school, church, city, county, housing, or nonprofit land, the agreement may need more review. That is not a reason to avoid the site. It is a reason to make responsibility clear before volunteers build something that may have to move.

Test soil and choose the right growing method

Soil safety is a first-season decision, not a later improvement. Urban and roadside soils may carry lead, petroleum residue, construction debris, or other contaminants. Extension soil tests can help with nutrients and pH, but contamination concerns may need additional testing or raised-bed decisions.

Use this rule: if the soil history is uncertain, do not grow edible crops directly in it until the team understands the risk. Raised beds with clean soil, geotextile separation, mulch paths, and clear digging rules may be the right first step.

Soil planning should include:

  • Soil nutrient and pH testing
  • Contamination history review
  • Bed depth and soil volume
  • Mulch source and safety
  • Compost source and maturity
  • Drainage after heavy rain
  • Where volunteers may dig

The first 90 days should leave the site safer and more understandable than it was before.

Plan water like it is the garden’s budget

Water is often the real limit. A site with beautiful beds and no reliable water will exhaust volunteers. A site with reliable water and a simple layout can survive a rough first season.

Before planting, decide:

  1. Who can turn water on and off.
  2. Which hose reaches every bed.
  3. What happens when a hose breaks.
  4. Which crops get priority during heat.
  5. Who checks after extreme heat or wind.
  6. Whether rain barrels are legal, safe, and useful for the site.

For Texas sites, mulch is part of the water plan. So is shade for volunteers. A garden that asks people to water in brutal heat without shade, water, and rest is not caring for the people who care for the plants.

Build a first-season crop plan around reliability

New gardens often overplant because seeds are cheap and hope is easy. The better first-season question is which crops will teach the team without creating too much loss.

Choose crops that match:

  • The season
  • The watering plan
  • The volunteer skill level
  • The harvest route
  • The site pests
  • The amount of shade

In hot Texas conditions, a first garden may need tough warm-season crops, herbs, mulch-heavy beds, and partial shade for people more than a delicate crop list. The site should learn its own patterns before it tries to impress anyone.

Decide who receives the harvest

Harvest can become awkward if the garden waits too long to decide where food goes. Write the rule early.

Common harvest routes include:

  • Shared among volunteers who worked the shift
  • Given to nearby households
  • Routed through a pantry or community fridge partner
  • Used in a class, meal, or demonstration
  • Left for open harvest during posted hours

Each route has tradeoffs. Pantry routes need packaging, timing, and food safety care. Open harvest needs signs and trust. Volunteer shares can build commitment but should not quietly exclude neighbors. The best route is the one the site can explain plainly.

Create roles for different bodies and schedules

A garden should not only welcome people who can lift, dig, and work in heat. Some of the most important garden jobs are lighter or more flexible.

Offer roles such as:

  • Water check
  • Seed starting
  • Tool cleaning
  • Sign making
  • Harvest weighing
  • Data entry
  • Photo documentation
  • Neighbor outreach
  • Compost log
  • Shade and water station support

This matters for elders, disabled volunteers, court-related service participants with restrictions, parents with children, and people with limited time. A resilient garden has more than one way to contribute.

Sources and further reading

Common questions

What should a new community garden do before planting?

Confirm land permission, water access, sunlight, soil safety, volunteer access, maintenance roles, and harvest plans before planting. These decisions prevent most first-season failures.

Should a first-year garden start large?

Usually no. Start with a manageable number of beds, a steady watering plan, and crops the team can tend. Expansion should follow reliable care.

Why are garden records important?

Records show who worked, what was planted, what failed, what was harvested, what supplies are needed, and how service hours were earned.

Related guides

Put this into work

Bring a project need, offer materials, or join a local service shift.