How Do You Manage a Community Health Worker Program?

What should you define before launching a CHW program?

Write down who the program serves, what support it offers, and how someone enters and leaves the service.

CDC describes community health workers as trusted frontline workers who connect people with health and social services. That description is a starting point, not a complete operating specification for every employer or payer.^[1]

Create a one-page service description with your staff and community partners. Include the population, languages, service area, referral routes, hours, expected support, and boundaries. Describe what staff should do when a person needs something outside that scope. A referral to another service needs an owner and a next step, not just a phone number at the end of a conversation.

Separate the intended benefit from the activity. "Help participants understand and access an agreed service" is a purpose. "Make three calls" is an activity. You may track both, but a call quota alone cannot show that someone received useful support. Treat this guide as an operational planning framework and confirm program-specific obligations separately.

How do you design a CHW program with the community?

Use structured conversations with potential participants, workers, and partners to choose a concrete service gap and test your assumptions.

Before choosing forms or software, write a problem statement that names a situation people actually encounter. For example: people referred from a neighborhood clinic cannot reliably reach the community service they selected. That is more actionable than a mission to improve access everywhere. Ask where the handoff fails, which people experience the failure, what they already try, and what assistance they would welcome. Treat the first explanation as a hypothesis to investigate, not a diagnosis of the community.

Include people who did not complete an existing program as well as those who did. A feedback process built only around current participants may miss inconvenient hours, unclear invitations, inaccessible locations, or reasons someone did not want the service. Offer more than one way to contribute. Short conversations, a facilitated small group, and an anonymous response option can produce different information. Explain how comments will be used and avoid collecting personal health histories when the planning question does not require them.

Turn each finding into an operational choice. If people cannot answer calls during work, decide whether your team can offer agreed evening contact windows. If referral partners send incomplete information, decide what intake staff need before accepting a referral and how they will obtain missing information. If a proposed change needs money or staffing that you do not have, record that constraint. Asking for input without explaining what can change creates expectations the program may not meet.

Which CHW service model fits your organization?

Choose a starting model around the problem, location, and handoffs you can support, then define how other services connect to it.

A clinic-linked model might concentrate on the transition from an appointment to an agreed community action. A community-based model might begin with outreach and participant-selected priorities. A partnership model might connect a referring organization, an employer of CHWs, and several receiving services. These are planning examples, not official classifications. The important decision is where responsibility begins, who owns follow-up, and what evidence shows that the responsibility has been completed or transferred.

Map the participant journey on a single page. Start with the first invitation, continue through contact and agreement, then show each service step, referral, follow-up, and closure. Under every arrow, write who acts and how the next person learns that action is needed. If the only explanation is that someone will remember to call, the process is relying on personal memory. Add a named owner and an agreed work queue before expanding it.

Test the journey from the participant's perspective. Can someone understand who is contacting them, why, whether participation is optional, and what will happen next? Can they correct information or change a contact preference without telling three teams? Avoid making a person retell their circumstances simply because each partner has a separate intake form. At the same time, do not assume every partner may access the same information. Have the responsible privacy lead define what may be shared and through which approved process.

Start with a bounded service and a workable handoff. Adding a second population or funding stream can change staffing, documentation, eligibility, and reporting. Review those changes deliberately instead of adding a tag and assuming the original workflow still fits. A useful expansion decision names what will stay shared and what needs separate instructions.

What belongs in your CHW launch checklist?

Assign an owner and a practical acceptance check to each part of the service before taking new referrals.

Use a short readiness meeting to review open items. A checked box should point to evidence: an approved procedure, a completed practice scenario, or a confirmed person responsible for the next action. Mark unresolved dependencies explicitly. It is more useful to know that an intake handoff still has no backup than to label the entire program ready.

How should intake move from referral to an agreed plan?

Confirm the reason for referral with the participant, record contact preferences, and agree on the next action together.

A referring organization may describe a need differently from the person receiving support. Begin by asking what matters to the participant and whether the proposed support is wanted. Record only the information needed for your role and service. Follow your organization's consent and information-sharing process before exchanging records with another organization.

Define separate states for referral received, contact attempted, connected, enrolled, and closed. A person who has not answered is not automatically refusing support. A referral that was sent is not automatically accepted. Decide how staff record unsuccessful attempts and when a supervisor should review whether another approach is appropriate.

For a fictional example, a clinic refers someone for help understanding an appointment process. The participant identifies transportation as the immediate obstacle. The worker confirms the preferred contact method, discusses available options within the program's scope, and agrees to follow up on a specific day. The record should preserve that actual sequence rather than replacing it with the referrer's original assumptions.

What should CHW hiring and onboarding include?

Assess the role you actually need, verify applicable qualifications separately, and rehearse the work before independent assignments.

Write the job description from the service model. Describe expected activities, locations, scheduling, supervision, language needs, documentation, and boundaries. Distinguish essential requirements from skills that can be developed during onboarding. Verify any credential or enrollment conditions against the program's own sources. A generic job title does not establish that a person is qualified for every service your organization offers.

Use practice scenarios that reflect the work. Ask how a candidate would explain a referral, respond when a participant chooses a different priority, or seek help when a request is outside the role. Assess communication and judgment without asking candidates to disclose private personal experiences to prove they are credible. Decide in advance what good performance looks like so different interviewers evaluate the same job rather than their own preferences.

An onboarding plan should connect instruction to a demonstration. After reviewing contact procedures, the worker practices a first call. After learning documentation expectations, they write a fictional note and receive feedback. After reviewing escalation procedures, they identify the correct contact for a scenario that cannot wait for the next supervision meeting. Completion of a slide presentation alone does not show that these tasks can be performed reliably.

Give new workers a named person for routine questions and an alternate when that person is unavailable. Explain which decisions they can make, which need consultation, and how to record an unresolved issue. During the first weeks, ask which steps require workarounds. Those questions often reveal unclear instructions or duplicated entry that experienced staff have learned to tolerate.

Build continued learning into the operating calendar. Select topics from actual review findings, such as unclear follow-up ownership or inconsistent referral closure. Keep coaching specific and respectful. The goal is to improve the service and support staff judgment, not to turn every difficult encounter into a performance failure.

When should you pause intake or redistribute a CHW caseload?

Look for unfinished commitments and capacity constraints, then choose the intervention that addresses their cause.

Compare planned and actual workload using the capacity calculation below. An unanswered call, a long visit, and a multi-agency handoff consume different amounts of time. Use worker feedback to understand the difference before interpreting a lower contact count as poor performance.

A workload review is not emergency triage. Clinical or safety concerns should follow the organization’s established escalation process. For ordinary work, record the specific commitment at risk and the person responsible for resolving the capacity problem.

How many participants can a CHW support?

Estimate workload from the time and complexity of the actual service. There is no universal caseload number supplied by this guide.

Use a weekly capacity worksheet that includes participant contact, preparation, travel, documentation, partner follow-up, supervision, training, and unexpected work. A calendar with only appointment blocks hides much of the service. Ask workers to review the assumptions before treating the estimate as a staffing target. For a new program, use the worksheet to identify what needs measuring during the pilot rather than presenting an untested estimate as a standard.

Consider this fictional example. A worker has 40 scheduled hours in a week. The program reserves 8 hours for supervision, meetings, training, and general administration, and 4 hours for interruptions and urgent coordination. That leaves 28 hours for planned participant-related work. If one service cycle averages 45 minutes of contact, 20 minutes of preparation and documentation, and 25 minutes of travel and follow-up, it uses 90 minutes. Twenty-eight hours divided by 1.5 hours gives about 18 complete cycles, not 18 new enrollments.

Now change the travel assumption. If travel and follow-up take 55 minutes instead of 25, the same cycle uses two hours and the estimate falls to 14 cycles. This does not mean the worker became less productive. The operating conditions changed. A geographic expansion, a receiving partner with long waits, or a need for additional communication support can change the workload even when the participant count stays the same.

Convert cycles into caseload only after considering frequency. Ten people needing weekly contact and ten needing monthly contact create a different schedule from twenty people needing weekly contact. Also review the work that is waiting: unanswered referrals, unfinished notes, and overdue follow-ups. An apparently manageable active caseload can conceal a growing backlog. Use trends and worker feedback together to decide whether to slow intake, redistribute work, revise a process, or add capacity.

Use these numbers only as an illustration of the calculation. They are not industry averages, recommended ratios, or payer limits. Keep leave coverage and vacancies visible in the plan. A model that works only when every position is filled and nobody is absent is not a dependable promise to participants.

How do you build referral partnerships that actually work?

Agree on acceptance criteria, communication routes, response expectations, and what counts as a completed handoff.

A resource directory tells staff where a service might exist. A working referral relationship also tells them whether the service is accepting people, what information is needed, which contact route is approved, and who responds when the first attempt fails. Assign someone to maintain the directory and record when important details were last confirmed. Do not ask every worker to independently rediscover the same eligibility or contact problem.

With each priority partner, walk through one fictional referral from beginning to end. Ask how the receiving team acknowledges receipt, how an appointment or other next step is communicated, and what happens if the person cannot be reached. Agree on the information your team needs back to continue its own work, subject to the applicable sharing rules. A partner's ability to receive a form does not establish permission to exchange every record attached to it.

Define referral statuses in ordinary language. Sent means the request left your team through the intended route. Accepted means the receiving service acknowledged that it can take the next step. Connected means you have evidence of the agreed connection. Service received requires its own evidence. These proposed definitions may need adapting to your funder's contract, but they should not collapse into a single completed checkbox.

For a fictional example, a participant chooses a food-support organization. The CHW sends the agreed referral, then learns the organization has a waiting list. The referral was sent successfully, but the participant has not received the service. Record the waiting status and discuss alternatives with the participant. Closing the referral as successful would hide the barrier and make the program's report misleading.

Review recurring failures with partners rather than blaming participants. If forms are repeatedly returned, simplify or clarify the required information. If a service has stopped accepting referrals, update the directory and staff instructions. A useful partnership review ends with an owner, an agreed change, and a date to check whether the change worked.

How should a CHW team prepare for community and field work?

Plan communication, travel, accessibility, and backup arrangements around the settings where staff and participants actually meet.

List the settings your program intends to use: an office, a community location, a participant-selected meeting place, a phone call, or another approved arrangement. For each, decide how appointments are confirmed, what information staff need beforehand, how they contact a supervisor, and how records are completed through approved tools. Confirm any service or payer restrictions separately. A convenient meeting format is not automatically an authorized billing format.

Develop a staff safety procedure with the people responsible for that area in your organization. Include check-in expectations, what to do when a location or situation feels unsafe, and who responds if a worker cannot be reached. Workers should know they can follow the approved safety process without being penalized for failing to complete a planned visit. This guide does not replace emergency procedures or training for a particular setting.

Plan for ordinary disruptions too. A bus is late, a phone is disconnected, a room is unavailable, or a worker loses network access. Decide how staff communicate a change and where unfinished work remains visible. If your proposed software requires connectivity, test the actual service locations and establish an approved fallback. Do not assume a mobile-friendly screen means offline capability.

Ask participants what makes communication usable for them. Record agreed contact times, language or accessibility needs, and relevant restrictions through your approved process. Avoid interpreting an unanswered call as a refusal of help. At the next appropriate opportunity, confirm whether the contact method still works. A reliable relationship depends on a process that can accommodate real circumstances.

What should CHW supervision cover each week?

Use supervision to review role boundaries, difficult handoffs, participant priorities, documentation quality, and worker support needs.

Choose a cadence that fits the program and any applicable requirements. A practical agenda includes unresolved cases, upcoming commitments, a small sample of notes, and barriers that require management action. Distinguish a worker's learning need from a system problem such as an unavailable referral partner or a form that asks the same question three times.

Practice exceptions before they happen. Rehearse how a worker responds when someone requests advice outside the role, wants a different worker, asks to stop contact, or disputes a record. Use fictional information. The goal is to help staff locate the right procedure and support person, not to improvise a new policy in the moment.

What does a useful weekly CHW operations meeting look like?

Review the work that needs a decision, protect time for staff questions, and leave with named actions rather than a longer status report.

Use a short agenda built around unresolved work. Start with upcoming coverage gaps and time-sensitive handoffs, then review overdue follow-ups, referrals waiting for partner action, and recurring documentation questions. Leave room for workers to identify a barrier that the dashboard does not show. Do not require everyone to repeat every completed encounter. The meeting should help the team make decisions that cannot be made from a list of activity totals alone.

In a fictional example, three workers each have a similar number of participants. One has eight referrals waiting on the same receiving organization, another has several long-distance visits, and the third has capacity for additional follow-up. Equal participant counts hide the different workloads. The supervisor might contact the receiving partner, revise travel scheduling, and redistribute a bounded set of follow-ups with appropriate participant communication. Simply assigning everyone the same numerical target would not address the differences.

For every decision, record the action, responsible person, due date, and evidence of completion. If the action is to clarify a partner's intake criteria, completion means obtaining and communicating the answer, not merely sending an email. If a worker needs help with an unclear note requirement, identify who owns the policy question and when the worker can expect guidance. Keep unresolved decisions visible at the next meeting until their disposition is clear.

End by checking whether staff can actually complete the commitments made. Ten new action items without protected time may worsen the backlog. Prioritize the changes that address the largest barrier or most immediate obligation, and explicitly defer lower-priority work. Review whether the meeting itself is helping: are questions resolved sooner, are fewer handoffs lost, and do workers know where to seek help between meetings? These are suggested management checks, not required performance measures.

How do you budget for a sustainable CHW program?

Estimate the full cost of delivering and supporting the service, then compare confirmed funding with conservative activity assumptions.

Start with personnel and the time needed around participant contact. Include compensation, employer costs, supervision, administration, training, leave coverage, travel, communications, equipment, software, and interpretation or accessibility arrangements where relevant. Separate startup costs from recurring costs. Record which figures come from an actual quote or approved budget and which remain estimates. This makes the plan easier to update when a staffing or purchasing decision changes.

A fictional monthly budget might include $24,000 in personnel and employer costs, $4,000 in supervision and administration, $2,000 in travel and communications, and $1,000 in software and equipment costs. The total is $31,000. If the program supports 100 distinct participants that month, the simple cost per participant is $310. If it supports 80, the same calculation becomes $387.50. Neither number is a reimbursement rate or a measure of service quality.

Keep unit definitions consistent when comparing budgets. A participant, an encounter, an outreach attempt, and a completed referral are different denominators. A program can appear cheaper per contact by making many short attempts without improving meaningful engagement. Pair cost measures with the purpose of the service and information about workload, participant priorities, and follow-through.

Build a funding worksheet with confirmed amounts, restrictions, expected payment timing, and unresolved conditions. Grant income, service contracts, donations, and reimbursement may have different documentation and allocation rules. Have the responsible finance lead determine how those rules apply. Do not assume that every valuable CHW activity can be billed or that expected claims will be paid on the schedule needed to meet payroll.

Review a conservative scenario before expanding. What happens if referral volume is lower than expected, payment arrives later, or a key partner stops accepting people? Decide which expenses can change and which commitments must continue. A sustainability plan should explain how current participants will be supported during a funding interruption, not just how the next grant application will be written.

How should you test the program before expanding?

Run a small, defined pilot that includes an ordinary encounter and the exceptions your team expects to face.

• Walk a fictional referral through intake, assignment, an encounter, documentation, follow-up, and closure.
• Test a missed contact, worker absence, duplicate referral, changed preference, and unresolved service request.
• Check who can view records, who reviews notes, and how a correction is handled.
• Reconcile the pilot report to the example records and explain every count.
• Record each issue, its owner, and the evidence needed to close it.

Agree on a review point before starting. Look at what staff and participants found confusing, which handoffs stalled, and whether the records are usable by the next authorized person. Do not expand solely because a launch date has arrived. Expand when the team can explain and repeat the workflow, with unresolved limitations understood.

What should the first 90 days of a CHW program look like?

Use the first three months to establish the service, test a limited workflow, and make an evidence-based expansion decision.

Days 1 through 30 can focus on decisions and preparation. Finish the service description, partner map, staffing assumptions, funding review, and draft documentation process. Assign owners to unresolved dependencies. Work with a small set of fictional scenarios before accepting live referrals. At the end of this period, the team should be able to explain the participant journey and demonstrate each handoff. This is an example schedule, not a required launch timetable.

Days 31 through 60 can focus on a bounded pilot once applicable prerequisites are met. Choose a volume the team can support and review frequently. Record time spent on the work, common missing information, handoff failures, and participant feedback. Keep a decision log so staff can distinguish an approved change from an improvised workaround. If a critical problem appears, reduce intake or pause the affected workflow while it is resolved.

Days 61 through 90 can focus on whether expansion is justified. Compare the planned workload with observed work. Review outstanding referrals, follow-up delays, documentation quality, and the experience of participants and staff. Identify which issues came from unclear instructions, insufficient capacity, partner constraints, or tools. More software or more staff may help some problems, but neither automatically fixes an undefined service.

End the pilot review with a concrete decision: continue at the current size, expand a defined part of the program, revise and retest a workflow, or stop a service that cannot be supported. Name the evidence behind the decision and the next review date. Do not report the pilot as successful solely because the planned number of people enrolled. Enrollment is the start of the relationship, not proof that the intended support occurred.

How should CHW programs handle closure and reentry?

Agree on how support ends, explain any remaining next steps, and provide a clear route back when the program permits reentry.

Define closure reasons carefully enough to support both continuity and reporting. A person who achieved their agreed priority, someone who chose to stop, and someone your team could not reach have different experiences. Avoid using a single successful completion label for all three. Record the appropriate status through your approved process and do not interpret inability to make contact as evidence that support is no longer needed.

Before a planned closure, review outstanding referrals and responsibilities with the participant where possible. Explain which actions your team will complete, which belong to another service, and how the participant can ask a question later. If another organization will continue support, verify the intended handoff rather than assuming that sending a referral transferred responsibility. Keep information sharing within the applicable approved process.

For reentry, decide what needs updating and what history should remain available to authorized staff. A returning participant may have different priorities, contact preferences, or service eligibility. Do not blindly restart an old plan, and do not create a duplicate identity merely to represent a new period of support. Have the responsible team define how a new service episode connects to the existing record. Clear closure and reentry procedures make continuity easier to understand for participants and staff alike.

How can you connect this work to your software evaluation?

Bring one specific workflow to a demonstration and compare the steps against your actual operating requirements.

Smores Health provides participant records, staff coordination, documentation, and reporting workflows. Ask which forms, roles, review steps, and reports fit your program today and which need configuration. The downloadable worksheets are planning resources; their presence does not mean every field is already an available product feature.^[2]

Frequently asked questions

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.

1. Resources for Community Health Workers: Centers for Disease Control and Prevention. Role and resource overview, published December 3, 2024. Checked October 9, 2026. Operational worksheets in this guide are original Smores Health examples, not CDC forms.
2. Smores Health: Operate: Smores Health. Product overview. Confirm your program configuration, included services, and rollout scope in a walkthrough and written agreement.
3. Smores Health: Document: Smores Health. Product overview. Confirm your program configuration, included services, and rollout scope in a walkthrough and written agreement.