Operational playbooks

Templates that turn intent into repeatable Sunday behavior

Policy binders are necessary; they are not sufficient. These workflows give your team sample language and follow-up ideas you can adapt to your campus, then apply to real scenarios you already train for. Layer TEXT on top when you want duty state and broadcast discipline without inventing a new app culture.

This page = SMS demos. For narrative playbook notes without phone UI, start at use cases. Watchlist governance and screenshots: watchlist access control.

Duty dashboard used to support Sunday operational templates

Adapt with counsel you trust

These templates are starting points, not substitutes for local legal, insurance, or pastoral guidance. They are written to match real Sanctuary Signal SMS behavior: on-duty check-in, direct messaging by saved name, team broadcasts, and role routing such as @MEDIC or @LEO where enabled.

How to use these templates

Each workflow below lists a realistic church safety scenario, sample text-message exchanges, and a follow-up idea. Replace sample names and locations with your team's roster and campus language. The goal is not to script every incident, but to give your team short, repeatable wording that works in live SMS coordination.

Important: CHECKIN is like clocking in for your shift - one text to mark yourself active on duty. It is not the same as a location update like "im at childrens wing."

Examples below use sample roster names from Sanctuary Signal demo mode. Replace names like @Sam, @Mia, or @Lee with the actual teammates saved in your roster.

Think of CHECKIN as punching in for the shift. After that, use normal short texts for where you are posted and what you need.

Footnotes

Keywords vs human messages: System commands include CHECKIN, STATUS, HELP, and ?. @Name, @ALL, @MEDIC, and @LEO are routing patterns. Plain replies and coordination text are normal SMS once someone is on duty. Some routing behavior depends on admin settings.

Sunday service safety team checklist

Confirm staffing before doors open and let the supervisor quickly spot coverage gaps.

Sam Supervisor Casey Member Alex Member Lee Officer

The story moves between three phones. Pick a volunteer to see only what appears on their screen. Lee is on the roster but has no texts in this opening beat.

Click a team member name to switch screens.

Casey Member
Pre-service coverage
CHECKIN
System
✓ Casey, you're checked in!

CHECKIN - Mark yourself as on-duty
STATUS - See all on-duty users
[Any message] - By default, sends only to Supervisor
@ALL [message] - Send to all checked-in users only
@Name - Send direct message
@LEO / @Police / @PD [message] - Send to active LEO on duty
@MEDIC [message] - Send to all active Medical users
#new / join #1 / #list / #leave - Private channel chat (#1-#9)
[Plain message while in #N] - Sends to your active channel. Use #leave to exit channel mode
WATCHLIST - Open mobile watchlist link
? / HOWTO - Show this command list
@Sam east lot parking crew in place
System
✓ Message sent to Sam Supervisor

Private DM active with Sam Supervisor for 5 minutes. Plain messages stay private until [time], then return to on-duty supervisor / owner routing.
From Sam
[From Sam Supervisor] copy stay there thru open

This is the intended Sanctuary Signal pattern: volunteers first mark themselves on duty with CHECKIN, then use direct messages for assignments and handoffs. Supervisors can use STATUS to see who is available before shifting coverage.

Medical incident workflow

Get the right medical help moving fast without over-texting the whole team.

Alex Member Sam Supervisor Mia Medic

Who is involved: Alex (reporting), Sam (Supervisor), and Mia (Paramedic).

Follow Alex's request, Sam's skill review, and Mia's dispatch on three phones.

Alex Member
Medical request
@MEDIC older male slipped by nursery hall. hip pain. awake and talking
System
✓ Your MEDIC request was routed to (Sam Supervisor) for immediate review.
System
Your MEDIC request was dispatched to: Mia Medic.
Mia Medic
[Mia Medic] copy en route

This example assumes member @MEDIC requests are routed to the on-duty supervisor for review and skill-based dispatch. See medical incident use case.

Suspicious person / BOLO workflow

Share observations fast, compare against known concerns, and escalate only when needed.

Casey Member Sam Supervisor Lee Officer

Who is involved: Casey or Alex (observer), Sam (Supervisor), Lee (LEO if assigned).

Follow the thread on Casey's, Sam's, and Lee's phones through WATCHLIST and @LEO escalation.

Casey Member
BOLO observation
@Sam gray hoodie male near east doors again. think he may match prior concern
System
✓ Message sent to Sam Supervisor

Private DM active with Sam Supervisor for 5 minutes. Plain messages stay private until [time], then return to on-duty supervisor / owner routing.
From Sam
[From Sam Supervisor] check WATCHLIST and lmk if you get a match
WATCHLIST
System
Sanctuary Signal: You've requested a secure link to the watchlist. The link expires in [X] minutes or first use.
[secure link]
Reply STOP to cancel. Reply HELP for help.
Watchlist opened
Watchlist 4/10
Kevin Do*** Photo 1/3

Previously involved in heated dispute with pastor over counseling matter; returned multiple times attempting to reinitiate confrontation.

< Photo Ask supervisor
Watchlist action

Opened library and viewed Kevin Doyle entry and photos

Watchlist action

Tapped Ask supervisor on the selected entry

@Sam looks close to Kevin Doyle on watchlist. same hoodie, same build
From Sam
[From Sam Supervisor] copy keep eyes on. east doors for possible watchlist match. gray hoodie, medium build.

Watchlist Module (Suspicious Person Watch) is an optional TEXT add-on. Casey's in-thread watchlist card and Sam's alert above mirror the field flow on watchlist access control. Narrative context: BOLO use case · add-on details. Keep BOLO messages observational: location, clothing, direction, behavior.

Parking lot coordination

Handle blocked lanes or vehicle concerns without tying up the whole team.

Casey Member Sam Supervisor Lee Officer

Who is involved: Casey (parking lot observer), Sam (Supervisor), and Lee (LEO).

Direct messages to Sam, then @LEO when the lane stays blocked.

Casey Member
East fire lane
@Sam vehicle blocking fire lane east side
From Sam
[Direct from Sam Supervisor] copy try owner contact first
@Sam owner not found yet. lane still blocked

Follow-up: Facilities signage update or Sunday logistics change for next week. See parking lot escalation.

Children’s ministry escalation

Route children's area concerns to leadership and security without over-alerting the whole team.

Karen Sam Supervisor Casey Member Sally

Who is involved: Karen (children's check-in), Sam (Supervisor), Casey (responding team member), and Sally (children's lead).

Direct-message handoff from Karen to Sam, Sam assigns Casey, then Sam forwards Casey's reply for Sally's awareness.

Karen
West kids wing
@Sam need security support at west kids wing check-in desk

Use direct-name messages when the right responder is already known. Reserve @ALL for wider team coordination. See children's area incident.

Lost child procedure

Coordinate immediate search actions without public speculation.

Karen Sam Supervisor Casey Member Alex Member

Who is involved: Karen (reporting), Sam (Supervisor), Casey (exit coverage), and Alex (lobby coverage).

Private report to Sam, then a short @ALL assignment with exit coverage replies.

Karen
Report
@Sam lost child reported in west wing. last seen near check-in
System
✓ Message sent to Sam Supervisor

Private DM active with Sam Supervisor for 5 minutes. Plain messages stay private until [time], then return to on-duty supervisor / owner routing.

This is one of the better uses of @ALL: short, clear, assignment-oriented, and time-sensitive.

Severe weather communication

Keep protective actions short, authoritative, and easy to relay.

Sam Supervisor Casey Member Alex Member Mia Medic

Who is involved: Sam (Supervisor), Casey (ushers), Alex (glass entry watch), and Mia (medical readiness).

Sam sends one short @ALL; checked-in teammates reply with quick copies.

Sam Supervisor
Shelter posture
@ALL shelter posture for main auditorium. ushers hold doors. security watch glass entry points
System
✓ Message sent to 3 checked-in user(s)
From Casey
[From Casey Member] copy - will alert the ushers
From Alex
[From Alex Member] watching the big glass entry
From Mia
[From Mia Medic] copy medical kit staged

Follow-up: Facilities inspection, insurance documentation, and volunteer recognition as your policy requires.

Post-service summary

When the last volunteer checks out, supervisors receive a structured recap: who was on duty, which keywords fired, and the message timeline leadership can review without digging through personal phones. The goal is calm accountability, not surveillance.

Pair this template habit with your end-of-shift accountability guide so finance, insurance, and pastoral follow-up know where to look after Sunday.

Sample end-of-shift email summary listing on-duty volunteers and flagged activity

Template packs (quick reference)

Messaging rules starter

Broadcast authority, role routing, and coordination handoffs by incident type.

On-duty startup checklist

CHECKIN confirmation, zone assignments, and supervisor handoff points.

Incident routing examples

Medical, BOLO, children's area, parking lot, and perimeter workflows.

Apply templates to real scenarios

Template FAQ

Are these templates a substitute for local policy?

No. They are starting points your church should adapt with legal, insurance, and pastoral guidance.

How do these sample text exchanges map to the product?

These examples reflect real Sanctuary Signal patterns: CHECKIN for on-duty status, STATUS to see active teammates, @Name for direct messages, @ALL for explicit team-wide broadcasts, and role-routing such as @MEDIC or @LEO when enabled by your team settings.

Reply HELP or ? from your phone for the live command list.

Use these templates as a starting point

Then structure them inside Sanctuary Signal for Sunday operations.

Request more info