Sample comms plan
Broadcast authority, role routing, and coordination handoffs by incident type.
Operational playbooks
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.
These templates are starting points, not substitutes for local legal, insurance, or pastoral guidance. When you operationalize them in SMS, keep language concise, routes explicit, and leadership authority clear.
Each workflow below lists purpose, people typically involved, sample message lines, and follow-up ideas. Replace role names and locations with your campus language, then apply templates to real scenarios your team already rehearses. Your written policy defines thresholds and outside help - not sample SMS lines on a marketing page.
When you are ready to operationalize phrasing in SMS, Sanctuary Signal TEXT supports duty state and broadcast discipline so playbooks become habits instead of wishful thinking.
Purpose: Confirm readiness before doors open.
Who is involved: Team lead, zone volunteers, children’s liaison, medical responder if assigned.
Sample message flow:
CHECKIN North Lobby
STATUS
@TeamLead Parking team ready, perimeter walk complete
When your policy may require wider help (example): Missing check-in from a required zone before service.
Follow-up action: Supervisor assigns coverage or pulls a floater from a low-risk post.
Purpose: Get trained help and clear space without broadcasting sensitive details.
Who is involved: Nearest volunteer, medical responder, security lead, pastoral contact as defined by policy.
Sample message flow:
@Medic Medical assistance requested near nursery hallway
@TeamLead Lobby clear, directing traffic away from scene
STATUS
When your policy may require wider help (example): EMS requested or medical responder cannot be located per your local procedure.
Follow-up action: Document timeline, preserve privacy, debrief with leadership. See medical incident use case.
Purpose: Share observations discreetly and avoid congregation-wide alarm.
Who is involved: Observer, security lead, pastoral leadership at a defined threshold.
Sample message flow:
@TeamLead Adult male gray hoodie repeated perimeter passes near east doors, no hostile behavior yet
STATUS
BROADCAST Leadership: Team is monitoring parking lot situation. No action needed from volunteers yet.
When your policy may require wider help (example): Behavior crosses your church's written threshold for law enforcement notification.
Follow-up action: Watchlist note, facilities check, and calm leadership communication. See suspicious person BOLO.
Purpose: Move traffic safely and surface risks early.
Who is involved: Parking captain, perimeter volunteers, security lead.
Sample message flow:
STATUS Parking Lot clear
@TeamLead Vehicle blocking fire lane, owner paging
When your policy may require wider help (example): Hostile encounter, medical event, or severe weather exposure.
Follow-up action: Facilities signage update or Sunday logistics change for next week. See parking lot escalation.
Purpose: Protect children first, communicate through ministry channels, involve security when needed.
Who is involved: Room lead, children’s director, security lead, pastoral leadership.
Sample message flow:
@ChildrensDirector Need security liaison at west kids wing desk
@TeamLead Acknowledged, sending supervisor
When your policy may require wider help (example): Missing child, injury beyond basic first aid, or custody dispute.
Follow-up action: Written incident summary and pastoral care plan. See children’s area incident.
Purpose: Rapid, verified reunion without public speculation.
Who is involved: Children’s lead, security lead, designated search pairs, communications person.
Sample message flow:
@TeamLead Lost child protocol initiated, west wing, code name BLUEBIRD
STATUS
When your policy may require wider help (example): Time threshold exceeded or campus perimeter concern.
Follow-up action: Drill debrief, signage review, parent communication template update.
Purpose: Move people safely and keep messages authoritative.
Who is involved: Security lead, facilities, pastoral leadership.
Sample message flow:
BROADCAST Leadership: Shelter posture for main auditorium. Ushers hold doors, security monitors glass entries.
STATUS
When your policy may require wider help (example): Local warning system upgrade or building damage risk.
Follow-up action: Facilities inspection, insurance documentation, volunteer recognition.
Purpose: Close the loop and capture accountability without shame.
Who is involved: Team lead, supervisors, optional pastoral liaison.
Sample message flow:
@TeamLead Shift summary: two medical assists (minor), one parking assist, no security incidents
When your policy may require wider help (example): Any incident requiring follow-up beyond the Sunday window.
Follow-up action: Email summary archive, training tweak, or equipment fix. See end-of-shift accountability.
Broadcast authority, role routing, and coordination handoffs by incident type.
Check-in confirmation, zone assignments, and supervisor handoff points.
Medical, BOLO, children’s area, parking lot, and perimeter workflows.
No. They are starting points your church should adapt with legal, insurance, and pastoral guidance.
They illustrate concise phrasing. In TEXT, CHECKIN, STATUS, @Name direct messages, and supervisor broadcasts map to structured routing your admin configures.
Then structure them inside Sanctuary Signal for Sunday operations.