Behavioral threat assessment software
Referrals about students of concern, the team's meetings and decisions, and every follow-up in one record, so the next person to look sees the whole history.
Who uses it
BIT and CARE team chairs
The full list of open concerns, who owns each one and what happens next.
Counseling and student affairs
Referrals routed to the team with the context the referrer gave.
Campus safety and school police
Safety information recorded alongside the team's response.
Faculty and staff who refer
One form to raise a concern, instead of deciding which office to email.
What behavioral threat assessment covers
- Referrals from faculty
- Staff
- Students and families
- Students of concern
- Threat assessment steps
- Team meetings and decisions
- Interventions
- Supports and follow-up tasks
- Links to conduct or Title IX cases when a concern becomes one
The BIT module
Behavioral intervention is a module a department turns on. With it off, none of it appears. With it on, the team's work sits on the case itself rather than in a separate spreadsheet.
- Risk assessments recorded with their level, the date and who assessed, and visible at a glance on the case.
- Intervention plans with a status and their steps tracked to completion.
- Your team's own risk factors, protective factors and assessment references, set up per department.
Your team decides what it uses and what each assessment means. Casearoo records the team's work; it doesn't score students or make clinical judgments.
Built for BIT and CARE teams
The behavioral intervention module: case management shaped around how your team actually meets.
The behavioral intervention module, switched on per department
Behavioral intervention is a capability you switch on per department. Configure referral handling, risk review and monitoring for the teams running one.
A referral route anyone on campus can use
Faculty, staff, students and families refer through a form your team shapes. A referral may be left anonymous, and later questions still reach whoever raised it. The anonymous reporting system page describes how that follow-up works, from the access key to the check-in portal.
Context visible before the meeting starts
Flag a prior referral, an existing support relationship or a safety concern, and the team sees it the moment that student reappears.
Outreach that follows the same pattern
Capture your usual sequence of contact attempts and checks, then apply it to a new referral with owners and dates already set.
Review dates attached to the student
Register the review types your team holds and place them on the referral, so monitoring never depends on recollection.
Silence that gets noticed
Alert the assigned member when an outreach goes unanswered or a review approaches, by role rather than by broadcast.
Members see referrals, the chair sees everything
Grant the team access to what it reviews and reserve the full history for the chair, with every view recorded.
BIT case reports: referral volume and response time
Measure where referrals originate, how quickly first contact happened, and what the term looked like overall.
Questions we get
Can anyone submit a referral?
Yes. A public or internal form feeds the team's queue, so a concern reaches the team without the referrer knowing which office handles it.
Does it handle behavioral threat assessment as well?
The team builds its own case types and steps, so behavioral threat assessment can run as its own process alongside general concerns.
Who can see a BIT case?
Access follows the role. Team members see the team's cases; other departments don't.
What happens when a concern becomes a conduct or Title IX case?
Cases can be connected across departments, so the new case starts with the history rather than a blank page.
Can a student submit a referral about a friend?
Yes. Public forms can accept referrals from anyone, which matters because peers often notice a change before staff do.
Does it keep a history across semesters?
Yes. Earlier concerns stay on the record, so a team sees the pattern at the first meeting rather than discovering it on the third report.
Can we record the team's reasoning, not just the outcome?
Yes, and this is the part most teams miss. The basis for a decision can be recorded at the time it is made, which is the only point at which it can be captured honestly.
Who gets notified when a new concern arrives?
Whoever you nominate, by concern type. Routing is a setting rather than a convention somebody has to remember.
Can clinical notes be kept out of the general case view?
Yes. Sensitive entries can be restricted to named people while the rest of the team still sees that the case exists and what stage it is at.
Does it prompt the follow-up after a plan is set?
Yes. Check-ins carry dates and owners, and overdue follow-up surfaces rather than quietly lapsing, which is where support plans usually fail.
Hop toKeep reading
See it on your own process
Thirty minutes, no slide deck. Bring the workflow that gives you the most trouble and we will build it on the call.
Schedule a demo