Shooting reported 1800 block W Jefferson avoid area
AI-generated · every claim is source-linkedTUalert reported a shooting on the 1800 block of W. Jefferson Street and ordered people to avoid the area.
- Alerts
- 2
- Response
- —
- Killed
- —
- Injured
- —
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.
How the first alert is built
To check this alert, SuperGrok Heavy 4.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: Shooting reported on the 1800 block of W. Jefferson St. Avoid the area. Police are responding.
Sourcepresent25/25
Final assessment
Majority 25/25 present. Institutional branding appears via "TUalertEMER: Shooting reported on the 1…", which marks the sender.
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
- present: Institutional branding appears via "TUalertEMER: Shooting reported on the 1…", which marks the sender.
- present: The notice identifies who is speaking through "TUalertEMER: Shooting reported on the 1…".
- present: Source is present because "TUalertEMER: Shooting reported on the 1…" names the issuing campus or alert brand.
- present: A campus or alert signature ("TUalertEMER: Shooting reported on the 1…") supplies the authority line.
- present: Sender identity is clear from the wording "TUalertEMER: Shooting reported on the 1…".
- present: The alert tags an official issuer with "TUalertEMER: Shooting reported on the 1…".
- present: Who is sending this is stated through "TUalertEMER: Shooting reported on the 1…".
- present: Branded language "TUalertEMER: Shooting reported on the 1…" functions as the source element.
- present: Campus naming in "TUalertEMER: Shooting reported on the 1…" tells recipients the origin of the message.
- present: An official voice is established by "TUalertEMER: Shooting reported on the 1…".
- present: The opening or body includes "TUalertEMER: Shooting reported on the 1…" as institutional source.
- present: "TUalertEMER: Shooting reported on the 1…" is enough to code source present under the branding rule.
- present: Recipients can tell the sender from "TUalertEMER: Shooting reported on the 1…".
- present: Source scores present: "TUalertEMER: Shooting reported on the 1…" is an authority marker.
- present: The university or college is referenced as "TUalertEMER: Shooting reported on the 1…".
- present: Alert-system or school labeling ("TUalertEMER: Shooting reported on the 1…") covers source.
- present: Issuing body is identifiable from "TUalertEMER: Shooting reported on the 1…".
- present: "TUalertEMER: Shooting reported on the 1…" operates as a branded signature for source.
- present: The text attributes the message via "TUalertEMER: Shooting reported on the 1…".
- present: Source present: campus authority language "TUalertEMER: Shooting reported on the 1…".
- present: Readers see "TUalertEMER: Shooting reported on the 1…" and know which campus is speaking.
- present: Official sender cue "TUalertEMER: Shooting reported on the 1…" is explicit in the text.
- present: Source is coded yes based on "TUalertEMER: Shooting reported on the 1…".
- present: The phrase "TUalertEMER: Shooting reported on the 1…" identifies the responding institution.
- present: Authority is named through the fragment "TUalertEMER: Shooting reported on the 1…".
Hazardpresent25/25
Final assessment
Majority 25/25 present. Hazard is specific: the text names "TUalertEMER: Shooting reported on the 1…".
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
- present: Hazard is specific: the text names "TUalertEMER: Shooting reported on the 1…".
- present: A concrete threat appears as "TUalertEMER: Shooting reported on the 1…".
- present: The what of the emergency is "TUalertEMER: Shooting reported on the 1…", not a vague incident label.
- present: "TUalertEMER: Shooting reported on the 1…" satisfies hazard by naming the condition or threat.
- present: Readers learn the hazard type from "TUalertEMER: Shooting reported on the 1…".
- present: Hazard present via the explicit phrase "TUalertEMER: Shooting reported on the 1…".
- present: The threat is particularized as "TUalertEMER: Shooting reported on the 1…".
- present: Coding H=1 because "TUalertEMER: Shooting reported on the 1…" is a named hazard.
- present: Specific danger language: "TUalertEMER: Shooting reported on the 1…".
- present: The alert states the problem as "TUalertEMER: Shooting reported on the 1…".
- present: Hazard element met by "TUalertEMER: Shooting reported on the 1…".
- present: "TUalertEMER: Shooting reported on the 1…" is more than a generic emergency word.
- present: Threat identity is clear from "TUalertEMER: Shooting reported on the 1…".
- present: The message pins the hazard to "TUalertEMER: Shooting reported on the 1…".
- present: Named condition "TUalertEMER: Shooting reported on the 1…" counts as hazard.
- present: H is present: "TUalertEMER: Shooting reported on the 1…" tells what is wrong.
- present: Concrete hazard wording includes "TUalertEMER: Shooting reported on the 1…".
- present: The incident type is given as "TUalertEMER: Shooting reported on the 1…".
- present: "TUalertEMER: Shooting reported on the 1…" is the stated threat or weather/system hazard.
- present: Hazard codes yes on "TUalertEMER: Shooting reported on the 1…".
- present: Specifics beat generics here: "TUalertEMER: Shooting reported on the 1…".
- present: The text's hazard signal is "TUalertEMER: Shooting reported on the 1…".
- present: What happened is labeled "TUalertEMER: Shooting reported on the 1…".
- present: Hazard present with the phrase "TUalertEMER: Shooting reported on the 1…".
- present: Threat naming succeeds through "TUalertEMER: Shooting reported on the 1…".
Locationabsent0/25
Final assessment
Majority 25/25 absent. No building, campus, street, or area is named.
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
- absent: No building, campus, street, or area is named.
- absent: Location is absent: the text never says where.
- absent: There is no place cue for recipients to orient to.
- absent: L=0 because spatial reference is missing.
- absent: The alert omits campus or site detail.
- absent: Where this applies is never stated.
- absent: No location language appears in the body.
- absent: Place naming fails on this wording.
- absent: Readers get no geographic anchor.
- absent: Location element is not satisfied.
- absent: Without a place name, L is zero.
- absent: The message leaves location unspecified.
- absent: No hall, campus, or area reference is present.
- absent: Spatial information is missing entirely.
- absent: L fails the place-naming test.
- absent: Affected site is not identified.
- absent: Location codes absent here.
- absent: The text is silent on where.
- absent: No campus geography is given.
- absent: Place element cannot be coded present.
- absent: Where-cue is blank in this alert.
- absent: Location not established by the wording.
- absent: Site detail is omitted.
- absent: No area or building reference exists.
- absent: L is absent on a pure no-place text.
Guidancepresent25/25
Final assessment
Majority 25/25 present. Guidance is the instruction "Avoid the area".
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
- present: Guidance is the instruction "Avoid the area".
- present: Protective action appears as "Avoid the area".
- present: Recipients are told to act via "Avoid the area".
- present: "Avoid the area" is a direct what-to-do line.
- present: G=1 because "Avoid the area" instructs the audience.
- present: The alert directs action with "Avoid the area".
- present: Guidance present: "Avoid the area".
- present: A clear instruction is "Avoid the area".
- present: What to do is stated as "Avoid the area".
- present: "Avoid the area" counts as protective guidance.
- present: Action language "Avoid the area" meets guidance.
- present: The message tells people "Avoid the area".
- present: Guidance codes yes on "Avoid the area".
- present: Operational direction: "Avoid the area".
- present: Instructional content includes "Avoid the area".
- present: "Avoid the area" is audience-facing guidance.
- present: G is present via the cue "Avoid the area".
- present: Protective or operational order "Avoid the area" is explicit.
- present: The text's guidance signal is "Avoid the area".
- present: Recipients receive the directive "Avoid the area".
- present: What-to-do element satisfied by "Avoid the area".
- present: "Avoid the area" tells the public how to respond or operate.
- present: Guidance met through "Avoid the area".
- present: Action instruction present: "Avoid the area".
- present: The alert's order to the audience is "Avoid the area".
Timeabsent0/25
Final assessment
Majority 25/25 absent. No clock time, date, or recency word such as now or today appears.
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
- absent: No clock time, date, or recency word such as now or today appears.
- absent: Time is absent from the alert text.
- absent: Nothing tells recipients when this applies.
- absent: T=0 because temporal cues are missing.
- absent: No day, hour, or immediate language is stated.
- absent: The message omits timing entirely.
- absent: Time element fails on this wording.
- absent: When is left unspecified.
- absent: No calendar or clock reference is present.
- absent: Temporal information cannot be found.
- absent: Without a time cue, T is zero.
- absent: The alert is silent on schedule.
- absent: Time codes absent here.
- absent: Recency language is missing.
- absent: T fails the when test.
- absent: No today/now/clock marker appears.
- absent: Timing is not established by the text.
- absent: Date and hour are both omitted.
- absent: Temporal element is not satisfied.
- absent: The body lacks any when cue.
- absent: Time not present under the rubric.
- absent: Schedule detail is blank.
- absent: No temporal anchor is given.
- absent: T is absent on timeless wording.
- absent: When-information is not included.
Impactabsent0/25
Final assessment
Majority 25/25 absent. No consequence or severity language appears beyond naming a hazard.
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
- absent: No consequence or severity language appears beyond naming a hazard.
- absent: Impact is absent: the text does not say what the threat could do.
- absent: Nothing states danger level, injuries, or disruptive effect.
- absent: I=0 because severity or harm is not conveyed.
- absent: Hazard may be named, but impact language is missing.
- absent: The alert omits consequence wording.
- absent: Impact fails the harm-or-severity test.
- absent: Readers are not told stakes or effects.
- absent: No life-safety or operational impact phrase is present.
- absent: Impact element codes absent.
- absent: Without consequence language, I is zero.
- absent: Severity is left unstated.
- absent: The text stops short of impact.
- absent: Harm potential is not described.
- absent: I fails on bare description without effects.
- absent: No dangerous/closed/injury-style impact cue appears.
- absent: Impact not established by the wording.
- absent: Consequence detail is missing.
- absent: The message lacks severity framing.
- absent: I is absent under the impact rule.
- absent: Stakes for people or property are not stated.
- absent: No disruption or harm language is included.
- absent: Impact cannot be coded present here.
- absent: Effect-on-campus language is omitted.
- absent: Severity/consequence element fails.
Coded by SuperGrok Heavy 4.5
Systematic AI judgments with visible reasoning, not human-validated codings.
Background
Key Findings
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.
- Social
- Social
Campus Alert Archive. "Temple University: Shooting reported 1800 block W Jefferson avoid area." Incident of July 30, 2026. Added August 2026. https://campusalertarchive.com/case/temple-university-jefferson-st-shooting-avoid-area-2026-07-30/
Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.