Skip to content
Campus Alert Archive
Temple

Shots fired on 1300 block of Susquehanna Ave

AI-generated · every claim is source-linked
PAshots firedemergency notificationhigh confidence

Temple TUalert reported shots fired on the 1300 block of Susquehanna Ave with avoid-area guidance, then cleared the area.

Alerts
2
Response
—
Killed
0
Injured
0
Institution
Temple University
Public R1 · PA
All Temple cases →
~37,000 studentsTUalert
Official alert policy
Read when and how Temple says it will use TUalert: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

2 messages in sequence · 2 verified verbatim

Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.

INITIAL ALERTTwitter/X
Verified verbatim123 chars
TUalertEMER: Shots fired reported on the 1300 block of Susquehanna Ave. Use caution. Avoid the area. Police are responding.
Full text from @TempleAlert 2024591188695675103
ALL CLEARTwitter/X+14 min
Verified verbatim79 chars
TUalertEMER: Police have cleared the area on the 1300 block of Susquehanna Ave.
Full text from @TempleAlert 2024594586539004274
Message elements

How the first alert is built

To check this alert, Claude Opus 5 (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.

TUalertEMER: Shots fired reported on the 1300 block of Susquehanna Ave. Use caution. Avoid the area. Police are responding.

  • Sourcepresent25/25

    Final assessment

    Present, 25 of 25. The sender tag "TUalertEMER" opens the message and "Police are responding" identifies the responding agency. Unanimous.

    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
    1. present: The message opens with the "TUalertEMER" sender tag and notes police response.
    2. present: "TUalertEMER" brands the message and police are named as responding.
    3. present: "TUalertEMER" is a branded signature and police are named as responders.
    4. present: The branded prefix "TUalertEMER" plus responding police establish who is speaking.
    5. present: "TUalertEMER" serves as the branded sender identification.
    6. present: "TUalertEMER" signs the message and police are named as responders.
    7. present: "TUalertEMER" identifies the alerting system and police are named as responders.
    8. present: The message carries the "TUalertEMER" branded tag and credits police as responders.
    9. present: "TUalertEMER" plus the note that police are responding satisfies sender identification.
    10. present: "TUalertEMER" brands the message and police are identified as responders.
    11. present: "TUalertEMER" identifies the alert system, and police are named as responding.
    12. present: The branded "TUalertEMER" prefix and the police reference show who is sending.
    13. present: "TUalertEMER" serves as the issuing system's tag, and police are named as responding.
    14. present: "TUalertEMER" identifies the alerting system and police are named as responding.
    15. present: "TUalertEMER" brands the message and police are identified as responding.
    16. present: "TUalertEMER" plus responding police establish who is sending and acting.
    17. present: "TUalertEMER" is the branded signature of the sending alert system.
    18. present: "TUalertEMER" identifies the sending alert system and police are named as responding.
    19. present: "TUalertEMER" brands the message and police are cited as responding.
    20. present: The "TUalertEMER" tag plus "Police are responding" establish who is speaking.
    21. present: "TUalertEMER" serves as the branded sender signature for this notification.
    22. present: "TUalertEMER" identifies the sender as the campus alert system.
    23. present: "TUalertEMER" identifies the alert system, and responding police are mentioned.
    24. present: The alert is signed "TUalertEMER" and refers to police responding.
    25. present: "TUalertEMER" identifies the alert system, and police are named as responding.
  • Hazardpresent25/25

    Final assessment

    Present, 25 of 25. "Shots fired reported" specifies gunfire as the hazard rather than an unnamed emergency.

    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
    1. present: "Shots fired reported" specifies the hazard precisely.
    2. present: "Shots fired reported" names a specific weapons threat.
    3. present: "Shots fired reported" is a specific named hazard.
    4. present: "Shots fired reported" is a specific weapons hazard.
    5. present: "Shots fired reported" is an explicit, specific threat description.
    6. present: "Shots fired reported" is a specific and concrete threat.
    7. present: "Shots fired reported" specifies gunfire as the threat.
    8. present: "Shots fired reported" names a specific gunfire threat.
    9. present: "Shots fired reported" specifies gunfire as the hazard.
    10. present: "Shots fired reported" names a specific firearm threat.
    11. present: "Shots fired reported" names a specific violent hazard.
    12. present: "Shots fired reported" names a concrete weapons hazard.
    13. present: "Shots fired reported" names a specific weapons threat.
    14. present: "Shots fired reported" specifies a gunfire hazard.
    15. present: "Shots fired reported" specifies the threat precisely.
    16. present: "Shots fired reported" names the specific hazard.
    17. present: "Shots fired reported" specifies the threat precisely.
    18. present: "Shots fired reported" names a concrete weapons threat.
    19. present: "Shots fired reported" names the specific threat.
    20. present: "Shots fired" is an explicit, specific hazard.
    21. present: "Shots fired reported" specifies the hazard precisely.
    22. present: "Shots fired reported" specifies the threat precisely.
    23. present: "Shots fired reported" names a specific gunfire hazard.
    24. present: "Shots fired" names a concrete threat.
    25. present: "Shots fired" names a concrete weapons threat.
  • Locationpresent25/25

    Final assessment

    Present, 25 of 25. The alert locates the gunfire on "the 1300 block of Susquehanna Ave", a specific block.

    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
    1. present: It locates the event at "the 1300 block of Susquehanna Ave".
    2. present: It locates the report at "the 1300 block of Susquehanna Ave".
    3. present: The alert names "the 1300 block of Susquehanna Ave" as the site.
    4. present: It cites "the 1300 block of Susquehanna Ave" as the place.
    5. present: The location "the 1300 block of Susquehanna Ave" is stated directly.
    6. present: It locates the event at "the 1300 block of Susquehanna Ave".
    7. present: "the 1300 block of Susquehanna Ave" locates the event.
    8. present: It specifies "the 1300 block of Susquehanna Ave".
    9. present: Location is given as "the 1300 block of Susquehanna Ave".
    10. present: It specifies "the 1300 block of Susquehanna Ave" as the scene.
    11. present: It places the event on "the 1300 block of Susquehanna Ave".
    12. present: Specifies "the 1300 block of Susquehanna Ave".
    13. present: The alert cites "the 1300 block of Susquehanna Ave." as the site.
    14. present: "the 1300 block of Susquehanna Ave" is a specific block.
    15. present: It locates the event at "the 1300 block of Susquehanna Ave".
    16. present: The alert cites "the 1300 block of Susquehanna Ave".
    17. present: It names "the 1300 block of Susquehanna Ave" as the place.
    18. present: It specifies "the 1300 block of Susquehanna Ave".
    19. present: The "1300 block of Susquehanna Ave" gives the place.
    20. present: It names "the 1300 block of Susquehanna Ave".
    21. present: It cites "the 1300 block of Susquehanna Ave" as the location.
    22. present: It names "the 1300 block of Susquehanna Ave" as the place.
    23. present: "1300 block of Susquehanna Ave" gives a concrete address range.
    24. present: It cites "the 1300 block of Susquehanna Ave."
    25. present: It cites "the 1300 block of Susquehanna Ave" as the place.
  • Guidancepresent25/25

    Final assessment

    Present, 25 of 25. "Use caution. Avoid the area." is direct protective guidance to recipients, and no read read it otherwise.

    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
    1. present: "Use caution. Avoid the area" is direct protective guidance.
    2. present: "Use caution. Avoid the area" is a direct protective instruction.
    3. present: "Use caution. Avoid the area" tells readers what to do.
    4. present: "Use caution. Avoid the area" is protective guidance aimed at readers.
    5. present: The message directs recipients to "Use caution. Avoid the area".
    6. present: The instruction "Avoid the area" is a clear protective action.
    7. present: "Use caution. Avoid the area" tells recipients how to protect themselves.
    8. present: Recipients are told to "Use caution. Avoid the area".
    9. present: The protective instructions are to use caution and avoid the area.
    10. present: "Use caution. Avoid the area" is direct protective guidance.
    11. present: "Use caution. Avoid the area" tells readers what to do.
    12. present: Tells recipients to use caution and avoid the area.
    13. present: It instructs readers to use caution and avoid the area.
    14. present: "Use caution. Avoid the area" is explicit guidance to the reader.
    15. present: Recipients are instructed to use caution and avoid the area.
    16. present: It instructs recipients to use caution and avoid the area.
    17. present: Recipients are instructed to use caution and avoid the area.
    18. present: Recipients are told to "Use caution. Avoid the area."
    19. present: "Use caution. Avoid the area" is protective guidance to recipients.
    20. present: "Use caution. Avoid the area" is a protective instruction.
    21. present: Recipients are instructed to use caution and avoid the area.
    22. present: "Use caution. Avoid the area" tells recipients what to do.
    23. present: Recipients are told to use caution and avoid the area.
    24. present: "Use caution. Avoid the area." is direct protective guidance.
    25. present: The instruction "Avoid the area" is protective action for the reader.
  • Timeabsent0/25

    Final assessment

    Absent, 0 of 25. The text gives no time, no date, and no recency wording for the shots fired report.

    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
    1. absent: No time, date, or recency indicator is present.
    2. absent: The text gives no clock time and no phrase marking how recent the event is.
    3. absent: No clock time, date, or word like "now" appears.
    4. absent: Neither a clock time nor a recency cue like "just now" appears.
    5. absent: There is no clock time, date, or recency phrase in the text.
    6. absent: The alert contains no time reference or freshness cue.
    7. absent: No time reference such as a clock time or "now" is given.
    8. absent: There is no statement of when the shots were fired or reported.
    9. absent: The text contains neither a time nor a recency expression.
    10. absent: No clock time, date, or recency phrasing appears in the text.
    11. absent: Nothing in the text indicates when the shots occurred.
    12. absent: No timestamp or recency language accompanies the report.
    13. absent: No time stamp or recency phrase such as "just now" is present.
    14. absent: No timestamp or recency phrase is present in the text.
    15. absent: There is no time reference of any kind in this text.
    16. absent: There is no clock time, date, or word signalling recency.
    17. absent: No clock time or recency marker such as "just now" is present.
    18. absent: No clock time, date, or recency phrase appears.
    19. absent: Nothing indicates when this happened or that it is ongoing.
    20. absent: No time stamp or recency word appears in the message.
    21. absent: The alert offers no clock time, date, or word signaling recency.
    22. absent: No clock time or recency marker is included in the text.
    23. absent: The text offers no clock time or phrase indicating how recently this happened.
    24. absent: Nothing indicates when the shots occurred or how recently.
    25. absent: No clock time or recency marker appears in the message.
  • Impactabsent0/25

    Final assessment

    Absent, 0 of 25. Potential consequences of the gunfire, such as injury or continuing danger, are never mentioned in the message.

    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
    1. absent: Potential consequences of the gunfire are not mentioned.
    2. absent: No wording conveys potential harm or how dangerous the situation might be.
    3. absent: The message omits any description of danger or consequences.
    4. absent: The text stops at the hazard and offers no severity or harm statement.
    5. absent: The alert conveys no potential consequence or severity of the gunfire.
    6. absent: Potential harm from the gunfire is never articulated.
    7. absent: Severity or potential harm is left unstated.
    8. absent: Nothing describes what the gunfire could do or how dangerous it is.
    9. absent: No severity or consequence language accompanies the report of shots.
    10. absent: Consequences or severity of the shots fired are never spelled out.
    11. absent: No potential harm or severity is conveyed beyond the hazard label.
    12. absent: Potential harm from the gunfire is never spelled out.
    13. absent: The message omits any statement of danger level or possible injury.
    14. absent: The message stops at naming gunfire without describing risk or harm.
    15. absent: Potential harm is left unstated; only the event and advice appear.
    16. absent: The message stops at the hazard and gives no severity or outcome.
    17. absent: The message stops at the report and states no consequence or danger level.
    18. absent: The message omits any description of potential harm or severity.
    19. absent: The alert conveys no consequence or danger level.
    20. absent: The alert does not say what the gunfire could do or how dangerous it is.
    21. absent: It does not say what the gunfire could do or call the situation dangerous.
    22. absent: Potential injury or danger is never spelled out.
    23. absent: Nothing conveys what the gunfire might do or how dangerous it is.
    24. absent: The message omits any description of risk or consequence.
    25. absent: The alert never says what the gunfire might cause or how dangerous it is.

Coded by Claude Opus 5

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

About this analysis
Context

Background

Temple University TUalert emergency notifications via official @TempleAlert X account.
Analysis

Key Findings

Complete TUalertEMER short-form text
Campus protective or operational guidance
Outcome
Police cleared the area.
Provenance

Sources

Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.

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

Campus Alert Archive. "Temple University: Shots fired on 1300 block of Susquehanna Ave." Incident of February 19, 2026. Added July 2026. https://campusalertarchive.com/case/temple-university-susquehanna-shots-fired-2026-02-19/

Download case JSON

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

Tags
shots-firedtualerttemple
Added July 2026Updated July 2026Via ingestion