Family-service nonprofits depend on strong referral networks to connect clients with housing assistance, food programs, counseling, healthcare, employment resources, childcare, and emergency services. Unfortunately, much of that referral knowledge lives in experienced employees instead of approved organizational documentation.
When a case manager leaves, retires, or changes roles, valuable knowledge about trusted community partners, referral requirements, eligibility criteria, and escalation procedures often disappears with them. New employees spend months rebuilding relationships and rediscovering information the organization once knew.
To retain institutional knowledge, referral processes must become organizational assets instead of personal expertise.
Referral Networks Change Constantly
Community resources evolve throughout the year.
Partner organizations modify eligibility requirements. Contact people change. Programs reach capacity. New funding becomes available while older programs disappear.
Without a structured process for updating this information, employees begin relying on outdated spreadsheets, email threads, handwritten notes, or verbal recommendations.
Critical referral knowledge often includes:
- Community partner directories
- Eligibility requirements
- Required documentation
- Intake procedures
- Program limitations
- Emergency contacts
- Escalation paths
- Follow-up expectations
- Referral forms
- Approval requirements
The Administration for Children and Families provides information on many federal family-support programs, while the 211 Network helps connect individuals with local community resources. Each nonprofit must still maintain its own approved referral procedures and trusted partner information.
Create a Governed Referral Knowledge Base
SharePoint provides a central location for organizing approved referral guidance.
Each referral resource should identify:
- Program owner
- Organization contact
- Last verification date
- Required documentation
- Eligibility notes
- Related forms
- Internal approval requirements
- Review schedule
Program managers should own service procedures, while leadership establishes governance for reviewing and updating referral information.
To retain institutional knowledge, every important referral process should have an assigned owner instead of relying on institutional memory.
Preserve Authoritative Systems
SharePoint should organize operational guidance—not replace operational systems.
The case-management platform remains authoritative for client records and referral history.
The CRM remains authoritative for partner relationship management when applicable.
Accounting software remains authoritative for payments and financial records.
SharePoint explains how employees should use those systems while maintaining approved procedures, templates, FAQs, and resource directories.
Access to confidential participant information should remain restricted through Microsoft 365 permissions. Public resource information may be widely available, while case notes, participant records, legal documentation, and financial information require tighter security boundaries.
Give Employees Immediate Access to Approved Guidance
Maisy allows staff to retrieve approved referral guidance through natural conversation.
Pixeldust configures Maisy through Copilot Studio using SharePoint as the governed knowledge source. Employees can ask questions such as:
- Which housing partner serves this county?
- What documentation does this agency require?
- Where is the current referral form?
- Who approves emergency referrals?
- Which organization should receive this client?
Maisy retrieves approved guidance based on each employee’s Microsoft 365 permissions. It does not determine client eligibility, select service providers, approve exceptions, interpret regulations, or replace professional judgment.
How Maisy Helps
Pixeldust works with family-service nonprofits to identify undocumented referral knowledge, outdated partner information, duplicate resource lists, and inconsistent procedures. We organize approved content within SharePoint, establish ownership and review schedules, configure Microsoft 365 permissions, and build Maisy through Copilot Studio to retrieve trusted guidance.
The result is faster referrals, more consistent service delivery, reduced dependency on individual employees, and a practical way to preserve critical organizational knowledge as staff, partners, and community resources continue to evolve.
