Stay-in-place for a second shots-fired report at Calhoun and South Market
AI-generated · every claim is source-linkedUC Public Safety told people to stay put for an emergency on calhoun/south market, reported shots fired on scene, and issued an all-clear.
- Alerts
- 3
- Response
- —
- Killed
- —
- Injured
- —
Alert Sequence
3 messages in sequence · 3 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.
UC Emergency- Police responding to emergency reported on calhoun/south market If safe, stay at your location. Be observant/take action as needed. More info soon
Sourcepresent25/25
Final assessment
The alert is signed as UC Emergency, so a named sender is present. Source is coded 25/25.
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: Opens with UC Emergency, a branded campus agency source.
- present: UC Emergency again identifies the university office that issued the alert.
- present: UC Emergency is a branded sender tag and Police names the responding agency.
- present: Same named sender: UC Emergency.
- present: The branded opener UC Emergency identifies the sender.
- present: Issuer label UC Emergency at the start.
- present: UC Emergency is a branded sender tag, and Police responding names the agency.
- present: UC Emergency names the campus channel as source on the later night.
- present: UC Emergency is a branded signature, and Police responding names the authority.
- present: UC Emergency is a branded sender tag.
- present: Alert prefix UC Emergency names the sender on the later product.
- present: UC Emergency- brands the sender.
- present: UC Emergency is a branded sender tag.
- present: The message opens with the branded source label UC Emergency on the later night.
- present: UC Emergency brands the campus channel.
- present: UC Emergency brands the sending system.
- present: UC Emergency is the sender tag, with Police named as the authority on scene.
- present: UC Emergency is a branded sender tag.
- present: UC Emergency brands the sender.
- present: Same channel source UC Emergency on the later night.
- present: The opener UC Emergency brands the sender.
- present: The message is signed UC Emergency and names Police as the responding authority.
- present: UC Emergency- is a branded alert signature at the start.
- present: Same channel source on the later UC blast.
- present: UC Emergency brands the sender.
Hazardabsent1/25
Final assessment
The text only says an unspecified emergency, which is not a named hazard type. Hazard is coded 1/25.
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
- absent: Same generic emergency wording; not a specific hazard type.
- absent: The incident remains a generic emergency rather than a defined hazard.
- absent: Only emergency reported appears, with no specific hazard such as shots fired.
- absent: Again only emergency. No specific threat is named.
- absent: Only emergency reported appears, too generic to name the actual hazard.
- absent: Police response to an unspecified emergency.
- absent: emergency reported is generic wording.
- absent: The word emergency is not a specific hazard type on this later product.
- absent: The text says only emergency reported.
- absent: Only a generic emergency is reported.
- absent: Police response to a reported emergency is not a typed threat on the later product.
- absent: The phrase emergency reported is generic.
- absent: Only the generic phrase emergency reported appears.
- absent: The event is called only a generic emergency on the later night.
- absent: The body only says emergency reported.
- absent: emergency reported uses the generic word emergency.
- absent: The word emergency is too generic to count as a named hazard.
- absent: emergency reported does not name a specific threat.
- absent: emergency reported is generic and does not name a specific threat type.
- absent: Unspecified emergency on the later night.
- absent: Only emergency reported appears; that generic word does not specify the type.
- absent: Emergency reported is generic and does not say what kind of threat is occurring.
- absent: The text names only an emergency and never specifies the actual threat type.
- present: This rater scored unspecified emergency as a partial hazard on the later UC blast.
- absent: emergency reported is generic wording.
Locationpresent25/25
Final assessment
The incident is placed on Calhoun/South Market. Location is coded 25/25.
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
- present: Gives calhoun/south market as the place.
- present: Calhoun and South Market are named as the reported site.
- present: The report is located on calhoun/south market.
- present: Calhoun and South Market are given as a slash pair.
- present: on calhoun/south market states the location of the report.
- present: Place is Calhoun and South Market.
- present: Location is given as calhoun/south market.
- present: calhoun/south market are named streets.
- present: Location is calhoun/south market, a named street pair.
- present: The event is located on calhoun/south market.
- present: Place is on Calhoun and South Market.
- present: The event is located on calhoun/south market.
- present: Place is given as on calhoun/south market.
- present: A location is given as on Calhoun and South Market.
- present: on calhoun/south market is the street location given.
- present: It locates the report on calhoun/south market.
- present: On calhoun/south market locates the report at that street pair.
- present: The event is located on calhoun/south market.
- present: Location is given as calhoun/south market.
- present: Location is on calhoun/south market.
- present: On calhoun/south market locates the report at a named intersection.
- present: The report is located on calhoun/south market.
- present: The report is located on calhoun/south market.
- present: Location is weaker: on calhoun/south market, lowercase.
- present: Location is given as on calhoun/south market.
Guidancepresent25/25
Final assessment
Recipients are told to stay if safe and to be observant or take action as needed. Guidance is coded 25/25.
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: Same stay if safe plus observant and take action guidance.
- present: Recipients are instructed to remain in a safe place.
- present: It instructs If safe, stay at your location.
- present: Same stay if safe line as the other UC product.
- present: Recipients are told If safe, stay at your location.
- present: If safe, stay in place; await further info.
- present: If safe, stay at your location tells people what steps to take.
- present: Stay if safe is guidance on the later night.
- present: If safe, stay at your location are protective instructions.
- present: If safe, stay at your location are protective instructions.
- present: Stay put if safe and stay alert on the later product.
- present: If safe, stay at your location instructs recipients how to act.
- present: If safe, stay at your location are protective instructions.
- present: Recipients are told to stay if safe on the later night.
- present: Recipients are told if safe to stay at your location.
- present: If safe, stay at your location instruct recipients what to do.
- present: Stay at your location if it is safe tells people what action to take.
- present: If safe, stay at your location tells people to remain in place.
- present: Recipients are told to stay at your location if safe.
- present: Same stay-if-safe guidance on the later night.
- present: Stay at your location if safe are protective instructions.
- present: It instructs people to stay at your location if safe.
- present: If safe, stay at your location is a remain-in-place instruction.
- present: Same thin guidance on the later UC blast.
- present: If safe, stay at your location directs recipients to remain.
Timeabsent0/25
Final assessment
No clock time, duration, or expiration is given. Time is coded 0/25.
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: More info soon is future follow up, not when the event happened.
- absent: More info soon is a follow-up pledge, not a timestamp.
- absent: More info soon is a later-update promise, not a clock time.
- absent: More info soon is a follow-up promise, not a hazard time window.
- absent: More info soon is not a clock time or recency word.
- absent: No time, duration, or timestamp given.
- absent: More info soon is a promise of a later update, not a when.
- absent: Time is absent on this later product.
- absent: More info soon times a later update, not the emergency.
- absent: More info soon promises a later update and is not a time marker.
- absent: More info soon is an update notice only.
- absent: More info soon promises a later update, not a time for the hazard.
- absent: More info soon looks ahead to updates and is not a recency cue.
- absent: No clock time, date, or other temporal marker is stated on the later night.
- absent: More info soon promises a later update and is not a stamp.
- absent: More info soon promises a later update but is not a recency marker.
- absent: More info soon refers to a later update, not when the event is happening.
- absent: More info soon is a follow-up promise, not a clock time.
- absent: More info soon promises a later update but does not time the event.
- absent: More info soon is a weak time cue, not an incident time.
- absent: More info soon is a promise of a later update, not a recency marker.
- absent: More info soon only promises a later update.
- absent: More info soon talks about a later update, not when the incident is happening.
- absent: More info soon is not an incident time or duration.
- absent: More info soon only promises a later update.
Impactabsent0/25
Final assessment
There is no wording about injury, death, or other harm. Impact is coded 0/25.
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 harm or severity beyond the word emergency.
- absent: No harm to people or disruption of buildings is described.
- absent: No harm, consequence, or severity is described.
- absent: No injuries, closures, or other consequence is stated.
- absent: Nothing describes what the emergency could do.
- absent: Unspecified emergency with update pending.
- absent: No consequence or severity language is present.
- absent: Impact is absent on this later product.
- absent: The message does not say how serious the emergency is.
- absent: No injury, damage, or other consequence language is stated.
- absent: No harm, damage, or other impact is given on the later product.
- absent: Nothing describes what the emergency could do.
- absent: The message does not describe harm or danger.
- absent: No injury, death, or other harm is reported on the later night.
- absent: The text does not describe harm or how serious it is.
- absent: The text never says what the emergency could do.
- absent: No consequence, injury risk, or severity language appears.
- absent: No consequence or severity language appears.
- absent: No consequence or severity language appears.
- absent: Impact is still not stated beyond police responding.
- absent: Nothing describes what the unnamed emergency could do.
- absent: The wording does not describe any potential harm.
- absent: Nothing describes severity or consequences.
- absent: Impact is not a stated harm on the later UC blast.
- absent: No consequence or severity language about harm is present.
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
- Social
Campus Alert Archive. "University of Cincinnati: Stay-in-place for a second shots-fired report at Calhoun and South Market." Incident of August 30, 2026. Added August 2026. https://campusalertarchive.com/case/university-of-cincinnati-calhoun-south-market-shots-fired-2026-08-30/
Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.