Community Resource Referral Log
Log each community resource referral in one place, from consent and contact method to follow-up status and outcome notes. Use it to coordinate housing, employment, and support-service referrals without losing the audit trail.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Nonprofit Social Services · Healthcare Care Coordination · Workforce Development · Community Health · Public Sector Human Services
Overview
The Community Resource Referral Log template records the full lifecycle of a referral: when it was made, who made it, why it was needed, what resource was contacted, whether consent was obtained, and what follow-up or outcome followed. It is designed for teams coordinating housing, employment, food, transportation, counseling, or other support services where a simple note is not enough.
Use this template when you need a repeatable record for warm handoffs, case management, or wraparound care coordination. It helps staff keep referral details, outreach attempts, appointment dates, and escalation notes in one place so cases do not stall between organizations. The audit trail section is especially useful when several staff members touch the same referral or when you need to show what action was taken and when.
Do not use this template as a general client intake form or as a broad case file. It is not meant to collect every possible personal detail, and it should not be expanded into a catch-all record that ignores data minimization. If the referral does not require consent, follow-up, or outcome tracking, a lighter log may be enough. If the case involves sensitive health information, keep the fields limited to the minimum necessary and use only the contact and disclosure details needed to complete the referral.
Standards & compliance context
- Keep the form aligned with GDPR data minimization by collecting only the person and referral details needed to complete and document the referral.
- If the log includes health-related information, apply the minimum-necessary principle and avoid adding diagnosis or treatment details that are not required for the referral.
- For any public-facing or shared intake workflow, ensure the fields and labels meet WCAG 2.1 AA accessibility expectations, including clear required versus optional indicators.
- If the referral process is used in HR or intake contexts for accommodation support, include a clear prompt for reasonable-accommodation needs only when relevant to the workflow.
- Use consent_to_share and consent_notes to document disclosure boundaries before sending PII to an outside resource.
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
Referral Record
This section captures the basic referral facts so anyone reviewing the log can quickly see when the referral happened, who initiated it, and why it was made.
- Referral Date
- Referral Source
-
Primary Reason for Referral
Select all that apply. Collect only what is needed for care coordination.
-
Referral Summary
Briefly describe the need and any relevant context. Avoid unnecessary PII.
Person and Consent
This section matters because it documents who the referral is for and whether information can be shared, which protects privacy and keeps the workflow lawful and clear.
-
Person's Name
Optional if your workflow allows anonymous submission or uses an internal identifier instead of a name.
-
Internal Client or Case ID
Use an internal ID instead of collecting extra PII when possible.
- Preferred Contact Method
-
Consent to Share Referral Information
Required before sharing any PII with an external resource provider.
-
Consent Notes
Document any limits on consent, disclosures provided, or preferred communication boundaries.
Resource Referral Details
This section identifies the outside service and how the handoff was made, which helps staff confirm the right resource was contacted and scheduled if needed.
- Resource Category
- Resource or Provider Name
- Referral Method
- Scheduled Appointment Date
-
Resource Contact Information
Optional. Include only if needed for follow-up coordination.
Follow-Up and Outcome
This section shows whether the referral was completed, still open, or needs more outreach, which is essential for case management and continuity of care.
- Is Follow-Up Needed?
- Follow-Up Due Date
- Current Follow-Up Status
-
Outcome Notes
Document outreach attempts, barriers, and next steps without unnecessary PII.
- Number of Outreach Attempts
Status, Escalation, and Audit Trail
This section creates the record of current status, escalation decisions, and staff actions so the referral can be reviewed, handed off, or audited later.
- Referral Status
- Escalation Needed?
- Escalation Reason
-
Audit Trail Notes
Record key actions, dates, and handoffs for the referral history.
How to use this template
- 1. Set up the form with required fields for referral date, referral source, referral reason, resource category, and referral status, and keep optional fields optional unless your program truly needs them.
- 2. Assign the log to the staff member who makes the referral or owns the case so one person is responsible for updating follow-up status and audit trail notes.
- 3. Enter the person and consent details before sharing information, including the contact method, consent to share, and any limits or notes about what may be disclosed.
- 4. Record the resource referral details immediately after the handoff, including the resource name, referral method, appointment date if scheduled, and the best contact information for the outside provider.
- 5. Update follow-up fields after each outreach attempt or status change, then close the record with outcome notes, escalation details if needed, and a clear final referral status.
Best practices
- Use a date picker for referral dates, due dates, and appointment dates so staff do not enter inconsistent date formats.
- Keep referral reason and outcome notes specific enough to support follow-up, but avoid collecting unnecessary personal detail that is not needed to complete the referral.
- Make consent_to_share explicit and separate from general intake consent so staff can see exactly what was approved for disclosure.
- Use conditional logic to show escalation fields only when escalation_needed is true, which keeps the form shorter and easier to complete.
- Limit contact_method to the channels your team actually uses, such as phone, text, email, or in-person handoff, so reporting stays clean.
- Record number_of_outreach_attempts at the time of each attempt instead of reconstructing it later from memory.
- Write audit_trail_notes as a factual timeline of actions, handoffs, and updates rather than narrative commentary.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What kinds of referrals does this log cover?
This template is built for community resource referrals such as housing, employment, food support, transportation, behavioral health, and other wraparound services. It works best when you need to record the referral itself, the consent to share information, and whether follow-up is still needed. If your process is only a simple contact list with no outcome tracking, this template is more detailed than you need.
Who should complete the referral log?
It is typically completed by case managers, care coordinators, social workers, intake staff, or program staff who make or track referrals. The person entering the record should be the one who knows the referral source, the resource contacted, and the current status. If multiple people touch the case, the audit trail notes should make ownership and handoffs clear.
How often should follow-up be updated?
Update it whenever a referral is made, a follow-up attempt happens, or the resource reports a status change. For active cases, many teams review follow-up due dates daily or during scheduled case review meetings. The key is to keep the follow-up status current so the log reflects what happened, not just what was planned.
Do I need consent before recording or sharing referral details?
If the log includes personally identifiable information or any details shared with an outside resource, you should record whether consent to share was obtained and any limits on that consent. Use the consent notes field to capture scope, date, and any restrictions. If your workflow allows anonymous submission or de-identified tracking, use that only when it still supports the referral process.
What are the most common mistakes when using this template?
Common mistakes include leaving the referral reason too vague, skipping the contact method, and not recording the number of outreach attempts. Another frequent issue is marking a referral complete without documenting the actual outcome or next step. This template helps avoid those gaps by separating the referral, follow-up, and escalation fields.
Can I customize the fields for our program?
Yes. You can add program-specific fields such as eligibility criteria, service priority, interpreter needs, transportation barriers, or internal case owner. Keep the form aligned with data minimization by only collecting fields you will actually use. If a field is not needed to make the referral or track the outcome, it should stay optional or be removed.
How does this compare with tracking referrals in ad hoc notes or email?
Ad hoc notes and email threads are hard to search, easy to miss, and often lack a consistent audit trail. This template standardizes the same core data every time: who was referred, to what resource, with what consent, and what happened next. That makes it easier to review open cases, hand off work, and report on referral outcomes.
Can this log connect to other systems or workflows?
Yes. It can be paired with case management, CRM, intake, or task systems through integrations or manual handoff. The most useful setup is one where referral status and follow-up due dates can trigger reminders or assignment changes. If you integrate it, keep the source of truth clear so the audit trail stays consistent.
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 —...
-
Discover 4 proven keys to successful project management and team collaboration — from transparent goal-setting to real-time communication and workflow...
-
Boost team collaboration with modern tools that improve visibility, accountability, and communication for stronger project outcomes.
-
Compare the best employee apps of 2026—MangoApps, Blink, WorkJam, Flip, and more—to find the right fit for your frontline workforce.
-
Discover how continuous feedback, dynamic goal-setting, and psychological safety replace annual review dread with a no-surprise performance culture that...
Ready to use this template?
Get started with MangoApps and use Community Resource Referral Log with your team — pricing built for small business.
