The five-minute answer
Run the tomorrow test.
Ask one question: if the current leader became unavailable tomorrow, could another authorized person run the next thirty days without reconstructing the garden from text messages, personal email, memory and favors? National Council of Nonprofits recommends both emergency transition plans and deliberate cross-training. NC State likewise says durable garden records should be accessible to multiple members and warns when key functions collapse into one-person systems.
Authority
Who can decide, sign, spend, close, communicate, reassign plots and contact the landowner?
Records
Can another steward find agreements, rosters, finances, minutes, maps, permits and open issues?
Accounts
Are email, cloud files, domain, social media and financial systems organization-controlled rather than trapped in one person's account?
Relationships
Does the garden own the relationship with the landowner, utility, Extension office, vendors, donors and donation recipients?
Bench
Can at least one other person perform each critical role, and has that person actually practiced it?
Capability promise
After this guide, a garden leader should be able to transfer leadership without transferring chaos.
The dependency map
Founder dependence has more than one form.
The following six dependencies are a New World Survival diagnostic model. A garden can look well staffed and still fail the tomorrow test if one person holds several of these alone.
1 · Authority
Only one person can authorize spending, speak for the sponsor, sign the lease, make plot decisions or close the site.
2 · Information
Rules, maps, contracts, meeting history, maintenance records or contact lists live in one person's files or memory.
3 · Digital access
Email, website, social account, cloud drive or billing system is tied to one person's personal account, phone or recovery email.
4 · Money
One volunteer receives money, deposits it, pays bills, reconciles accounts and sees the bank statement without independent review.
5 · Relationships
The landowner, utility, Extension agent, donor, vendor or food-recipient contact knows only the founder.
6 · Technique
Only one person knows the irrigation shutoff, annual plot process, bookkeeping workflow, website update or recurring compliance task.
The procedure
A ten-step succession and institutional-memory system.
Identify the governing home.
Is the garden an independent nonprofit, informal association, municipal program, school program, church ministry, HOA project or program of another nonprofit? Record who legally owns contracts, bank accounts, insurance, domain names, grants and improvements. Succession cannot be designed correctly if the garden mistakes a sponsor's authority for the founder's authority.
Run the tomorrow test role by role.
List every critical responsibility and ask whether another authorized person can perform it now. NC State notes that steering committees may manage membership, waiting lists and dues and emphasizes accurate, current records. National Council of Nonprofits recommends emergency transition plans, deeper leadership benches and cross-training.
Create the Emergency Leadership Transition Card.
Name who temporarily holds operational authority, who communicates with members/sponsor, who can access money and records, which decisions must wait for the board/sponsor, and what urgent calendar deadlines occur in the next thirty days. Do this while the current leader is healthy and available.
Build the garden's record architecture.
NC State recommends storing records where multiple members can access them, including a secured shared notebook or online drive. Create governed folders for authority/legal, members/plots, finances, land/site, water/infrastructure, tools, safety/incidents, donation/partners, grants/donors, meetings/decisions and annual reports. The garden should know where the authoritative copy lives.
Adopt a retention-and-destruction rule appropriate to the organization.
Do not keep everything forever and do not let individuals delete records ad hoc. National Council of Nonprofits notes that retention requirements vary by document, state and organization and recommends a written policy. IRS rules require tax-exempt organizations to keep books and records supporting their filings and activities. If the garden operates under a municipality, school, church or nonprofit sponsor, follow that sponsor's retention policy rather than inventing a separate schedule.
Move critical digital access out of personal custody.
Inventory organizational email, domain/website, cloud storage, social media, newsletter, payment, bank and vendor accounts. Record the service, organizational owner, current administrators, recovery method and where credentials are securely managed. Do not put actual passwords or recovery codes in the printable binder. CISA recommends password managers and multifactor authentication for organizational accounts.
Preserve financial controls during handoff.
A treasurer transition should not temporarily erase checks and balances. National Council of Nonprofits emphasizes clarity about who has access to bank accounts and who has authority to spend money, and recommends separating duties where practical. Reconcile accounts, document outstanding bills/reimbursements/grants, update authorized users through the institution's proper process and make sure another authorized person reviews statements.
Transfer relationships and decision history.
Introduce the successor to the landowner, sponsor, utility, Extension office, vendors, donors, food-recipient partners and institutional contacts. Pair the contact list with a short relationship note: what they provide, what the garden promised, next deadline and current unresolved issue. Preserve meeting minutes and a decision log so the successor can distinguish an intentional policy from a habit nobody remembers choosing.
Cross-train through real work.
National Council of Nonprofits recommends cross-training and leadership-development opportunities. A backup is not trained because their name appears in a spreadsheet. Have the backup actually run plot assignment, reconcile one month, lead a workday, contact the landowner, operate the water shutoff, update the website or prepare the annual meeting under supervision.
Make departure and onboarding explicit.
Close out open decisions, return keys/assets, remove unneeded access, update signers/admins, communicate the transition and give the successor room to lead. The outgoing founder can remain a mentor if invited, but should not continue making decisions through private side channels after authority has transferred. Review the transition after the first operating cycle and correct missing records or permissions.
The continuity binder
Store the map to the records, not every sensitive record in one binder.
A succession binder should tell the next leader what exists, where the authoritative record lives, who may access it and what must happen next. It should not become an insecure duplicate of passwords, bank credentials, protected student records or unnecessary member personal information.
Authority records
Governing documents, sponsor agreement, bylaws/rules, lease/license, insurance, permits, grants and current authorized signers.
Operations
Annual calendar, plot map, waiting-list process, maintenance routines, tool/infrastructure records, water plan and emergency contacts.
Money
Budget, account location, current balance reports, dues, bills, grants, reimbursements, restricted funds and review/approval process. Do not print credentials.
Digital systems
Service, organizational owner, admins, MFA/recovery method, password-manager location and renewal date. No raw passwords in the binder.
Relationships
Landowner, sponsor, utility, Extension, vendors, donors, schools, donation recipients and neighboring/community contacts with next commitments.
Decision memory
Meeting minutes, current policies, decision log, unresolved issues, lessons learned and why a recurring practice exists.
Digital continuity
Do not solve succession by making security worse.
The garden needs transferable access, but a printed password list or shared personal login creates a different failure. CISA recommends strong passwords, password managers and MFA for organizational systems. The practical goal is controlled administrative continuity.
Where the service allows it, use a garden/sponsor account and named administrators rather than tying the garden to a founder's personal email, phone number or social-media identity.
A password manager can hold strong unique credentials. Record where the approved vault lives and how authorized recovery works, not the password itself.
CISA recommends MFA wherever possible, particularly for email, file storage and privileged accounts. Design recovery so one departing person's personal device is not the only second factor.
When a role ends, review admins, authorized users, recovery contacts, keys and codes. Preserve records while removing access that is no longer needed.
Financial continuity
A new treasurer should inherit controls, not unchecked access.
For gardens operating as or under nonprofits, IRS recordkeeping rules and the sponsor's accounting policies govern the formal records. National Council of Nonprofits recommends internal controls that define who has account access and spending authority and use checks and balances rather than sole unchecked custody.
Close the old period
Reconcile the account, list unpaid bills/reimbursements, grants/restrictions, receivables and cash on hand before role transfer.
Transfer authority formally
Use the bank/sponsor's authorized-user or signer process. Do not hand over a personal login as a substitute for changing authorized roles.
Keep a second reviewer
A new treasurer should not become the only person who sees bank statements, reimbursements and spending decisions.
Retain supporting records
IRS says exempt organizations must keep books and records that support receipts, expenditures, activities and tax filings. Retention duration depends on record type, law and policy.
Founder workload
Burnout prevention is partly an architecture problem.
This page does not diagnose personal burnout. It looks for organizational conditions that make exhaustion predictable: the same person carries authority, knowledge, relationships, routine chores and emergency response because the garden never built backups.
| Observed pattern | System response |
|---|---|
| Founder is copied on every decision | Define decision rights by role and let role holders decide within them. |
| Nobody else knows the landowner | Add a second relationship owner and conduct a joint introduction. |
| Founder performs every unpleasant recurring chore | Assign rotating duties or a named committee with real membership, not a “committee of one.” |
| Founder rewrites volunteers' work | Create clear finish standards, train once, inspect appropriately, then allow others to own the result. |
| Founder cannot take a week away | Use the Garden Resilience absence handoff and practice backup authority. |
| Potential successor never gets real authority | Transfer a bounded role before the formal succession so competence can be observed and built. |
Decision table
Healthy, watch, correct or stop.
| Finding | Disposition | Action |
|---|---|---|
| Every critical role has an active backup who has practiced it | Healthy | Keep cross-training and annual review. |
| Records are shared but only one person has decision authority | Watch / Correct | Define emergency delegation and governing approval path. |
| Garden email/domain/bank access uses founder's personal identity | Correct | Migrate to sponsor/organization-controlled administration through the service's proper process. |
| Treasurer is sole account viewer, spender and reconciler | Correct | Add appropriate review/segregation under sponsor/accounting policy. |
| Leader departs suddenly and no transition authority exists | Stop nonessential decisions | Use governing documents/sponsor authority to appoint temporary leadership before making commitments. |
| Outgoing leader will not return keys, records, organizational accounts or assets | Stop / escalate | Secure accounts/assets and involve sponsor, governing body, bank/provider or professional adviser as appropriate. |
Failure diagnostics
Leadership loss usually reveals a system that was already fragile.
The leader leaves and nobody knows renewal dates.
Likely cause: calendar was personal. Response: build a shared annual deadline register tied to owners and source documents.
The successor gets folders but cannot act.
Likely cause: information transfer without authority transfer. Response: update signers, administrators, approvals, sponsor relationships and decision rights.
Nobody knows why a controversial rule exists.
Likely cause: policy without decision history. Response: preserve minutes/decision log showing what problem the rule addressed and when it should be reviewed.
The founder “retires” but still approves everything privately.
Likely cause: role transfer without authority boundary. Response: define mentor versus decision-maker and direct operational requests to the successor.
A departed volunteer still controls the garden's social/email account.
Likely cause: personal account ownership. Response: recover/migrate through provider processes, change admins/recovery methods and inventory accounts.
Every new leader rebuilds the garden's system from scratch.
Likely cause: records exist but lessons, decisions and operating procedures do not. Response: maintain decision history, annual reports, procedure cards and open-issues register.
Stop conditions
Do not solve continuity by ignoring authority, privacy or security.
What varies locally
The garden's legal home determines who can transfer what.
Do this yourself
Run the 60-minute founder-dependency test.
- List the ten decisions/tasks most likely to be needed in the next thirty days.
- Name the current role owner for each.
- Name a backup who has actually performed it.
- For every blank backup, mark a dependency.
- Locate the authoritative land agreement, insurance record, rules/bylaws and current plot roster.
- Locate the current bank/financial report and identify who independently reviews it.
- Inventory the garden's email, cloud, domain, social and payment accounts without writing down raw passwords.
- Verify at least two authorized people can recover/access the critical organizational systems through approved methods.
- Name five external relationships and confirm the garden has more than one path to each.
- List the next five annual renewal/reporting deadlines and their owners.
- Choose one decision whose reasoning exists only in someone's memory and write the decision history.
- Give the binder to another leader and ask them to explain how the garden would operate next month if you were unavailable.
Prove it
A durable garden can survive a leadership vacancy without losing control.
Sources and method
Community-garden records meet nonprofit continuity practice.
Prepared in September 2026 from NC State community-garden organization and recordkeeping guidance, current National Council of Nonprofits succession/document/financial-control resources, IRS recordkeeping requirements for tax-exempt organizations and current CISA small-organization account-security guidance.
Leadership roles, steering committees, delegation, accurate waiting-list/dues records and the committee-of-one risk.
NC State Extension · Record Keeping and EvaluationGarden records should be stored where multiple members can access them and used for long-term planning/evaluation.
National Council of Nonprofits · Succession PlanningEmergency transition plans, deeper leadership bench, cross-training, communication and deliberate onboarding.
National Council of Nonprofits · Document Retention PoliciesWritten retention/destruction policy, cloud/physical records, state variation and institutional-memory considerations.
National Council of Nonprofits · Internal ControlsAccount access, spending authority, segregation/review and checks and balances for nonprofit finances.
IRS · Recordkeeping Requirements for Exempt OrganizationsTax-exempt organizations must maintain books and records supporting activities, receipts, expenditures and required filings.
CISA · Require Multifactor AuthenticationCurrent organizational MFA guidance for email, file storage and privileged accounts.
CISA · Use a Password ManagerSecure password storage, recovery considerations and MFA for the credential vault.
Prepared by: New World Survival · Reviewed: September 4, 2026 · Verify locally: governing authority, state nonprofit law, sponsor policy, banking, privacy, document retention, tax/grant records and digital account-transfer procedures.
Common questions
Questions that expose the difference between having records and having continuity.
Should the founder keep access after leaving?
Only if there is a current authorized role that requires it. Review keys, bank access, cloud admins, social accounts, domain control and recovery methods at transition. Mentor status alone is not a reason to keep operational access.
Should we keep every garden record forever?
No. Retention requirements vary by document, sponsor, law and state. Use a written retention/destruction policy. Preserve records that have continuing legal, financial, property, governance or institutional-memory value.
Can we just put all the passwords in a sealed binder?
That creates unnecessary credential risk. Use an approved secure credential manager with MFA/recovery, and let the binder identify account owners, administrators and recovery procedures rather than raw secrets.
What if the garden is informal and not a nonprofit?
The continuity principles still apply, but the authority may belong to a landowner, church, municipality, school, HOA or informal member agreement. Do not borrow nonprofit legal procedures unless they actually govern the garden.
How do we know someone is ready to succeed the leader?
Have them perform real bounded responsibilities before transition. A capable successor can explain the role, locate records, make authorized decisions, complete recurring tasks and know when to escalate.
What is the strongest sign founder dependence is falling?
The founder can be unavailable without stopping routine decisions, and new leaders can operate from shared systems while preserving financial controls, relationships and safety boundaries.
Next skills
Succession becomes easier when the year's recurring work is visible before the leader changes.
Prerequisite
Garden Resilience
Emergency absence and minimum viable operation are the short-term version of leadership continuity.
Garden ResilienceNext Run-the-Garden guide
The Annual Community Garden Operating Calendar
Put renewals, plot assignments, meetings, inspections, water shutdown/startup, budgets, workdays, donation reviews and reporting dates into one owned calendar.
The Annual Community Garden Operating CalendarOperations
How to Run a Community Garden
Use the governance guide for roles, meetings, money, enforcement and annual operating review.
How to Run a Community GardenAnnual dependency check
Leadership depth should be tested as part of the annual health audit.
Do not wait for a departure to discover that a critical role has no practiced backup. Carry the role-and-backup matrix into the annual institutional health review.
Annual Garden Health AuditInstitutional turnover
Faith-community gardens must survive clergy, staff and ministry-leader transitions.
The host specialist maps property authority, institutional records, keys, money, pantry relationships and the garden calendar into the succession system.
Garden Programs for Houses of WorshipSeed-library continuity
Do not let seed intake judgment live with one volunteer.
The seed-library specialist turns legal correspondence, acceptance tiers, labels, inventory, storage and annual cleanout into transferable institutional records.
How to Build a Seed LibraryTool-library continuity
Tool inspection and repair knowledge must be transferable.
The Tool Library specialist turns collection scope, recall checks, condition status, repair vendors, borrower policy and inventory into records a backup can operate.
How to Build and Run a Community Tool LibraryCompost-system continuity
Do not let intake and batch judgment live with one experienced composter.
The community-compost specialist turns feedstock policy, legal checks, carbon supply, batch records, nuisance response and finished release into a system a backup can operate.
Community Compost SystemsInstructor succession
Do not let recurring workshops exist only in one teacher's memory.
The workshop specialist defines the instructor package, proof rubric and train-the-trainer rehearsal needed to transfer recurring garden education.
Teaching Garden Workshops That Build Real Skills