Planning a community kitchen bulk bean buying and cooking day

A community kitchen bean-buying and cooking day works best when shopping, preparation and eating are treated as one shared project. Cowichan Valley residents can borrow the same practical rhythm used by Australian community groups: agree on the menu, pool money and skills, cook in batches, then sit together for a meal. The result is cheaper food, fewer solitary kitchen sessions and stronger connections between neighbours.

For an Australian version, work in grams and kilograms, expect 500 g or 1 kg packs, and compare prices at Coles, Woolworths or a local IGA. A council library, neighbourhood centre or community hall can provide the space, while participants may bring a plate, a snap-lock container or a keep cup. A friendly “no worries” approach, a clear head count and a Saturday arvo start time help a mixed group feel comfortable.

Choose the menu before the shopping list

Start with the number of people and what the beans are for. For a main meal, allow roughly 80–100 g of dried beans per person; for a side or mixed dish, 40–60 g. Dried beans expand to about two to two-and-a-half times their uncooked weight, so a 1 kg bag becomes around 2–2.5 kg cooked. Record the target cooked yield beside each recipe.

Choose dishes that can share equipment and ingredients, such as a lentil and vegetable curry, baked beans and a bean salad. Keep the first menu to two cooked dishes plus one salad or wrap, then plan rice, herbs and toppings separately. Ask about allergies, gluten needs and vegetarian diets before ordering; label every ingredient and keep an alternative portion in mind.

The Cowichan Community Kitchens website offers recipes, cooking sessions, events and newsletters, making it a useful starting point for a Cowichan Valley event. Adapt the quantities to your own head count rather than copying a large commercial recipe.

Build the budget and buying plan

Build a spreadsheet with every ingredient, quantity and estimated unit price. Include dried or tinned beans, onions, garlic, tomatoes, spices, herbs, salad ingredients, cooking oil, serving spoons, gloves, bin liners and transport. A supermarket bag may look cheaper per kilogram, but soaking, fuel and storage should be included in the real cost per cooked serve.

Set a spending limit before anyone shops and choose one nominated buyer to prevent duplicate orders. Reserve a small contingency for extra produce or forgotten basics, but keep it under 10 per cent of the budget. Record payments and receipts, and ask the treasurer to reconcile them after the meal.

If the group needs to subsidise ingredients or equipment, local businesses can help through cash or in-kind support. The nonprofit’s community sponsors page explains how organisations can support its work, and the same approach can be adapted for a local cooking day.

Assign roles and make the day easy to join

Create a simple roster covering shopping, money, food safety, preparation, cooking, welcoming guests, serving and cleaning. Each shift should have a lead and a backup, while less experienced volunteers handle sorting, labelling, washing, peeling and packaging. This keeps the event welcoming to people who want to contribute without taking on a professional kitchen task.

Confirm RSVPs through the community newsletter, an email list or a local social media group, then post the head count, parking details, accessibility information and what to bring. Check the venue’s council food-handling rules, insurance requirements and first-aid arrangements. Offer a no-cooking role for anyone who prefers not to work near hot equipment, and make sure the welcome table explains where to put coats and bags.

Prepare the kitchen and teach as you cook

Set up separate stations for dry goods, washing, chopping and hot cooking. Provide handwashing facilities, sanitiser, paper towels, scales, large bowls, colanders, chopping boards and clearly marked allergen containers. Keep raw meat and strong allergens away from beans and ready-to-eat salads, and use clean utensils for serving. Before the session, send volunteers to the knife skills guide for a practical refresher on grip, board stability and safe cutting.

Soak dried beans overnight, then cook them in batches with enough water to expand freely. Record when each batch enters the pot so it is ready at serving time, and keep one labelled batch free from ingredients that may cause an allergy concern. If the community site includes a cob oven, reserve it for roasting vegetables or baking bread rather than beans, which are easier to control by gentle simmering.

A sample Saturday arvo could run from 9:00 am for setup, 10:00 am for shopping and preparation, noon for cooking and 4:00 pm for the shared meal. Give volunteers a printed run sheet with arrival times, job locations, rest breaks and the names of the first-aid and food-safety leads. A short demonstration at the start is more useful than a long lecture.

Serve the meal and keep the community at the table

Set out the food in a buffet order: plain portions first, then toppings, cutlery, napkins and labelled allergen information. Keep hot dishes above 60°C and chilled ingredients below 5°C, following the venue’s food-safety guidance. Ask guests to use a clean plate for each visit, and provide containers for leftovers so nobody carries an open scoop home on the bus.

A local connection can make the event feel less like a bulk-cooking exercise. If the venue wants a supplier connection, ask Tea Farms whether it can contribute produce, a speaker or contacts for local sourcing, confirming any contribution before advertising it. While people eat, invite recipes, gardening tips and volunteer offers; collect brief written feedback and use it to adjust the next gathering.

Plan the follow-through

Send surplus food only through an organisation that can accept and store it safely, and follow local food-donation requirements. Clean the venue, return borrowed equipment, reconcile receipts and record the number of serves, food cost, volunteer hours and leftovers. A short summary can then go into the community newsletter, thank sponsors and identify which supplies are worth buying for the next event.

Create one shared event brief with the date, head count, menu, buyer, kitchen lead and order deadline.