Student Support Referral Guide
The Student Support Referral Guide helps staff match a learning, personal, or practical concern to the right locally approved first role. It clarifies privacy boundaries and when to use local urgent procedures.
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: K–12 education · Higher education · Vocational and technical education · Multi-campus learning networks
Overview
The Student Support Referral Guide is a reference page for staff deciding which local role to consult first when a student concern affects learning access, personal wellbeing, or practical participation. Its opening guidance says to start with the kind of help needed, then follow the approved route for the student's campus or school. A comparison table makes the three concern patterns and their illustrative first-role categories easy to scan.
The page uses fictional Northbridge Learning Network examples to show how a staff member might handle course access difficulty, a personal concern, or a practical barrier. These examples describe referral coordination, not an assessment of a student's needs. The FAQ reinforces the privacy boundary: do not use the guide as a case record or put sensitive details in a broad staff message. Share only what the local approved process requires through its designated channel.
Use this template as a starting point for a staff-facing referral reference after local owners confirm role names, channels, privacy instructions, and urgent handoffs. It is not a student intake form, clinical resource, emergency contact directory, or substitute for safeguarding and other approved procedures. If local guidance differs, the relevant campus or school's process takes precedence. The fictional example names Campus and Academic Operations as the content-owner role; adopting organizations should identify their own accountable owner and correction path, and update the page when routes change.
Standards & compliance context
- Treat this page as staff navigation guidance, not a student case record, clinical advice, or authorization to assess a concern.
- Follow applicable privacy and student-record requirements through the locally approved process, and share only information that process requires.
- Use the designated local urgent-response procedure when a concern may need immediate attention; this template does not supply emergency contacts.
- Check the page for WCAG 2.1 AA accessibility, including meaningful headings, readable table structure, keyboard access, and sufficient contrast.
- Have the appropriate local policy owner verify that role descriptions and handoff instructions align with current safeguarding and institutional procedures.
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
Choose the right first conversation
Start by identifying the kind of help needed and checking the approved route for the student's campus or school.
-
A staff reference for matching a concern to a locally approved support route Start with the kind of help needed. For a learning or access barrier, consult the role responsible for learning support. For a personal concern, use the designated trained support role. For a practical barrier, consult the relevant student-services role. Follow the approved route for the student's campus or school. Northbridge Learning Network is a fictional example used to make the referral choices concrete. This guide supports staff navigation only; do not use it for student case records or clinical advice. Local approved procedures govern decisions, privacy boundaries, and urgent handoffs.
Match the concern to a first role
Use these illustrative patterns to select a role to consult, then confirm the local handoff process.
-
Illustrative role categories only; use the approved route for your campus or school. Learning participation or access Repeated difficulty opening course materials or following a learning activity Learning-support role — clarify the learning barrier and the appropriate support route. Personal or wellbeing concern A student raises a personal concern that staff should not assess or discuss broadly Designated trained support role — make a discreet handoff through the locally approved process. Practical barrier A practical issue appears to be affecting attendance or participation Relevant student-services role — identify the service area and the approved way to connect the student.
See how the distinction works
These fictional scenarios show how staff can coordinate a referral without assessing a student's needs.
-
These fictional examples show referral coordination, not an assessment of a student's needs. Course access difficulty A student reports that course materials have been difficult to access across several sessions. The staff member consults the learning-support role about the approved route, rather than forwarding course notes to a broad group. A personal concern A student mentions a personal issue after class. The staff member avoids probing for details in a group setting and connects with the designated trained support role using the local process. A practical barrier and a careful handoff A staff member notices that a practical issue is interrupting participation. In an approved referral channel, they share only the context needed to identify the right service area and handoff; they do not copy the full conversation into a general message.
Keep the handoff appropriate
Keep sensitive information out of general messages and follow local privacy and urgent-response procedures.
-
If local guidance differs, follow the approved process for the relevant campus or school. What information belongs in a referral? Use the information and channel specified by the locally approved referral process. Share only what is needed for the receiving role to understand the reason for the handoff. Do not use this intranet page as a record of a student's case. Should I include details in a general message or in this guide? No. Do not put identifiable student details or sensitive case information in this guide or a broad staff message. Use the designated, approved route and follow its privacy instructions. What if I cannot tell which role is appropriate? Consult the local referral process owner or the designated trained support role for your campus or school. Do not send the concern to a broad distribution list simply to find an owner. What if the concern may need immediate attention? Use the urgent process approved for the relevant campus or school and involve the designated local role. This guide does not provide emergency contacts or replace local urgent-response procedures.
Make the local handoff
Use the approved local channel and keep the route details current through the accountable content owner.
-
Before referring a concern, consult the approved route for the staff member's campus or school and use its designated channel. If the concern may require immediate attention, follow that location's designated urgent process rather than relying on this general guide. Campus and Academic Operations is the content-owner role for this fictional example. The accountable local owner maintains the route details and directs staff to the appropriate correction or help path.
How to use this template
- Replace the fictional network and illustrative role categories with locally confirmed names, responsibilities, and approved referral routes.
- Ask the accountable local process owner to verify the designated channels, privacy instructions, urgent handoff wording, and correction path before publishing.
- Publish the page where staff can find it during student-support conversations, and explain that it guides navigation rather than recording cases or assessing needs.
- When a concern arises, identify whether it is primarily about learning access, a personal concern, or a practical barrier, then consult the corresponding local role and process.
- Share only the information the approved route requires, using its designated channel rather than this page or a broad staff message.
- Review the page when roles, channels, or procedures change, and direct staff to the local urgent process whenever immediate attention may be needed.
Best practices
- Use locally recognized role names and verify that each role is authorized to receive the type of referral described.
- Keep the concern categories broad enough to guide a first conversation without implying diagnosis or eligibility decisions.
- State the approved channel beside each handoff instruction so staff do not guess where sensitive information belongs.
- Keep student case details out of the reference page, general messages, and other locations not approved for case information.
- Make the campus or school scope explicit because referral routes may differ by location.
- Identify the content owner and a correction route so staff can report a broken or outdated referral path.
- Review urgent-process wording with the local owner and avoid substituting general guidance for emergency procedures.
- Use the comparison table for quick scanning and keep supporting explanations in short, clearly headed sections.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Which student concerns does this guide cover?
It distinguishes three broad patterns: learning or access barriers, personal concerns, and practical barriers affecting participation. The role categories are illustrative, not a campus directory or a judgment about a student's needs. Staff should confirm the approved route for the student's campus or school.
How often should the referral routes be reviewed?
Review route details whenever local roles, channels, or procedures change, and on the schedule set by the accountable local owner. The example identifies Campus and Academic Operations as the content-owner role, but does not establish a review date or cadence. Add a local review trigger and correction path when configuring the page.
Who should use this guide and who owns it?
Staff use it to choose an appropriate first role and consult the local handoff process. The receiving role depends on the concern and the campus or school. In the fictional example, Campus and Academic Operations owns the guide content; each organization should name its accountable local owner and help route.
Does this template replace safeguarding, clinical, or emergency procedures?
No. It is a staff navigation reference, not clinical advice, a case record, or an urgent-response procedure. Follow the approved local process for safeguarding, privacy, urgent concerns, and other regulated decisions. Have the appropriate local policy owner confirm that the page points staff to authoritative procedures.
What should I do if I am unsure which role to consult?
Check the referral process approved for the relevant campus or school, or ask its local process owner or designated trained support role. Do not send sensitive details to a broad distribution list to locate an owner. If the concern may need immediate attention, use the location's designated urgent process.
What information should a referral include?
Use only the information and channel required by the approved local process. Share the minimum context needed for the receiving role to understand the handoff. Do not put identifiable student details or sensitive case information in this intranet page or a general staff message.
How can we customize the example for our school or campus?
Replace the fictional organization and role categories with confirmed local role names, route details, and approved channels. Preserve the distinction between learning access, personal concerns, and practical barriers only where it fits local procedures. Add a named content-owner role, correction route, review trigger, and the approved urgent-process reference without inventing contact details.
Does the page connect to a referral system or student record?
No connected referral workflow or student-record integration is specified in this template. The page provides static guidance for staff and should not collect or store case details. If your intranet supports links, configure them only to verified, approved local destinations.
How should we roll this out to staff?
Have local support and privacy owners confirm the role mapping, channels, and urgent handoff language before publication. Explain that the page helps staff choose a first conversation but does not authorize assessment or replace local procedures. Tell staff where to report outdated route details, then review the page when those routes change.
Why use this guide instead of asking around informally?
An ad-hoc approach can send sensitive information to people who do not need it or leave staff unsure about the right first role. This page makes the three concern patterns and privacy boundary easy to scan. It still depends on accurate, maintained local routes and does not replace direct consultation when the approved process requires it.
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 Student Support 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.
