Follow-Up Management for SDoH Programs: A Practical Guide

Follow-up management in SDoH programs means one thing: documenting that a referral was made, tracking whether the patient connected with the resource, and recording whether the need was resolved. It is closed-loop referral and care coordination, not a reminder queue. The AMA’s guidance on closed-loop referral systems and tools like PRAPARE for SDoH screening both assume this level of accountability. Platforms such as WellCheck’s EquiLoop are built specifically to manage that workflow from intake to outcome.

Your immediate next step: pick one outcome to track this week and assign a staff member to follow up within 30 days.

• Choose one outcome state: referral acceptance, patient contact, or services received.
• Assign one role (CHW, care coordinator, or patient navigator) as the responsible follow-up contact.
• Set a 30-day window as the default resolution check cadence.
• Document the result in a structured field, not a free-text note.

Key Takeaways

Effective follow-up management for SDoH programs requires a defined data model, assigned staff roles, a 30-day contact cadence, and outcome-level reporting that moves beyond referral volume to documented need resolution.

Table of Contents

• What does closed-loop follow-up management actually require?
• What data fields and outcome states do you need to capture?
• Who does follow-up, and when should it happen?
• Which workflow and technology path fits your program’s capacity?
• What KPIs and reporting do funders actually want?
• What barriers consistently block follow-up, and how do you address them?
• How do you build a follow-up management plan in 90 days?
• EquiLoop and the Workforce Development Academy for follow-up management
• Sources

What does closed-loop follow-up management actually require?

Closed-loop follow-up management covers the full arc: screen → refer → follow up → resolve. A referral that leaves your system without a return status update is not a closed loop. It is a one-way transaction, and funders are increasingly unwilling to fund those.

The Leavitt Partners Playbook for SDOH Referral Management and Data Exchange identifies three operational pillars every referral program must address: placing limited burden on care teams, tailoring referrals to individual patient needs, and facilitating fully closed-loop tracking. Programs that skip any one of these tend to fall back on manual spreadsheets and lose staff buy-in within months. The same source notes that data aggregation at the outcome level, not just the service volume level, is what drives program sustainability and funder confidence.

For program directors, the practical implication is this: your program’s long-term funding depends on whether you can show resolved needs, not referral counts.

Pro Tip: Start with one social need domain (food, housing, or transportation) and one outcome state. Prove the workflow closes the loop before adding domains or partners.

What data fields and outcome states do you need to capture?

A minimum data model does not need to be complex. It needs to be consistent. The fields below are sufficient for most funder dashboards and closed-loop reporting.

Each referral should move through a defined status sequence. The UCSF PULSE guidance describes a status model that works well operationally:

• Referral initiated: sent to CBO or internal navigator.
• Referral accepted: CBO or navigator confirms receipt.
• Patient contact: staff reached the patient to confirm awareness and intent.
• Enrolled: patient has begun the intake process with the resource.
• Services received: patient confirms or CBO confirms delivery.
• Need resolved: documented as resolved, partially resolved, or not resolved, with a timestamp.

Timestamping each transition is what makes the data reportable. Without it, you can count states but not time-to-resolution, which is a metric most funders now expect.

Who does follow-up, and when should it happen?

Accountability gaps in follow-up almost always trace back to unclear role assignment, not lack of effort.

Suitable roles for follow-up navigation include case managers, community health workers (CHWs), care coordinators, patient navigators, population health nurses, and rooming staff when navigation capacity is limited. The PULSE guidance recommends that navigation staff have protected time and clear escalation protocols, and that outreach can occur during subsequent clinical visits when dedicated navigation capacity is constrained.

Time estimates per activity, for staffing math:

1. Initial outreach attempt (phone or portal message): 5–10 minutes.
2. Documentation of attempt and outcome: 3–5 minutes.
3. Escalation to supervisor or alternate resource: 10–15 minutes.
4. Resolution confirmation and status update: 5–8 minutes.

Recommended cadence:

1. First contact attempt within 3–7 days of referral initiation.
2. Second attempt by day 14 if no response.
3. Resolution check by day 30.
4. Escalate to a supervisor or alternate resource if no contact by day 30.

Tracking patient outreach attempts with consistent documentation, whether by phone log, EHR note, or platform event, is what separates a defensible follow-up record from a gap in the chart.

Which workflow and technology path fits your program’s capacity?

Three workflow patterns cover most program configurations. The right choice depends on your EHR, your CBO relationships, and your staff capacity.

A. EHR-integrated bidirectional workflow. The referral is sent from the EHR, the CBO receives it through a connected portal or FHIR-based exchange, and status updates flow back into the EHR automatically. High data visibility, low manual burden once configured, but requires EHR vendor cooperation and CBO technical capacity.

B. Platform-based workflow with CBO updates. A third-party platform (such as EquiLoop) sits between the clinical system and the CBO. Staff enter referrals in the platform, CBOs log status updates through a portal or mobile interface, and the platform surfaces outcomes for reporting. This path works when EHR integration is not yet feasible and when you need funder-ready dashboards without waiting for IT cycles.

C. Manual fallback using shared logs. A shared spreadsheet with defined columns (referral ID, date, CBO, status, follow-up date, resolution) combined with EHR tickler reminders. Functional for small programs or pilots, but it does not scale and creates data quality risk as volume grows.

The Best Practices Toolkit from the Colorado Health Institute recommends written consent when ongoing status exchange is anticipated and outlines practical exchange methods ranging from shared spreadsheets to interoperable platforms, depending on local capacity.

Pro Tip: If you are starting with a spreadsheet, structure it now with the same field names you would use in a platform. Migration is far easier when the data model is consistent from day one.

What KPIs and reporting do funders actually want?

Most programs can report referral volume. Fewer can report what happened after the referral. That gap is where program sustainability is decided.

Core KPIs for a funder-ready dashboard:

• Referral volume: total referrals initiated per period.
• Referral acceptance rate: percentage accepted by the CBO.
• Patient contact rate: percentage of referred patients successfully reached.
• Enrollment rate: percentage who began the resource intake process.
• Services-received rate: percentage who confirmed receipt of services.
• Need resolution rate: percentage with a documented resolved or partially resolved outcome.
• Average time-to-resolution: mean days from referral initiation to resolution status.

A funder dashboard should present these as a funnel: volume at the top, resolution rate at the bottom. The drop-off between each stage tells the program where the workflow is breaking. A study published in JABFM found that only about one-third of patients started services within four weeks, and that resources allowing direct access (call or drop-in) were associated with higher odds of connection. That finding belongs in your program narrative to funders.

What barriers consistently block follow-up, and how do you address them?

Operational barriers:

• Stale resource directories with outdated contact information or eligibility criteria.
• Inconsistent CBO engagement when no formal agreement defines response expectations.
• Lack of interoperable technology between clinical and community systems.
• Insufficient staff time when follow-up is added to existing caseloads without protected hours.

Patient-facing barriers:

• Resource unavailability (waitlists, geographic gaps).
• Administrative complexity in application processes.
• Transportation and language access constraints.
• Low trust in outreach from unfamiliar organizations.

Mitigation steps, in priority order:

1. Assign a staff member as directory owner with a quarterly verification cadence. Research on primary care referral practices consistently finds that directories go stale without dedicated ownership.
2. Execute MOUs with CBO partners that define response timeframes and status update expectations.
3. Score resources by access type: direct access (call or walk-in) versus application-required. Prioritize direct-access options in referral routing when patient barriers are high.
4. Build escalation protocols: if a patient cannot connect with the referred resource within 30 days, the assigned staff member routes to an alternate resource and documents the reason.
5. Simplify patient-facing steps wherever possible. Programs that reduced application complexity showed higher odds of successful connection in retrospective analyses.

How do you build a follow-up management plan in 90 days?

Use this checklist as a Decision-4-style planning activity. Complete each row before moving to the next phase.

The AMA’s closed-loop referral guidance recommends training in trauma-informed communication and cultural humility as a core component, not an optional add-on. Digital tools alone do not produce consistent follow-up results. Staff who understand how to navigate patient hesitancy and CBO processes are what close the loop in practice.

A 90-day pilot should target one social need domain, one CBO partner, and one outcome state. Measure the resolution rate at day 90, identify the largest drop-off point in the funnel, and use that finding to adjust the workflow before scaling.

EquiLoop and the Workforce Development Academy for follow-up management

Programs that have mapped their data model and assigned roles are ready to move beyond spreadsheets. EquiLoop, WellCheck’s closed-loop referral platform, is built around the workflow described above: SDoH screening and intake, referral routing to clinical and community partners, bidirectional status tracking, and funder-ready outcomes dashboards. It is locally configurable, meaning each deployment is set up around the partner network and reporting requirements the organization already has. It complements existing EHRs rather than replacing them.

For programs that need to build staff capacity alongside the platform, WellCheck’s Workforce Development Academy provides white-labeled training and credentialing for CHWs, navigators, and care coordinators who perform follow-up. The Academy covers the practical navigation tasks and communication skills that make closed-loop follow-up work in the field.

To see how EquiLoop maps to your program’s referral pathways and reporting requirements, schedule a 30-minute demo at calendly.com/wellcheck/demo-discuss. When you book, request a pilot scoped to at least one referral outcome so you can see resolution-rate reporting from day one.

Sources

• Playbook for SDOH Referral Management and Data Exchange
• Social Needs Referrals in Primary Care (PULSE) — UCSF
• Best Practices Toolkit: Community-Clinical Linkages for Chronic Disease Prevention and Management

Recommended

• SDoH Z Codes: A 2026 Guide for Healthcare Professionals | WellCheck
• Social Needs Definition: A Clinical and Policy Guide | WellCheck
• Community Case Management: 10 Strategies That Work | WellCheck