Start with the work, not the titles
A community garden needs people to keep paths clear, welcome newcomers, organize shared supplies, and make decisions when plans change. It does not necessarily need a complicated hierarchy. Before assigning titles, list the work that happens during a typical growing season. Include visible jobs, such as coordinating workdays, and quieter ones, such as answering messages or keeping track of tool repairs.
Ask gardeners which tasks they can take on and how much time they can reliably offer. A small garden might manage with a few coordinators who share responsibilities. A larger one may need separate people for communications, site care, plots, and events. Try to give every recurring task a named contact and a backup. That way, a holiday, illness, or busy week does not leave an important job unattended.
Define roles that people can actually fill
Write a short description for each leadership role. A site coordinator might schedule shared maintenance and flag problems with paths, water access, or communal beds. A membership contact might orient new gardeners and maintain a contact list. A supplies steward might monitor tools and bring proposed purchases to the team. Someone can also organize meeting notes and keep agreed decisions in a place members can find.
Keep each description focused on responsibilities, not personal authority. For example, a supplies steward can report that a hose needs replacing without automatically having permission to spend shared funds. State which tasks a role holder may handle independently and which require group approval. If the workload becomes too large, divide the role or invite a helper rather than relying on one especially dependable volunteer indefinitely.
Make decision rules before a difficult decision arrives
Gardeners may agree easily about a spring cleanup and disagree strongly about plot assignments, water use, or changes to a shared bed. Decide in advance which choices the leadership team can make, which need input from all members, and how that input will be gathered. Routine scheduling may need only a coordinator's call. A major change to garden layout deserves broader discussion before anyone starts digging.
Choose a workable method for reaching decisions. The team might seek general agreement first, then use a vote if discussion stalls. Specify who may vote, what counts as enough participation, and how absent members can contribute. Keep notes that record the decision, the person responsible for the next step, and when the group will review the result. Clear records help prevent the same conversation from starting over each season.
Set terms and a simple handoff process
Term limits give volunteers a natural chance to step back and make room for new leaders. Choose a term long enough for someone to learn the role but short enough that the commitment feels manageable. A garden could tie terms to its growing season and allow a limited number of renewals. Staggering role changes can help experienced members remain available while newcomers learn.
Decide how replacements will be invited or selected before a term ends. Share role descriptions early, encourage interested gardeners to shadow current leaders, and avoid treating prior leadership experience as the only qualification. A useful handoff includes contact information the garden is permitted to share, upcoming tasks, supply records, access arrangements, and notes on unfinished decisions. Keep these materials in a shared location rather than a volunteer's private inbox.
Keep leadership accountable and welcoming
A leadership team works best when members can see what it is doing and raise concerns without needing to join it. Hold meetings at predictable times, circulate brief notes, and offer more than one way to give feedback. Not everyone can attend an evening meeting or speak comfortably in a group. When possible, make responsibilities small enough for people with different schedules and abilities to participate.
Build in a regular check-in about the structure itself. Ask whether roles are balanced, decisions are understandable, and new gardeners know whom to contact. If conflict arises, return to the garden's agreed process, listen to the people affected, and document the outcome without turning meeting notes into a record of personal grievances. Leadership is not about making every choice alone; it is about helping the garden make choices it can carry forward together.
