Referral basics
Identify the student and context.
Collect school identifiers, referrer, date, grade, classroom or courses, and a broad routing category.
- Student identifier and grade.
- Referrer role and contact.
- Classroom, period, and date.
Describe your school's referral process. Makeform builds a focused form for student strengths, teacher observations, prior strategies, and requested support.
Route referral records to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a starting point, adapt it, and send it to the Makeform builder.
Audience
Classroom teachers referring students for learning support
Format
Structured referral with skill-area branching
Prompt size
324 chars
Example form structure
Structured referral with skill-area branching
Student, grade, classroom, and referring teacher
Strengths, interests, and successful conditions
Which academic skill areas need review?
Strategies tried, duration, and student response
What support or decision are you requesting?
Suggested routing tags
Academic support
Attendance follow-up
Classroom participation
Ask for frequency, duration, setting, and a recent example. Specific observations give the team more to work with than labels such as unmotivated or disruptive.
Step 1
Observe
record a specific pattern, setting, and recent example
Step 2
Try
list strategies, duration, consistency, and student response
Step 3
Refer
request a focused review from the student support team
Step 4
Plan
route the record into discussion and follow-up
Better referral inputs
Separate direct observation from interpretation, record prior action, and state the help requested.
Prompt for a recent example, setting, frequency, duration, and classroom effect without asking teachers to assign labels.
Repeat fields for the strategy, start date, frequency, duration, and observed response.
End with the help needed: consultation, observation, monitoring, coordination, or a meeting.
Flexible by school level
Keep core fields consistent and show conditional questions by concern and grade span.
Capture skill areas, routines, strengths, family communication, and strategy responses.
Compare patterns across subjects, periods, transitions, and staff observations.
Organize course, assignment, attendance, and support patterns across classrooms.
Show academic, attendance, participation, or behavior follow-ups only when selected.
Build the referral workflow
Start with the questions your team reviews, then refine them for concrete classroom information.
Name the school level, referrers, concern categories, prerequisite steps, and possible team outcomes.
Add short examples, require only essential questions, use team language, and remove unused fields.
Show follow-ups based on concern type or grade span so teachers see relevant questions.
Publish the form and route submissions to the team's notification or tracking destination.
Referral form vs email
A structured form collects dates, strategies, and examples in the same order each time.
Field guide
Six field groups keep referrals centered on observable information and a defined request.
Referral basics
Collect school identifiers, referrer, date, grade, classroom or courses, and a broad routing category.
Strengths
Ask about interests, successful settings, relationships, routines, and conditions where the concern is less visible.
Concern description
Ask what happened, where, when, how often, and for how long. Prefer dated examples over trait labels.
Strategies tried
Repeat fields for each strategy so reviewers can compare duration, consistency, and observed change.
Perspectives and contact
Capture relevant student input, family communication, staff consultation, dates, and factual summaries.
Requested support
Let the teacher select a support type and ask the team a short question, with separate urgent routing.
Related tools
Connect referrals with progress, attendance, family feedback, work samples, and incident records.
Document distinct incidents separately from referrals.
Open toolFAQ
Answers for teachers and teams designing consistent referral intake.
It is a structured request for support. It records strengths, observable concerns, setting and frequency, prior strategies, student response, communication, and the support requested.
Include a recent example, frequency, setting, strengths, strategies tried, implementation duration and consistency, and observed change. Add relevant conversations or files when useful.
Ask what was seen or heard, when and where it occurred, how long it lasted, and what happened before and after. Use dated examples and avoid prompts asking teachers to diagnose causes.
Yes. Keep identity, strengths, concern, strategies, contacts, and requested support shared. Show academic, attendance, or classroom follow-ups conditionally.
Use one repeating block per strategy with its goal, start date, frequency, duration, staff responsible, consistency, and observed response.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and use the referral form without a response cap. The paid tier removes the Makeform badge.
The form can display existing urgent-routing instructions, but it should not replace immediate-response procedures. Keep routine and same-day routes distinct.
Define who receives it, where it is reviewed, how missing information is requested, when discussion occurs, and where next actions are recorded.
Give every referral a useful starting point.