Seventeen Agencies, One Roof: Co-Location Solves Facilities, Not Data

In today’s competitive nonprofit environment, you must make services easier to access while proving that community investment produces meaningful results. You often manage scattered systems, overlapping clients, and different reporting expectations across funders, boards, and public partners. This is where shared KPI definitions and a practical reporting rhythm become invaluable. Co-location can bring people and services together, but only shared data practices can bring the community story into focus.

1. Celebrate the Infrastructure

The Mary Jane Reed and Robert W. Reed CommunityLink represents an important milestone for Shelby County. Located at 2311 S. Miller St. in Shelbyville, Indiana, the nonprofit center includes approximately 31,000 square feet of office and meeting space, a centralized food pantry, and child playscapes.

The facility will bring 17 social service agencies together under one roof. Healthy Shelby County is hosting a community open house on Wednesday, September 30, 2026, from 3:00 to 6:00 p.m. You can learn more through the CommunityLink open house announcement on SERVE SHELBY.

You should celebrate this kind of community infrastructure. A shared location can reduce barriers, simplify navigation, create stronger relationships among providers, and make it easier for families to find help. Healthy Shelby County’s convening role and the related SERVE SHELBY platform show how local coordination can improve access to resources.

The important next step is ensuring that the shared front door produces a shared understanding of service activity. The building solves a facilities challenge. Your reporting system still needs to solve the data challenge.

2. Align the Unit of Analysis

Co-location changes the unit of analysis. Before agencies share a building and an intake process, each organization can reasonably focus on its own clients, services, and outcomes. After co-location, one family may move through several agencies during the same service journey.

For example, one household may receive food assistance, recovery support, transportation help, and family services from four partner agencies. If each agency counts that household as a separate person served, the county’s combined total becomes inflated. If no agency includes the household in a shared count, the result becomes understated.

Both errors can remain invisible inside individual dashboards. Each agency may have accurate records for its own work while the collaborative report tells an inaccurate story about the community.

Research from the Stanford Social Innovation Review emphasizes that shared measurement works when partners agree on consistent metrics and use them for learning, comparison, and decision-making. You do not need to erase each agency’s individual dashboard. You need to distinguish clearly between agency-level activity and collaborative-level results.

That distinction gives you a more credible answer to three different questions:

• How many unique people accessed services?

• How many services or referrals did partners deliver?

• What outcomes did the collaborative help people achieve?

Those questions require different measures. Treating them as one number creates confusion.

3. Prevent Reporting Collisions

The first operating period of a shared-service model often reveals three predictable collision points. You can address each one before it becomes a board, county, or funder reporting problem.

Duplicate counting

You may see the same person recorded under multiple agencies, intake forms, or spellings of a name. A shared navigator may create an initial record, while a partner agency creates another record after accepting the referral.

You need a common client identifier or a documented matching process. You should never rely on guesswork when deduplicating people. A name-only match can combine two different individuals, while a minor spelling difference can split one person into separate records.

Your compact should define when a person receives a collaborative identifier, which fields support matching, and who resolves uncertain matches. You should also separate unique people from service events. One person can legitimately receive multiple services without becoming multiple people in the collaborative count.

Definition drift

Words that appear simple can mean different things across agencies. “Household,” “enrolled,” “served,” “unduplicated,” “completion,” and “navigated” may each carry different reporting rules.

You should define the terms that affect the shared story in writing. For example, “served” might mean that a person completed an intake, received a direct service, or simply contacted a navigator. Each definition produces a different result.

A shared data dictionary gives every partner the same reference point. You can place it in a shared Microsoft 365 folder, a partner portal, or another location that every participating agency can access. The essential requirement is not the software. It is consistent use.

Referral attribution

Referral reporting creates another point of tension. When a shared navigator connects a person to a partner agency, you need to determine what the navigator reports and what the receiving agency reports.

The referring organization contributed access. The receiving organization delivered the service. The collaborative may report the combined journey. Those three facts can all be true at the same time.

Your rules should distinguish between referral made, referral accepted, service scheduled, service completed, and outcome achieved. You should also decide whether collaborative reporting emphasizes sole credit or shared contribution. For collective work, contribution usually gives a more accurate picture than assigning one organization exclusive ownership of a complex outcome.

4. Build a Shared Data Compact

A data compact gives you a lightweight operating agreement for shared reporting. It does not require every agency to adopt the same case-management system or abandon its existing funder requirements.

You can begin with a practical agreement that covers several essential decisions:

• Which client identifier or matching logic you will use

• Which shared terms you will define and maintain

• Which data each agency owns

• Which aggregate measures the collaborative owns

• Who can access individual-level information

• Who reports to the community, county, and funders

• How often partners submit or review information

• How you will correct errors and resolve disagreements

You should also include privacy and consent expectations. A shared intake process can improve access, but it should not create uncertainty about how personal information moves between agencies. Each partner should understand what information it collects, what it shares, why it shares it, and who can view it.

For example, you might define the collaborative snapshot as a monthly view of unique people, completed referrals, services delivered, and selected outcomes. Each agency can continue using its own program dashboard for detailed operations. The shared snapshot gives leaders a common view without forcing every partner into an identical workflow.

5. Create One Monthly Snapshot

A shared snapshot turns the data compact into a repeatable management practice. Without a recurring review, definitions can drift, missing data can accumulate, and partners may discover inconsistencies only when a major report is due.

Your monthly snapshot should remain focused. You can include:

• Unique people served across the collaborative

• Agency-level service activity

• Referrals made and received

• Referral completion

• Common outcomes

• Data quality concerns

• Questions requiring partner decisions

You should pair the snapshot with a short discussion. The goal is not to rank agencies or create a new compliance burden. The goal is to identify what the shared data suggests and what action you should take next.

For instance, a rise in referrals with few completed handoffs may point to a scheduling, transportation, communication, or eligibility barrier. You cannot identify that pattern reliably if each agency uses a different definition of “completed referral.”

A monthly rhythm also gives you a defensible reporting history. When a county leader or funder asks how the collaborative is progressing, you can show how the measurement approach works over time instead of assembling a last-minute spreadsheet.

6. Prepare for Regional Collaboration

The CommunityLink model matters beyond Shelby County. Shared-service models, backbone organizations, and collective-impact efforts continue to develop across Kentuckiana. Co-location is often the first step toward stronger coordination and joint funding requests.

A joint proposal built from incompatible definitions creates unnecessary risk. One agency may report households, another may report individuals, and another may report contacts. One partner may count a referral when it is made, while another counts it only after a service occurs.

You can prevent that problem by establishing the data compact before a major grant opportunity appears. You can then describe the collaborative’s shared outcomes, reporting cadence, and quality controls with greater confidence.

The Genesis Strategic Consulting blog includes additional guidance on grant reporting, data preparation, and operational reporting systems. These practices can help you connect program activity to board- and funder-ready evidence without requiring every partner to hire a full-time analyst.

Final Thoughts

The Mary Jane Reed and Robert W. Reed CommunityLink gives Shelby County an impressive platform for access, navigation, and collaboration. The next essential step is creating a shared language for people served, services delivered, referrals completed, and outcomes achieved.

If you are part of a co-located nonprofit group, backbone organization, or community collaborative, the Genesis Reporting Diagnostic can help you identify definition gaps, clarify reporting ownership, and establish one shared snapshot with a practical monthly rhythm.

The building can bring partners together. Your data compact can help you tell the community’s story accurately, consistently, and with the confidence that future funding decisions require.