Smores Health for your team
How does Smores Health support your recovery organization?
Bring your team's daily work and program reporting together in Smores Health. Connect the services you provide with the records and reports your organization uses.
Run the program
Coordinate staff assignments, schedules, and supervision in one workspace.
Support your community
Organize individual sessions, groups, referrals, and follow-ups around participants.
Explain the work
Use program reports and exports for leadership, planning, and funder conversations.
Your services, staff roles, documentation, and reporting needs shape the setup. Bring a workflow or report to explore the configuration options for your organization.
Jump to a section
What does an RCO need from software?
An RCO needs an operating system that reflects its community-led, recovery-oriented mission while giving staff and leaders reliable control over services, relationships, records, resources, funding, and accountability.
Peer-work guidance emphasizes recovery orientation, person-centered practice, mutuality, relationship, and role clarity. Product design should reinforce those principles and allow the organization to distinguish community participation, peer service, volunteer activity, grant deliverable, and billable service when applicable.[1][2]
Which RCO workflows should be connected?
Start with the organization's actual service map. A recovery center, outreach team, training organization, recovery residence, and Medicaid peer provider can share a mission while needing different records and controls.
| Criterion | How to evaluate it |
|---|---|
| Community entry | Walk-in, referral, outreach, event, anonymous resource use, enrollment, and participant choice remain appropriately distinct. |
| Peer relationships | Matching, assignments, preferences, continuity, communication, goals, follow-up, and transfers support trust and role clarity. |
| Programs and services | Individual support, groups, events, education, navigation, volunteer work, and other offerings use the correct workflow. |
| Workforce | Staff, volunteers, peers, supervisors, credentials, training, schedules, sites, tasks, and access are governed. |
| Funding | Grant, contract, donation, settlement, fee, and Medicaid activity can be classified and reported without changing the service truth. |
| Community accountability | Reach, engagement, service, experience, outcomes, stories, spending, and board or funder reports remain traceable and respectful. |
Which RCO scenarios should a vendor demonstrate?
Use a community member who enters through a low-barrier event, chooses peer support, receives a referral, joins a group, and later participates in an outcome or funder report.
| Workflow moment | What good looks like | Evidence to request |
|---|---|---|
| Low-barrier access | Program can record appropriate activity without requiring unnecessary clinical or identifying data | Anonymous, minimal, and enrolled paths |
| Peer relationship | Participant preference, assigned peer, goal, service, communication, and follow-up stay connected | Transfer and coverage scenario |
| Community program | Groups, events, resources, volunteers, attendance, and participant privacy are supported | Recurring group and open event |
| Multiple funders | The same truthful service can support appropriate program classification without double counting | Grant, settlement, and Medicaid separation |
| Board report | Leadership can explain reach, services, engagement, outcomes, funding, missingness, and limitations | Trace totals to source records |
What should an RCO ask vendors?
Ask whether the product works for community recovery activity as well as formal services. Require a clear answer about minimum data, participant choice, volunteers, nonclinical language, and mixed funding.
- Can people receive low-barrier community support without completing fields that are not required for that purpose?
- How are staff, volunteers, certified peers, supervisors, visitors, and participants represented with different permissions?
- Can one program support groups, events, individual peer work, outreach, navigation, and resources without clinical workarounds?
- How are multiple grants, contracts, settlement funds, and billable services classified without double counting or rewriting records?
- Can the RCO export usable participant, service, volunteer, program, funding, outcome, and governance data if it changes vendors?
Which product type is usually the best fit?
Purpose-built peer or recovery software is often the strongest starting point, but housing, clinical, engagement, or general CRM products may fit when those operating models are central and the complete workflow is proved.
Do not choose a product only because it uses recovery language. Test roles, services, participant experience, reporting, security, records, governance, cost, support, and exit. Include peers and community members in the decision through an accessible and meaningful process.
Frequently asked questions
Can Smores Health fit the way our recovery organization works?
Smores Health can be configured around staff roles, services, documentation, and review workflows. Bring an example of your day-to-day process and reporting needs to a walkthrough to explore the setup for your program.
Does every RCO need an EHR?
No universal rule applies. It depends on the organization's services, provider status, contracts, records, funding, and applicable law. An RCO should obtain qualified review for its specific model.
Can one system manage volunteers and staff?
Potentially, if roles, permissions, training, supervision, service attribution, sensitive information, and employment or volunteer records remain appropriately distinct.
Should all community activity require participant registration?
Not necessarily. Collect only what the purpose and applicable requirement justify. Preserve low-barrier and anonymous pathways when the program allows them.
Can an RCO use several funding sources in one platform?
Yes when the system preserves service truth, eligible cost or activity rules, allocation, approval, reporting definitions, and prevents unsupported double counting.
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.
- 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.
- Smores Health Platform: Smores Health. Smores Health's five connected product pillars and human-guided approach.
- Operate: Peer Support Workforce and Caseload Management: Smores Health. Smores Health workforce, caseload, schedule, supervision, and task workflows.
- Deliver: Sessions, Groups, and Telehealth: Smores Health. Smores Health service coordination, referrals, and follow-up workflows.
- Understand: Dashboards, Outcomes, and Reporting: Smores Health. Smores Health dashboards, outcome measures, exports, and funder reporting.
- 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.
- 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.