Community Health Worker Encounter Documentation
Document patient encounters, social needs, referrals, and follow-up actions in one CHW encounter form. Use it to keep continuity of care clear, capture consent, and support reporting without over-collecting PII.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Community Health · Primary Care · Behavioral Health · Public Health · Nonprofit Care Coordination
Overview
Community Health Worker Encounter Documentation is a structured workplace form for recording what happened during a CHW interaction, why the encounter occurred, what social needs were identified, which interventions or referrals were offered, and what follow-up is needed next.
Use this template when your team needs a consistent record for outreach visits, phone check-ins, community navigation, or referral support. The form is designed to capture the essentials without turning every encounter into a long narrative: date and time, encounter type, patient identifier, consent to document, presenting concerns, urgent safety concerns, needs identified, referrals made, and next steps. That structure makes it easier to hand off work, review unresolved needs, and support reporting across programs.
Do not use this form as a catch-all intake packet or as a substitute for clinical documentation that belongs in the medical record. If the encounter does not involve patient services, social needs screening, or referral follow-up, a lighter contact log may be enough. Keep the fields focused on what the CHW actually observed or completed, and avoid collecting unnecessary PII. The best version of this template uses clear required versus optional fields, conditional logic for only the relevant needs, and a plain-language note about what happens after submission.
Standards & compliance context
- Use data minimization consistent with GDPR Article 5 by collecting only the patient information needed for the encounter record and follow-up.
- If the form is used in a health-related workflow, apply the minimum-necessary principle and avoid collecting sensitive details that are not needed for care coordination.
- Include consent-to-document language when recording patient information, especially if the encounter includes social needs or referral details.
- If the form is public-facing or patient-completed, make it accessible under WCAG 2.1 AA with clear labels, logical tab order, and readable validation messages.
- If the form is used for HR-style intake or accommodation support, include a clear prompt for reasonable accommodation needs and route those responses appropriately.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Encounter Details
This section anchors the record with when, where, and how the encounter happened, plus the minimum identifier needed to match the patient correctly.
-
Encounter Date
Date the encounter occurred.
-
Encounter Time
Optional time of the encounter.
-
Encounter Type
Select the primary mode of contact.
-
Encounter Location
Where the encounter took place, if relevant.
-
Patient Identifier
Enter the local patient ID or other internal identifier. Avoid collecting SSN or other unnecessary PII.
-
Consent to Document Encounter
Confirm that the patient was informed about documentation and any applicable sharing for care coordination and reporting.
Reason for Encounter
This section explains why the interaction occurred and whether any urgent safety issue needs immediate attention.
-
Primary Reason for Encounter
Choose the main reason for the encounter.
-
Referral Source
How the patient was connected to CHW services.
-
Presenting Concerns
Briefly summarize the issues discussed. Include only information needed for follow-up.
-
Any urgent safety concern identified?
Indicate whether an immediate safety issue was identified.
-
Urgent Safety Concern Details
Describe the concern and any immediate escalation or handoff completed.
Social Needs Screening
This section captures the needs identified during the encounter so the team can route support and track patterns over time.
-
Social Needs Identified
Select all needs discussed or identified during the encounter.
-
Food Insecurity Details
Document relevant details, barriers, and household context as needed.
-
Housing Instability Details
Document housing-related barriers or risks using minimum necessary detail.
-
Transportation Barriers Details
Describe transportation barriers affecting access to care or services.
-
Other Needs Details
Describe any additional social needs not listed above.
Interventions and Referrals
This section shows what the CHW actually did, which referrals were offered, and whether the patient agreed to them.
-
Interventions Provided
Select all actions completed during the encounter.
-
Referrals Made
Add one row for each referral or resource connection.
- Referral Type Options
-
Patient Accepted Referral or Resource?
Indicate whether the patient accepted the referral or resource.
-
Barriers to Follow-Through
Document barriers that may affect completion of the referral or next steps.
Follow-up and Next Steps
This section turns the encounter into an action plan by documenting the next contact, escalation status, and assigned follow-up.
-
Follow-up Needed?
Indicate whether additional follow-up is needed.
-
Planned Follow-up Date
When the next contact should occur.
-
Next Steps
Summarize the plan, responsibilities, and any handoff completed.
-
Escalation or Handoff Completed?
Indicate whether the issue was escalated to a supervisor, clinician, or partner organization.
-
Escalation Details
Document who was contacted and what information was shared using minimum necessary detail.
CHW Notes and Certification
This section preserves any final context and confirms who completed the documentation and attested to its accuracy.
-
Additional Notes
Include any other relevant details not captured above.
-
CHW Name
Name of the community health worker completing the form.
-
CHW Signature
Signature confirming the encounter documentation is accurate.
-
Attestation
I certify that this documentation is accurate and completed in accordance with organizational policy and applicable privacy requirements.
How to use this template
- Set up the encounter details section first by choosing the date, time, encounter type, location, and a patient identifier that matches your program’s privacy rules.
- Record the reason for the encounter and the referral source, then use the presenting concerns and urgent safety fields to capture only what is needed for follow-up or escalation.
- Complete the social needs screening by selecting the relevant needs and opening the matching detail fields only when a need is identified.
- Document the interventions provided, the referral type, whether the patient accepted the referral, and any barriers that may affect follow-through.
- Add follow-up needs, a follow-up date if one is planned, and any escalation details so the next person knows exactly what action is pending.
- Finish with CHW notes, your name, signature, and submission attestation, then route the form to the assigned reviewer or care team workflow.
Best practices
- Use conditional logic so food, housing, transportation, and other needs only appear when the screening indicates they apply.
- Mark required fields sparingly and keep optional fields available for context that is helpful but not essential.
- Use a date picker for encounter and follow-up dates, a time field for encounter time, and multi-select fields for referral types and needs identified.
- Document urgent safety concerns in a dedicated field and escalate them immediately instead of burying them in free-text notes.
- Record whether the patient accepted each referral, because a referral that was offered is not the same as a referral that was taken up.
- Keep patient identifiers minimal and avoid collecting extra PII unless the information is needed for care coordination or reporting.
- Write follow-up next steps as concrete actions with an owner and timing, not as vague reminders.
- Review the form for accessibility and plain language so staff can complete it consistently and patients are not asked to repeat the same information.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template is for documenting a community health worker encounter from start to finish: the reason for the visit, social needs identified, referrals made, and the next follow-up step. It helps keep the record consistent across outreach, clinic, and care coordination workflows. It is especially useful when multiple people may need to understand what happened after the encounter.
Who should complete this form?
A community health worker, outreach specialist, or other designated care coordination staff member should complete it after the encounter. In some workflows, a supervisor may review the submission for escalation or quality checks. The person completing it should be able to confirm what was observed, what was discussed, and what actions were taken.
How often should this form be used?
Use it for each documented encounter, whether the interaction happens in person, by phone, or in the community. If your program has multiple touchpoints with the same patient, complete a new entry for each encounter so the timeline stays clear. That makes it easier to track changes in needs, referrals, and follow-up status over time.
What patient information should be collected?
Collect only the minimum necessary information needed to identify the patient and support the encounter record. Use a patient identifier that fits your workflow instead of asking for unnecessary sensitive data, and include consent to document when required. If your program does not need a specific field, leave it out rather than adding extra PII.
Does this form need consent or privacy language?
Yes, if you are recording patient information or social needs, the form should include a clear consent-to-document field and a brief explanation of how the information will be used. That supports data minimization and helps the patient understand what happens after submission. If your workflow allows anonymous or de-identified reporting, note that in the setup and use it where appropriate.
What are the most common mistakes when using this template?
Common mistakes include leaving out the encounter reason, writing vague referral notes, and failing to record whether the patient accepted the referral. Another frequent issue is collecting too much detail in free text when a structured field would be easier to review later. It also helps to document urgent safety concerns clearly so escalation is not missed.
Can this template be customized for different programs?
Yes, it can be adapted for housing navigation, food access, maternal health outreach, chronic disease support, or school-based programs. You can add conditional logic so only relevant needs appear after the screening section. You can also rename referral options, adjust required fields, and tailor follow-up steps to local workflows.
How does this compare with ad-hoc notes or free-text documentation?
Ad-hoc notes are faster at the moment, but they are harder to review, compare, and report on later. This template gives you a repeatable structure for encounter details, social needs, referrals, and follow-up actions, which improves continuity of care. It also reduces the chance that a key field, like consent or escalation status, gets missed.
Can this connect to other systems or workflows?
Yes, the fields can map to case management, EHR, referral tracking, or reporting workflows if your process supports integrations. Structured fields like encounter date, referral type, and follow-up date are easier to sync than long narrative notes. If you plan to integrate it, keep the field names stable and avoid overloading one field with multiple meanings.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
See how MangoApps Forms helps teams collect, track, and analyze employee data in real time — with mobile access, file uploads, and enterprise-grade security.
-
MangoApps AI agents now take action across 21 apps—approving leave, advancing candidates, managing schedules—not just surfacing recommendations.
-
Spring '26 adds real-time Google & Outlook calendar sync, Google Workspace file creation in Files, upgraded Messenger, and expanded mobile parity.
-
Learn how nonprofit tracking of KPIs, donations, and operational workflows reduces turnover and improves decision-making with the right knowledge management...
Ready to use this template?
Get started with MangoApps and use Community Health Worker Encounter Documentation with your team — pricing built for small business.
