Institutional reference · Version 2026.08 — Controlled Review
This page is for authorized campus implementation teams. It does not instruct an individual responder, grant authority, or convert generic contacts and thresholds into local policy.
Name the sponsoring authority, implementation lead, participating units, intended use, affected populations, covered hours and locations, dependencies, prohibited representations, and success measures.
Do not proceed until scope is authorized.
Name who approves emergency routes, clinical interfaces, suicide-safety and threat processes, accessibility, privacy, required reporting, records, transport, training, public claims, release, emergency corrections, closure, and version retirement.
For each function, record provider, hours, eligibility, access method, expected response, Decision Authority, alternate route, failure action, current owner, and how acceptance and outcome are verified.
Do not publish until routes are validated.
Protect SAFE CARE’s named functions and distinctions while replacing generic placeholders with approved local routes, role limits, records, privacy controls, accessible formats, and version information.
Teach each role what it must recognize, perform, transfer, supervise, or govern. Require observable performance, accessible instruction, calibrated facilitation, remediation, and explicit limits on certification or qualification claims.
Run representative scenarios across days, nights, weekends, handoffs, unavailable services, access barriers, conflicting information, privacy constraints, deteriorating conditions, missed follow-up, and reopening. Record defects and retest corrections.
Do not launch until training and failure testing are complete.
Assign quality review, route validation, version ownership, change approval, emergency correction, archive, distribution, withdrawal, retraining, feedback, and recurring evaluation. Keep the authoritative location and superseded status visible.
The implementation team should include authorized owners for emergency operations, student affairs, residential life, behavioral health, medical response, disability and language access, equity, privacy, records, required reporting, transport, training, communications, technology, and evaluation. Participation does not erase distinct authority: document who decides, who advises, who performs, who verifies, and who retains unresolved work.
Preserve the course architecture and protected terms: SAFE and CARE; Operating Picture; Communication Access; Next Safe Action; Functional Stabilization; Stabilization Cycle; Coordination Gap; the full resource-state sequence; Functional, Continuity, Communication, and Verification Ownership; Decision Authority; Warm Handoff; connection and outcome verification; task, function, and case completion; and precise reopening. Local examples may change. These functions and distinctions should not be silently redefined.
| # | Controlled artifact | Minimum local content |
|---|---|---|
| 1 | Scope and authority charter | Sponsor, audience, setting, permitted uses, exclusions, decision rights, status |
| 2 | Role and capability matrix | Role scope, authority, prohibited actions, capability activation, retained responsibility |
| 3 | Emergency and specialized-procedure map | Medical, suicide-safety, threat, violence, legal, reporting, and other controlling routes |
| 4 | Local response-path map | Exact SAFE CARE interfaces, entry points, owners, completion cues, and return routes |
| 5 | Resource directory and failure map | Hours, eligibility, access, alternates, maximum waits, contingencies, tested status |
| 6 | Communication and accessibility plan | Language, disability, technology, privacy, sensory, and effective-communication supports |
| 7 | Record and privacy specification | Official systems, minimum necessary use, working-copy rules, correction, retention, access |
| 8 | Training and facilitation package | Role-based objectives, prerequisites, scenarios, performance criteria, remediation, facilitator controls |
| 9 | Pilot and failure-test plan | Cases, off-hours conditions, route failures, access barriers, metrics, defect ownership, retest |
| 10 | Quality and change-control plan | Review cadence, complaints, equity, incidents, approvals, urgent correction, archive, withdrawal |
| 11 | Local Route, Authority, and Version Matrix | Validated contacts, hours, steps, alternates, role authority, system destination, owner, test date, version |
Tool 11 is the operational index for local release control, not a generic contact list. Each entry should identify the function, official route, access conditions, alternate, Decision Authority, role permissions, controlling source, validation owner and date, current version, and next review. A route is not validated merely because a phone number works.
Before release, authorized teams must resolve:
Do not publish generic thresholds, contacts, reporting rules, or authority as universally valid. Label unresolved items and withhold operational release until the appropriate owner resolves them.
| Role depth | Expected performance |
|---|---|
| Awareness | Recognize the path, emergency override, role boundary, and correct activation route |
| First receiver or student employee | Receive, route, preserve immediate safety, communicate within role, and maintain responsibility until accepted |
| Designated responder | Perform the complete SAFE sequence and transition open work into CARE |
| CARE or case owner | Coordinate, preserve continuity, record, verify, repair, and reach an authorized disposition |
| Supervisor, trainer, or implementer | Coach judgment, review performance, govern local routes, analyze failure, and control versions |
Competency claims should be limited to observed course performance under stated conditions. Completion does not establish professional qualification, licensure, legal authority, continuing-education credit, or certification. Facilitators need approved guidance for sensitive discussions, accessibility, scenario boundaries, correction of unsafe reasoning, emergency disclosures, participant support, and escalation of unresolved policy questions.
Pilot the entire pathway rather than isolated lessons. Test concurrent needs, shift changes, multiple settings, unavailable providers, delayed acceptance, failed handoffs, inaccessible communication, transportation breakdown, incomplete records, unanswered outreach, closure disagreement, and precise reopening. Track whether participants preserve evidence states, role limits, owners, time controls, contingencies, and verification.
Launch only when the sponsor confirms authorized scope; approved owners; validated routes and alternates; accessible training and resources; official record and privacy rules; qualified facilitation; completed failure tests; corrected material defects; operational support; version control; and a withdrawal plan. Publish the authoritative location, effective status, owner, review date, and superseded-material process.
After launch, review performance, near misses, complaints, student and responder experience, access and equity, route failures, documentation quality, ownership loss, outcomes, and unintended effects. Every material change should record the reason, approving authority, affected artifacts, validation, effective date, communication plan, retraining need, and archived predecessor.
