Smores Health for your team
What can your supervisors explore in Smores Health?
Start with one everyday supervisory task. Follow the staff responsibility, the record needing review, and the next action your team needs to take.
See staff responsibilities
Review staff assignments, caseloads, and scheduled work. Discuss how supervisors coordinate support across your team.
Follow a note through review
Explore documentation review, feedback, and corrections. See how an author and reviewer take part in the process.
Plan the follow-up
Discuss how tasks, schedules, and program reporting fit your supervision routine. Identify which steps need configuration for your team.
Your roles, services, and review process shape the setup. Bring a blank note form and a supervision workflow question. Confirm the scope for reflective supervision records and credential requirements separately during the demo.
Jump to a section
What should supervision software support?
It should support the formal operating responsibilities around supervision while preserving the human relationship and clearly separating note review, credential requirements, reflective support, performance management, and escalation.
CMS explains that states establish peer qualifications and supervision details for Medicaid benefits, while peer-work guidance emphasizes role clarity and recovery-oriented practice. The product must allow local requirements without implying one national supervision rule.[1][2][3]
Which supervision records should be distinct?
Keep each record tied to its purpose, access, retention, and responsible roles. Combining everything into one general supervision note can overexpose sensitive reflection and confuse review responsibilities.
| Criterion | How to evaluate it |
|---|---|
| Relationship | Assigned supervisor, peer, program, site, service scope, start, end, coverage, delegation, and required qualification. |
| Supervision session | Date, type, attendance, duration when required, purpose, agreed actions, follow-up, and minimum appropriate content. |
| Documentation review | Record, author, reviewer, status, issue, return, correction, approval, timing, and full version history. |
| Credential oversight | Requirement, evidence, verification, expiry, renewal, restriction, owner, and action remain separate from supervision content. |
| Support and escalation | Requested help, safety or boundary concern, responsible response, urgency, confidentiality limits, and closure. |
| Workforce decision | Coaching, workload, role, formal performance, and employment actions follow appropriate processes and access. |
Which supervision scenarios should be tested?
Test routine supervision, a returned note, supervisor absence, cross-site coverage, expired evidence, a sensitive concern, and role termination with each user view.
| Workflow moment | What good looks like | Evidence to request |
|---|---|---|
| Routine session | Correct relationship, purpose, actions, due dates, and limited record | Peer and supervisor views match policy |
| Note review | Queue, deadline, supported issue, return, correction, approval, and history | No silent co-authoring or overwrite |
| Coverage | Temporary qualified supervisor receives appropriate work and access | Access ends when coverage ends |
| Sensitive concern | User understands confidentiality limits and can reach the responsible response path | Access and escalation are purpose-limited |
| Offboarding | Open reviews, relationships, tasks, access, and retained records transition correctly | Historical authorship and supervision remain intact |
What should a supervision vendor prove?
Ask the vendor to show who can see each type of content and how state, payer, credential, service, and organization requirements are versioned.
- Can reflective supervision content be kept separate from documentation review, quality data, and formal employment records?
- How does the product verify that an assigned or covering supervisor meets the program's current requirement?
- Can a reviewer identify an issue without changing the peer author's signed content?
- What alerts are deterministic, what recommendations are automated, and who remains responsible for action?
- Can the organization export supervision evidence and history without exposing unrelated sensitive content?
How should supervision technology be governed?
Define each supervision purpose, required record, access group, retention rule, escalation boundary, and responsible role before configuring forms, dashboards, reminders, or reports.
Do not infer supervision quality from meeting count or approval speed alone. Use technology to protect time, route work, and make obligations visible while qualified supervisors retain judgment and peers retain a trustworthy place for appropriate support.
Frequently asked questions
What can we see in a Smores Health supervision demo?
Bring a blank note form and one supervisor workflow. We can walk through staff coordination, documentation review, feedback, and follow-up, then discuss the configuration and scope your program needs. A note review workflow does not replace the human supervision relationship.
How often must peer supervision occur?
There is no single national answer. Check the current state, payer, benefit, credential, contract, service, and organization requirements that apply.
Is note approval the same as supervision?
No. Documentation review may be one supervisory responsibility, but reflective support, role development, credential requirements, case consultation, and employment management are distinct.
Should supervision notes be visible to everyone in leadership?
No default should be assumed. Define the purpose, sensitivity, authorized roles, applicable obligations, retention, and escalation needs for each record type.
Can software decide whether a peer needs corrective action?
No. It can surface defined evidence and workflow status, but responsible people must consider context, fairness, role, policy, and appropriate process.
Sources and product pages
Sources support the specific guidance cited above. Program guidance is not a universal requirement. Product pages describe capabilities to verify against your organization’s needs.
- Medicaid and CHIP Coverage of Peer Support Services FAQ: Centers for Medicare & Medicaid Services. Federal baseline explaining state authority over peer qualifications, supervision, and benefit design.
- Core Competencies for Peer Workers in Behavioral Health Services: Substance Abuse and Mental Health Services Administration. Federal framework for recovery-oriented peer work, role clarity, and person-centered practice.
- Operate: Peer Support Workforce and Caseload Management: Smores Health. Smores Health workforce, caseload, schedule, supervision, and task workflows.
- Document: Notes, Assessments, and Supervisor Review: Smores Health. Smores Health structured notes, assessments, signatures, and review workflows.
- Understanding Confidentiality of Substance Use Disorder Records: U.S. Department of Health and Human Services. Official federal overview of 42 CFR Part 2 applicability, consent, use, disclosure, and breach obligations.