How to run a lunch-break recipe swap at work
· Editorial team newsfromla7.com

Run a lunch-break recipe swap by asking colleagues for one recipe each, collecting contributions in a consistent format, and using lunch to share practical cooking tips. Keep participation optional and give everyone access to the recipes afterward. The proposed setup below fits a 30-minute break and welcomes both beginners and experienced cooks.
Set a small scope and send a clear invitation
Choose one manageable theme for the first swap: weekday dinners, packed lunches, pantry meals, or dishes colleagues enjoy making. A broad enough theme lets people contribute without buying ingredients or learning something new. Make clear that this is a recipe exchange; bringing food is optional and unnecessary.
As an editorial proposal, invite contributions several days ahead and set the deadline before the lunch session. Include the time, location, theme, submission method, and where the finished collection will live. Use a shared space and communication channel appropriate for your workplace.
Keep the invitation relaxed: “Bring one recipe you enjoy making, plus a tip that helps it work. You’re also welcome to come, listen, and collect ideas.” Allow colleagues to submit a recipe even if their schedule prevents them from attending.
Give everyone the same recipe format
A consistent format makes contributions easier to compare and follow. Ask people to include enough detail for someone who has never made the dish. The following submission format is a proposal for the swap:
- Recipe name and contributor’s preferred display name.
- Yield or number of servings.
- Preparation and cooking time, with any soaking, chilling, or resting time stated separately.
- Ingredients with quantities and any preparation needed, such as drained beans or chopped onions.
- Numbered instructions, including temperatures and signs that each stage is complete.
- Equipment needed, especially anything beyond ordinary pots, pans, and utensils.
- Original source or family attribution, whether the contributor has cooked it, and one useful tip.
Invite contributors to record changes they have actually used, such as a different ingredient or adjusted quantity. Keep untried substitutions clearly marked as suggestions. Separating recipes people have cooked from those they only want to try helps readers understand what the contributor can speak about firsthand.
Collect and organize recipes before lunch
Choose one collection method: a shared document, a folder with an index, or printed pages in a binder. Digital and paper systems are both options; choose according to how colleagues prefer to access recipes. Avoid requiring a new account just to take part.
- Gather submissions in one place, including typed versions of handwritten contributions where needed.
- Check for missing quantities, unclear steps, or unexplained equipment, and ask the contributor to clarify.
- For published recipes, retain the original link or cookbook title and page number alongside the contributor’s notes.
- Add a few useful categories, such as soups, vegetarian meals, packed lunches, or one-pot dishes.
- Prepare an index with recipe names and contributors so attendees can quickly find what interests them.
Keep categories limited at first. A small collection does not need a complicated filing system. Add more specific labels only when they help people locate recipes.
Use lunch for tips and practical questions
The proposed 30-minute agenda below leaves room to eat while keeping the exchange focused. For a larger group, invite a few contributors to speak and let everyone else add notes to the collection.
- First five minutes: welcome everyone, show where the recipes are stored, and explain the speaking order.
- Next 15 minutes: give each featured contributor a brief turn to describe the dish, its trickiest step, and one helpful tip.
- Next seven minutes: take questions about ingredients, equipment, timing, and techniques.
- Final three minutes: explain how to access the collection and invite corrections or follow-up notes.
Help beginners by asking concrete questions: How small should the vegetables be cut? What does “softened” look like? Which steps can happen while something else cooks? Invite experienced cooks to explain unfamiliar terms. Give quieter attendees the option to write a question instead of speaking.
Share a collection people can use again
After lunch, send one message with the collection’s location and any answers that needed clarification. Check that intended participants can open it, and provide a printable option if requested. Ask before sharing colleagues’ names or personal recipe stories beyond the group.
As a follow-up proposal, invite anyone who cooks a contributed recipe to add a short note about what they changed or found unclear. Keep the original instructions intact and place adaptations underneath. Choose a next theme only if colleagues want another session; the first swap is complete once everyone has a usable recipe collection.