Planning Team
Accountability, built in.
Every event has one owner, one task list and one record of decisions. The committee plans, the staff execute, and both can see the whole picture. Nothing lives in someone’s inbox.
The problem
The handoff is where events break.
In most synagogues a committee decides, a staff member does, and the two meet in a phone call, a hallway, or a message thread nobody can find three weeks later. Details change and only half the people hear. Someone assumes someone else booked the room.
When the event is over, the knowledge of how it ran leaves with the person who ran it. The Planning Team gives every event one shared workspace, so the decision, the task and the person responsible are always in the same place.
What the team sees
Six things that stop falling through the cracks.
One owner, one list
A named owner and a single to-do list with a person and a date on every item. Open items are visible to the whole team, so follow-up is a glance, not a chase.
Decisions, written down
Log a decision in one line and it stays with the event. Months later, “why did we do it that way” has an answer.
Everyone was told
Updates post to the event’s activity feed, where the whole team reads them. When a detail changes, there is a record of what changed and when.
Committees and staff together
Volunteer committee members get the access they need and nothing more, in the same space where staff execute. No second version of the truth.
Ownership is a label, not a lock
The rabbi may own the event while the assistant runs it. Any organizer can edit any event; the owner’s name stays on it for accountability.
Built for turnover
When a staff member leaves or a new one joins, the history is already there. They open last year’s event, see what was done and by whom, and pick up where it stopped.
How a team uses it
From first idea to the day itself.
Create the event
Describe it once. The planning workspace opens with it.
Invite the team
Staff lead, committee chair, volunteers. Each with the access that fits.
Plan in one place
Tasks, decisions and updates in one feed, with owners and dates.
Approve and run
One approval before publishing. On the day, the run sheet draws from the same record.
Good to know
Before you ask.
Not a CRM. Keep yours.
EzzyWorks runs events only. Your membership system stays where it is. The Planning Team is about who does what for an event, not about member records.
Staff join by invitation only.
Nobody reaches your planning workspace through public signup. You decide who is on the team and what each person can see and edit.
The history stays with the event.
After the event, the tasks, decisions and debrief stay with it. When you create next year’s version, they are already there, so you start from what actually happened.
Related: the EzzyWorks blog, and on ShulWorks, why we built EzzyWorks.
See the Planning Team on one of your events.
A 30 minute walkthrough. Bring a real event and we set it up together.