National Community Health Worker Awareness Week | August 24-28, 2026
National Community Health Worker Awareness Week 2026: Build a Reliable Path from Awareness to Action
Recognition becomes operational when leaders protect community trust, define the work, fund the workforce, close referral loops, and use a 90-day test to learn whether access actually improved.
Observance identity: The congressional resolution supporting the fourth annual week recognizes community health workers as trusted community members and cross-sector connectors. It designates August 24-28, 2026, and is an official identity source, not evidence of intervention effect. Read H. Res. 1187.
Awareness that changes conditions
Recognize the workforce without turning trust into an unlimited resource
National Community Health Worker Awareness Week offers healthcare executives a rare management opportunity. The week can make a historically underrecognized workforce visible while also testing whether the organization has built conditions worthy of the trust community health workers carry. Community health workers may be known locally as promotores de salud, community health representatives, outreach workers, navigators, peer workers, or by many other respected titles. The title matters less than the relationship: the worker is trusted by, connected to, or unusually knowledgeable about the community served.
That relationship can improve the fit between services and real life. Community health workers may help people understand options, surface barriers, prepare questions, navigate health and social services, connect with an accountable team, and build individual or community capacity. They also help organizations see the distance between a policy on paper and an accessible service in practice. The work can reveal transportation barriers, language needs, technology exclusion, confusing eligibility rules, fear created by prior experiences, and handoffs that appear complete in a database but never became usable help.
Trust, however, is not a commodity that a health system can simply acquire by hiring a trusted person. It is relational and can be damaged when a community health worker is asked to defend an inaccessible process, collect information without a clear purpose, make promises that the organization cannot keep, or absorb community frustration without authority to obtain a response. Awareness should therefore include an executive promise: the organization will not use the worker's credibility to hide system unreliability.
A 2026 mixed-methods study of community health workers in Arkansas found that clinical integration depends on role clarity, onboarding, open communication with supervisors, realistic expectations, and collaborative relationships.1 The sample was self-selected and limited to one state, so it does not prescribe a national model. It does support a practical conclusion: appreciation without work design is incomplete. A credible week should clarify what community health workers can do, who must respond when they escalate a need, and how the organization will support them after the event ends.
Community-led
Priorities and definitions are shaped with community members and community health workers, not merely announced to them.
Role-clear
Scope, consent, documentation, supervision, escalation, and clinical boundaries are explicit for the selected pathway.
Workforce-safe
Compensation, workload, coverage, training, technology, psychological safety, and development are treated as operating requirements.
Accountable
Each commitment has an owner, resources, measures, a review date, a feedback route, and a decision rule.
The week should also avoid assigning one workforce responsibility for outcomes that depend on the whole system. A community health worker can help identify a need and support a connection, but cannot create an appointment slot, affordable medication, safe housing, transportation capacity, interpreter availability, insurance eligibility, or a receiving service's response. Reliable access requires executives to distinguish the community health worker contribution from the organizational capacity that must surround it. When that distinction is visible, the workforce can be recognized without being blamed for constraints it did not create.
Evidence with controlled claims
Use the literature to design a local test, not to manufacture certainty
The selected evidence base includes 15 peer-reviewed records ordered newest first. It intentionally spans recent clinical-integration research, language-concordant navigation, workforce training, digital-tool usability, service education, workforce planning, compensation, cost and cost-effectiveness, primary-care role synthesis, and chronic-disease reviews. The studies come from different countries, health systems, populations, interventions, and outcome definitions. That diversity is useful for identifying design questions, but it prevents a single pooled claim about what every community health worker program will achieve.
The evidence is used in layers. Direct integration and workforce studies inform role clarity, supervision, onboarding, and team relationships. Intervention studies show what happened in a defined population under a defined model; they do not prove that the same result will occur locally. Validation studies inform how to test a measurement tool in context. Reviews identify recurring themes and gaps, while their conclusions remain bounded by the included literature. Economic reviews can guide questions about affordability and reporting, but heterogeneous costs cannot become a universal budget or return-on-investment promise.
| Design group | Count | Use in this brief | Do not infer |
|---|---|---|---|
| Review or synthesis | 5 | Identify recurring program, role, economic, and implementation considerations. | A uniform effect, payment model, cost, or staffing standard. |
| Experimental or quasi-experimental | 4 | Examine defined intervention components, outcomes, and implementation conditions. | Transferability to another population, workforce model, or setting without testing. |
| Mixed-methods or implementation | 3 | Understand experience, integration, training, workflow, and local adoption. | Causation from perception, self-report, or one implementation site. |
| Workforce modeling or measurement | 3 | Inform measurement discipline, capacity questions, and contextual validation. | A universal tool, ratio, productivity target, or workload threshold. |
Evidence boundary: The bars are exact counts of selected records, not effect sizes or certainty grades. Each record appears once for display even when it could fit more than one category.
Integration evidence supports clear interfaces
The Arkansas integration study described a workforce that values collaboration while encountering differences between expectations and actual work.1 A randomized trial among 287 Korean American older adult-caregiver dyads tested a language-concordant community health worker intervention for dementia-care linkage. At six months, verified linkage occurred for 16.7% of intervention dyads and none of the control dyads, while several caregiver outcomes did not show a comparable change.2 The trial demonstrates a specific linkage result in one linguistic and clinical context. It does not show that navigation alone resolves every access barrier or that a six-month design is sufficient for every outcome.
These two records point toward the same operating need from different directions. The community health worker must know the intended population, what can be offered, how consent is obtained, what information is necessary, who accepts the connection, what follow-up is expected, and how a failed connection is recovered. The receiving service must also know what it owns. A referral is not reliable merely because the sender completed a field. It becomes reliable when the recipient accepts responsibility, the person understands the next step, and the system has a visible response when the expected service does not occur.
Training and digital tools require contextual validation
Recent studies show encouraging changes after defined training or education, but they also demonstrate why leaders must separate learning outcomes from downstream health outcomes. A 2026 study involving 54 promotoras in southern New Mexico reported improved skin-cancer knowledge, confidence, and comfort after an educational intervention.4 The study did not establish changes in completed referrals, diagnoses, treatment, or equity. A 2025 quasi-experimental study in eastern Uganda reported improvements in maternal-health knowledge, attitudes, and antenatal-care attendance after a community health worker-led education model.7 Its rural setting, pre-post design, and maternal-health focus limit transferability. An Atlanta training-program evaluation reported strong participant ratings and perceived gains while calling for sustainable funding and longer-term outcome measurement.5
A five-year rural Nepal study examined a full-time, salaried, supervised community health worker model that included postpartum contraceptive counseling.6 Its nonrandomized pre-post design and integrated maternal-health context require caution, but the program description reinforces the importance of supervision, compensation, longitudinal follow-up, and implementation measurement. A broader systematic review of chronic-disease interventions among vulnerable populations found a varied evidence base rather than one uniform effect.14 Together, these records support a bounded local pathway with explicit components and outcomes.
Digital support also needs more than a deployment date. A 2026 Rwanda study adapted and tested measures of mobile-health usability and acceptability with expert review and community health worker participation.3 The work supports local language, face validity, reliability testing, and contextual assessment. It does not prove that a particular application improves care or that one usability score is valid everywhere. During awareness week, executives should ask community health workers which tools remove duplicate effort, which create more channel burden, what happens during downtime, and whether data collection has a clear purpose and governance owner.
Economics and workforce design require transparent assumptions
A 2025 scoping review of HIV, tuberculosis, and malaria programs found that many included scenarios were cost-effective relative to alternatives, but costs varied widely and reporting methods were heterogeneous.9 Another 2025 scoping review identified fixed, performance-based, income-generating, and combined compensation models, with irregular payment emerging as a common weakness.10 These reviews cannot set a local wage, payment mechanism, or business case. They do support fair and reliable compensation, community health worker participation in payment design, and economic evaluation that states perspective, time horizon, resources, comparators, and uncertainty.
Workforce planning must likewise make assumptions visible. A 2025 overview of African workforce estimates showed how requirements change when community health workers are modeled as full-time or part-time.8 It is not a staffing standard for a U.S. organization. Its transferable lesson is that workload estimates are meaningless without specifying time, geography, travel, task mix, supervision, administrative work, training, leave, and the share of working time actually available for service. Awareness should prompt leaders to examine those assumptions rather than celebrate heroic overextension.
Five days, one governed commitment
Use the observance as a short discovery-to-action cycle
The five-day observance can become a disciplined improvement campaign if every day produces a small, verifiable output. The goal is not to redesign the entire community health program in one week. It is to select one access problem that matters to the community, understand how the current pathway behaves, define a safer operating model, and authorize a 90-day test. The campaign should include community health workers across shifts, sites, employment arrangements, languages, and tenure. It should also provide more than one participation method so that attendance at a single meeting does not determine whose voice counts.
Day 1: listen and define access in community terms
Begin with a facilitated session led with community health workers and community partners. Ask what people are trying to accomplish, where they lose the path, what information is confusing, which requirements create avoidable burden, what feels unsafe, and what a respectful recovery looks like after a missed connection. Do not begin with the organization's preferred solution. Capture exact process conditions rather than personal identifiers. Separate barriers the team can redesign from structural constraints that require executive or policy action.
Select one bounded pathway for the 90-day test. Examples might include connection to a primary-care intake, follow-up after a positive community screening, a maternal-health education and referral pathway, or navigation to an approved social-service partner. Define what is outside scope. If the pathway includes clinical screening, clinical advice, direct services, or protected information, approved protocols and qualified supervision must govern those components. Community health workers should never be pushed beyond local scope because the campaign created enthusiasm.
Day 2: map the current state and expose invisible work
Map every step from the community member's perspective and the workforce perspective. Show how a need is identified, how consent is recorded, which information is collected, how the receiving service is selected, what the community health worker does while waiting, how acceptance is signaled, what happens after a missed call or appointment, and how the person learns the outcome. Mark duplicate entry, repeated storytelling, unowned queues, informal texting, language handoffs, travel, technology problems, and work completed outside paid time.
The map should include the receiving team's work. A pathway may fail because eligibility rules are unclear, referral information is incomplete, appointment capacity is absent, outreach channels are inaccessible, or no one is accountable for a returned referral. Label those conditions as system causes. Do not describe them as community health worker performance. The purpose of mapping is to locate interfaces that need ownership and resources, not to create surveillance of individual workers or community members.
Day 3: define the future-state loop and practice recovery
Design the smallest future-state loop that can be tested safely. Specify the entry criteria, minimum necessary information, consent, sender, accountable receiver, acceptance signal, expected action, exception route, follow-up responsibility, closure definition, and feedback to the community member. Then run short simulations. Include a routine case, missing information, language or accessibility need, inability to contact the person, rejection by the receiving service, urgent concern, privacy uncertainty, and technology downtime. The team should know which conditions require clinical escalation and which require operational recovery.
Local design required: The steps are a governance pattern, not a clinical workflow. Define urgency, time rules, consent, documentation, supervision, exceptions, and closure for the selected population and service.
Day 4: protect the workforce and resource the test
Review whether the future-state process can be performed within paid time and approved scope. Estimate demand, travel, documentation, follow-up attempts, supervision, team meetings, training, data-quality review, translation, accessibility support, technology, and backup coverage. Identify what the organization will stop doing or simplify so that the pilot does not merely add work. State compensation and reimbursement assumptions. A pilot that depends on unpaid labor, personal devices, informal data storage, or unmeasured after-hours work is not ready.
Confirm that community health workers have a named supervisor who understands the role, a rapid route for clinical questions, a psychologically safe way to report that workload is unmanageable, and access to learning from difficult cases. Training should include the actual tools and exception conditions in the pilot. It should not be used to solve missing capacity, ambiguous policy, disrespectful team behavior, or inaccessible systems. Those are leadership responsibilities.
Day 5: recognize specifically and sign the 90-day charter
The public recognition moment should be specific about contribution and honest about organizational responsibility. Describe how community health workers help make needs, barriers, choices, and next steps visible. Thank community partners and the clinical and social-service teams that accept connections. Avoid promising outcomes the evidence does not establish. Do not display individual stories, photographs, locations, or health information without informed permission and a clear purpose.
Close the week by signing one 90-day charter. The charter names the executive sponsor, community health worker co-lead, community partner, clinical owner, operational owner, receiving-service owner, data steward, privacy and compliance contacts, and finance or payer partner. It defines the pathway, population, exclusions, baseline window, measures, resources, meeting cadence, feedback channels, accessibility provisions, stop conditions, and decision date. Recognition becomes credible because an accountable operating commitment is visible.
A reliable access operating system
Build support around the relationship instead of routing everything through it
A dependable community health worker model requires more than an outreach function. It is an operating system with community governance, role architecture, supervised practice, accessible channels, receiving-service ownership, feedback, data stewardship, sustainable financing, and leadership response. The community health worker sits at important interfaces, but should not become the only bridge. If every exception depends on one person's personal relationships or memory, the organization has created fragility rather than access.
Operating principle: Every surrounding component needs a named owner. The community health worker should not be treated as the substitute for absent capacity, inaccessible policy, or unresponsive services.
Community governance is different from community outreach
Outreach asks people to participate in an existing program. Governance gives community members and community health workers influence over priorities, definitions, safeguards, measures, and decisions. For the 90-day test, specify which decisions are co-designed, who represents the community, how participants are selected, what support or compensation is provided, and how disagreements are handled. Avoid asking one community health worker to speak for an entire neighborhood, language group, identity, or lived experience.
Feedback must have an operating destination. Create a route for community members to report that information was unclear, a connection failed, a channel was inaccessible, or the process felt unsafe. State response time, ownership, language access, confidentiality, and escalation. Aggregate themes when counts are small. Do not expose identifiable stories in leadership reports or public recognition materials. The purpose is to improve the pathway, not to convert lived experience into promotional content.
Receiving-service ownership makes navigation real
Navigation often fails at the receiver boundary. The community health worker may prepare a connection correctly, but the receiving team may have no capacity, reject the referral without a usable explanation, be unable to reach the person, or close the case without returning the outcome. The pilot should therefore include a service-level agreement that is realistic for the selected pathway. It should state what constitutes acceptance, how incomplete information is resolved, what happens when capacity is unavailable, who attempts follow-up, and how the community member learns the next step.
The agreement should distinguish operational and clinical escalation. An inability to schedule an appointment may need an operational owner; a concerning symptom or change in condition may require a clinically approved pathway. Community health workers need training to recognize the boundary and immediate access to the appropriate supervisor. They should never be expected to make clinical judgments outside their approved role or to hold risk while waiting for an unresponsive system.
Data should reduce uncertainty without expanding surveillance
Collect only the information necessary to operate and evaluate the pathway. Define purpose, lawful basis, consent, access, retention, correction, sharing, and deletion. Explain the data practice in plain language. Do not require community health workers to collect sensitive social information simply because a field exists. A measure is not justified merely because it could be interesting. Each item should connect to a care, access, equity, safety, workforce, or evaluation decision.
Technology must work in the environments where community health workers and community members use it. Test language, reading level, disability access, connectivity, device constraints, offline operation, login burden, duplicate documentation, and downtime recovery. The 2026 usability-validation study is particularly relevant because it treated contextual adaptation and worker participation as part of measurement quality.3 A locally validated tool still does not prove outcome improvement, but it is a better foundation than assuming that software acceptance can be inferred from deployment.
Executive response closes the governance loop
Some barriers require decisions above the pilot team. Eligibility rules may need clarification. Appointment capacity may be structurally inadequate. Payer policy may not support the work. A vendor may control an inaccessible interface. Travel and mileage policies may create unpaid burden. Clinical departments may disagree about ownership. The sponsor should maintain an executive constraint log that records the issue, immediate risk control, decision owner, due date, and outcome. Unresolved constraints should be visible at the 30-, 60-, and 90-day reviews.
The sponsor must also protect the pilot from success theater. If baseline data are missing, say so. If the result is mixed, explain what changed and what did not. If demand exceeds capacity, do not pressure workers to close cases faster. If a subgroup experiences worse access, pause expansion and investigate. A reliable operating system is one that can surface an unfavorable signal and respond without blaming the workforce or hiding the result.
Workforce conditions are intervention conditions
Support the people whose relationships make the pathway possible
Community health worker performance cannot be separated from employment and program conditions. Role ambiguity, delayed payment, uncovered leave, high travel burden, fragmented supervision, unsafe caseloads, unreliable technology, and disrespectful team relationships can undermine an otherwise thoughtful model. Conversely, role clarity, dependable compensation, participatory supervision, reasonable workload, usable tools, team acceptance, and development can make it easier for workers to use their skills without sacrificing wellbeing.
Qualitative tool: This fishbone is an unranked hypothesis set, not a frequency chart. Validate causes with local community health workers, community members, and receiving teams before choosing countermeasures.
Make scope concrete at the level of recurring work
A broad job description does not answer the questions that arise during a real connection. For each common pathway, define what the community health worker may explain, collect, document, schedule, deliver, observe, or escalate. Name what requires a licensed professional or another role. Include privacy, consent, language access, mandatory reporting, urgent concerns, and conditions in which the worker should stop the interaction and contact a supervisor. Review the design with people who actually perform and receive the work. A primary-care synthesis identified recurring community health worker roles while also showing variation across programs, a useful reminder to define the local model rather than import a generic role list.13
Onboarding should use realistic cases rather than only policy slides. Workers and supervisors should practice incomplete information, changed eligibility, similar names, a person who withdraws consent, inability to reach the receiving team, a safety concern, a request outside scope, and a digital outage. Debrief where the system made the correct action difficult. Training success is not merely completing a module; it is demonstrating that the worker and surrounding team can operate the approved pathway and recover safely.
Use supervision to support judgment and learning
Supervision should be regular, accessible, and appropriate to the work. A supervisor needs enough understanding of the community health worker role to help with priorities, boundaries, ethical tensions, workload, and team interfaces. Clinical questions need a qualified clinical route. Operational questions need an owner who can change process. Reflective discussion may help workers process difficult interactions, but it should not become a substitute for behavioral health support, safety response, or correcting harmful working conditions.
Review caseload as a demand-and-capacity problem. Counts alone are misleading because cases differ in travel, language, complexity, outreach attempts, coordination, documentation, and emotional load. A reasonable review uses time samples, pathway complexity, geographic conditions, paid hours, planned leave, training, team duties, and worker feedback. It also examines work the organization has made invisible, including preparation, unsuccessful contacts, transportation, community events, relationship maintenance, and after-hours follow-up.
Compensation and development should match the value and requirements of the role
The compensation review should include wages, payment reliability, benefits, travel, mileage, devices, connectivity, training time, supervision time, community events, translation or interpretation expectations, documentation, and required credentials. The 2025 compensation review found no one-size-fits-all model and emphasized context and community health worker participation.10 Local leaders must also consider labor law, payer policy, grant restrictions, collective bargaining, equity, and total compensation. Awareness week should not announce a payment solution before these constraints are understood, but it can make a transparent review commitment.
Development should be equally concrete. Ask workers about mentoring, continuing education, cross-training, leadership opportunities, research participation, data skills, digital confidence, and career interests. State which opportunities are paid, how selection occurs, and how access will be equitable across locations and schedules. Do not imply that additional training automatically leads to promotion when no pathway exists. If advancement criteria are unclear or inconsistent, make that a leadership action item.
Psychological safety is essential because community health workers often see both community distress and system failure. Workers need a protected way to say that a task is outside scope, a case is unsafe, workload is unmanageable, or a partner is unresponsive. Leaders should review whether speaking up leads to timely help and learning. A nominal reporting channel is not enough if workers expect retaliation, loss of hours, damaged relationships, or no response. The pilot charter should name who receives concerns, the immediate support available, how confidentiality is protected, and when the sponsor reviews recurring issues.
A scorecard for access, trust, and workforce protection
Measure whether the pathway worked without rewarding unsafe shortcuts
Campaign activity is not the primary outcome. The number of social posts, events, training completions, or referrals sent may describe effort, but it does not show whether people obtained usable support or whether community health workers were protected. The executive scorecard should combine pathway reliability, experience, equity, workforce conditions, safety, and resource use. Every measure needs a written numerator, denominator, exclusions, time window, data source, owner, review cadence, and action rule. A primary-care performance framework likewise emphasizes the interaction between worker, community, program, and health-system conditions rather than treating performance as an individual trait.12
| Domain | Example measure | Denominator or source | Stratify or balance with | Decision use |
|---|---|---|---|---|
| Choice and consent | Eligible participants who understood options, data use, and the next step | Participants offered the selected pathway | Language, disability access, channel, site | Revise explanation, consent, or access method |
| Prepared connection | Connections meeting the locally defined minimum-information rule | Connections sent during the period | Sender, pathway type, missing-field reason | Improve intake without adding unnecessary data |
| Receiver acceptance | Eligible connections accepted or redirected to an accountable alternative | Connections requiring receiver action | Service, urgency, capacity reason | Clarify ownership or address capacity constraints |
| Loop closure | People who received the intended service or a documented recovery plan | Accepted connections due for follow-up | Language, geography, payer, access need | Adapt follow-up and recovery design |
| Experience and trust | Participants who knew the next step and felt treated with respect | Voluntary accessible feedback sample | Channel, language, disability, subgroup size | Co-design communication and protect privacy |
| Workforce | Community health workers report clear scope, usable tools, supervision, and manageable workload | Anonymous or protected workforce pulse | Site, schedule, tenure, employment arrangement | Pause growth or resource the model |
| Safety and recovery | Defined high-risk exceptions receiving timely approved response and learning review | Exceptions meeting the local case definition | Cause group, pathway stage, recurrence | Strengthen controls and escalation |
| Resources | Paid worker time and program resources used per completed pathway, with uncertainty | Locally defined cost perspective and period | Travel, training, technology, supervision | Inform affordability and sustainability |
No universal target is implied. Establish a local baseline and choose thresholds with community health workers, community members, clinical and operational owners, and data-governance leaders.
Use a denominator that reflects opportunity
Counts can mislead. An increase in referrals sent may reflect greater need, easier documentation, or pressure to produce volume. A decrease may reflect improved prevention, reduced outreach, lost capacity, or exclusion. Define the eligible population and the pathway stage for every rate. Track the number of people offered the pathway, those who chose it, connections sent, connections accepted, services completed, recovery plans activated, and people unreachable under the approved rule. Report exclusions and missing data.
Do not convert a response-time measure into a universal clock. Urgent and routine needs differ. Travel, accessibility, service capacity, and participant preference matter. Define time rules for the selected pathway with clinical and operational owners. Measure the reasons for delay and identify which owner can act. If the receiver lacks capacity, do not label the community health worker as slow. If speed improves while informed choice, respect, or safety worsens, the design is not successful.
Pair reliability with experience and equity
A completed appointment does not fully describe access. The person may not have understood why the service mattered, may have faced disrespect, may have repeated sensitive information, or may be unable to follow the next plan. Use a small number of voluntary, accessible questions co-designed with community members. Ask whether the person understood the next step, had a usable contact route, experienced communication in the preferred language and format, and knew what to do when the plan changed.
Stratification can reveal inequity but can also create privacy risk. Choose lawful, community-informed dimensions that connect to a decision, such as language, geography, disability access, digital channel, age group, or payer. Suppress or combine small cells under an approved rule. Do not collect identities merely to fill a dashboard. If a subgroup shows worse acceptance, closure, experience, or burden, review the pathway with affected community members before expansion.
Protect the workforce with balancing measures
A new access pathway may improve visible outcomes by transferring work to the community health worker. Balance closure measures with paid time, workload, repeated outreach attempts, travel, after-hours activity, duplicate entry, technology downtime, supervision availability, and psychological safety. Review whether clinical or administrative teams are redirecting work without resources. Ask whether workers can take leave and breaks without abandoning a community relationship. A high closure rate built on unpaid overtime is a warning, not a success.
Training measures also need balance. The recent education studies reported improved knowledge or service use in defined settings.47 Locally, leaders should measure whether training is relevant, paid, accessible, retained, and supported by the surrounding system. Pair a knowledge check with observed simulation, worker confidence, error recovery, and downstream service data. Do not attribute a failure to worker competence when the receiver, policy, capacity, or technology made the correct action impossible.
Use economic measures carefully
Program cost should include more than wages. State whether the perspective includes employer, payer, partner, community, or participant costs. Include supervision, training, travel, mileage, devices, connectivity, data systems, translation, accessibility, evaluation, administration, and volunteer or partner contributions when relevant. Report the period and separate start-up from recurring resources. If estimating return on investment, specify the comparator, attribution assumptions, time horizon, uncertainty, and who realizes the savings.
The 2025 economic scoping review identified substantial variation in cost and reporting across programs.9 An earlier systematic review also found that CHW interventions and economic evidence were heterogeneous.15 One evidence-based U.S. program reported a positive return on investment under its defined model and analytic assumptions.11 These findings support disciplined local evaluation. They do not justify a generic claim that every program saves money. Sustainability may still be warranted because of access, equity, community capacity, or quality goals, but the value proposition should be explicit and honest.
A decision-ready 90-day test
Move from observance week to an accountable implementation cycle
The 90-day plan should be small enough to govern and meaningful enough to test a real access problem. A single pathway, one defined population, and one receiving service are often sufficient. The team is not trying to prove that community health workers are valuable; the literature and lived experience already show important contributions across many settings. The local question is narrower: can this organization operate the selected pathway reliably, equitably, safely, and sustainably under stated conditions?
Illustrative sequence: Adjust the timeline to risk, approvals, data readiness, workforce capacity, partner agreements, and community preference. Do not start service delivery before required governance and training are in place.
Days 0-15: authorize, protect, and establish the baseline
Confirm the pathway, population, goals, exclusions, and decision rights. Obtain required legal, privacy, compliance, clinical, labor, accessibility, and partner approvals. Establish community participation and compensation. Document the current state, workforce time, receiver capacity, existing outcomes, data limitations, and known safety concerns. Define every measure before looking for improvement. Create the constraint log and name the stop conditions.
Examples of stop conditions include an uncontained safety risk, activity outside approved scope, a privacy breach, inaccessible consent, unavailable clinical escalation, unpaid or excessive worker burden, discriminatory effect, partner nonperformance, or data quality too poor to support safe operation. A stop does not mean failure. It means the governance system worked before harm or false confidence expanded.
Days 16-30: build, simulate, train, and start small
Finalize the future-state pathway and receiving-service agreement. Configure the smallest necessary data workflow. Test language and accessibility. Train community health workers, supervisors, and receiving staff together so each role understands the whole loop. Simulate routine and exception cases, correct gaps, and confirm backup coverage. Begin with a small volume or limited geography that allows close support. Hold brief daily or twice-weekly huddles during the first operating period.
At day 30, review process fidelity, worker experience, unresolved constraints, safety signals, early equity patterns, and data quality. Do not demand outcome certainty from a small early sample. Decide whether the pathway is safe enough to continue, which adaptations are necessary, and whether additional resources or approvals are required. Document the reason for every change so the final review can distinguish the intended model from the model actually delivered.
Days 31-60: operate, recover failures, and learn with the community
Continue the pilot at the authorized scope. Review unaccepted connections, incomplete intake, missed contacts, inaccessible communication, service delays, and worker burden. Use case-based learning without public blame. Return to community members and community health workers with what the team heard, what changed, and what remains unresolved. Update training, forms, scripts, routing, coverage, or receiver agreements only through the approved change process.
At day 60, examine whether the pilot is producing the intended pathway rather than simply generating more activity. Review closure and recovery, participant understanding, workforce conditions, safety, resource use, and stratified outcomes. If a receiving-service constraint is dominant, escalate it to the sponsor. If community trust is being placed at risk by unkept promises or weak follow-up, reduce or pause enrollment until the system can respond.
Days 61-90: assess sustainability and make an explicit decision
During the final phase, stabilize only the components supported by evidence and experience. Estimate recurring resources, supervision, workforce capacity, technology, partner commitments, and funding. Review whether the pilot can survive leave, turnover, downtime, and fluctuations in demand. Confirm that the operating model does not depend on one community health worker's relationships or unpaid effort. Prepare the result in plain language for workers, community partners, leadership, and receiving teams.
The day-90 decision is scale, adapt, pause, or stop. Scale only when safety controls, workforce support, receiver capacity, community acceptability, data quality, and resources are credible. Adapt when the underlying pathway is promising but a defined element needs another bounded test. Pause when a remediable dependency is not ready. Stop when the pathway is unsafe, inequitable, unsupported, ungovernable, or not producing sufficient value relative to burden. Record who made the decision, the evidence used, uncertainty, dissent, and the next review date.
The executive commitment to publish internally after the week
We recognize community health workers by improving the conditions around their work. For the selected pathway, we will name what the community defined as important, what community health workers contributed, what the receiving system must own, what resources are authorized, how consent and privacy are protected, how workforce concerns reach leadership, what measures will be reviewed, and when the scale, adapt, pause, or stop decision will occur.
The commitment should include named owners and dates. It should not promise a result before the test begins. At day 90, publish an accessible internal summary of what was attempted, who participated, what changed, what did not, what unintended effects appeared, what constraints remain, and what decision was made. Community health workers and community partners should review the summary before it is used publicly.
National Community Health Worker Awareness Week becomes more than recognition when the organization uses visibility to strengthen governance, workforce conditions, and the reliability of access. The aim is not to convert relationship-based work into a mechanical queue. It is to ensure that trust is met by a responsive system: one that listens, accepts ownership, protects the workforce, measures what matters, learns from failure, and tells the truth about what it can and cannot deliver.
Peer-reviewed references
References, newest first
The evidence set was assembled through an institutional health-research library using full-text and peer-reviewed controls, then checked record by record for design, population, results, limitations, citation details, and DOI. The citations are presented newest first. Public DOI links are provided for reader verification.
- McElfish PA, et al. Integrating community health workers into clinical settings. Health Expectations. 2026;29(1). https://doi.org/10.1111/hex.70604
- Han H-R, et al. Efficacy of a language-concordant community health worker intervention to improve community-to-clinic linkage for dementia care: results of randomized trial PLAN. Alzheimer's & Dementia. 2026;22(6). https://doi.org/10.1002/alz.71541
- Nkurunziza J, et al. Adapting and validating tools to assess the usability and acceptability of mHealth tools among community health workers in rural settings. JMIR mHealth and uHealth. 2026;14:e64916. https://doi.org/10.2196/64916
- Bhakta SD, et al. Skin cancer recognition and education among community health workers in Southern New Mexico. International Journal of Environmental Research and Public Health. 2026;23(8):994. https://doi.org/10.3390/ijerph23080994
- Crawford K, et al. Evaluating the impact of a community health worker training program. Journal of Health, Population and Nutrition. 2025;44:256. https://doi.org/10.1186/s41043-025-01011-0
- Choudhury N, et al. “Now that they come to our doorsteps to teach us these things…”—postpartum contraception outcomes from a pre-post effectiveness-implementation study of an integrated community health worker intervention in rural Nepal. Reproductive Health. 2025;22:258. https://doi.org/10.1186/s12978-025-02225-5
- Lee S, Kasibante S, Eminai A, et al. Effectiveness of a community health worker-led education intervention on knowledge, attitude, and antenatal care attendance among pregnant women in Eastern Uganda. Journal of Health, Population and Nutrition. 2025;44:232. https://doi.org/10.1186/s41043-025-00876-5
- Asamani JA, Okoroafor SC, Mwinga K. Community health worker requirements to accelerate progress towards universal health coverage in Africa: an overview of contemporary estimates and implications of full-time versus part-time working arrangements. INQUIRY. 2025;62:00469580251323381. https://doi.org/10.1177/00469580251323381
- O'Donovan J, Baskin C, Stansert Katzen L, et al. Costs and cost-effectiveness of community health worker programs focussed on HIV, TB and malaria infectious diseases in low- and middle-income countries (2015-2024): a scoping literature review. PLOS Global Public Health. 2025;5(5):e0004596. https://doi.org/10.1371/journal.pgph.0004596
- Samb OM, Niang M, Gelinas E, Diouf NT, Agbadje TT, El Haouly A. Financial motivation models for community health workers in low- and middle-income countries: a scoping review. Global Health Action. 2025;18(1):2480412. https://doi.org/10.1080/16549716.2025.2480412
- Kangovi S, Mitra N, Grande D, Long JA, Asch DA. Evidence-based community health worker program addresses unmet social needs and generates positive return on investment. Health Affairs. 2020;39(2):207-213. https://doi.org/10.1377/hlthaff.2019.00981
- Agarwal S, Sripad P, Johnson C, et al. A conceptual framework for measuring community health workforce performance within primary health care systems. Human Resources for Health. 2019;17:86. https://doi.org/10.1186/s12960-019-0422-0
- Hartzler AL, Tuzzio L, Hsu C, Wagner EH. Roles and functions of community health workers in primary care. Annals of Family Medicine. 2018;16(3):240-245. https://doi.org/10.1370/afm.2208
- Kim K, Choi JS, Choi E, et al. Effects of community-based health worker interventions to improve chronic disease management and care among vulnerable populations: a systematic review. American Journal of Public Health. 2016;106(4):e3-e28. https://doi.org/10.2105/AJPH.2015.302987
- Viswanathan M, Kraschnewski JL, Nishikawa B, et al. Outcomes and costs of community health worker interventions: a systematic review. Medical Care. 2010;48(9):792-808. https://doi.org/10.1097/MLR.0b013e3181e35b51