1. Member Request
A team member requests watchlist access through structured command messaging.
Controlled awareness, clear authorization, and full post-shift accountability.
Sanctuary Signal enforces a structured watchlist workflow so access and updates are governed by role and leadership oversight.
A team member requests watchlist access through structured command messaging.
Supervisor/leadership evaluates request against role and operational need.
Approved members receive access with traceable usage and update history.
Click any image to zoom
Watchlist requests are visible and reviewable by leadership.
Watchlist updates are logged with clear traceability.
Message history provides full shift reconstruction for follow-up.
MEDICAL, LEO, and WATCHLIST keywords remain auditable in shift summary records.
Watchlist handling is sensitive because it blends pastoral care, safety, and privacy. Strong governance is less about a particular product feature and more about who may initiate a request, who approves access, how long identifiers are retained, and how you prove that only authorized people saw sensitive threads. Message history that can reconstruct a shift helps after an event, but the operational win is everyday restraint: fewer people in the loop by default, and clearer escalation when something crosses a threshold.
Teams that do this well pair technical controls with rehearsal. Once a quarter, walk a tabletop scenario: a parking-lot concern, a children’s area question, and a medical assist. Ask which roles should be notified first, what language volunteers should use, and how supervisors will document outcomes. For related patterns, read incident coordination and shift summaries so your watchlist process does not become an orphan workflow disconnected from the rest of Sunday communication.