Multi-Campus Prayer Request Workflow: Roles, SLAs, and Weekly Cadence

Strategy for multi-site prayer ministry is the easy part — every leader agrees that prayer should be unified, fast, and pastoral. The hard part is the operations: who is responsible for which request, how fast it has to move, what happens when no one picks it up, and how the whole system gets reviewed each week so it doesn't quietly decay.

This is an operations playbook for the team actually running the prayer ministry across two, five, or ten campuses. If you've already read our strategic guide to multi-site prayer management, this is the next layer down.

The Operating Model in One Picture

Three layers: a church-wide director who owns the system, a coordinator per campus who runs daily operations, and the actual prayer team and wall at each site.

Define the Roles (Exactly)

Vague roles are the #1 cause of dropped requests. Write these down and assign names.

Church-wide Prayer Director (1 person)

Owns the platform, policies, and tier definitions

Reviews analytics weekly and meets with coordinators monthly

Handles cross-campus escalations and sensitive cases

Not in the daily intake queue

Campus Prayer Coordinator (1 per campus, plus a backup)

Owns the intake queue for their campus

Triages every request within the SLA

Routes to chain, wall, or pastoral follow-up

Maintains the local chain roster (adds, removes, re-confirms)

Prayer Team Members (10–40 per campus)

Receive chain notifications and pray

Mark themselves unavailable during travel

Submit answered-prayer reports back to the coordinator

On-Call Pastor (rotates)

Owns Tier 1 critical-response within 30 minutes

Handles requests requiring pastoral conversation, not just prayer

Moderator (can be the coordinator or a separate volunteer)

Approves requests for the public prayer wall

Removes flagged content

Enforces anonymity rules

In a small church one person can wear three hats. Write that down too — "Sarah is Director + Campus A Coordinator + Moderator" — so the load is visible.

Set Real SLAs (Not Aspirations)

A service-level agreement is a promise about how fast something happens. Write these on a single page and review them monthly.

Two rules that make SLAs actually work:

Measure them. A coordinator dashboard or a weekly report should show actual vs. target response times. If you can't see misses, you can't fix them.

Have an explicit fallback. If the coordinator hasn't acknowledged a T1/T2 request within the SLA, it auto-escalates to the director. No request should ever sit unowned.

Escalation Paths

Every request needs a defined "what if no one responds" path:

T1 not acknowledged in 15 min: Auto-page on-call pastor + director

T2 not acknowledged in 2 hrs: Notify backup coordinator

T3 sitting >72 hrs: Surface in director's weekly review

Flagged content (any tier): Immediately hidden + notify director

A "request acknowledged" event is just the coordinator clicking accept/route. It doesn't mean the work is done — it means a human owns it.

The Weekly Cadence Template

Steal this rhythm. Adjust timing to your team.

Monday — Director

Review last week's metrics: volume per campus, SLA hit rate, oldest unresolved request

Send a 3-bullet update to coordinators

Flag any campus running more than 20% over normal volume

Tuesday–Thursday — Coordinators

15 min daily intake review (morning + late afternoon)

Triage new submissions to tier

Route to chain / wall / pastor

Close out resolved requests

Friday — Coordinators

Send the weekly Tier 3 digest to the campus chain (group ongoing requests into one email — not 14 separate notifications)

Post any answered-prayer celebrations to the campus wall

Re-check that no request is stuck unowned

Sunday — All campuses

Brief prayer team huddle (10 min before service)

Coordinator shares 1–2 specific requests the team should hold during service

Monthly — Director + all coordinators

45-minute video call

Walk through SLA misses (no blame — find the system fix)

Refresh chain rosters: who's added, who's removed, who needs re-confirmation

Decide one thing to change for the next month

Quarterly — Director

Re-confirm chain membership across every campus (reply-to-stay email)

Audit privacy: are anonymity defaults still being honored?

Update tier definitions if drift has crept in

What to Track (and What to Ignore)

Track:

Volume per campus per week

SLA hit rate per tier

Median time-to-acknowledge

Active chain members per campus

Answered-prayer ratio (closed-as-answered / total)

Ignore:

Total prayer count as a vanity metric

Per-member submission counts (this isn't a leaderboard)

"Engagement" if it's not tied to actual response times

Cross-Campus Coordination Rules

A handful of policies that prevent the most common multi-campus problems:

Default routing: A request goes to the requester's home campus chain unless tagged otherwise.

Cross-campus visibility: Public wall posts are visible church-wide by default; chain notifications are not.

Cross-campus escalation: Coordinators can request cross-campus prayer support by tagging the director — never by direct-messaging another campus's chain.

One source of truth: All requests live in one platform with per-campus scoping. Spreadsheets per campus = duplication and drift.

Tools That Make This Workflow Possible

Doing all of the above on email and spreadsheets is technically possible — and exhausting. The workflow above presumes a tool with:

Per-campus moderation queues (coordinators only see their queue)

Tier tagging with notification rules (T1 triggers SMS, T3 triggers digest)

Auto-escalation on SLA miss

Role-based access (director sees everything, coordinator sees their campus, moderator sees the wall)

Analytics broken down by campus and tier

Audit trail for who acknowledged and acted on each request

PrayerConnect was built around this operating model — the multi-site features include per-campus routing, moderation scoping, and analytics designed for exactly this workflow.

FAQ

How many campuses before you need a formal workflow like this?

Two. The moment requests can be misrouted, you need explicit ownership.

Should every campus have the same SLAs?

Yes for T1/T2 (these are pastoral commitments). T3/T4 can flex per campus volume.

What if a campus coordinator quits?

That's why the backup coordinator role is non-optional. Director assumes the role temporarily and recruits within two weeks.

How do you prevent coordinator burnout?

SLAs that match volume, a real backup, batched digests instead of one-off notifications, and an explicit "off duty" rotation. Burnout is a workflow problem, not a willpower problem.

The Bottom Line

Multi-campus prayer ministry doesn't fail because people stop caring — it fails because no one defined who owns what by when. Roles, SLAs, escalation, and a weekly cadence turn prayer from a fragile volunteer effort into a durable ministry that scales with your church.