Nonprofit Program Referral Guide
A nonprofit referral-routing page that helps staff compare sample program scopes, find the approved eligibility source, and prepare a partner handoff without storing beneficiary case records in Sites.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Community nonprofits · Social services · Workforce development organizations · Community health and support networks
Overview
The Nonprofit Program Referral Guide is a service-oriented intranet page for staff who need to route a potential referral without treating a summary page as an eligibility decision. Its fictional Harborlight Community Network example compares three program scopes: first contact and general service navigation, employment-readiness workshops and coaching, and community connection and practical support navigation. A companion column identifies the approved eligibility or scope source staff must consult for each sample program.
The page is useful when program staff or partner coordinators need a quick starting point before discussing a service or preparing a handoff. It includes decision scenarios for straightforward and ambiguous needs, five ordered referral preparation steps, answers to common handoff questions, and a worked example where two program scopes appear relevant. That example demonstrates the key action: pause and ask the responsible program role rather than infer eligibility from the comparison.
This guide is not an eligibility policy, referral form, case-management record, or substitute for local privacy and consent procedures. It does not establish program availability, acceptance, response times, or a universal partner channel. Before publishing, replace fictional content with confirmed program scopes, approved source references, responsible roles, and the established handoff route for each location. Keep beneficiary details in the organization's approved system, not Sites. The sample identifies the Public Service and Program Operations owner and calls for review when a program scope, eligibility source, or partner handoff changes; set any additional review cadence your organization requires.
Standards & compliance context
- The template directs staff to consult current approved eligibility guidance rather than treating its illustrative program comparison as an eligibility determination.
- Its sample referral steps defer consent, required information, and permitted sharing to the applicable approved process; confirm local privacy and confidentiality requirements before use.
- The page explicitly excludes beneficiary case records and follow-up details from Sites, directing staff to the organization's approved process and system.
- Use accessible headings, readable table labels, and clear instructions that do not rely on color alone, consistent with WCAG 2.1 AA practices for intranet content.
- The template does not establish compliance with any jurisdiction-specific law or regulation; have the appropriate organizational owner review local requirements and source references.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Which service path should I check?
Start with the stated need, then use the current approved source for the relevant program and location.
-
A routing reference for program staff and partner coordinators Fictional example: Harborlight Community Network is a nonprofit with three sample programs. Use the distinctions below to identify the approved eligibility source to consult—not to decide eligibility from this page. Check the current approved source for the program and location before discussing or making a referral. Sites is for this routing guidance, not beneficiary case records; handle referral information only through the organization's approved process.
Compare the sample program scopes
Use these fictional distinctions to find a source to consult, not to decide eligibility.
-
Illustrative distinctions only. Each program's approved eligibility source—not this comparison—determines whether a referral fits. Harborlight Welcome Desk First contact and general service navigation Welcome Desk service scope and current intake guidance Harborlight Skills Pathway Employment-readiness workshops and coaching Skills Pathway eligibility guidance and current program scope Harborlight Neighbour Support Community connection and practical support navigation Neighbour Support service scope and current referral guidance
Choose a path—or pause
These scenarios show when to check a program source and when to stop for clarification.
-
Use the stated need to guide which approved source to check; do not infer eligibility. The person needs help finding the right service Check the Welcome Desk scope and current intake guidance. If the need points to a specific service, consult that program's approved source too. The person asks about employment-readiness support Check the Skills Pathway eligibility guidance and scope before describing it as a possible fit. The need spans programs or remains unclear Pause before referring. Ask the responsible program lead which approved source and handoff route apply. The receiving partner cannot accept the referral Follow the established partner handoff process and ask the program lead to identify an appropriate next step; do not promise an alternative service.
Prepare and hand off a referral
Follow the organization's approved process for permitted information and the established partner channel.
-
Follow the organization's approved process for the program and location. This sequence is a coordination aid, not a substitute for an approved referral procedure. Check the approved source Consult the current eligibility guidance and scope for the program. If you cannot identify the applicable source, ask the responsible program role before proceeding. Explain the proposed path Describe the program's scope in plain language and avoid promising acceptance or eligibility. Give the person a chance to ask questions. Prepare only permitted information Use the information and consent steps required by the applicable approved process. Do not put beneficiary details in Sites. Use the established partner channel Send the referral through the approved channel for that program and location. Include only information permitted by the process. Clarify the next step Use the established handoff process to confirm what the receiving partner will do next. If the referral cannot proceed or the next step is unclear, consult the responsible program role.
Questions that come up during routing
Use these answers to avoid guessing about missing information, partner decisions, or case-record storage.
-
The need seems to fit, but the eligibility source is unclear. Should I refer? Do not guess. Ask the responsible program lead which current approved source applies and what handoff route to use. Some referral information is missing. Can I send what I have? Check the applicable approved process for required information and what can be shared. If it does not say what to do, ask the responsible program role before sending anything. The partner cannot accept the referral. What should I tell the person? Explain only what the partner has confirmed. Follow the established handoff process and ask the program lead about an appropriate next step; do not promise a place, service, or response time. Can I save referral details here so another coordinator can follow up? No. This page is a routing reference, not a beneficiary case record. Use only the organization's approved process and system for referral information and follow-up.
Worked example: when two scopes seem possible
The example shows why staff should consult the responsible program role when available guidance does not resolve an overlapping need.
-
A coordinator at Harborlight hears that a person wants help with both finding local support and preparing to return to work. The coordinator checks the Welcome Desk scope and the Skills Pathway guidance. The available approved guidance does not establish that either program is the right fit for this combination. Rather than choosing based on the comparison, the coordinator pauses and asks the responsible program lead which source and partner handoff apply. The coordinator has the stated service need and the source already checked ready to discuss, and shares any further information only as the approved process permits. The program lead clarifies the route before a referral is sent. Ownership: The responsible program role clarifies ambiguous scope and handoffs. The Public Service and Program Operations owner maintains this guide against approved program sources; review it when a program scope, eligibility source, or partner handoff changes.
How to use this template
- Replace the fictional program names and scope descriptions with confirmed services, and identify the current approved eligibility source and handoff route for each program and location.
- Assign a guide owner and responsible program roles, then verify who can clarify ambiguous scopes and what change triggers a page review.
- When a service need arises, compare it with the listed scope and consult the relevant approved source before describing the program as a possible fit.
- Explain the proposed path without promising eligibility or acceptance, then follow the approved process for consent and permitted referral information.
- Send only permitted information through the established partner channel, and use the handoff process to clarify what happens next.
- If the source, required information, partner response, or next step is unclear, pause and ask the responsible program role; do not record beneficiary details in Sites.
Best practices
- Label sample scopes as illustrative and place the approved eligibility source beside each program so staff do not mistake the comparison for a decision rule.
- Name the applicable program and location in source references where requirements differ, and verify each destination before publishing.
- Keep the referral sequence focused on actions staff can take: check the source, explain the path, prepare permitted information, use the approved channel, and clarify the next step.
- State plainly that Sites is not for beneficiary case records, and identify the organization's approved system or process without inventing a destination.
- Use role names such as responsible program role in the guide, then replace them only with confirmed ownership information.
- Review the page whenever a program scope, eligibility source, or partner handoff changes, and record any required review cadence according to organizational practice.
- When more than one scope seems possible, tell staff to pause and consult the responsible role rather than choose from the comparison table.
- Keep partner outcomes qualified: describe only what the receiving partner has confirmed, and avoid promises about acceptance, alternative services, or response times.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Does this guide determine whether someone is eligible for a program?
No. Its comparison table shows illustrative program scopes and names the approved source staff should consult. Eligibility decisions must follow the current approved guidance for the relevant program and location. If the applicable source is unclear, pause and ask the responsible program role.
Which programs and locations does this template cover?
The example uses three fictional Harborlight Community Network programs: Welcome Desk, Skills Pathway, and Neighbour Support. Their descriptions are sample content, not claims about real services or local eligibility. Replace them with confirmed program scopes and approved source references for your organization and locations.
Who should run the referral process, and who maintains this page?
Program staff or partner coordinators can use the page to check a service path and prepare a handoff. The sample assigns guide maintenance to the Public Service and Program Operations owner, while the responsible program role clarifies ambiguous scope and handoffs. Substitute roles only after confirming your organization's ownership.
How often should the guide be reviewed?
The example calls for review when a program scope, eligibility source, or partner handoff changes. Set an additional routine review cadence if your organization requires one, and show the review owner and trigger on the page. Do not imply the guide is current until its references have been checked.
Can staff store beneficiary details or follow-up notes in Sites?
No. The page explicitly serves as routing guidance, not a beneficiary case record. Staff should use only the organization's approved process and system for referral information, consent, and follow-up. If that process is unclear, ask the responsible program role before sharing information.
What should staff do when a referral is incomplete or a partner cannot accept it?
Check the applicable approved process to determine what information is required and permitted before sending anything. If the partner cannot accept the referral, follow the established handoff process and ask the program lead about an appropriate next step. Do not promise eligibility, acceptance, a substitute service, or a response time.
Can we adapt this guide for our programs and referral channels?
Yes. Replace the fictional program names, scopes, source references, ownership roles, and handoff instructions with confirmed local information. Keep the distinction between routing guidance and eligibility decisions, and preserve the instruction not to store beneficiary case records in Sites. Remove any program row that does not have a verified source and handoff route.
Does this template connect to eligibility databases or partner systems?
No connection is specified in the supplied page structure. Program names and source descriptions are authored page content, not live eligibility data or referral workflows. Add links or connected blocks only through your site's supported setup, after verifying the destination and access requirements.
Why use a structured guide instead of asking a colleague each time?
The comparison table, routing scenarios, ordered handoff steps, and worked example make the intended checks visible in one place. The guide does not replace program expertise: staff should still pause and consult the responsible role when scopes overlap or sources are unclear. Keep the page aligned with approved references so it does not become a competing or stale policy.
What regulatory or privacy rules does the template satisfy?
The page is not a legal or regulatory determination and does not name a jurisdiction-specific standard. Its sample content directs staff to use approved processes for consent, permitted information, and referral handling, and excludes beneficiary case records from Sites. Have the appropriate privacy or compliance owner confirm local requirements before publishing.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Nonprofit Program Referral Guide ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
