Picture a fellowship hall at a quarter to seven on a Wednesday evening. Six folding tables, fluorescent tubes buzzing overhead, and on the centre table, instead of the usual scalloped potatoes and meatballs, twenty-four small cups of raw celery and garlic paste.
Nobody has done this. I'm telling you up front that it's a thought experiment, with no real church and no real people in it. But I've spent enough years around both software and church basements to know exactly how it would go.
A church potluck is a shared meal where everyone brings a dish to a common table, with no caterer and no central menu. It's one of the least efficient systems in the world, and I'd say that's on purpose.
What an optimizer would see
I was a software engineer for fifteen years before I was a pastor for fifteen. Engineers are trained to look at a human system and hunt for friction. Four casseroles with mushroom soup and crushed crackers? Redundant supply chain. Three desserts heavy on sugar? Nutritional imbalance. Sign-up sheet twenty entries short? A scheduling problem, solved by pasting the list into a language model and asking it to balance the menu.
Imagine that it does what it was asked. It flags the casseroles as duplicates. It reassigns the longtime cooks to vegetable platters. It decides the apple pie that one cook has brought to every funeral lunch for forty years is a glycemic risk, and offers her a job at the compost bin. For the six dietary needs on the list it invents one steamed loaf, the colour of river silt, that soaks up every drop of gravy within reach.
Funny, yes. But notice that every one of those decisions is defensible on paper. That's the problem.
Why the repetition is the point
When a spreadsheet sees four identical dishes of pasta and tuna, it sees waste. A good elder sees four people, maybe widows or widowers who live alone, each bringing the one dish their hands know how to make with dignity.
Take the repetition out, and you've optimized the people out of the room.
Nobody drives through freezing rain on a Sunday because they want a balanced ratio of greens and grains. They come to sit across from someone who will listen to a story about a hip replacement while a paper plate bends under a slice of pie.
The apostle Paul had something to say about this kind of argument, and it wasn't about macronutrients. In Romans 14 he tells the church to accept the believer whose faith is weak "without quarreling over disputable matters." One person eats anything, another eats only vegetables, and Paul says God has accepted both. Food can divide a church quickly, and a tool that issues menu rulings from above would be walking straight into it.
Where a tool can help
I'm not against software in the church kitchen. A shared sign-up sheet that shows who's bringing what helps. A reminder text the day before helps. A clear label on the dish that's gluten-free or nut-free helps a lot, and it helps without telling anyone what to cook.
The best approach to dietary needs is labelling, not restriction. Give the allergy-safe dishes a spot at the table, leave everyone's recipes alone, and let people choose with good information.
And a phone assistant can take care of the office side of supper night, like answering the call from a visitor who wants to know what time it starts and whether they should bring something. At ChurchWiseAI that's the kind of job our phone assistant does, answering in the church's name and passing messages to the person the church chooses. It doesn't plan the menu. It shouldn't.
The last word goes to the pie
If your church ever runs its potluck through an algorithm, put the spreadsheet in the recycling bin on Friday and give the pie table back. Some things in church life are meant to be abundant, repetitive and a little messy. That's where the community actually lives.
Frequently asked questions
Should churches use software to organize a potluck?
For simple jobs, yes: collecting sign-ups, sending a reminder, and counting how many are coming. Letting software assign menus or reassign longtime cooks risks hurting people over something that was never broken.
How can a church handle dietary restrictions without offending anyone?
Label dishes clearly and give allergen-free options a visible spot, rather than limiting what people may bring. People with restrictions can choose safely, and everyone else keeps cooking what they love.
What church tasks are good candidates for automation?
Repetitive, factual ones: reminders, room bookings, bulletin formatting and answering routine phone questions like times and directions. Anything involving pastoral care or a person's dignity should stay with people.
What does the Bible say about disagreements over food?
In Romans 14:1-4, Paul tells believers to accept those whose faith is weak and not to quarrel over disputable matters, including what people eat. He reminds the church that each person answers to their own master.