Loading...
safety

School Behavioral Threat Assessment Screening and Case Form

School Behavioral Threat Assessment Screening and Case Form documents the initial screen, full-team assessment, management plan, and follow-up for a student threat case. Use it to keep decisions, notifications, and next steps organized.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: K 12 Education · School District Administration · Student Support Services · Campus Safety

Overview

This School Behavioral Threat Assessment Screening and Case Form is built to document a student concern from the first referral through closure. It includes the submission notice and consent acknowledgment, student and case identification, initial screening, behavioral indicators, full-team assessment, management plan, notification log, and sign-off fields so the case stays traceable from start to finish.

Use it when a report suggests a possible threat, escalating behavior, or a pattern of concerning conduct that needs structured review. The form helps the team record what was observed, what sources were reviewed, what risk level was assigned, and what interventions were put in place. It is especially useful when multiple staff members need a shared record and when the school needs an audit trail for decisions, notifications, and follow-up.

Do not use it as a substitute for emergency response. If there is an immediate safety issue, activate the school crisis process and contact emergency services as needed before completing the form. It is also not the right place to collect unrelated personal history or excessive PII. Keep the record focused on the minimum information needed to assess risk, support the student, and protect the school community.

Standards & compliance context

  • The form supports data minimization by limiting collection to information needed for threat assessment and case management.
  • If the form is public-facing or used for self-referral, it should meet WCAG 2.1 AA accessibility expectations, including clear labels and keyboard-friendly controls.
  • Any consent or acknowledgment language should explain what information is collected, who can see it, and what happens after submission.
  • Use role-based access and an audit trail so sensitive student information is only visible to staff with a legitimate need to know.
  • If the case involves disability-related concerns or accommodation needs, the form should allow careful, non-stigmatizing documentation and avoid unnecessary medical detail.

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

Submission Notice and Consent

This section confirms who submitted the concern, whether consent or acknowledgment was captured, and whether the situation required immediate emergency action.

  • Submission Type (required)
  • Your Role (required)
  • Acknowledgment of PII and case handling (required)

    I understand this form collects PII needed for school safety case management, may be shared with the threat assessment team on a need-to-know basis, and will be retained in the case record for audit trail purposes.

  • Is there an immediate threat to life or imminent violence risk? (required)

    If yes, activate emergency response and district crisis procedures immediately.

Student and Case Identification

This section creates the case record and ties the assessment to the correct student, school, and reference number.

  • Student Full Name (required)
  • Student ID
  • Date of Birth

    Collect only if needed to distinguish students with similar names.

  • School Name (required)
  • Grade Level (required)
  • Case Opened Date (required)
  • Case Reference Number

Initial Screening and Referral Details

This section explains what was reported, where it came from, and why the case moved into the threat assessment process.

  • Referral Source (required)
  • Date Reported (required)
  • Brief Summary of Concern (required)

    Describe the observable behavior, statement, or event using objective facts.

  • Type of Concern (required)
  • Is a specific target identified? (required)
  • Target Details

    Enter only the minimum necessary information about the target.

  • Screening Disposition (required)

Behavioral Indicators and Context

This section captures observable warning signs, stressors, and protective factors so the team can assess context instead of relying on a single incident.

  • Recent Changes in Behavior
  • Observed Warning Signs
  • Known Access to Weapons or Means (required)
  • Access Details

    Document only the minimum necessary details for safety planning.

  • Recent Stressors or Triggers
  • Protective Factors

Full-Team Assessment

This section documents the multidisciplinary review, the information considered, the risk decision, and any notification choices.

  • Team Review Date (required)
  • Team Members Present (required)
  • Information Sources Reviewed (required)
  • Team Risk Level (required)
  • Rationale for Risk Level (required)

    Summarize the facts, not opinions, that support the team’s determination.

  • Law Enforcement Notification Needed? (required)
  • Parent/Guardian Notification Needed? (required)

Management Plan and Interventions

This section turns the assessment into action by assigning interventions, monitoring, and a review date.

  • Intervention Categories (required)
  • Safety Plan Summary

    Include supervision, restricted access, and immediate response steps.

  • Counseling or Support Referral
  • Schedule or Setting Change Details
  • Monitoring Frequency (required)
  • Responsible Staff (required)
  • Next Review Date (required)

Notifications, Documentation, and Audit Trail

This section records who was notified, when, and why, which is critical for continuity and accountability.

  • Notification Log (required)
  • Records Retention Note

    Store the case record according to district policy, applicable state requirements, and the school’s audit trail procedures.

  • Submission Timestamp

Follow-Up, Closure, and Sign-Off

This section shows whether the case is ready to close, what follow-up remains, and who approved the final status.

  • Case Status (required)

    Select the current status after review.

  • Closure Criteria Met?
  • Follow-Up Actions Completed
  • Team Lead Signature (required)
  • Team Lead Name (required)
  • Sign-Off Date (required)

How to use this template

  1. 1. Start a new case by entering the submission type, submitter role, consent acknowledgment, and whether an immediate emergency response was required.
  2. 2. Identify the student and case by completing the name, student ID, school, grade level, case opened date, and case reference number fields.
  3. 3. Record the referral source, concern summary, threat type, target details, and screening disposition so the initial screen shows why the case was opened.
  4. 4. Add observable behavioral indicators, recent stressors, protective factors, and any known access to weapons using the appropriate field types and conditional logic.
  5. 5. Complete the full-team assessment with the review date, team members, information sources, risk level, rationale, and notification decisions.
  6. 6. Document the management plan, follow-up cadence, responsible staff, review due date, closure criteria, and final sign-off before archiving the case.

Best practices

  • Use observable language in the concern summary and warning-sign fields instead of labels or assumptions.
  • Keep required fields limited to the minimum needed for intake so urgent referrals are not slowed down.
  • Use conditional logic to show weapon-access, parent-notification, or law-enforcement fields only when they apply.
  • Record the rationale for the risk level in plain language so the team can review the decision later.
  • Set a specific review due date and monitoring frequency so follow-up does not depend on memory.
  • Log every notification with the date, recipient, method, and purpose to preserve the audit trail.
  • Avoid collecting unrelated health, discipline, or family details unless they directly affect the case.
  • Close the case only after the closure criteria are met and the final actions are documented.

What this template typically catches

Issues teams running this template most often surface in practice:

The referral is vague because the concern summary records opinions instead of specific observed behavior.
The team review is incomplete because information sources reviewed and rationale are left blank.
The management plan is too general and does not assign a responsible staff member or review date.
Notification details are missing, making it hard to confirm whether parents or law enforcement were contacted.
The form collects too much PII at intake, including details that are not needed for the case.
Conditional fields are not used, so users see too many irrelevant questions during urgent screening.
The case is marked closed before follow-up actions and monitoring outcomes are documented.

Common use cases

Middle School Counselor Intake
A counselor receives a report about escalating peer conflict and threatening language. The form captures the initial screen, observed changes, and whether the case should move to a full-team review.
High School Threat Assessment Team Review
An administrator, counselor, and school resource officer review a case together. The template records the sources reviewed, risk level, rationale, and the intervention plan assigned to each staff member.
District Safety Office Case Tracking
A district safety lead uses the form to keep a consistent record across schools. The notification log and audit trail help show what actions were taken and when the case was reviewed.
Student Support and Reentry Planning
After a concerning incident, the team uses the management plan section to document counseling referral, schedule changes, and monitoring frequency before the student returns to regular routines.

Frequently asked questions

What is this template used for?

This template is used to document a school behavioral threat assessment from the first referral through closure. It captures the initial screening, observed warning signs, team review, intervention plan, notifications, and follow-up actions in one record. That makes it easier to keep the case consistent, track decisions, and maintain an audit trail.

Who should complete the form?

The initial screening is usually completed by the designated school administrator, counselor, or threat assessment coordinator. The full-team assessment section should be completed by the multidisciplinary team members who reviewed the case. The sign-off fields help show who made the final decision and when.

How often should this form be updated?

Update it whenever new information changes the risk picture, the safety plan, or the notification status. At minimum, complete it at intake, after the full-team review, after each major intervention change, and at closure. If the case remains open, the follow-up section should reflect the current monitoring cadence.

Does this form replace emergency response procedures?

No. If there is an immediate emergency, the form should not delay calling emergency services or following the school’s crisis protocol. The submission notice should record whether immediate emergency action was needed, but urgent response comes first. This template is for documentation and case management, not for replacing real-time safety steps.

What information should be minimized in this form?

Collect only the PII and case details needed to assess and manage the concern. Use the minimum-necessary principle and avoid adding unrelated medical, disciplinary, or family information unless it directly affects the case. If your process allows anonymous submission for referrals, that can reduce unnecessary data collection at intake.

How can schools customize the template?

Schools can tailor the threat type options, intervention categories, team roles, and notification log to match local policy. Conditional logic can hide fields that do not apply, such as law enforcement notification details when no notification is needed. You can also adapt the form for elementary, middle, or high school workflows.

What are the common mistakes when using a threat assessment form?

Common mistakes include leaving the rationale blank, skipping the notification log, and using vague descriptions instead of observable behaviors. Another issue is marking too many fields required, which can slow urgent reporting and encourage incomplete entries. The form works best when it uses clear field types, progressive disclosure, and a defined follow-up path.

Can this be integrated with other school systems?

Yes. Many schools connect the case form to student information systems, incident reporting tools, counseling workflows, or secure document storage. The key is to preserve the audit trail and limit access to staff with a legitimate need to know. Any integration should respect privacy rules and local retention policies.

How does this compare with ad hoc notes or email threads?

Ad hoc notes and email threads make it harder to see what was reported, who reviewed it, and what action was taken. This template creates a structured record with consistent fields for screening, team assessment, interventions, and closure. That improves handoffs, reduces missed follow-up, and makes review easier later.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use School Behavioral Threat Assessment Screening and Case Form with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?