A 160-attendance Upper Peninsula winter church

A 160-attendance Upper Peninsula winter church runs Planning Center People, Services, and Giving with Clearstream, Mailchimp, and Google Sheets. Staff: 1 full-time, 2 part-time. Built for lake-effect Sundays, not a metro suite.

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 160-attendance Lutheran church in Michigan’s Upper Peninsula. One full-time pastor and two part-time staff. Lake-effect snow can cancel worship with little warning. Some families drive thirty minutes on ice. Guests include local households and cabin visitors. Internet thins out when storms hit the peninsula uplink.

Why does this mix exist?

They kept Planning Center People as one login a council member can run when the pastor is on hospital runs into town. Services keeps weekend teams honest when GroupMe panic fails in a whiteout. Giving covers winter weeks when lobby cash dips. Clearstream carries cancels and funeral notices by text and voice because Facebook posts miss households without reliable data (an upper peninsula winter church). Mailchimp stays plain on the free tier. Sheets stay printable when phones freeze in the lot.

How the week actually runs

Saturday, staff check lake-effect and ice notes before anyone posts a cancel. Reply-to stays on the church number when Clearstream goes out early. Sunday cards enter People when the uplink holds; otherwise paper cards wait in a labeled drawer (an upper peninsula winter church). Snow-route tags keep volunteer asks from assuming every family lives in town. Tuesday guests get Clearstream texts; personal phones stay out of the weather failure path. Driver lists live on the Sheet with a named lead. A printed Services run sheet stays in the sacristy.

What breaks if you copy this blindly

Buying a heavy suite you cannot staff during storm travel weeks. Treating every household as a single in-town address. Relying on Facebook as the only cancel channel. Leaving visiting helpers with export rights. Assuming every guest will install an app with weak cabin signal. Forcing image-heavy email that never loads. Skipping the printed run sheet because “everyone has the app.”

What they would change next

Train a second People admin before the pastor’s next hospital week. Print large-type give cards. Put background-check dates on kids tags before Advent. Name a backup Clearstream sender before first lake-effect week. Add a do-not-contact path for cabin visitors who ask for space after they leave.

How should you use this page?

If your church lives with lake-effect cancels, ice roads, and thin volunteer weeks, pick tools that survive offline Mondays and voice cancels. Keep human thank-yous. Prefer one paid people database and one cancel channel people answer. If your town has reliable fiber and short dry drives, you may need less Clearstream voice and more steady Mailchimp cadence instead.

Field note after a lake-effect cancel

Snow closed the county road at 6am. Facebook reached town rentals. Clearstream voice reached elders who never open email before noon. The lesson was not more apps. It was the channel people answer when the lake throws snow.

Field note after an ice-drive volunteer ask

A volunteer text assumed an in-town family could cover ushering after a late Saturday plow. Greeters now mark snow-route tags on the card, and Monday asks stay honest. Care includes knowing how far people actually drive on ice.

Field note after a cabin-visitor export revoke

Short-term cabin helpers kept export rights after a summer week. They now revoke visitor admin the Sunday the team leaves. Hospitality includes closing doors.

Adoption check

If two people cannot name the weekly job without a slide deck, wait (an upper peninsula winter church).

Care-first check

Ask who revokes export rights the Sunday a short-term helper leaves.

Keep the public checklist honest: named tools, ordered steps, real cost, last-checked date.

Cut seats that only work with weekly heroics from the team on an upper peninsula winter church.

Backup completion

Ask for substitute completion after a single fifteen-minute handoff (an upper peninsula winter church).

Keep named tools, ordered steps, real cost, and a last-checked date on every public page you copy.

Choose ordinary faithfulness over shelfware that looked impressive (an upper peninsula winter church).

Who owns admin

On a team sized like 1 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 Sheets: $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: 1 full-time, 2 part-time. Region context: US Upper Midwest. Copy the ownership pattern before you copy every logo.

Copy this if

Copy this mix when your church is near 150-400 attendance (Lutheran), 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 160-attendance Upper Peninsula winter 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 Sheets) 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 1 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.