A 170-attendance Utah Wasatch Valley church

A 170-attendance Utah Wasatch Valley church runs Planning Center People, Services, and Giving with Clearstream, Mailchimp, and Google Forms. Staff: 2 full-time, 2 part-time. Built for canyon weather and ski weekends, not a fixed metro rhythm.

By Caleb Brooks · Published September 2026· Editorial standards · Conflict of interest

Field guide page: steps and costs from hands-on church-tech work, written under a pen name. Church names stay private. See how we write and verify.

What kind of church is this?

A 170-attendance nondenominational church in Utah’s Wasatch Valley. Two full-time staff and two part-time roles. Ski weekends thin the room. Canyon roads and winter inversions cancel or delay services a few times a year. Guests include local households and newcomers settling along the valley corridor.

Why does this mix exist?

Planning Center People holds newcomers and care notes in one place. Services flexes weekend teams when ski weekends empty the room. Giving covers members who travel. Clearstream carries cancels by text and voice because Facebook posts miss households on weak canyon data. Mailchimp stays plain on the free tier. Google Forms handles light class RSVPs with Monday matching into People.

How the week actually runs

Saturday, staff check canyon and inversion notes before anyone posts a cancel. Clearstream goes out early with a reply path to the church number. Sunday cards enter People when the uplink holds; otherwise paper cards wait in a labeled drawer. Services prints a run sheet for phone-free volunteers. Tuesday guest texts use Clearstream. Light class RSVPs land in Forms and match into People on Monday under a named owner.

What breaks if you copy this blindly

Buying a heavy suite sized only for peak non-ski Sundays. Treating every household as always in town on winter weekends. Relying on Facebook as the only cancel channel. Leaving short-term helpers with export rights. Using Forms for every camp without household matching. Skipping printed run sheets because “everyone has the app.”

What they would change next

Train a second People admin before ski season peaks. Print large-type give cards. Put background-check dates on kids tags before Advent. Name a backup Clearstream sender before canyon storm season. Add a do-not-contact path for newcomers who ask for space after they leave.

How should you use this page?

If your church lives with canyon cancels, ski-weekend dips, and steady newcomers, pick tools that flex without a second vendor tax. Keep human thank-yous. Prefer one paid people database and one cancel channel people answer. If attendance is steady every winter weekend, you may need less cancel voice and more steady Mailchimp cadence instead.

Field note after a canyon-road cancel

Ice closed the canyon at 6am. Facebook reached valley condos. Clearstream voice reached elders who never open email before noon. The lesson was not more apps. It was the channel people answer when the canyon closes.

Field note after a ski-weekend volunteer ask

A volunteer text assumed January ushers were free during a holiday ski weekend. Greeters now mark travel weeks on the card, and Monday asks stay honest. Care includes knowing who left town.

Field note after a Forms-to-People lag

Class RSVPs sat in a sheet for nine days. They named a Monday matcher and cut the lag to one afternoon. Free forms still need an owner.

Backup login card

Store a labeled spare login card in the office safe for the backup admin.

One-sentence give path

Can the foyer greeter explain how to give in one sentence?

Restricted care notes

Benevolence notes stay in a restricted view, never in blast templates.

Storm-season drill

Run a full cancel path on a spare phone before canyon storm season starts.

October cuts

Heroic Christmas weeks mean you should have cut steps in October.

Keep named tools, ordered steps, real cost, and a last-checked date near the top (utah wasatch valley church).

Prefer one clear weekly owner over three half-owned tools (utah wasatch valley church).

Confirm live pricing the week of the vote, not from last year’s PDF (utah wasatch valley church).

Ordinary care finished beats impressive software abandoned (a utah wasatch valley church). Keep cancel messages on a channel people answer when roads close (a utah wasatch valley church).

Prefer one paid people database and one cancel channel people answer (a utah wasatch valley church).

Confirm live pricing the week of the vote, not from last year’s PDF (a utah wasatch valley church). Shelfware starts when Tuesday has no owner. Keep ownership written where a substitute can find it (a utah wasatch valley church).

Prefer one paid people database and one cancel channel people answer (a utah wasatch valley church).

Who owns admin

On a team sized like 2 full-time, 2 part-time, one named staff lead should hold master admin for the people database and any tool that can export households or send church-wide texts. Ministry directors get limited views for their rosters. Greeters and foyer volunteers should search and check in, not download the full list.

Write a backup admin before vacation weeks. Role changes get a five-minute access checklist the same week: remove logins, remove export rights, confirm the backup still works. Leftover volunteer IT access is how old Sheets and pastoral notes leak into personal inboxes.

If engineers or “techy” members help, they still need a staff owner. Unpaid IT without an owner becomes a single point of failure when that member moves.

What this stack costs

Software lines from this page (confirm the week you brief elders):

• Planning Center People: $14/mo
• Planning Center Services: $0 (bundled with People on this plan)
• Planning Center Giving: Processing fees on this plan
• Clearstream: $29/mo
• Mailchimp: $0
• Google Forms: $0

Add card processing fees beside any giving tool. December volume can dwarf the SaaS stickers. Put weekly admin hours beside each line on the board packet. A cheap tool with unpaid heroics is not cheap.

Attendance bracket on this page: 150-400. Staff shape: 2 full-time, 2 part-time. Region context: US Intermountain West. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near 150-400 attendance (Nondenominational), you can staff the Monday jobs these tools assume, and you will name owners for guest follow-up, scheduling, and giving reconcile. Steal the weekly rhythm and the permission habits first. Steal the logo list second.

Good signs you are ready: cards leave the building with a named enterer, texts leave a church-owned number or watched inbox, and one person can explain each tool in one sentence.

What breaks first

What usually breaks first when churches copy A 170-attendance Utah Wasatch Valley church without the staffing: guest cards sit until Wednesday, personal phones become the cancel channel again, dual databases appear “for transition,” or export rights stay with former volunteers. The tools (Planning Center People, Planning Center Services, Planning Center Giving, Clearstream, Mailchimp, Google Forms) only work when the Monday owners are real.

Refuse a second people list. Refuse automations nobody watches. Refuse measuring success by open rates while replies sit unread. If your staff hours are thinner than 2 full-time, 2 part-time, shrink the stack before you expand it.

Board packet checklist

1. Name master admin and backup for the ChMS (church management system).
2. List monthly software fees and estimated processing fees on one page.
3. Write the weekly job each tool serves in one sentence.
4. Schedule a ninety-day pre-renewal review with actual hours beside each fee.
5. Confirm vendor quotes the same week elders vote.

Keep churchRef and slug stable when you link workflows to this stack. This page is a field pattern, not a mandate to buy everything at once.