This website is not monitored for emergencies.Call or text 988Call 911 for immediate danger
Role Clarity

Partnership Architecture, Team & Governance

Build a coalition that can decide, deliver, repair, document, and sustain the work without confusing collaboration with undefined authority.

Listen, map, assign, and verify before rollout.
ClassificationNonclinical Community Prevention & Early Response
Operating statusControlled Working Edition
Release gateLocal adoption and verification required
The practical question

Listen, map, assign, and verify before rollout.

Use this page as a controlled working guide. Adapt language and activities to the population, verify local resources, assign ownership, and preserve the clinical and life-safety boundaries described throughout the model.

STRIDE presenting a prevention roadmap connecting safety, community, growth, learning, and care.
Organize 04
SEC-15

Partnership without role confusion

Partnership works when organizations share purpose without blurring authority, records, consent, money, or scope. Collaboration is not commingling. Each partner should know what it owns, what it contributes, what it may not promise, and how the handoff is completed.

Levels of partnership

LevelCommitmentEvidence
AwareReceives updates and understands the initiative.Contact record; information distribution
SupportivePromotes activities or contributes limited resources.Written commitment; communication plan
ContributingProvides staff time, space, transportation, materials, outreach, or subject-matter support.Resource commitment; owner; schedule
Co-implementingShares planning, delivery, review, and problem-solving responsibilities.MOU; workplan; governance participation
StrategicShares long-term outcomes, infrastructure, funding strategy, and system-change work.Formal agreement; dashboard; annual review

Successful collaboration standard

Partner commitment builder

BPTC-W-009Planning worksheet — not a record of service
Deidentified planning onlyDo not enter participant, staff-performance, incident, consent, or other identifiable information. This worksheet may save locally and may be included in the JSON export.
Organize 05
SEC-16

Build a team that can decide, deliver, and repair

A committee can talk for years without becoming an operating team. The governance structure must connect authority, lived experience, program delivery, clinical safety, family voice, youth voice, data, and community relationships.

RoleCore ownershipRequired evidence
Executive SponsorApproves scope, resources, boundaries, and public commitments; removes barriers; receives dashboard reports.Authority memo, budget, quarterly review
Program Director / Community Prevention LeadOwns implementation, partner coordination, schedule, staffing, action plan, and completion evidence.Weekly tracker, action plan, partner log
Clinical AdvisorReviews safety, scope, referral pathways, curriculum risk, and clinical escalation without turning education into unauthorized treatment.Clinical review notes, escalation protocol
Youth LeadAdapts content by age, protects youth safety, coordinates caregivers, and confirms staff readiness.Youth schedule, guardian workflow, safety checklist
Adult LeadCoordinates adult education, peer support, referral, family engagement, and stability pathways.Adult pathway tracker, completed handoffs
Peer / Lived-Experience LeaderBuilds engagement, hope, practical navigation, and credible support within defined peer scope.Peer activity log, referral follow-up
Data & Quality LeadMaintains measures, attendance, survey integrity, dashboard, findings, and improvement actions.Monthly dashboard, CQI log
Community Partner LiaisonClarifies partner contribution, referral acceptance, communication, and accountability.MOU or partner agreement, contact log
FacilitatorDelivers approved content, practices skills, documents participation and concerns, and escalates risk.Session plan, attendance, facilitator reflection
Caregiver / Resident Advisory VoiceTests relevance, access, dignity, and practicality; identifies blind spots before scale.Advisory notes, change recommendations

Standing meeting anatomy

OpenPurpose, safety, conflicts, and previous commitments.
SeeCurrent data, participant voice, incidents, barriers, and changes in the environment.
DecideWhat requires action, what can wait, who decides, and what needs escalation.
AssignOwner, due date, support, dependency, and completion evidence.
CloseRead back decisions, confirm next meeting, and document unresolved risk.
Conflict standard

Disagreement is not failure. Hidden authority, vague goals, broken promises, and undocumented decisions are failure points. Address the task, the process, the relationship, and the power dynamic separately.

Team charter

BPTC-W-010Planning worksheet — not a record of service
Deidentified planning onlyDo not enter participant, staff-performance, incident, consent, or other identifiable information. This worksheet may save locally and may be included in the JSON export.
Deidentified planning only