Homelessness nonprofits rarely work alone. Outreach teams, shelters, housing navigators, healthcare providers, food programs, government agencies, and community partners may all support the same population.
Coordination breaks down when employees cannot quickly find current referral procedures, partner requirements, program limits, or internal responsibilities. Staff may duplicate work, send incomplete referrals, or provide conflicting instructions because critical guidance is scattered across email, spreadsheets, meeting notes, and personal contact lists.
Why Coordination Knowledge Becomes Fragmented
Each program develops its own procedures and relationships. One team knows the shelter network, another manages rental assistance, and another coordinates healthcare or transportation.
Important coordination knowledge may include:
- Partner contact information
- Referral requirements
- Eligibility guidance
- Required documentation
- Service-area boundaries
- Capacity-check procedures
- Consent requirements
- Escalation contacts
- Follow-up responsibilities
- Program ownership
To retain institutional knowledge, nonprofits must capture these operational details without copying confidential participant records into general documentation.
The HUD Exchange homelessness assistance resources provide federal guidance for homelessness programs. Each organization must still document how its own teams and partners coordinate services.
Define Ownership and Approval
Every referral pathway and coordination procedure should have an identified owner.
Program directors may own service procedures. Partnership managers may maintain agency contacts. Compliance staff may approve consent and information-sharing guidance. Leadership may control emergency exceptions and organizational commitments.
Each resource should identify:
- The responsible owner
- The approving authority
- The last verification date
- The next review date
- The intended users
- Related forms and checklists
- The authoritative operational system
- The escalation process
This keeps informal workarounds and outdated partner information from becoming accepted practice.
Use SharePoint for Approved Guidance
SharePoint can serve as the governed source for referral procedures, partner directories, blank forms, FAQs, and coordination checklists.
The case-management system remains authoritative for participant records, assessments, referrals, and service history. A CRM may remain authoritative for formal partner relationships. The accounting system remains authoritative for financial transactions.
SharePoint should explain how staff use those systems correctly without duplicating protected records.
Permissions must separate general service guidance from confidential participant, medical, legal, financial, HR, and safeguarding information.
Make Coordination Guidance Searchable
Maisy gives authorized employees a conversational way to retrieve approved guidance.
Pixeldust configures Maisy through Copilot Studio using SharePoint as the governed knowledge source. Microsoft’s Copilot Studio SharePoint documentation explains how agents can retrieve SharePoint content according to the signed-in user’s permissions.
Employees can ask:
- Which partner handles this type of referral?
- What documentation is required?
- Who owns the follow-up?
- Where is the current consent form?
- Which system contains the official participant record?
Maisy can retrieve approved information. It should not determine eligibility, promise service availability, authorize spending, assess participant safety, or replace case managers and program leaders.
How Maisy Helps
Pixeldust identifies duplicate resource lists, undocumented coordination practices, outdated contacts, and repeated staff questions. We work with leadership to verify guidance, assign ownership, establish review dates, define authoritative systems, and apply Microsoft 365 permissions.
Approved content is organized in SharePoint, then Maisy is configured through Copilot Studio and tested against realistic coordination questions.
This gives teams faster access to trusted guidance, improves handoffs across programs, and helps the organization retain institutional knowledge without replacing case-management systems or human decision-makers.
