What Public Health Dashboard Examples Should Show Program Leads

For this article, public health dashboard examples means closed-loop referral and care-coordination dashboards, not the population-level surveillance boards you see cited in most search results. If you run referrals for an AHEC, FQHC, health department, or rural health network, the dashboard you need proves that a referral led to a delivered service, not just that it was sent.

A dashboard worth using shows six things at minimum:

• Referral status funnel tracking a case from screening to acceptance to service delivery to closure
• Time-to-service trend flagging cases stuck past 30 days
• Provider engagement table showing which partners accept, decline, or ignore referrals
• Outcomes-by-need chart breaking down resolution rates by category (housing, food, transportation)
• Geographic supply/demand map showing where need outpaces partner capacity
• Client timeline card showing the full path for any single case

The Measurement & Evaluation Playbook organizes these into six KPI categories. WellCheck’s EquiLoop platform builds dashboards around this exact structure.

Key Takeaways

Closed-loop referral dashboards must prove that referrals resulted in delivered services, using widgets and KPIs mapped to the six categories in the Measurement & Evaluation Playbook.

Table of Contents

• What Good Closed-Loop Referral Dashboards Show
• Copyable Visual Patterns for Referral Dashboards
• Defining the KPIs That Hold Up Under Funder Scrutiny
• Turning Dashboard Signals into Quality Improvement and Funder Reports
• A 90-Day Checklist for Standing Up Your Dashboard
• Dashboard Examples Across Different Care Coordination Contexts
• Design Choices That Keep a Referral Dashboard Usable
• Choosing the Right Chart for Referral and Outcome Data
• Where Dashboard Projects Usually Stall
• What Closed-Loop Dashboard Data Actually Shows in Practice
• Where WellCheck Fits if You’re Building This Now
• Sources

What Good Closed-Loop Referral Dashboards Show

A dashboard that only counts referrals sent tells you activity happened. It doesn’t tell you whether anyone got help. That distinction is exactly what funders now ask about, and it’s why the six categories in the Measurement & Evaluation Playbook exist: they force a dashboard to answer operational questions, not just report volume.

1. Navigation quality. A staff performance view showing which coordinators close referrals fastest, and which cases sit unresolved long enough to trigger an escalation flag. This isn’t about ranking staff. It’s about catching the case that fell through before it becomes a missed 90 day window.

2. Demand and supply. Which needs show up most often in screenings, and whether your partner network has the actual capacity to meet them. A dashboard that shows 40 housing referrals a month against one housing partner with three open slots is telling you something you need before your next grant renewal, not after.

3. Provider engagement. Acceptance rates, average response time, and a running list of which partners are actually active versus nominally listed. Programs using closed-loop tracking often find that a small number of partners drive most successful connections, according to Health Leads, which makes this table one of the more consequential views on the whole dashboard.

4. Network referral process. Funnel metrics and the percentage of referrals closed within 30, 60, and 90 days. Following up within roughly 30 days is associated with higher rates of successful connection, per SIREN/UCSF guidance, so that window should sit on the dashboard as a visible threshold, not a footnote.

5. Client outcomes. Resolved needs, bundled pathway completion (housing plus medication management plus primary care, for instance), and the closed-loop completion rate funders increasingly require over raw referral counts.

Copyable Visual Patterns for Referral Dashboards

You don’t need to invent these widgets from scratch. Each one maps to specific data fields your intake and referral system already captures, if it’s set up to capture them.

Referral funnel mockup. Track referral date, need category, partner assigned, status (sent, accepted, in progress, closed, finished incomplete), and closure reason. Filter by ZIP code, referral source, and need type. The “finished incomplete” status matters here: AHRQ’s Community HUB guidance treats it as a distinct outcome that needs its own documented reason, not a silent drop from the count.

Partner engagement matrix. Columns for referrals received, accepted, and closed. Rows segmented by organization type and language support offered, so gaps in language access show up visually instead of buried in a spreadsheet.

Time-to-service trend with alert band. A line chart with a shaded target zone (often 0 to 30 days) and a hard alert past 60 days.

Geographic supply/demand map. A choropleth showing need density against partner capacity by county or ZIP, paired with a ranked hotspot list.

Client timeline card. A single-case view running screening through referral, acceptance, service delivery, and closure, with dates at each step.

Defining the KPIs That Hold Up Under Funder Scrutiny

A KPI is only as trustworthy as its formula, and this is where a lot of programs get burned during an audit. If your numerator and denominator aren’t defined the same way every quarter, your closed-loop completion rate becomes a number nobody, including you, can defend.

Here’s how the six Playbook categories translate into formulas your team can actually calculate:

Two decisions determine whether these numbers mean anything: what counts in the denominator, and how you handle a “finished incomplete” Pathway. A case where the client couldn’t be reached after three attempts is not the same as a case where the partner had no open slots, and your dashboard should record the reason separately, per AHRQ’s HUB documentation standards.

Disaggregate everything by need type and ZIP code at minimum. Add REALD (race, ethnicity, language, disability) breakdowns where your intake system captures them, and report on a monthly operational cadence with a quarterly rollup for funders.

Turning Dashboard Signals into Quality Improvement and Funder Reports

A dashboard that just sits there generating numbers isn’t doing its job. The real value shows up when a stalled metric triggers a specific, testable change, and that’s what a PDSA (Plan-Do-Study-Act) cycle gives you.

1. Identify the signal. A dashboard showing time-to-service climbing past 45 days for housing referrals in one county.
2. Test a change. Add a second housing partner or shift intake staff coverage for two weeks.
3. Measure the result on the same dashboard view, same KPI, same window.
4. Adopt or discard based on what the numbers actually show, not on how the change felt.

Different stakeholders need different slices of the same data. Operations staff should check the dashboard daily. Clinical leads need a weekly rollup focused on outcomes and escalations. Funders typically want a quarterly export with acceptance rates, time-to-service, and closed-loop completion broken out by need category.

Pro Tip: Tag every closure reason at the point of closure, not after the fact. Retroactively assigning “finished incomplete” reasons from memory during a quarterly report is where data quality quietly falls apart.

Aggregate closure reasons across the quarter and you get something more useful than a report. You get a case for what capacity gap needs funding next.

A 90-Day Checklist for Standing Up Your Dashboard

Getting a dashboard live isn’t a technical project alone. Leavitt Partners’ referral system guidance makes the point that dashboards succeed when workflows and stakeholder agreements come first, not after the software is installed.

Governance

1. Write SOPs for consent capture and define the referral coordinator role clearly.
2. Draft data-sharing agreements with each partner before go-live.
3. Confirm partner service availability on a recurring schedule, not just at onboarding.

Technical

• Define required data fields for every Pathway (status, dates, closure reason, need category).
• Map EHR or SHARP integration points so screening data flows without duplicate entry.
• Build consent capture directly into the intake form.

Operational

• Onboard partners with a written data expectations checklist.
• Train staff on documentation standards; the Workforce Development Academy offers structured coursework for this if your team needs a formal training path.
• Set reporting cadence (daily operations, weekly clinical, quarterly funder) and hold to it through the first 90 days.

Dashboard Examples Across Different Care Coordination Contexts

Closed-loop referral dashboards flex depending on what your program is actually coordinating, and the widget mix shifts with it.

A chronic disease management program running a diabetes referral pathway needs a dashboard weighted toward the client outcome view: how many clients referred to nutrition counseling or medication management actually completed the service, and whether the bundle (primary care plus a social need like transportation) reduced missed appointments. The time-to-service trend matters less here than the outcome-by-bundle breakdown, because chronic conditions play out over months, not days.

A vaccination coverage effort run through an FQHC or health department outreach team leans harder on the geographic supply/demand map. The question isn’t just who got screened. It’s which ZIP codes show low uptake against where mobile clinics or partner sites actually operate, so outreach staff know where to redeploy.

A rural network coordinating multiple social needs at once, food, housing, transportation, needs the full six-category view, because the bottleneck could be in any category and shifts month to month. This is the context where the partner engagement matrix earns its place on the front screen rather than a secondary tab, since capacity gaps show up first in that table.

None of these are population surveillance boards tracking case counts across a region. They’re operational tools built around one client’s path through your network, aggregated up to a program level.

Design Choices That Keep a Referral Dashboard Usable

A dashboard nobody opens twice a week isn’t helping anyone, no matter how complete the data behind it is. Design decisions determine whether staff actually use it.

Put the referral funnel and time-to-service trend above the fold. Those two views answer the question a program director asks first, are cases moving, and where are they stuck. Buried metrics don’t get checked.

Color coding needs restraint. Red for overdue, yellow for approaching a threshold, green for on track works because it’s simple, not because it’s flashy. A dashboard with a dozen colors competing for attention slows down the exact staff member trying to spot a problem in ten seconds.

Accessibility isn’t optional when your users include coordinators working from a tablet in the field, not just an analyst at a desktop. Text needs to hold up at a smaller screen size, and color coding needs a non-color backup (an icon, a label) for staff with color vision differences.

Filters should match how your team actually thinks about a caseload, by partner, by need category, by ZIP code, by coordinator, not by whatever fields happened to be easiest to pull from the database. If your team constantly exports to a spreadsheet to re-sort data, the dashboard’s filters are wrong.

Keep the client timeline card one click away from any summary view. A director looking at a stalled metric needs to drill into the actual case, not just the aggregate number, within seconds.

Choosing the Right Chart for Referral and Outcome Data

Not every metric belongs in a bar chart, and picking the wrong chart type is one of the more common ways a good dashboard gets ignored.

Funnel charts fit referral status best, because the whole point is showing where volume drops off between stages: sent, accepted, service delivered, closed. A simple bar chart loses that stage-to-stage relationship.

Line charts with a shaded target band work for time-to-service, because the story is trend against a threshold, not a single number. Watching the median creep from 22 days to 38 days over a quarter tells staff something a static KPI card never will.

Choropleth maps are the right call for geographic supply and demand, since the point is spatial: where does need cluster relative to where partner capacity actually sits. A table of ZIP codes buries that pattern.

Matrix or heat map views suit provider engagement, because you’re comparing two dimensions at once, partner and metric, and a heat map lets a busy coordinator spot the underperforming partner by color before reading a single number.

Avoid pie charts for outcome categories with more than four or five slices. They’re hard to read accurately and worse, they invite comparing angles instead of the actual numbers.

Where Dashboard Projects Usually Stall

Most closed-loop dashboard efforts run into the same handful of problems, and recognizing them early saves months.

Inconsistent data entry is the most common one. If one coordinator logs a closure reason and another leaves it blank, your closed-loop completion rate is unreliable the moment you try to report it. The fix is a required field at the point of closure, not a cleanup pass at quarter end.

Partner data lag shows up when a community partner doesn’t report back on service delivery in a timely way. AHRQ’s HUB guidance recommends built-in check-ins with partners specifically to close this gap, rather than waiting for the partner to initiate contact.

Tool fragmentation happens when screening lives in one system, referrals in email, and outcomes in a spreadsheet. No dashboard can unify data that was never connected in the first place; the fix is workflow integration before dashboard design, not after.

Overbuilt dashboards try to show everything to everyone and end up showing nothing clearly to anyone. Leavitt Partners’ SDOH referral management guidance points out that technology has to align with existing workflows rather than get imposed on top of them, which is exactly where overbuilt dashboards go wrong: they reflect what a vendor could build, not what a coordinator actually needs to check each morning.

What Closed-Loop Dashboard Data Actually Shows in Practice

Numbers from operational deployments make the case for closed-loop tracking better than any hypothetical. One rural program, spanning both clinical and social services referrals, screened a substantial number of individuals and delivered tens of thousands of services, with a high closed-loop completion rate.[^1]

That completion rate matters because it answers the exact question funders ask and generic referral counts can’t: not how many people were screened, but how many of the resulting referrals actually led to a delivered service. A screening number alone tells a funder nothing about follow-through. A very high closed-loop rate tells them the referral pipeline works.

The gap between those two numbers, screenings versus completion rate, is where most programs lose credibility during a grant renewal. A program that can only report “we screened many people” gets a very different response than one that can also say “and most of the resulting referrals closed with a service delivered.” The second version is the one that gets refunded.

This is also the case for building the widgets described earlier into your own dashboard rather than treating them as optional add-ons. The demand-versus-supply view, the provider engagement table, and the time-to-service trend are what generate a number like this in the first place. Without them, you’re guessing at why completion rates move.

[^1]: Rural health hub deployment with a multi-partner ecosystem. Includes both clinical and social services referrals.

Where WellCheck Fits if You’re Building This Now

WellCheck’s EquiLoop platform manages the full workflow described in this article: SDoH screening and intake, referral routing to clinical and community partners, follow-up and status tracking, and the outcomes dashboards and funder-ready reporting that turn raw referral activity into a defensible completion rate. It’s configured around the partner network and reporting requirements your organization already has, rather than asking you to rebuild your workflows around a new tool.

If training staff and community health workers on documentation standards is part of your rollout, the Workforce Development Academy offers white-labeled coursework for navigators and coordinators, credentialing included.

Programs evaluating referral management software usually reach a point where spreadsheets and disconnected systems can’t produce the closed-loop numbers a funder is asking for on this year’s renewal. If that’s where your team is, a 30-minute conversation is a reasonable next step. Schedule a demo to see how EquiLoop’s dashboard maps to your current partner network and reporting cycle.

Sources

• Introducing The Health and Human Services Referral Systems’ Measurement and Evaluation Playbook
• Community HUB Quick Start (AHRQ)
• Health Leads social health data toolkit
• PULSE social needs referrals in primary care (SIREN/UCSF)

Recommended

• Social Drivers of Health: A Guide for Public Health Leaders | WellCheck
• Community Care Outreach: Digital Closed-Loop Workflows | WellCheck
• Follow-Up Management for SDoH Programs: A Practical Guide | WellCheck