Setup-crew scheduling for a rented-space church
The setup roster lives in Tithely volunteer scheduling. The admin sends exactly one WhatsApp message every Thursday with Sunday's crew; nothing else goes in the main group except emergencies. The one-sender rule exists because ministry chatter got the group muted and nobody showed up to set up sound.
What are the exact steps?
- Keep the roster in the ChMS, not in a chat thread
The setup roster lives in Tithely Church Management volunteer scheduling (the church's people system, formerly Breeze), so who is on crew is a record, not a scroll-back. Anyone can check it without asking the pastor. Schedule sound, kids room, and welcome table as separate roles for the 1:00 call time.
- Fill next Sunday's crew by Wednesday
The admin (ten hours a week) fills gaps by Wednesday using Tithely. If a role is empty, she texts specific people, not the whole group. Whole-group pleas train people to wait for someone else.
- One WhatsApp message, one sender, every Thursday
The admin sends one message with Sunday's crew and any announcements. Nothing else goes in the main group except this message and emergencies, by policy, not preference. Ministry chatter belongs in smaller threads. The one-sender rule exists because chatter got the group muted and nobody showed up to set up sound.
- Sunday 1:00: crew at the door
The host congregation's service ends at one. The crew is at the door when they let out, and sound, kids room, and welcome table go up in the thirty minutes before the 1:30 slot. Late crew means late service. Paper welcome cards sit on the table as soon as it exists; there is no time for iPad setup.
- Teardown before the clock and the host's next need
After service, the same roles pack gear so the room returns on time. The rental relationship depends on leaving the space ready. Note damages or missing pieces for the admin's Tuesday.
Which tools does this church use?
- Tithely Church Management Church database (ChMS)
The setup roster lives in its volunteer scheduling.
$0 incremental (part of the $72/mo flat plan)
- WhatsApp Communication
The Thursday crew message. Everyone already has it, including the abuelas, and nobody downloads a church app.
$0
Common questions
How do you keep a church WhatsApp group from getting muted?
One message a week from one sender. This church used to let every ministry post in the main group; by spring people had muted it, the Sunday crew message got missed, and nobody showed up to set up sound. Now it is the Thursday message and emergencies only.
Do you need a church app for volunteer scheduling?
Not at this size. The roster lives in the ChMS built-in volunteer scheduling and the weekly crew message goes out on WhatsApp, because everyone already has it (including the abuelas) and nobody downloads a church app.
What time does a rented-space setup crew need to arrive?
Here the host congregation lets out at 1:00 and service starts at 1:30. The crew is at the door at one. Thirty minutes is the whole window for sound, kids room, and welcome table.
Before you start
You need Tithely volunteer scheduling set up for setup roles, a WhatsApp group with a written one-sender rule, and a clear 1:00 arrival expectation in the rental rhythm. Tell ministry leaders where else to post (small threads, not the main group). If the main group is already noisy, mute-history is your warning light. Reset the rule in writing before the next muted-message failure.
Why they built it
Renting someone else’s building compresses everything: the host congregation’s service ends at one, and sound, kids room, and welcome table have to exist by 1:30. There is no slack for a crew that does not show.
They learned the communication rule the expensive way. Every ministry used to post in the main WhatsApp group; by spring, people had muted it, the Sunday crew message went unseen, and nobody showed up to set up sound. Now the group carries one message a week (the admin’s Thursday crew list) plus emergencies. The rule costs every ministry a channel and buys back the one message that has to get through.
What they’d do differently
Nothing about the one-sender rule. It works. They would have written it before the mute crisis. The pastor’s open worry is that the WhatsApp group has slowly become the church directory, and not everyone in it should see everyone’s number. No fix yet; they are watching it. A shared church text number for guest follow-up is on the same honesty list.
Monday checklist
- Check Tithely for next Sunday’s setup roles; fill gaps by Wednesday.
- Thursday: admin sends the single WhatsApp crew message.
- Spot-check that no ministry chatter landed in the main group.
- Sunday: confirm crew at the door at 1:00.
- After service: teardown owners clear the room on time.
- Tuesday: admin notes no-shows and repairs the next roster.
Common mistakes
- Using the main WhatsApp group as a general ministry feed.
- Asking “who can help Sunday?” to everyone instead of naming people.
- Keeping the roster only in chat scroll-back.
- Arriving at 1:15 and hoping thirty minutes still exists.
- Letting guest phone numbers accumulate in the crew group.
Field note after the muted-group Sunday
Nobody came to set up sound. The Thursday crew message had gone to a group people muted after months of event spam. They stripped the main group to one sender and one weekly message. Ministries complained for two weeks, then adapted. The sound still needs humans at 1:00.
Field note after a late subway crew
One sound volunteer texted at 1:05 from a delayed train. The floater role (when filled) covers that. When it is empty, the pastor starts setup in work clothes from the transit job. They now treat the floater slot like a required instrument, not a luxury.
The Monday digest
One short Monday email with a complete how-to for churches your size: named tools, ordered steps, and real cost. Reply anytime. A person reads it. Unsubscribe in one click.
Almost in. Check your email and confirm before we send the Monday how-to.