REPORT
Why updating resource directories is so difficult — and how Jinship solves it
The problem is not simply that nonprofits need a better directory. The deeper issue is that resource information lives in fragmented silos, changes quickly, and is rarely maintained inside the real workflow where new information is actually learned.
The core thesis
1
Directory accuracy breaks when maintenance is treated as separate admin work instead of being captured at the moment of outreach and verification.
THE PROBLEM
The information layer is fragmented by default
Open Referral describes community resource data as fragmented, redundant, and spread across disconnected systems, which makes it hard for people to see the safety net and hard for providers to stop re-checking data instead of helping clients. In practice, that means directories live across shared drives, Google Docs, spreadsheets, PDFs, emails, and individual staff memory all at once.
Information is scattered
Teams inherit messy internal folders and local workarounds, so the directory is usually a patchwork, not a maintained system.
Records drift quickly
Capacity, waitlists, hours, intake rules, and phone responsiveness change constantly, which means “accurate last month” is often wrong now.
Knowledge becomes tribal
Frontline workers often know which programs are actually usable, but that knowledge sits in private notes and experience rather than a shared operating layer.
Open Referral’s strategic overview says repeated efforts to create centralized directories still yield more and more sources of less and less reliable information because the production and sharing of resource data remains fragmented.
WHY IT IS HARD
The workflow breaks in predictable places
Keeping resource information current requires repeated verification, but the people closest to the truth are already overloaded and usually not incentivized to maintain every directory that depends on them.
Messy source files
The starting point is unstructured and duplicated.
Outreach happens
Staff learn new facts during real calls and referrals.
Notes stay local
Updates get buried in personal notes or memory.
No one syncs it
Editing the directory later becomes optional work.
Team repeats effort
Coworkers hit the same dead ends again.
OPERATIONAL STRUGGLES
What staff and managers actually feel
The visible pain is not abstract data quality. It shows up as wasted calls, inconsistent quality across staff, slow onboarding, and no shared view of which resources are really usable right now.
Frontline reality
Caseworkers lose time to avoidable friction
Calling numbers that no longer work.
Re-checking agencies already checked by teammates.
Relying on institutional memory to avoid dead ends.
Doing verification work that never compounds.
Management reality
Leadership lacks a live operating picture
Different staff hold different versions of reality.
New hires depend on tribal knowledge.
There is no clean way to see stale or hard-to-reach resources.
Directory maintenance feels necessary but never complete.
WHY IT HAS NOT BEEN FIXED
This is a supply problem, not just a search problem
Open Referral argues that communities keep producing more unreliable sources because providers lack strong incentives to update every directory and because interoperability and governance, not just interface design, are the underlying challenge. That is why better search alone does not solve stale data.
ASSUMPTION 1
Build a better directory
This improves presentation, but not the production of trustworthy updates.
ASSUMPTION 2
Let providers self-update
Open Referral notes provider self-reporting is unreliable because ownership is unclear, requests are repetitive, and maintenance is rarely the top priority.
ASSUMPTION 3
Use AI to clean it up
Open Referral says AI alone is poorly suited to fix the resource directory dilemma when the underlying records themselves are weak and fragmented.
REALITY
The hard part is sustained maintenance
The same organization may appear under multiple names and still require local knowledge plus manual review to align datasets, which shows how stubborn the data maintenance problem really is.
WHY DATA DECAYS
The ecosystem keeps asking for updates the same wrong way
Open Referral’s strategic framing is that without common infrastructure, communities keep paying to recreate the same resource information in siloed systems. That is why the old model creates administrative fatigue instead of durable trust.
Periodic surveys
Too infrequent to reflect changing capacity.
Self-service portals
Depend on provider time they often do not have.
Search upgrades
Help people navigate stale information more efficiently.
AI-only workflows
Still inherit the quality limits of the source data.
“More and more sources of less and less reliable information” is the trap. Jinship needs to win by changing the maintenance loop, not by becoming one more directory.
Grounded in Open Referral’s strategic overview.
THE SOLUTION
Jinship turns outreach into the update engine
The product logic is simple: ingest the messy directory teams already have, give them a web-based system of record, and let staff update live status in one click while they conduct outreach. That directly attacks the gap between learning new information and recording it for the whole organization.
Ingest
Pull from drives, docs, spreadsheets, and files teams already use.
Normalize
Convert scattered resource data into a shared web directory.
Outreach
Staff call, verify, and learn what is true in the moment.
One-click status
Mark accepting, waitlist open, full, no answer, or outdated info instantly.
Shared memory
The whole team sees the latest operational signal, not just the individual worker who learned it.
WHY THIS WORKS
It solves the exact points where the old model breaks
Jinship works because it lowers update friction, converts tribal knowledge into shared memory, and makes the directory better as teams use it rather than asking them to maintain it separately. That is the opposite of the older “please update your directory later” workflow.
Lower friction
92
Capture live knowledge
88
Reduce duplicate outreach
84
Create system intelligence
79
Open Referral frames the long-term opportunity as improving resource data quality, reducing production costs, improving service delivery, and generating better intelligence for policy and allocation. Jinship fits that logic by making updates operationally cheap and analytically useful at the same time.
THE SOLUTION
Jinship turns outreach into the update engine
The product logic is simple: ingest the messy directory teams already have, give them a web-based system of record, and let staff update live status in one click while they conduct outreach. That directly attacks the gap between learning new information and recording it for the whole organization.
ONE-LINE PITCH
Resource directories fail because updates are separated from the real work
Jinship fixes that by making outreach itself the maintenance loop, so every verification step improves the shared directory, reduces repeated dead ends, and creates a live map of friction across the safety net.
Not another directory
— a living operations layer for keeping resource information useful.
jinship
contact hello@jinship.com for any questions :)