Every synagogue in North America runs on volunteer labor. And almost every one of them has quietly built a system where volunteers can’t actually do anything without staff permission. This is how community burns out.
These aren’t dramatic failures. They’re a thousand small frictions that add up to volunteers quietly giving up.
The committee meets Sunday. The announcement needs to go out Tuesday. The request goes to the office Monday morning, gets seen Wednesday, and goes out Thursday — past peak attention. Multiply by every week of the year.
The directory is in a shul management system with one admin seat. The calendar is in someone’s Outlook. The mailing list is on a platform only the bookkeeper knows the password to.
Shiva meal sign-ups in a Google sheet. Chevra kadisha on a WhatsApp group. Kiddush sponsor list on a yellow legal pad. The context lives in people’s heads.
The most common exit interview from synagogue volunteering is not “I didn’t care.” It’s “I spent more time chasing approvals than doing the thing.”
Almost every piece of software your synagogue uses — ShulCloud, Rakefet, Breeze, ChMS tools — was designed for a professional administrator sitting at a desk. That’s fine. But it means the 95% of shul activity that happens outside that desk has no system.
Permissions default to closed. One or two people hold the keys. Self-serve is a support ticket.
Part-time, distributed, context-heavy. Happens evenings and weekends. Needs coordination, not administration.
Volunteers end up in consumer tools (WhatsApp, Google Sheets, paper) that don’t know they’re running a synagogue.
The shul staff isn’t the enemy. They’re overloaded because the system routes everything through them.Shadow Shul
Shadow Shul is a workspace for the groups doing the work — not a replacement for the shul’s system of record.
See How It Works