Shooting on the 900 block of Diamond Street

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.

• Sourcepresent25/25

  Final assessment

  Present: TUalertEMER brand in first-burst TUalert.

  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: Alert system signature TUalertEMER is named.
  2. present: Branding TUalertEMER counts as source.
  3. present: Branded signature TUalertEMER identifies the sender.
  4. present: Coded: TUalert emergency brand is named.
  5. present: TUalertEMER identifies who is transmitting.
  6. present: Coded: issuer brand is visible.
  7. present: Coded: source tag is present.
  8. present: Coded: branded sender TUalertEMER appears.
  9. present: Sender tag TUalertEMER is present.
  10. present: Coded: TUalertEMER brands the alert.
  11. present: Agency/alert brand TUalertEMER names the issuer.
  12. present: Official alert signature TUalertEMER is present.
  13. present: Source is clear via TUalertEMER.
  14. present: The message opens with TUalertEMER.
  15. present: Coded: sender identity is branded.
  16. present: Coded: alert system signature TUalertEMER is named.
  17. present: Coded: branding TUalertEMER counts as source.
  18. present: Coded: branded signature TUalertEMER identifies the sender.
  19. present: Coded: TUalert emergency brand is named.
  20. present: Coded: tUalertEMER identifies who is transmitting.
  21. present: Coded: issuer brand is visible.
  22. present: Coded: source tag is present.
  23. present: Coded: branded sender TUalertEMER appears.
  24. present: Coded: sender tag TUalertEMER is present.
  25. present: Coded: TUalertEMER brands the alert.
• Hazardpresent25/25

  Final assessment

  Present: named crime/hazard in first-burst TUalert.

  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: Coded: offense type Shooting is named.
  2. present: Hazard named as Shooting.
  3. present: The message names Shooting as the event.
  4. present: Coded: specific hazard is named.
  5. present: Coded: crime type present.
  6. present: Coded: hazard is concrete.
  7. present: Coded: incident type named.
  8. present: Offense is stated as Shooting.
  9. present: Hazard is concrete: Shooting.
  10. present: Specific threat Shooting is stated.
  11. present: Coded: hazard wording is present.
  12. present: Specific crime Shooting is identified.
  13. present: Threat type Shooting appears in the text.
  14. present: Coded: threat type present.
  15. present: Incident type Shooting is explicit.
  16. present: Coded: offense type Shooting is named.
  17. present: Coded: hazard named as Shooting.
  18. present: Coded: the message names Shooting as the event.
  19. present: Coded: specific hazard is named.
  20. present: Coded: crime type present.
  21. present: Coded: hazard is concrete.
  22. present: Coded: incident type named.
  23. present: Coded: offense is stated as Shooting.
  24. present: Coded: hazard is concrete: Shooting.
  25. present: Coded: specific threat Shooting is stated.
• Locationpresent25/25

  Final assessment

  Present: street/block location in first-burst TUalert.

  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: Coded: geo reference present.
  2. present: Coded: street location is named.
  3. present: Where is stated via 900 block of Diamond St.
  4. present: Coded: place reference 900 block of Diamond St appears.
  5. present: Block/street 900 block of Diamond St anchors location.
  6. present: The message places the event at 900 block of Diamond St.
  7. present: Area is specified: 900 block of Diamond St.
  8. present: Coded: location cue is present.
  9. present: Location is concrete: 900 block of Diamond St.
  10. present: Coded: geographic detail present.
  11. present: Coded: location is concrete.
  12. present: Location given as 900 block of Diamond St.
  13. present: Coded: area is given.
  14. present: Street block 900 block of Diamond St is named.
  15. present: Place is identified as 900 block of Diamond St.
  16. present: Coded: geo reference present.
  17. present: Coded: street location is named.
  18. present: Coded: where is stated via 900 block of Diamond St.
  19. present: Coded: place reference 900 block of Diamond St appears.
  20. present: Coded: block/street 900 block of Diamond St anchors location.
  21. present: Coded: the message places the event at 900 block of Diamond St.
  22. present: Coded: area is specified: 900 block of Diamond St.
  23. present: Coded: location cue is present.
  24. present: Coded: location is concrete: 900 block of Diamond St.
  25. present: Coded: geographic detail present.
• Guidancepresent25/25

  Final assessment

  Present: avoid/caution instruction in first-burst TUalert.

  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: Protective instruction: Avoid the area.
  2. present: Coded: avoid/caution guidance given.
  3. present: Coded: safety guidance present.
  4. present: Coded: protective action stated.
  5. present: Coded: what-to-do language present.
  6. present: The text tells people to Avoid the area.
  7. present: Recipients are told to Avoid the area.
  8. present: Guidance is present via Avoid the area.
  9. present: Coded: guidance Avoid the area is present.
  10. present: Coded: audience instructions appear.
  11. present: Recipients get action cue Avoid the area.
  12. present: Protective action Avoid the area is explicit.
  13. present: Coded: protective guidance present.
  14. present: Instruction appears: Avoid the area.
  15. present: Audience is directed: Avoid the area.
  16. present: Coded: protective instruction: Avoid the area.
  17. present: Coded: avoid/caution guidance given.
  18. present: Coded: safety guidance present.
  19. present: Coded: protective action stated.
  20. present: Coded: what-to-do language present.
  21. present: Coded: the text tells people to Avoid the area.
  22. present: Coded: recipients are told to Avoid the area.
  23. present: Coded: guidance is present via Avoid the area.
  24. present: Coded: guidance Avoid the area is present.
  25. present: Coded: audience instructions appear.
• Timeabsent0/25

  Final assessment

  Absent: no clock time or recency cue in first-burst TUalert.

  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: Nothing marks time or recency.
  2. absent: No recency language is present.
  3. absent: The message does not say when the event occurred.
  4. absent: Coded: no time reference.
  5. absent: Coded: no temporal cue.
  6. absent: No clock time or date is given.
  7. absent: Coded: time element absent.
  8. absent: Coded: timing not stated.
  9. absent: Coded: no when cue.
  10. absent: No clock time, date, or recency word such as now appears.
  11. absent: Temporal detail is absent.
  12. absent: Timing is not anchored in the text.
  13. absent: Coded: when-information is absent.
  14. absent: Coded: temporal anchor missing.
  15. absent: No date or clock time is stated.
  16. absent: Coded: nothing marks time or recency.
  17. absent: Coded: no recency language is present.
  18. absent: Coded: the message does not say when the event occurred.
  19. absent: Coded: no time reference.
  20. absent: Coded: no temporal cue.
  21. absent: Coded: no clock time or date is given.
  22. absent: Coded: time element absent.
  23. absent: Coded: timing not stated.
  24. absent: Coded: no when cue.
  25. absent: Coded: no clock time, date, or recency word such as now appears.
• Impactabsent0/25

  Final assessment

  Absent: no consequence/severity language in first-burst TUalert.

  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: Hazard name alone does not satisfy impact.
  2. absent: Coded: impact element absent.
  3. absent: No explicit consequence is present.
  4. absent: The text does not state what the hazard could do.
  5. absent: No life-threat or injury consequence is named.
  6. absent: Coded: impact language absent.
  7. absent: No consequence or severity language is stated.
  8. absent: Coded: severity language missing.
  9. absent: Coded: severity not indicated.
  10. absent: Impact is not conveyed beyond the hazard name.
  11. absent: Coded: outcome not stated.
  12. absent: Coded: no consequence wording.
  13. absent: Impact remains unstated.
  14. absent: Coded: no impact cue.
  15. absent: No harm or severity phrase appears.
  16. absent: Coded: hazard name alone does not satisfy impact.
  17. absent: Coded: impact element absent.
  18. absent: Coded: no explicit consequence is present.
  19. absent: Coded: the text does not state what the hazard could do.
  20. absent: Coded: no life-threat or injury consequence is named.
  21. absent: Coded: impact language absent.
  22. absent: Coded: no consequence or severity language is stated.
  23. absent: Coded: severity language missing.
  24. absent: Coded: severity not indicated.
  25. absent: Coded: impact is not conveyed beyond the hazard name.