BLOG POST

Three Questions for Better Community Resource Coordination

Technology should support the network, not be it

This is the third in a 4-part series based on an Expert Webinar held Aug 13, 2026 called “Building a Community Safety Net: Connecting People, Processes, and Tools to Coordinate Resources That Matter”. Speakers were Randi Harms and Loretta Severin from the University of Kansas Center for Public Partnerships and Research. Sign up to see the full video and get future Expert Webinar announcements.

Icon of a heart with a pulse

Pulse Check Points

The goal is to understand the system you need to support—and then choose technology that makes that system easier, more visible, and more sustainable

A workflow isn't finished when you document it. You need to test it, measure it, learn from it, and improve it.

Technology should support—not create—the process

Don't digitize a broken process. First build relationship, then design shared processes, then choose tools that support those relationships and processes.

The opportunity is to create a system that helps people get connected to the right resources with less effort for all involved.

Tools: Before You Buy Another Resource Coordination Tool

Technology can make it easier to connect people with services.

But technology can’t fix a resource coordination process that doesn’t work.

That’s an important distinction for public health organizations considering a new resource directory, referral platform, case-management system, or public health EHR.

When teams struggle to connect people with community resources, the natural response is often to look for a better tool. But the most important questions come before the technology:

  1. Who needs to work together?
  2. How do they need to work together?
  3. What problem do we actually need technology to solve?

 

These questions provide a practical starting point for stronger community resource coordination.

The goal isn’t to find one tool that does everything. It’s to understand the system you need to support—and then choose technology that makes that system easier, more visible, and more sustainable.

Community resource coordination starts with people

Every community already has a resource coordination system. It may not have a formal name. It may not have a shared workflow. It may not even exist in one piece of software. Instead, it may live in relationships.

A public health nurse knows who to call at the local housing organization. A community health worker knows which food program can usually respond quickly. A social worker knows which behavioral health provider has openings.

Those relationships can help families navigate complicated systems. But informal networks have limits.

People change jobs. Programs change. Staff go on leave. Funding shifts. New organizations enter the community.

When resource coordination depends on individual relationships, the system can become fragile.

That’s why the first question to ask is:

1. Who needs to work together?

Before selecting a technology, map the people and organizations involved in the work.

Ask:

  • Which organizations serve the people we are trying to reach?
  • Which providers make referrals to one another?
  • Which organizations receive those referrals?
  • Who needs to participate in the process?
  • Where do strong relationships already exist?
  • Where are the gaps?
  • Who is missing from the conversation?

 

A simple partner map can reveal a lot.  (see the previous blog post for details on how to do this)

You might discover that several organizations work closely together but don’t connect with other sectors that families also need. You might find that one person serves as the critical link between several organizations. Or you might discover that two organizations you assumed worked together rarely communicate at all.

These insights can help you understand the community resource coordination system you already have before you try to change it.

2. How do we need to work together?

Once you understand who needs to participate, define how they will work together. This step often gets overlooked.

Organizations may agree that they want to “improve referrals,” but that phrase can mean very different things to different people.

Instead, get specific.

Ask:

  • What constitutes a referral?
  • Who makes the referral?
  • Who receives it?
  • Who is responsible for follow-up?
  • What information should the referral include?
  • How quickly should someone respond?
  • What happens when the family cannot be reached?
  • When do we consider a referral successful?
  • How will providers communicate when something goes wrong?
  • How will staff learn the process?

 

These questions turn a broad goal into a workable process.

Don’t assume the process works just because everyone follows it

A community mentioned the Aug 13 Expert Webinar discovered an important lesson.

Partners had agreed that organizations should acknowledge referrals within five days. That sounded like a reasonable standard. But once they looked at what actually happened, they found that some referrals were being acknowledged and closed very quickly without meaningful follow-up with the family.

The process existed. The process was being followed.

But the process wasn’t producing the outcome the community wanted.

The partners used what they learned to refine their expectations around outreach and follow-up.

This illustrates an important principle for community resource coordination: A workflow isn’t finished when you document it.

You need to test it, measure it, learn from it, and improve it.

3. What problem do we actually need technology to solve?

Now you can start talking about technology. Instead of asking, “Which tool should we buy?”, ask: “What problem do we need a tool to solve?”

Start with the experience of the people doing the work. (See the last blog in the series about how to do partner mapping.)

  • Where are public health nurses losing time?
  • Where do referrals get stuck?
  • Where do families fall through the cracks?
  • What information needs to follow the person?
  • What does the care team need to know?
  • What do community partners need to see?
  • What do leaders need to measure?

 

Your answers will help you determine what role technology should play in your community resource coordination strategy.

Technology should support—not create—the process

Public health organizations often use multiple systems.

A resource directory might help providers find available services. A case-management system might help staff document and manage client needs. An EHR might provide the central record for health and service information. A referral platform might help organizations communicate about referrals and track what happens next.

Each tool can serve a different purpose.

The goal isn’t necessarily to replace everything with one system.

Instead, consider how your existing tools work together.

A public health EHR can become an important part of this infrastructure when it supports the workflows your team has already defined.

Depending on your needs, that might include:

  • Referral documentation so staff can record where and why they referred someone.
  • Care plans that connect resource needs with broader client goals.
  • Task management that makes follow-up responsibilities visible.
  • Alerts and reminders that prompt staff when action is needed.
  • Shared records that give authorized members of the care team the information they need.
  • Configurable workflows that reflect how your organization actually works.
  • Reporting and analytics that help leaders understand referral activity and identify gaps.

 

The key is alignment.

Don’t make the technology the process. Make the technology support the process.

Ask what the technology will help you learn

Technology can do more than make work faster. It can make community resource coordination more visible.

Before selecting a tool, ask what you want to learn from the data it generates.

  • Can you see where referrals are going?
  • Can you identify services that receive unusually high demand?
  • Can you see where referrals stall?
  • Can you identify resource gaps?
  • Can you understand whether some populations or geographic areas experience different outcomes?

 

Most importantly, can you tell whether coordination is improving the experience for the people and families you serve?

Those questions can help you evaluate technology based on its potential impact—not simply its list of features.

Don’t digitize a broken process

A new technology can make a good process more efficient. It can also make a confusing process more complicated.

  • If partners haven’t agreed on who responds to a referral, a digital referral system won’t resolve that disagreement.
  • If staff don’t know what information they should share, a new platform won’t automatically create clarity.
  • If organizations don’t trust one another, technology won’t build that trust overnight.

 

That’s why community resource coordination should follow a simple progression: People → Processes → Tools

People - Processes - Tools

First, build the relationships.

Then, design the shared processes.

Finally, choose the tools that support those relationships and processes.

The right tool depends on the right questions

There is no single technology solution for every community.

The best choice depends on your goals, your partners, your workflows, your resources, and the experience you want people to have.

Before you adopt or expand an electronic health record system (EHR) or invest in another referral tool, take a step back.

Ask:

  • Who needs to work together?
  • How do we need to work together?
  • What problem do we actually need technology to solve?

 

Those questions can help your team avoid buying technology simply because it promises more features.

Instead, you can choose technology because it solves a clearly defined problem—and helps your community build a stronger, more connected safety net.

That’s the real opportunity for community resource coordination: not simply adding another tool, but creating a system that helps people get connected to the right resources with less effort, fewer dead ends, and better visibility for everyone involved.

Watch for part 4 in this series coming soon:

4 part blog series overview

——

The graphics used for this article were generated with a series of AI-prompts.  The article was written by a human after getting an AI-generated outline of keypoints from the webinar transcript.

Share this case study: