Produce Sharing, Donation and Distribution

The five-minute answer

Establish ownership. Produce from an individual plot belongs to the gardener unless the garden's written rules clearly say otherwise. Do not assume unattended or overripe crops have become communal property.
Choose a channel. Use the least complicated channel that fits the purpose: personal sharing, member exchange, garden share table, community giveaway, charitable donation or institutional recipient.
Confirm the receiver before harvesting for an organization. Ask what they accept, how much they can use, preferred harvest day, packaging, washing, refrigeration and drop-off requirements.
Release only sound produce. Keep it whole unless the receiving system is equipped and permitted for cut produce. Exclude visibly spoiled, rotten, animal-contaminated, flood-contacted or otherwise questionable produce.
Protect the handoff. Use clean harvest containers, clean hands, suitable transport and appropriate temperature control. Keep produce out of sun, vehicles and unattended tables longer than the channel can safely tolerate.
Record what matters. A formal donation or institutional handoff should normally record source, date, crop, approximate amount, recipient and transporter. A simple member swap usually needs less.
Close the loop. Remove unclaimed produce before it becomes waste, ask recipients what worked, and change crop planning or distribution frequency when the same surplus repeatedly goes unused.

What this page covers, and what it does not

This page is about the distribution system. It starts when fresh produce is ready to move from the person or garden that grew it to another user. It does not replace the garden's crop-production, food-safety or donation-garden procedures.

Related topic	Primary job	Boundary for this page
Harvesting, Handling and Storing Garden Produce	How to harvest and handle produce well.	This page assumes sound harvest practices and concentrates on routing and custody.
Food-Bank and Donation Gardens	How a garden designed for donation organizes production and food-safety practices.	This page covers the broader choice among informal sharing, garden distribution and formal recipients.
Produce Donation Systems	Detailed charitable-donation procedures and food-safety controls.	This page links to that specialist process rather than reproducing it.
Planning What to Do With Surplus Produce	Household-level planning for eating, preserving, sharing and avoiding surplus.	This page stays at the community-garden distribution-system level.
Freezing, Dehydrating, Canning, Fermentation and Pickling	Safe preservation methods.	Home-preserved or processed foods are outside this fresh-produce routing system unless a recipient has an explicit lawful program for them.

Why distribution is a garden-system skill

A productive garden can still waste food. The failure is often not horticultural. It is logistical. Five gardeners may bring zucchini to the same table on the same afternoon. A pantry may have no refrigerator space. A senior center may accept tomatoes but not leafy greens. A public share table may be empty at lunchtime and full of wilted produce at sunset. A volunteer may wash everything even though the recipient asked for dry, field-cleaned produce. Another volunteer may assume that a federal food-donation law makes every possible sharing arrangement automatically protected.

A durable system makes a few decisions in advance: who owns the crop, who may release it, which channels exist, what each channel accepts, what quality standard applies, who is responsible during handoff, what gets recorded, and what happens when a channel cannot receive the harvest.

What you need

the garden's rules or plot agreement, especially any language about crop ownership and abandoned plots;
a list of possible distribution channels and contact people;
the recipient's written or verbal acceptance requirements;
clean harvest containers or approved packaging;
a way to protect produce from sun, dirt, animals, chemicals and unsuitable temperatures;
a simple distribution log for formal handoffs;
local health department, Cooperative Extension or recipient contacts for questions the garden should not improvise.

The six-channel distribution ladder

Not every surplus harvest needs the same institution. Use the smallest system that remains appropriate for the amount of food, the recipient and the level of responsibility.

Channel	Best fit	What must be clear	Typical record level
1. Personal sharing	A gardener gives produce directly to a friend, neighbor or another gardener.	The gardener owns the produce and the exchange is voluntary.	Usually none.
2. Member exchange	Gardeners trade or offer extra produce inside the garden membership.	Rules for what may be placed, when it must be removed and whether taking is open to all members.	Usually none or a simple use count.
3. Garden share table	A managed table or shelf offers whole fresh produce to gardeners, neighbors or visitors.	Permission, operating hours, eligible items, monitoring, end-of-day removal and local rules.	Simple daily check or weight count if useful.
4. Community giveaway	A scheduled free distribution event with volunteers present.	Site permission, receiving flow, food handling, quantity, leftovers, accessibility and local requirements.	Event totals and incident notes.
5. Charitable donation	Fresh produce is transferred to a food pantry, food bank, rescue organization or nonprofit program.	Recipient acceptance, timing, quality, packing, transport and local/state requirements.	Donation log and recipient record as requested.
6. Institutional recipient	A school, senior program, meal program, hospital, shelter or other institution receives garden produce.	The institution's procurement, food-safety, receiving, traceability and insurance requirements.	Recipient-defined documentation.

Choose the channel with seven gates

Run the harvest through these gates in order. A later gate cannot repair a failure at an earlier one.

Gate 1: Ownership and authorization

Ask who has the right to release the crop. Individual-plot produce should not be harvested for sharing simply because the gardener has not visited recently. If the garden reallocates abandoned plots, the rules should specify when that happens and what may be done with remaining crops.

Gate 2: Product condition

Share food, not disposal problems. Produce should be sound enough that the garden would be comfortable using it. Reject rotten or moldy items and produce with obvious fecal or other contamination. Whole produce is simpler to route than cut produce because cutting creates additional handling and temperature-control concerns.

Gate 3: Recipient fit

Ask what people can actually use. Donation programs repeatedly emphasize communication with receiving organizations because storage, operating hours, quantity and cultural preferences affect whether fresh produce will be used. A hundred pounds delivered to a site that can use twenty is not a successful donation.

Gate 4: Timing

Harvest close enough to handoff that the crop arrives useful, not exhausted. If a pantry is closed for two days, delay harvest where crop quality allows or route the produce elsewhere. Highly perishable crops need a shorter chain than winter squash or potatoes.

Gate 5: Handling and transport

Use clean hands, clean containers and clean transport areas. Keep produce away from chemicals, trash, animals and raw animal products. Protect it from heat and direct sun. When refrigeration is required for the crop or by the receiving organization, maintain it.

Gate 6: Rules and liability

Federal law provides important food-donation liability protections in defined circumstances, but it is not a blanket permission slip for every garden sharing arrangement. The Bill Emerson Good Samaritan Food Donation Act protects specified good-faith donations of apparently wholesome food, including many donations through nonprofit organizations. The law also now includes direct-to-individual protection for defined qualified direct donors. Whether a particular community garden or distribution arrangement fits a statutory category may require local legal or organizational review. Federal protection does not override state or local health rules.

Gate 7: Custody and closeout

Know when garden responsibility ends. For a staffed handoff, that point may be a signed or logged transfer. For a share table, responsibility includes monitoring and removing food that no longer belongs there. An unattended pile with no closing procedure is not a distribution system.

Distribution decision table

Finding	Disposition	Action
Produce owner agrees, crop is sound, receiver has confirmed quantity and timing.	Proceed	Harvest, protect, record as appropriate and transfer.
Produce is sound but the planned recipient has not confirmed storage or drop-off capacity.	Investigate	Contact the recipient before harvesting for them. Use another channel if needed.
Share table works, but food remains at closing or repeatedly wilts before pickup.	Modify	Reduce quantities, shorten hours, move to shade/cooling where appropriate, increase pickups or use a different channel.
Ownership is unclear or a volunteer plans to harvest another member's plot without authority.	Stop	Resolve the garden-rule issue before harvesting.
Recipient asks for washed produce but the garden lacks potable water or a clean wash setup.	Modify or Stop	Ask whether field-cleaned, unwashed produce is acceptable or use another recipient. Do not improvise a questionable wash process.
Produce contacted floodwater, visible animal feces, sewage or another serious contaminant.	Stop	Do not distribute. Follow authoritative disposal and site-recovery guidance.
A school or other institution wants garden produce but has not established receiving procedures.	Investigate	Use the institution's nutrition/food-service, health and risk-management channels before delivery.

A share table should make generosity easier without creating ambiguity or waste. Treat it as a small operating station.

Define who may contribute. Members only, approved community growers, or another defined group.
Define what may be placed. Start with whole, sound, fresh produce. Exclude home-canned foods, cut produce, unlabeled prepared foods and other categories unless a separate verified system covers them.
Set hours. Avoid a permanent unattended table unless the host and local rules support it and the garden can monitor food condition.
Provide shade and separation. Keep produce off the ground and away from chemicals, compost, trash, tools, pets and contaminated surfaces.
Use a clean surface and containers. Clean before opening and as needed during use.
Post simple instructions. Example: “Free garden produce. Take what you will use. Wash produce before eating. Please do not add cut, cooked or preserved foods.” Adapt to local requirements.
Assign a monitor. Someone should remove spoiled items, keep the station orderly and close it.
Have an end-of-day route. Remaining produce goes to a confirmed recipient, back to the contributor where practical, or to an appropriate waste/compost stream if no longer distributable.

How to run a scheduled community giveaway

A staffed giveaway can handle more produce and more people than a passive table, but it also creates more responsibility.

Choose a location the host allows for distribution.
Verify any local health, permitting or organizational rules that apply.
Forecast quantity and likely attendance conservatively.
Set the acceptance standard before produce arrives.
Provide clean receiving and display surfaces.
Keep distribution simple and dignified. Avoid unnecessary proof-of-need requirements unless the host program requires them.
Make access physically workable for older adults and people with disabilities.
Assign opening, monitoring and closing roles.
Record broad quantities and any incident or rejection that should change the next event.
Have a leftover route before opening.

How to route produce to a food pantry or nonprofit

Recipient communication comes first. Extension programs repeatedly advise gardeners to contact the pantry before harvest or delivery. The receiving organization knows its client demand, storage, hours and handling capacity.

Identify the recipient and a named contact.
Ask what crops are useful. Include preferred varieties or culturally familiar crops when the organization can identify them.
Ask what they do not accept. Do not assume every pantry accepts every crop or home-produced item.
Ask about quantity. A small site may have limited cold storage or distribution volume.
Ask about harvest and delivery timing.
Ask how they want produce packed and whether they want it washed. Do not impose one universal prewashing practice. Guidance varies by crop and recipient; washing can also shorten shelf life for some highly perishable produce.
Harvest with clean hands and clean containers. Do not harvest for donation while ill with symptoms that could contaminate food.
Keep produce whole. Minimize post-harvest handling unless the recipient has a defined process.
Transport promptly and cleanly.
Record the handoff. Date, crop, approximate amount, source/garden, recipient and transporter are usually enough for a small garden unless the recipient requires more.

Institutional recipients need their own receiving system

A school, senior center, congregate meal program, shelter or other institution may have procurement, receiving, insurance, refrigeration and traceability requirements beyond those of informal sharing. USDA guidance for school gardens, for example, permits schools to accept community-grown produce when it is safe and acceptable, but explicitly tells programs to check state, local and school-district requirements and to establish receiving controls.

Do not arrive with a harvest and ask staff to invent a policy at the loading door. Establish the relationship in advance, name the responsible staff member, document what will be accepted and follow the institution's procedures.

Build a release standard

A garden needs a simple, visible standard that prevents donation from becoming a way to unload produce no one wants. “Edible” is too vague for a shared operating system.

Release	Review	Reject from distribution
Whole, sound, reasonably mature produce; ordinary cosmetic variation; clean enough for the chosen channel; no visible spoilage.	Minor bruising, insect damage or short shelf life. Ask whether the specific recipient can use it promptly.	Rot, mold, sliminess, severe decay, visible fecal contamination, flood-contacted produce, questionable chemical exposure, or produce that violates a pesticide label harvest interval.

Cosmetic imperfection is not automatically a reason to reject food. The federal definition of “apparently wholesome food” recognizes that food can be suitable even when appearance, size, grade or surplus makes it less marketable. However, a recipient may still set its own quality standard, and a garden should respect it.

Do not make “wash everything” a universal rule

Produce handling guidance is more nuanced than a slogan. FDA advises consumers to wash fresh produce under running water before preparing or eating it and not to use soap or detergent. Donation programs may prefer field-cleaned, unwashed produce for some crops because added moisture can shorten shelf life. Other recipients may require washing. Therefore:

ask the recipient what condition it wants;
if washing is required, use potable water and a clean setup;
do not wash produce in questionable water;
do not use soap, detergent or unapproved produce washes;
allow produce to dry when appropriate before packing;
keep the final consumer instruction clear: fresh produce should be washed before preparation/eating unless it is specifically labeled as ready-to-eat by a lawful processing system.

Fairness, dignity and access

A distribution system is not healthy simply because produce leaves the garden. Consider who can use the channel and who is unintentionally excluded.

Do not let volunteers quietly reserve the best produce. If volunteers may take produce, define the rule openly.
Avoid “first come, first served” as the only method when timing predictably excludes working households. Rotate pickup times or use multiple channels when possible.
Do not require public disclosure of hardship unless the partner program requires eligibility documentation.
Ask recipients what crops people actually want. Culturally familiar produce is more useful than impressive harvest totals that go uneaten.
Design the physical handoff for real access. Consider path surface, reach, shade, seating, parking/transit and the ability to carry produce.
Measure waste as well as pounds distributed. A high distribution number can hide an unsuitable crop mix or poor timing.

Use the minimum record that matches the channel

Do not bury a small garden in paperwork. Increase record depth as responsibility increases.

Channel	Suggested record
Personal sharing	None.
Member exchange	Optional seasonal participation count.
Managed share table	Date, opening/closing check, approximate quantity if the garden measures impact, disposal/leftover note.
Community giveaway	Date, quantity, volunteer lead, leftovers, incidents/complaints.
Charitable donation	Date, crop, approximate amount/weight, donor source, recipient, transporter, any rejection or special handling note.
Institutional recipient	Use the institution's required receiving/traceability record.

Failure modes and corrections

What you observe	Likely system cause	Do now	Prevent recurrence
Share table repeatedly ends with wilted produce.	Too much volume, poor timing, heat exposure or weak demand.	Remove unsuitable food and route usable food promptly.	Shorten hours, reduce quantity, add a second channel, coordinate harvest.
Pantry rejects part of the delivery.	Recipient requirements were not confirmed or quality standard was unclear.	Ask why, record it, reroute only if still suitable.	Use a recipient acceptance sheet before the next harvest.
Volunteers harvest from member plots for donation.	Ownership and abandoned-plot rules are ambiguous.	Stop harvesting and return to leadership/rules process.	Write explicit authorization rules.
Large harvest arrives after recipient closes.	No confirmed handoff window.	Protect the crop and locate another confirmed recipient if quality allows.	Confirm day and time before harvest.
Best crops disappear before public distribution.	Volunteer/member privilege is undefined.	Pause informal taking.	Write a transparent allocation rule.
Recipient says certain crops go unused.	Crop plan was driven by what growers like to grow rather than recipient use.	Reduce future deliveries of that crop.	Collect recipient preference data before seed ordering.
Garden boasts about donated pounds but cannot explain destination or waste.	Impact metric is too shallow.	Review records and ask recipients about use.	Track acceptance, rejection and recurring leftovers in addition to pounds.
Unattended share station accumulates prepared foods from the public.	Scope and monitoring rules are missing.	Remove items not covered by the garden's verified system.	Post accepted-item rules and assign monitors.

Stop conditions

Stop if ownership is unclear. Resolve the plot or garden-rule issue before harvesting or distributing.
Stop distribution of produce that contacted floodwater, sewage, visible fecal contamination or another serious contaminant. Use authoritative recovery guidance.
Stop if a pesticide label's harvest interval or use requirements were not followed or cannot be established.
Stop if a recipient requires a handling step the garden cannot perform safely. Find another channel rather than improvise.
Stop institutional delivery when the institution has not approved a receiving process.
Stop using an unattended share point when spoiled food, pests, illegal dumping or repeated unsafe additions cannot be controlled.
Do not claim federal liability protection for a specific garden arrangement without establishing that the arrangement fits the law.

Verify this locally

Public share tables or free stands: municipal/county health department, property owner, sponsoring organization.
Food pantries and food banks: the receiving organization's current acceptance and food-handling policy.
Schools and institutional food service: nutrition director or food-service manager, health authority, risk management and district/host policy.
State food-donation and liability rules: state agriculture/health agency or qualified legal counsel when the organization is relying on statutory protection.
Tax deductibility: qualified tax adviser. Do not infer a deduction from the fact that food was donated.
Pesticide questions: product label, state pesticide regulator and Cooperative Extension.
Flood or contamination questions: local/state health or environmental agency and Cooperative Extension.

How to judge whether the distribution system is working

Do not evaluate the program only by pounds moved. A garden can report a large number while producing crops recipients do not want, overloading one volunteer, or discarding significant leftovers after the handoff. Review the system at least once each growing season.

Signal	Healthy pattern	Watch or correct
Recipient acceptance	Most planned deliveries are accepted as arranged.	Repeated rejection, surprise quantity or incompatible packaging.
Leftovers	Share-table or event leftovers are modest and have a known route.	Recurring wilted, spoiled or abandoned produce.
Crop fit	Recipients request or use the crops the garden supplies.	The same crop repeatedly goes unused.
Timing	Harvest and receiving windows are coordinated.	Produce waits in vehicles, sun or closed facilities.
Volunteer load	Harvest, transport and monitoring roles can rotate.	One person is the only driver, recipient contact and recordkeeper.
Records	Formal channels can reconstruct basic handoffs without burdensome paperwork.	No one can identify where a disputed or rejected delivery came from.
Fair access	Rules are visible and intended recipients can realistically use the channel.	Informal privilege, inaccessible pickup or timing excludes the same people repeatedly.
Safety and rule stops	Volunteers know when to pause and refer a question.	Unsafe food is routed onward because volunteers feel pressure not to waste it.

Do this yourself: map one harvest through the system

Choose one crop that is likely to be abundant in the next four weeks. Do not wait until harvest day.

Estimate the likely surplus after gardener use.
Name the owner or authorization source.
Choose a primary channel and a backup channel.
Contact the receiving organization if the channel is formal.
Write its acceptance, timing, washing, packing and quantity requirements.
Identify who harvests, who transports and where custody changes.
Choose the record the garden will keep.
Decide what happens if half the produce remains after the planned handoff.

If the exercise reveals that no one knows who may release the crop, when the recipient is open or what happens to leftovers, the garden has found a distribution-system gap before it became food waste.

Prove it

□ I can name the six distribution channels and explain when each becomes more demanding.
□ I can establish who has authority to release produce before harvesting it.
□ I can contact a recipient and document what, how much and when it will accept.
□ I can apply a release standard that does not confuse donation with disposal.
□ I can explain why prewashing is not a universal rule for donated produce.
□ I can operate a share table with opening, monitoring and closing responsibilities.
□ I can keep a proportionate handoff record for formal distribution.
□ I know when food safety, institutional policy, local law or liability requires outside verification.

Printable tool

Produce Sharing & Distribution Workbook

The standalone workbook includes the channel map, ownership check, recipient contact sheet, release standard, share-table opening/closing checklist, donation handoff log, problem/referral record and end-of-season distribution audit.

Open the printable workbook

Next skills

Prerequisite: Harvesting, Handling and Storing Garden Produce.
Specialist dependency: Produce Donation Systems.
Institutional dependency: Food-Bank and Donation Gardens.
Household surplus companion: Planning What to Do With Surplus Produce.
Resilience next step: Community Garden Drought Plan.

Sources and method

Prepared by New World Survival. Substantive review date: September 5, 2026. This guide synthesizes current FDA and USDA food-safety guidance, current federal food-donation law summaries, land-grant Extension guidance on fresh-produce donation, and community-garden operating principles. It is written as a national decision framework. Recipient requirements and state/local rules must be verified where applicable.

Important limit: This page is not legal advice and does not determine whether a particular garden, donor or distribution method receives liability protection under federal or state law.

After completing this guide, you should be able to