Bridge — Members ↔ Org

Volunteering.
Plan. Schedule. Accept. Show up.

The pastor builds Sunday's order of service. Assigns roles. Volunteers see the schedule on their phone. They accept or set unavailability. Reminders fire Saturday night. Service order publishes. They walk in Sunday knowing their cue. The full handshake, end to end.

Payments byStripe
0.8%ACH · capped at $5
PWANo App Store required
NativeQBO & PCO sync

Where most churches drop the ball

Scheduling is a relationship, not a spreadsheet.

Most churches schedule volunteers through some combination of: a shared Google Sheet, a separate Planning Center subscription, a group text from the worship pastor's personal phone, and the hope that nobody forgets. The result is the Sunday-morning panic when the bass player doesn't show up because they assumed they were off this week.

On TrueConnect+, the schedule is a two-way conversation in the same app the volunteer already uses for everything else. The pastor builds the assignment. The volunteer's phone gets the notification. They accept or decline. The pastor sees the response. If declined, the slot opens automatically and an alert goes out. The schedule is always live, always accurate.

The pastor's side

Build the service. Build the team. Publish.

Service planning

Service Types, Order of Service, Songs.

Service Types are templates: "Sunday AM Worship", "Wednesday Night", "First-Friday Outreach." Each generates dates per a recurrence rule. The Order of Service for any given date is what you build inside it: opening song, welcome, sermon, closing prayer, transitions.

Songs come from your library — every song with title, artist, default key, tempo, CCLI number, and chord chart. CCLI compliance is part of the data model. Worship pastors don't go searching for the chart on Sunday morning.

  • Service Types with recurrence rules
  • Per-service Order of Service (run-of-show)
  • Song library with CCLI tracking
  • Chord charts attached to songs
Teams + Roles + Assignments

The matrix view that answers 'who's serving Sunday?'

Build teams (Worship, Tech, Hospitality, Kids). Each team has roles (Acoustic Guitar, FOH Audio, Greeter, Room Lead). Roles are flagged required or optional.

The Assignments view is a matrix: rows are teams + roles, columns are upcoming Sunday dates, cells are the volunteers you've assigned. Color-coded by accept/decline status. The slot you can't fill is visually screaming for attention.

  • Teams with arbitrary roles inside
  • Required vs optional flagging per role
  • Matrix view: who serves which Sunday in which role
  • Status-colored cells (accepted / declined / pending)

The volunteer's side

My Schedule. My Availability. On my phone.

My Schedule

Every Sunday I'm serving. Every role. Every team.

The volunteer opens TC+ on their phone. "My Schedule" shows every assignment across every team they're on, sorted by date. Tap to accept. Tap to decline (with optional reason). Tap to see the order of service for that Sunday.

When the pastor publishes the run-of-show, the volunteer sees their cue points. The acoustic guitar knows they enter at minute 4 with song #2 in B-flat. No one asks "what key are we in?" from the green room.

  • Every assignment across every team
  • Accept / decline with reason
  • Order of Service visible per assignment
  • Cue notes per role per song
My Availability

Block out the weeks you can't serve. Once.

The vacation. The wedding. The work trip. Set unavailability windows once, in advance, and the pastor's scheduling tool knows not to assign you those Sundays. When they try, the matrix shows the conflict before the schedule goes out.

Reminders fire Saturday night for assignments accepted but not yet acknowledged. The volunteer who forgot they signed up gets pinged the night before, not the morning of.

  • Set unavailability windows in advance
  • Pastor's view shows the conflict before scheduling
  • Saturday-night reminders for upcoming shifts
  • One-tap swap requests between volunteers (roadmap)

The full lifecycle, one platform.

Plan. Build the team. Schedule. Publish. Notify. Show up.

Plan

Service Types

Recurring service templates. "Sunday Morning" generates every Sunday automatically. "First-Friday Outreach" on the first Friday of each month. The dates appear in your schedule without anyone typing them.

Build

Order of Service

The minute-by-minute run-of-show for each service. Opening, welcome, song one, song two, sermon, closing. Volunteers see their cues; the worship pastor sees the entire arc.

Music

Song Library

Every song with key, tempo, CCLI number, and chord chart. Reusable across services. CCLI usage logged automatically — your annual reporting is a click.

Structure

Teams + Roles

Worship, Tech, Hospitality, Kids — and the specific roles inside each. Required flags trigger warnings if a slot is unfilled close to Sunday.

Schedule

Assignments matrix

The 2D view of who's serving when. Drag to assign. See conflicts at a glance. Color-coded by status.

Notify

Schedule requests

When you assign a volunteer, a request fires to their phone. Accept, decline, or remind-me-later. Saturday-night reminders for unconfirmed shifts.

The Sunday-morning panic ends here.

Plan one service. Build one team. Schedule one volunteer. See the system in flight.