A 280-attendance Rock RMS Midwest heritage church

A 280-attendance Midwest heritage church runs Rock RMS for people, giving, communications, and check-in, plus Planning Center Services for weekend teams and Google Sheets for elder exports. Staff: 3 full-time, 4 part-time. Built for one database with a light scheduling lane.

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 280-attendance evangelical church in the Upper Midwest with deep local roots. Three full-time staff and four part-time roles. Families span multiple generations. Guests include locals and relatives home for holidays. The church outgrew a lighter CHMS and wanted one people database without forcing worship leads through heavy admin screens.

Why does this mix exist?

Rock RMS holds people, giving, communications, and check-in so household history stays in one place. Planning Center Services stays as a narrow lane for weekend teams because worship leads already know it and should not need Rock admin rights to fix a Sunday slot. Google Sheets carries elder exports and benevolence tracking with restricted access. The point is one source of truth for people money and care, plus a light tool for schedules.

How the week actually runs

Saturday, worship leads lock Services teams and print a run sheet. Sunday check-in runs in Rock with a paper clipboard fallback in the kids wing. Guest cards enter Rock when Wi-Fi holds. Giving and household updates stay in Rock so Monday thank-yous do not need a second export. Communications send plain templates from Rock segments. Benevolence notes never leave the restricted Sheet. Tuesday follow-up uses Rock tasks with a named owner.

What breaks if you copy this blindly

Turning every staffer into a Rock admin. Dropping Services before worship leads can run Rock schedules without help. Skipping a spare admin before upgrade weekends. Putting benevolence notes into email templates. Assuming Rock hosting is free. Forcing image-heavy blasts that older members never open. Running two people databases “during transition” for months.

What they would change next

Document the Rock upgrade checklist with the IT volunteer. Print large-type give cards. Put background-check dates on kids tags before Advent. Train a second Services admin for holiday services. Add a do-not-contact path for holiday-only visitors who ask for space after they leave.

How should you use this page?

If your church wants one serious people database and a separate light scheduling lane, this mix is a pattern worth testing. Keep human thank-yous. Prefer one people system of record and tight admin rights. If you have no volunteer who can touch Rock hosting, a lighter CHMS may fit better than this stack.

Field note after a dual-database month

They ran Rock and the old CHMS together “just through Easter.” Monday reconcile doubled and guest history split. They set a hard cutover Sunday and archived the old system read-only. Two people databases are not a transition plan.

Field note after a worship-lead permissions fight

A worship lead needed global Rock rights to fix one schedule. They kept Services for teams and limited Rock access instead. Rights should match the Monday job.

Field note after an upgrade-weekend spare login

Rock upgraded on a Friday. The only admin was at a funeral. A labeled spare login in the safe let the IT volunteer finish check-in testing. Spare access is hospitality for Sundays.

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.

Card-pile owner

Name who owns the after-service guest card pile before copying tools.

October cuts

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

Storm-season drill

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

Keep the last-checked date honest even when the stack feels familiar (rock rms midwest heritage church).

Substitute on the packet

A renewal packet without a substitute name stays incomplete.

Pre-storm practice

Practice the full cancel path on a spare phone ahead of storm season.

Tools that die on vacation weeks do not belong in the permanent stack (rock rms midwest heritage church).

Prefer one paid people database and one cancel channel people answer (rock rms midwest heritage church).

Keep named tools, ordered steps, real cost, and a last-checked date near the top (a rock rms midwest heritage church).