Jump to a section
What question should a CHW encounter note answer?
An authorized reader should understand what happened, why it mattered to the participant, and what needs to happen next.
CDC's CHW resource overview describes a role connecting communities with health and social services. An encounter record should make the work understandable without turning every interaction into an unsupported clinical assessment.[1]
Write to support continuity. A colleague covering an absence needs to know the agreed action and its owner. A supervisor needs enough detail to discuss quality and scope. A reporting lead needs reliable categories and dates. These needs overlap, but collecting every possible detail can make a record harder to use and expose unnecessary personal information.
This template is a general documentation aid. It is not a state-approved form, a billing code selector, or a determination that an encounter is reimbursable. Your program should decide which fields are required, optional, or inappropriate before using it with real records.
Which fields should your encounter template include?
Start with the encounter context, participant priority, activity, response, and follow-up, then add the fields your program requires.
| Field | What to capture | Quality check |
|---|---|---|
| Record reference | Approved participant identifier and program | The note belongs to the correct record. |
| Encounter context | Date, worker, setting, contact method, and relevant times | Planned appointments and completed contacts are distinguishable. |
| Purpose | The participant's priority and reason for this contact | The purpose describes this encounter, not a copied general goal. |
| Action | Education, navigation, or support actually provided | The reader can tell what the worker did. |
| Response | What the participant said, demonstrated, chose, or declined | Reported information is separated from observation. |
| Next step | Action, owner, timing, and unresolved barrier | A covering worker can continue the plan. |
| Review | Author, completion status, and required review | The record follows the organization's approved process. |
Where a payer or contract requires additional details, keep the requirement connected to its source. A universal field named "compliant" is not a substitute for the actual information being requested. Avoid forcing staff to choose an inaccurate service label simply because the correct activity is missing from a menu.
How do you document a participant changing their priority?
Record the change, the participant’s choice, and what happens to the earlier plan.
Fictional navigation example: The planned conversation concerned a community appointment. At the start, the participant asked instead for help finding the correct contact for a utility-assistance program. The worker clarified the new priority and reviewed the public intake information within the program’s scope. The participant chose to make the call independently. The earlier appointment task remained open, with the participant requesting that it be revisited at the next agreed contact.
This note explains why the work differed from the plan without labeling the participant resistant or implying that the earlier goal was completed. If the new request falls outside the worker’s role, document the request and the appropriate handoff rather than recording an intervention that was not provided.
Use the full practice record below for the encounter fields and follow-up structure. This example illustrates a change in priorities; it does not establish eligibility for reimbursement.
How should you document an education encounter?
Identify the education actually delivered, the material used, and the participant's demonstrated understanding or questions within your role.
Fictional example: Using a program-approved appointment-preparation worksheet, the worker helped the participant list questions for a forthcoming visit. The participant identified two questions and explained where they had written them. The participant asked a medication question; the worker directed that question to the appropriate clinical contact under the program's process. The agreed follow-up was to discuss whether the participant was able to use the question list.
The note should describe the response that occurred. Do not replace a brief explanation with "understands everything," or infer an improvement in health from completing a worksheet. If an education plan or curriculum is required for your service, record its identity using your approved system. Confirm state-specific documentation and billing rules separately.
Use participant language respectfully and selectively. A short relevant statement can clarify the person's priority. A lengthy personal history that is unrelated to the encounter usually does not improve continuity. Discuss sensitive or ambiguous documentation questions with the authorized supervisor.
How do you record missed contacts and unfinished referrals?
Record the attempt or referral as the event that occurred, and keep it separate from a completed encounter or confirmed service outcome.
For a missed contact, document the date, permitted contact method, result, and next planned action under your outreach procedure. Avoid labels such as "unmotivated" when the evidence is only that the person did not answer. There may be a changed phone number, access barrier, or preference that the team does not yet know.
For a referral, distinguish sending information, partner acknowledgment, scheduling, attendance, and confirmation that the requested service was received. Decide which of those milestones your team can actually verify. If the outcome remains unknown, preserve that state rather than counting it as either success or failure.
If multiple workers contribute, make ownership explicit. "Team will follow up" leaves each person free to assume someone else is responsible. Record the responsible role or assigned worker, the timing, and the authorized route for sharing information.
How should supervisors review notes and corrections?
Review accuracy, usefulness, role boundaries, and required fields, using the approved correction process rather than silently rewriting history.
Smores Health's documentation workflows include structured notes and review. Bring your blank note and a fictional correction scenario to test the required fields and review steps for your organization. Do not assume the downloadable worksheet is already installed as a CHW-specific product template.[2]
The correction example below shows the difference between correcting an encounter fact and recording a later development. The supervisor feedback section gives a practical way to request the missing information.
Which vague phrases should you replace in a CHW note?
Replace conclusions with observable actions, attributed reports, and a specific next step.
| Vague wording | More precise wording | Why it helps |
|---|---|---|
| Provided resources | Reviewed the published intake steps for the selected resource | Identifies the action |
| Participant doing well | Participant reported completing the agreed call | Attributes the information |
| Referral successful | Receiving service confirmed receipt; appointment not yet arranged | Separates receipt from service delivery |
| Noncompliant | Participant declined this option and requested another approach | Describes a choice without a character judgment |
| Team will follow up | Assigned worker will check the result at the agreed next contact | Makes responsibility visible |
Use these alternatives only when they accurately describe the encounter. A specific sentence is not inherently truthful, and a longer sentence is not inherently better. Do not copy a result from this table into a record when the result is unknown.
What should a covering worker be able to learn from the note?
They should be able to identify the current priority, unfinished work, and the next permitted action without reconstructing the entire history.
Give a reviewer a fictional record without explaining it aloud. Ask them to answer four questions: what did the participant want, what happened, what remains open, and what should I do next? If the reviewer must ask the original worker to reconstruct the encounter, identify the missing fact rather than adding more background indiscriminately.
Check copied-forward information against the current encounter. An old assignment or contact preference can make a detailed note misleading. Preserve historical facts as history, and record changes where the next authorized worker will find them. Keep internal staff performance feedback outside the participant narrative.
How do you test a CHW documentation template before rollout?
Use several fictional encounter types and ask both workers and reviewers to complete their normal tasks.
Test a successful contact, an unanswered attempt, an unfinished referral, a participant who changes their priority, and a record needing correction. Time the exercise and ask which fields are confusing or duplicated. The goal is to learn whether the template captures the necessary facts with a reasonable burden. Do not remove a verified requirement merely because it takes time; look for a clearer placement or workflow.
Ask a reviewer who did not observe the exercise to explain what happened and what should happen next. If they cannot, identify the missing information. If the form collects details nobody uses and no requirement supports, ask whether those fields should remain. Keep a version record and explain changes before staff adopt the new template. A well-designed form should make accurate documentation easier, while leaving room for the worker's judgment and the participant's own priorities.
What does a complete fictional CHW practice note include?
Connect the encounter details, participant priority, worker action, response, and follow-up in one readable record.
The following practice record shows how the pieces fit together for a general navigation encounter. It is fictional and contains no real participant information. It is complete for this teaching scenario, not a statement that every state, employer, or payer would accept these fields. Use your approved template and additional requirements for real services. The time shown describes the encounter and does not establish billable units.
Participant: Training Participant A. Worker: Training Worker A. Encounter: October 1, 2026, 10:00 to 10:25 a.m., local time. Format: telephone. Priority: participant wants to understand how to contact a community transportation program before a future appointment. Relevant context: participant reports having the program's telephone number but being unsure which option to choose. Contact and information-sharing steps follow the fictional organization's approved process.
Action: worker reviewed the program's public telephone menu with the participant and helped them identify the transportation intake option. Participant made the call and asked about availability. The receiving service requested a return call later that day; no ride was confirmed during this encounter. Worker and participant discussed the next contact step. This records what the worker did without implying the worker arranged a service that remains unconfirmed.
Response and next step: participant stated they understood which intake option to select and planned to call again that afternoon. Participant requested a follow-up the next morning. Training Worker A owns that follow-up and will ask whether contact occurred and whether further navigation support is wanted. Referral status: awaiting participant follow-up. Documentation status: practice draft awaiting the fictional review process. Author identification and finalization would use the organization's actual approved workflow.
A reviewer can now locate the encounter, understand the activity, and see the unresolved result. The note does not label the referral successful, infer a clinical outcome, or claim a payment category. It also avoids a long background narrative unrelated to the task. If the participant later confirms a ride, record that new information with its source and date rather than changing this earlier account to imply it was known during the encounter.
How should an unsuccessful contact attempt differ from an encounter note?
Record the attempt and the next action without inventing a conversation or participant response.
A fictional attempt record might say: October 2, 2026, 9:00 a.m. Training Worker A called through the approved contact route at the previously agreed time. No answer. No conversation occurred. Next action: review the agreed contact plan and make the next appropriate attempt under program procedure. If a message was actually left, record that fact as appropriate; do not automatically add a voicemail statement because it appears in a template.
The difference matters for continuity and reporting. A completed conversation can contain a participant response. An unanswered attempt cannot establish what the participant understood, wanted, or achieved. Keep any proposed next step distinguishable from a step the participant actually agreed to. The appropriate number and timing of further attempts depend on the program's procedures and the person's preferences, not a universal rule supplied by this article.
If repeated contact fails, ask whether the contact information or method needs review through the approved process. Do not classify the person as unwilling to participate solely because a call was unanswered. A useful record lets the next authorized worker see what was tried without repeating the same ineffective action indefinitely.
What should a correction preserve in a CHW record?
Preserve the original account and make the corrected fact, reason, author, and correction timing understandable through your approved process.
Consider a fictional note that lists an encounter as occurring at 10:00 a.m. The worker later checks an authorized contemporaneous record and discovers the actual start was 10:15 a.m. The correction should identify the specific fact and the basis for changing it. It should not imply that the correction was made at the time of service if it was entered later. The actual amendment mechanism depends on your record system and policy.
Do not use a correction to add an outcome that occurred after the encounter. If the participant later reports receiving a resource, that is new follow-up information. Distinguishing a factual correction from a later development helps readers reconstruct the sequence. If a change affects reporting or a submitted claim, route it to the responsible team rather than assuming that editing the note automatically corrects every downstream record.
Before approving a template, rehearse corrections with a draft and a finalized test record. Ask who can amend each, whether the original is preserved, and how another authorized reviewer finds the history. These are evaluation questions, not claims that a particular product supports every mechanism described here.
How can supervisors give specific, useful documentation feedback?
Name the missing fact and the reason it matters, then distinguish a record correction from a learning opportunity.
Useful feedback might be: The note says the referral was completed, but the described action only shows it was sent. Please clarify the actual status using the available evidence and identify the follow-up owner. This gives the worker a factual question to resolve. A comment such as make this more professional does not explain what is wrong or how to improve it.
Use a brief supervisor checklist: can I identify what happened, distinguish reports from observations, find the participant's response, locate the next action, and confirm required fields? If the answer is no, identify the specific gap. Review recurring patterns with the documentation lead. Several workers making the same mistake may point to an unclear field label or definition rather than several independent performance problems.
Keep the feedback proportionate. A clear short note can be more useful than a long one filled with copied text. The objective is a truthful, usable record that supports the next step, with the program's requirements satisfied.
How can the note support useful program reporting?
Use consistent categories and dates for counting, while preserving narrative detail that explains the individual encounter.
Agree on a short data dictionary: what counts as an attempt, completed encounter, education activity, and verified referral result. Decide whether one encounter can include multiple activities and how totals should be interpreted. Counting each activity as another encounter can inflate service volume.
Frequently asked questions
Is this a Medicaid-approved CHW note template?
No. It is an original planning template. Verify the specific state, payer, service, and organization requirements before using it as an operational record.
Should every contact be recorded as a completed service?
Record what occurred. An unsuccessful attempt, a planned appointment, and a completed encounter are different events and should remain distinguishable.
Can the same template work across programs?
The basic structure can be reused, but required fields, access, signatures, review, and service definitions need program-specific decisions. Avoid assuming one program's requirements apply everywhere.
Does a detailed note prove a service is payable?
No. Documentation and reimbursement decisions are separate. Coverage, provider eligibility, service conditions, and payer instructions also need verification.
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.
- 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.
- Smores Health: Document: Smores Health. Product overview. Confirm your program configuration, included services, and rollout scope in a walkthrough and written agreement.
- Smores Health: Operate: Smores Health. Product overview. Confirm your program configuration, included services, and rollout scope in a walkthrough and written agreement.