Gluts, Plans and the Community Kitchen

A community kitchen handles a glut by deciding, before the harvest, what it will do with the excess. The plan names the crops, the volumes, the preservation methods and the people responsible. That plan then travels back to the grower as a planting list for the next year, so the surplus is designed rather than endured. Menus, recipes and opening hours from a neighbourhood kitchen on Clifton Street survive as a record of how a fixed site coped with whatever the week delivered, and the Canteen on Clifton Street menus read as a sequence of decisions rather than a list of dishes.

The kitchen that cooks what a garden cannot sell is not solving a storage problem. It is running a negotiation between two calendars: the garden's, which is fixed by weather and day length, and the kitchen's, which is fixed by service, staff and shelf life. The plan is the document where those two calendars meet. Without it, the glut arrives as an emergency, and the emergency decides the menu.

The archive of a Cardiff canteen shows the same logic at work in a much smaller room. A kitchen with a printed menu and a short season has to choose early, and that choice is the plan.

How do you plan for a glut?

A glut is planned for by naming it in advance. The kitchen and the grower sit down before the seed order and agree on three numbers per crop: the expected harvest, the volume the kitchen can take fresh, and the volume it can process. The gap between the second and third numbers is the glut, and it is known months before it arrives.

The plan then assigns each gap a destination. A crop with a short fresh window and a long processing window goes to the kitchen's busiest preservation week. A crop that cannot be processed at all is capped in the planting list, or dropped. The grower is not asked to grow less out of caution; the grower is asked to grow what the kitchen has already agreed to receive.

Three details make the plan usable. First, dates rather than months: the week the broad beans peak, the week the courgettes run away. Second, a named person on each side, so the phone call happens before the crate is full. Third, a fallback for every crop, usually a second kitchen, a livestock holding or a compost heap, so nothing rots in a doorway while two organisations wait for each other to decide.

What can be preserved without a licence?

Most preservation that a community kitchen does is covered by ordinary food business registration, not by a separate licence. The distinction that matters is between processing food for sale and processing food for storage. A kitchen already registered to prepare and sell food can generally freeze, dry, ferment, pickle, chutney, jam and bottle high-acid products in the same premises, provided the process is documented and the storage is safe.

The line is crossed by low-acid canning, which is the bottling of vegetables, meats and stocks in sealed jars without acidification. That process carries a botulism risk and requires a validated process, a pressure canner and, in most jurisdictions, a documented food safety plan signed off by the local authority. A community kitchen that wants to bottle beans or stock should treat it as a separate project, not as an extension of jam week.

Fermentation sits in a useful middle ground. Salt brines, lactic ferments and vinegar pickles are low-risk when the recipe controls acidity and salt concentration, and they need no special licence in most of Canada and the United Kingdom. They do need a written recipe, a temperature log and a shelf that is not next to the fresh produce. Drying is the cheapest option and the most forgiving: herbs, mushrooms, tomatoes and fruit need airflow, low humidity and time, and they turn a two-week glut into a year of seasoning.

How does a kitchen tell a grower what to plant?

A kitchen tells a grower what to plant by sending back a record of what it actually used. The record is not a wish list. It is a count of crates received, crates cooked, crates preserved and crates refused, with the reason for each refusal written next to it.

That record changes the next seed order in three ways. It removes crops that arrived in volumes the kitchen could never absorb. It multiplies crops that processed well and sold well in preserved form. It adds crops that fill a gap in the kitchen's calendar, such as a winter brassica that keeps the menu local in February.

The grower keeps the final say, because the grower knows the soil, the rotation and the labour. The kitchen's job is to be honest about capacity. A kitchen that says it can take a tonne of tomatoes and then refuses half of them has taught the grower to ignore the next request. A kitchen that says it can take 200 kilograms, and takes 200 kilograms, has earned the right to ask for a different variety next year.

What is wasted, and why?

Waste in a community kitchen comes from four places, and only one of them is the garden. The first is timing: a crop peaks in a week when the kitchen has no staff, no freezer space or no service. The second is specification: the kitchen can use a cosmetically imperfect carrot but not a split one, and the grower has no market for the split ones either. The third is processing capacity: the kitchen can cook the glut but cannot cool, pack or store it fast enough. The fourth is communication: the crate arrives, nobody knows it is coming, and it sits.

Each cause has a different fix. Timing is solved by the planting list and by a shared calendar. Specification is solved by agreeing on grades in advance and by finding a use for the rest, usually livestock or compost. Processing capacity is solved by borrowing equipment, renting freezer space or scheduling a preservation week when volunteers are available. Communication is solved by a single point of contact on each side and a standing weekly call during the growing season.

The waste that remains is worth measuring, because it is the number that justifies the plan. A kitchen that records what it refused, and why, can show a grower exactly which crop is costing both organisations money. That record is also the evidence a funder or a local authority asks for when the kitchen applies for a larger freezer or a second stove.

Why the plan decides next year's planting

The plan is not a document about surplus. It is a document about intention. A kitchen that writes down what it will do with a glut is telling the grower what kind of garden to plant, and the grower is telling the kitchen what kind of menu to write. The two organisations are not separate: they are one supply chain with two calendars, and the plan is where the calendars are reconciled.

A kitchen that skips the plan does not avoid the work. It moves the work to the moment the crate arrives, when the options are fewer and the decisions are worse. A kitchen that writes the plan does the work in winter, when there is time, and spends the summer cooking instead of improvising.

The test of a good plan is simple. In August, when the courgettes are arriving faster than anyone can count them, nobody in the kitchen should be surprised. If they are, the plan was a wish list. If they are not, the plan is doing its job, and the seed order for next year is already written.