Coordinate complex human services
Bring participants, staff, services, referrals, documentation, communication, and follow-up into one operating system.
Community & Health Services
Smores Health helps community and health service organizations manage relationship-based programs across navigation, outreach, peer support, community health, and ongoing engagement.
A 20-minute walkthrough for your program.
For teams whose work happens in communities, homes, phones, programs, and conversations, not only inside clinics.

For community health worker program leaders
Community health worker software should help your team organize participant records, assigned work, encounters, documentation, and follow-up. Smores Health connects core coordination, note, and reporting workflows. Bring your program requirements to a walkthrough so you can see the fit, discuss configuration, and identify any additional needs before choosing a system.
By Smores Health. Reviewed October 9, 2026.
Explore participant records, staff assignments, schedules, and tasks. Walk through who owns the next step when a participant needs ongoing support or a worker is away.
Explore this workflowReview how staff capture service information and how notes move through review. Bring your approved fields and a fictional encounter to discuss the configuration your program needs.
Explore this workflowExplore reporting and exports alongside the underlying records. Bring your reporting definitions so the demonstration can distinguish people, encounters, activities, and outcomes.
Explore this workflowStart with your forms, roles, and one everyday scenario. Identify setup, training, and acceptance checks before expanding the workflow across your organization.
Explore this workflowUse a fictional participant who has an agreed next step, an assigned worker, and an upcoming contact. Ask to see how the team finds the record, documents completed work, and continues support when the responsible worker is unavailable. Then ask how that work appears in the program report. This makes the demonstration about your operating decisions instead of a tour of unrelated menus.
Our public resources are planning tools. They do not establish that every example field, integration, state-specific form, or billing workflow is included in your setup. Confirm specialized requirements directly. In particular, a documentation demonstration does not establish payer enrollment, claim acceptance, or live Medicaid billing for your program.
Choose the guide that matches your current decision. Each includes practical examples and a defined next step. The national guides cover operations; the Minnesota guide keeps state requirements and unresolved payer questions separate.
Plan a community health worker program with clear roles, intake, caseloads, supervision, documentation, and a practical launch checklist.
Write useful CHW encounter notes with a field checklist, fictional examples, correction guidance, and a free editable documentation template.
Define CHW program measures, referral outcomes, denominators, and reporting checks with worked examples and an editable monthly reporting worksheet.
Evaluate CHW software with a workflow scorecard, demo scenarios, total-cost questions, data export checks, and a practical implementation plan.
Review Minnesota CHW credentials, supervision, documentation, and unresolved billing questions with official sources and an operating-readiness checklist.
This page is for community health and outreach organizations evaluating the platform. Start with the work your team needs to perform and verify the fit in a demonstration. A similar job title does not mean two programs need the same forms, permissions, or reporting.
Yes. Bring blank forms and reporting specifications so we can discuss the required workflow and configuration. Use fictional examples rather than real participant records during the initial demonstration.
Start with a 20-minute walkthrough focused on your program. Explain what you are replacing, the staff who will use the system, and the workflow you most need to improve. Use the discussion to establish the next evaluation and implementation steps.
Bring participants, staff, services, referrals, documentation, communication, and follow-up into one operating system.
Give navigators, community health workers, peers, advocates, and coordinators tools designed around how they actually work.
Understand engagement, service delivery, unmet needs, program activity, and outcomes across your population.
Community care
The hardest problems in health often cannot be solved by another appointment.
People need help navigating systems, accessing resources, staying connected, building trust, and following through.
Smores Health gives organizations infrastructure for that work.
Programs
Platform
Enroll participants, communicate, conduct check-ins, share resources, manage groups, and keep people connected.
Manage caseloads, referrals, tasks, schedules, service plans, follow-up, and multidisciplinary workflows.
Capture activities, interactions, assessments, progress, service delivery, and required program documentation.
Measure reach, engagement, service utilization, workforce activity, needs, and outcomes.
Purpose-built
Traditional health IT is built around encounters. Community services are rarely that simple.
One participant may interact with a navigator, peer specialist, health worker, community organization, family member, and clinical provider across months or years. Smores Health helps organizations understand and coordinate that entire relationship network.
Choose one community health worker encounter and follow it through documentation, staff coverage, and reporting. Bring the team’s definitions of a person served, a completed encounter, and a referral result. That makes the demonstration specific enough to evaluate.
Use the buyer’s guide to compare the same tasks across vendors. Record what was demonstrated, what needs configuration, and what remains unanswered.
Use the buyer’s checklistSeparate people, encounters, referrals, and outcomes. Test a small fictional dataset against expected totals before relying on a dashboard.
Review CHW reportingIdentify staff roles, forms, training, and external requirements. Confirm any specialized payer or integration needs separately from the core documentation workflow.
Get pricing & infoPractical next steps
Use these guides to define what your community services team needs from software.
Test encounters, staff coverage, documentation, and reporting with a realistic scenario.
Compare participant tracking, multi-program records, pricing, and implementation.
Evaluate referral follow-up and clarify specialized housing-system requirements.
LET’S START WITH YOUR PROGRAM
Build the infrastructure for everything that happens around it.
Your team. Your questions. A real conversation.
A 20-minute walkthrough for your program.