Skip to content
Campus Alert Archive
Purdue

Bomb threat, September 23, 2015

AI-generated · every claim is source-linked
INbomb threatemergency notificationhigh confidence

On the morning of September 23, 2015, Purdue University Police responded to a bomb threat at Schleman Hall of Student Services, an academic-services building on Purdue's West Lafayette campus. Police and fire crews arrived around 11:45 AM CDT, evacuated the building, and conducted a two-hour sweep. PurdueALERT messages directed students and staff to avoid the building and follow shelter instructions. After roughly two hours, no explosive device was located and the building was reopened.

Alerts
3
Response
5 min
Killed
Injured
Institution
Purdue University
Public R1 · IN
All Purdue cases →
~41,000 studentsPurdueALERT
Official alert policy
Read when and how Purdue says it will use PurdueALERT: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

3 messages in sequence · 3 verified verbatim

INITIAL ALERTTwitter/X
Verified verbatim@PurdueALERT on X (verbatim)131 chars
Bomb threat reported at Purdue WL - Schleman Hall - 475 Stadium Mall Drive); avoid the area; check http://purdue.edu/ea for updates
Verbatim from official @PurdueALERT X post. Pre-280-char era; text is the complete status as transmitted (seq2 ends mid-phrase at the 140-char boundary).
Corrected to exact fxtwitter display text.
UPDATETwitter/X+1h 15m
Verified verbatim@PurdueALERT on X (verbatim)137 chars
Purdue WL advising to continue avoiding the area of Schleman Hall-475 Stadium Mall Dr, due to Bomb threat; check http://purdue.edu/ea for
Verbatim from official @PurdueALERT X post. Pre-280-char era; text is the complete status as transmitted (seq2 ends mid-phrase at the 140-char boundary).
Corrected to exact fxtwitter display text.
ALL CLEARTwitter/X+1h 44m
Verified verbatim@PurdueALERT on X (verbatim)101 chars
Purdue WL advising there is no ongoing threat to campus; Schleman Hall has resumed normal operations.
Verbatim from official @PurdueALERT X post. Pre-280-char era; text is the complete status as transmitted (seq2 ends mid-phrase at the 140-char boundary).
Channel corrected from reconstructed SMS to twitter-x per official X transmission.
Message elements

How the first alert is built

To check this alert, Claude (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.

Bomb threat reported at Purdue WL - Schleman Hall - 475 Stadium Mall Drive); avoid the area; check http://purdue.edu/ea for updates

  • Sourceabsent0/0

    Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.

    See all 25 individual reads

    Open to load the 25 reads.

  • Hazardabsent0/0

    What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.

    See all 25 individual reads

    Open to load the 25 reads.

  • Locationabsent0/0

    Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.

    See all 25 individual reads

    Open to load the 25 reads.

  • Guidanceabsent0/0

    The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.

    See all 25 individual reads

    Open to load the 25 reads.

  • Timeabsent0/0

    When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.

    See all 25 individual reads

    Open to load the 25 reads.

  • Impactabsent0/0

    What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.

    See all 25 individual reads

    Open to load the 25 reads.

Systematic AI judgments with visible reasoning, not human-validated codings.

About this analysis
Context

Background

On September 23, 2015, Purdue University Police and Fire responded to a bomb threat at Schleman Hall of Student Services on the West Lafayette campus. The building was evacuated around 11:45 AM CDT, with PurdueALERTs sent via SMS, email, and Twitter directing students and staff to avoid the area. Schleman Hall houses Purdue's Office of the Registrar, admissions, and other student-services operations, a high-foot-traffic but academically peripheral building whose evacuation disrupted services without canceling classes elsewhere. Police and fire conducted a two-hour sweep, found no device, and reopened the building in the afternoon. The case is a quiet but representative example of an R1 single-building bomb-threat response: the PurdueALERT system sends campus-wide notifications even for localized incidents, the standard three-message arc (initial + update + all-clear) is preserved, and academic operations elsewhere on the 41,000-student campus continue without disruption. The 2015 Schleman Hall incident sits between Purdue's January 2014 Andrew Boldt shooting in the Electrical Engineering Building and later bomb threats targeting the campus, illustrating how a single university's alert system handles a spectrum of incident severity over a multi-year window.
Analysis

Key Findings

Schleman Hall houses Purdue's Registrar and admissions operations; evacuating it disrupts student services without affecting classes elsewhere
PurdueALERT's three-message arc (initial + update + all-clear) is preserved even for a single-building, two-hour investigation
Other campus buildings explicitly continued operations during the evacuation, an important framing on a 41,000-student R1
Two-hour sweep duration is consistent with a single-building bomb-threat investigation without a found device
No public arrest was announced in the immediate aftermath; investigation referred to Purdue PD and federal partners
Outcome
Schleman Hall evacuated for approximately two hours. No device found, no injuries. Building reopened in the afternoon. Investigation referred to Purdue PD and federal partners; no public arrest was announced.
Provenance

Sources

  1. Social
  2. News
  3. Official
  4. Official
Cite this case

Campus Alert Archive. "Purdue University: Bomb threat, September 23, 2015." Incident of September 23, 2015. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/purdue-university-schleman-hall-bomb-threat-2015-09-23/

Download case JSON

Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.

Tags
bomb-threatevacuationpurdueschleman-hallpurduealertpublic-r1indianasingle-buildingfalse-alarmseptember-2015
Added May 2026Updated July 2026Via ingestion