Describe the concern and school process. Makeform creates a student warning form with observed facts, prior support, expected changes, follow-up dates, and acknowledgments.
Route completed forms to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose an example, adapt it, or send it to the builder as a starting point for your school's review process.
Audience
Teachers and administrators documenting repeated disruption
Format
Formal warning with student response and review date
Prompt size
318 chars
Example form structure
Formal warning with student response and review date
Student, grade, course, and staff member
What was directly observed?
Prior reminders or supports
Expected change and follow-up date
Student comments and acknowledgments
Suggested routing tags
Behavior warning
Academic warning
Follow-up due
Separate observed facts from interpretations, and give every warning a named follow-up date so the record shows what happens next.
Step 1
Document
record facts, dates, context, and prior support
Step 2
Explain
state the expectation and needed change
Step 3
Acknowledge
capture responses and receipt from each party
Step 4
Follow up
assign an owner, date, and next review
A useful warning record
Preserve what happened, let the student respond, define improvement, and make follow-up visible.
Prompt staff for dates, locations, observations, and earlier interventions instead of vague labels.
Give the student a response area and note who joined the conversation.
Capture the improvement target, support, owner, and review date together.
Common school workflows
Choose the closest workflow, then match its language, roles, and supports to school policy.
Observed behavior, expectations, prior redirection, student response, and check-in.
Missing work, dated indicators, outreach, tutoring, milestones, and review.
Attendance dates, contact attempts, student context, goals, and staff owner.
Team expectations, conduct, coaching, participation conditions, and acknowledgment.
Build the workflow
Generate the structure, add your school's process, route it to the right people, and keep the review date with the warning.
Choose behavior, academics, attendance, or activity conduct, then name the roles involved.
Add expectations, support options, acknowledgments, internal notes, and routing choices.
Use conditional sections for concern type, prior intervention, family contact, or administrator review.
Send the warning to designated recipients and use its follow-up date for the next conversation.
Choosing a format
A structured form gathers consistent facts, responses, actions, and follow-up details.
Field guide
Create a specific record while leaving room for student perspective and school support.
Student and school context
Collect only the student identifiers and school context needed to route the warning.
Observed concern
Ask for direct observations, dates, and work examples. Keep interpretation separate.
Prior interventions
Use a checklist to summarize reminders, conferences, tutoring, changes, or referrals.
Student response
Provide space for explanation, questions, disagreement, or a request for support.
Plan and expectations
State observable improvement, school support, ownership, and when progress will be reviewed.
Acknowledgment and review
Label each field as receipt, meeting participation, or agreement to an action step.
Related school tools
Use live Makeform tools for incident intake, progress updates, attendance records, family meetings, detention, and broader school reporting.
Capture an initial behavior event before staff decide whether a formal warning is appropriate.
Open toolDocument academic progress and compare later results with the goals in a warning.
Open toolSchedule family conversations connected to an academic or behavioral follow-up.
Open toolCollect attendance information when absence or tardiness is the central concern.
Open toolBuild a separate detention workflow when that action is part of school procedure.
Open toolCreate a broader school report for patterns that extend beyond one warning or course.
Open toolFAQ
Practical answers for administrators, teachers, counselors, and activity leaders building a consistent warning process.
It documents a behavioral, academic, attendance, or conduct concern and the conversation that follows: observed facts, prior interventions, expectations, student response, improvement steps, support, acknowledgment, and follow-up.
Include student and staff details, concern type, dates, factual description, earlier interventions, student comments, expected improvement, school support, owner, review date, and acknowledgments. Add internal notes only when needed.
Yes. Use a concern-type question and conditional sections. The behavior path can ask about conduct and expectations; the academic path can ask about assignments, performance, outreach, and milestones.
Not necessarily. Label acknowledgments precisely. A signature can record receipt or meeting participation without stating agreement. A response field lets the student add context or disagreement.
Enter directly observed actions, dates, locations, assignments, attendance events, or other examples. Keep conclusions separate, avoid vague labels, and invite student context.
You can collect family contact details and configure notifications or exports. Decide who gets a copy, which internal notes stay restricted, and how acknowledgment occurs.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge.
Record a follow-up date, responsible staff member, expected change, and school support. At review, document progress, student input, unresolved concerns, and the next school-defined action.
Make every warning point toward a next step.
