Referral Tracking and Closed-Loop Verification Form
Track outgoing and incoming referrals, document consent and PII handling, and verify whether the client actually connected to the receiving service. Built for case managers who need a clear closed-loop record and audit trail.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Healthcare · Behavioral Health · Social Services · Nonprofit Case Management
Overview
The Referral Tracking and Closed-Loop Verification Form records each step of a referral so your team can see what was sent, who received it, whether the client consented, and whether the connection was completed. It includes fields for referral direction, date, method, staff details, client identifier, information shared, receiving organization contact details, warm handoff status, follow-up plan, outcome, and an audit trail.
Use this template when your workflow depends on more than a simple referral log. It is a good fit for case management, discharge planning, care coordination, and any program that needs to demonstrate that a warm handoff occurred and that the client reached the receiving service. The form also helps teams document barriers, re-referral needs, and supervisor review when a case requires escalation.
Do not use this template as a broad intake form or as a substitute for a full clinical record. If you only need to capture a one-time contact list, this is more structure than you need. It is also not the right fit when no follow-up is expected, when the referral is anonymous and cannot be linked back to a client, or when the receiving service does not permit information sharing. In those cases, simplify the fields and keep only the minimum necessary data.
Standards & compliance context
- The consent and information_shared fields support GDPR data minimization by limiting collection and disclosure to what is needed for the referral.
- The form should follow the minimum-necessary principle for health-related referrals and avoid collecting sensitive PII that the receiving service does not need.
- If the form is used for public-facing intake or client self-referral, it should meet WCAG 2.1 AA expectations for labels, validation, and accessible error handling.
- For HR or accommodation-related referrals, the template can be adapted to capture ADA reasonable-accommodation prompts without asking for unnecessary medical detail.
- The audit trail and certification fields help preserve accountability for who completed the referral and when it was reviewed.
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 every handoff can be traced back to a date, method, and responsible staff member.
-
Referral ID / Case Number
Internal case or referral identifier. Do not enter the client’s full name or SSN in this field.
-
Referral Direction
Is this an outgoing referral you are sending, or an incoming referral received from a partner?
-
Date Referral Was Made
The date the referral was initiated or received.
-
Referral Method
How was the referral communicated?
- If 'Other', describe the referral method
- Referring Staff Member Name
- Referring Staff Role / Title
Client Consent and PII Handling
This section documents permission and limits on information sharing so the referral follows data minimization and privacy rules.
-
Client Identifier (Non-PII)
Use an anonymized or coded identifier (e.g., initials + last 4 of case number). Do NOT enter full name, SSN, or date of birth.
- Has the client provided informed consent to share information with the receiving organization?
-
Date Consent Was Obtained
Required if consent is ‘signed’ or ‘verbal’.
-
What information was shared with the receiving organization?
Select only what was actually transmitted. Collect the minimum necessary.
Receiving Organization Details
This section identifies where the referral went and what service was requested, which is essential for routing and follow-up.
- Receiving Organization / Program Name
-
Service Category
Primary service type the client is being referred for.
- If 'Other', describe the service category
- Receiving Organization Contact Name
- Receiving Organization Phone Number
- Was an appointment or intake scheduled at time of referral?
-
Scheduled Appointment Date
If an appointment was confirmed, record the date.
-
Referral Notes
Describe the presenting need, any barriers noted, or special instructions for the receiving organization. Avoid recording PII not covered by the consent obtained above.
Warm Handoff Documentation
This section shows whether the referral was actively handed off and what barriers may have interrupted the transfer.
-
Was a warm handoff completed?
A warm handoff involves direct staff-to-staff or staff-to-client-to-staff introduction, not just a resource list.
-
Were any barriers to a full warm handoff encountered?
Select all that apply.
-
Planned Follow-Up Contact Date
Set the date by which staff will contact the client or receiving organization to verify connection. Best practice: within 3–7 business days of referral.
- Planned Follow-Up Method
Follow-Up Contact and Closed-Loop Verification
This section confirms whether the client connected and records the evidence needed to close the loop.
- Has follow-up contact been completed?
- Actual Follow-Up Contact Date
- Who was contacted for follow-up?
-
Did the client connect with the referred service?
This is the closed-loop verification question.
- Describe the barrier encountered
- Is a re-referral or alternative resource needed?
-
Follow-Up Notes
Summarize the follow-up conversation, any next steps, and the current status of the referral. Avoid recording PII beyond what is necessary.
Outcome and Case Status
This section turns the referral into a final case status so teams can report outcomes and spot repeat failure points.
-
Overall Referral Outcome
Select the final status of this referral record.
-
Referral Close Date
Date this referral record is being closed. Leave blank if still open.
-
How would you rate the quality of this referral process?
Internal quality indicator for continuous improvement. 1 = significant gaps; 5 = seamless warm handoff and confirmed connection.
-
Process Improvement Notes (Internal)
Optional: note any systemic issues, partnership gaps, or process improvements identified through this referral. Used for QI review only.
Audit Trail and Certification
This section records who completed the form, whether review was needed, and when the record was certified for accountability.
- Name of Staff Completing This Form
- Role / Title
-
Does this referral require supervisor review?
Flag for supervisor review if the referral involved a safety concern, mandatory reporting, or a re-referral after failed connection.
- Reason for Supervisor Review
-
Certification
By submitting this form, I certify that the information recorded is accurate and complete to the best of my knowledge, that consent was obtained as documented, and that this record was created in accordance with agency policy and applicable privacy regulations (HIPAA, 42 CFR Part 2 where applicable).
-
Date of Submission
Date this form is being submitted.
How to use this template
- 1. Set up the referral record fields, service categories, and outcome options so staff can enter structured data instead of relying on free-text notes.
- 2. Assign the form to the staff member who initiates the referral and make the consent section required before any PII is shared.
- 3. Complete the receiving organization and warm handoff sections at the time of referral, including the planned follow-up date and contact method.
- 4. Use the follow-up section to document whether the client connected, what barriers were found, and whether a re-referral is needed.
- 5. Close the case by recording the outcome, quality rating, and submission details, then route any supervisor review before final certification.
Best practices
- Use a date picker for referral, consent, follow-up, and closure dates so staff do not enter inconsistent date formats.
- Mark only the fields needed for the workflow as required and keep the rest optional to support data minimization.
- Add conditional logic so referral_method_other, service_category_other, and barrier_description appear only when relevant.
- Record the exact information shared with the receiving organization instead of copying the full case file into notes.
- Document the follow-up method and planned date at the time of referral so the case does not depend on memory later.
- Capture whether the client connected, not just whether the referral was sent, because closed-loop verification depends on the outcome.
- Use an anonymous submission option only if your program allows de-identified referrals and the receiving service can act on them.
- Require a certification statement and audit trail fields for any workflow that needs supervisor review or compliance evidence.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this form used for?
This form records a referral from start to finish: who sent it, where it went, what information was shared, whether a warm handoff happened, and whether the client actually connected. It is designed for closed-loop verification, not just a one-time referral log. Use it when you need proof that follow-up occurred and the referral outcome is known.
Who should complete the form?
Case managers, care coordinators, social workers, discharge planners, or intake staff usually complete it, depending on your workflow. The referring staff member can enter the initial referral details, while the person handling follow-up can update the outcome and verification fields. If your process requires it, a supervisor can review the record before closure.
How often should referrals be reviewed and updated?
Update the form at each handoff point: when the referral is sent, when consent is obtained, when the receiving organization responds, and after follow-up contact. The follow-up date should reflect your actual cadence, not a placeholder. If the client has not connected, keep the record open until the barrier is resolved or the referral is closed with a documented reason.
What kind of referrals does this template cover?
It works for outgoing and incoming referrals across health, social services, housing, behavioral health, and community support programs. The service category field and conditional notes let you adapt it to different receiving organizations without changing the core workflow. If you need a highly specialized clinical intake, you may want a separate form with additional minimum-necessary fields.
How does this form support consent and privacy requirements?
The consent section helps you document that the client agreed to share information before any PII is transmitted. It also prompts you to record only the information shared, which supports data minimization and minimum-necessary handling. If your workflow allows anonymous or de-identified referrals, the form can be customized to reflect that.
What are the most common mistakes when using a closed-loop referral form?
Common mistakes include leaving the outcome blank, recording a referral without a follow-up plan, and collecting more PII than the receiving service needs. Another frequent issue is using free-text notes instead of structured fields for dates, contact method, and outcome. This template is designed to reduce those gaps by separating referral details, consent, follow-up, and final status.
Can this template be customized for different programs or service lines?
Yes. You can add service-specific conditional logic, change the service category list, or tailor the outcome options to match your program language. Many teams also add required fields for internal routing, such as program code, region, or priority level, while keeping the minimum-necessary principle intact.
How does this compare with tracking referrals in email or a spreadsheet?
Email and spreadsheets often lose the follow-up thread, make consent hard to verify, and create inconsistent records across staff. This template standardizes the fields needed for a closed-loop process, including warm handoff documentation, barriers, and audit trail. It is easier to review, easier to assign, and easier to prove what happened after the referral was made.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
Boost team collaboration with modern tools that improve visibility, accountability, and communication for stronger project outcomes.
-
Discover 4 proven keys to successful project management and team collaboration — from transparent goal-setting to real-time communication and workflow...
-
Compare the best employee apps of 2026—MangoApps, Blink, WorkJam, Flip, and more—to find the right fit for your frontline workforce.
Ready to use this template?
Get started with MangoApps and use Referral Tracking and Closed-Loop Verification Form with your team — pricing built for small business.
