Shooting on the 2000 block of North 10th 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: Branded signature TUalertEMER identifies the sender.
  2. present: Source is clear via TUalertEMER.
  3. present: Coded: TUalertEMER brands the alert.
  4. present: Coded: sender identity is branded.
  5. present: TUalertEMER identifies who is transmitting.
  6. present: Coded: branded sender TUalertEMER appears.
  7. present: Alert system signature TUalertEMER is named.
  8. present: Official alert signature TUalertEMER is present.
  9. present: Coded: source tag is present.
  10. present: Branding TUalertEMER counts as source.
  11. present: Sender tag TUalertEMER is present.
  12. present: Agency/alert brand TUalertEMER names the issuer.
  13. present: Coded: TUalert emergency brand is named.
  14. present: Coded: issuer brand is visible.
  15. present: The message opens with TUalertEMER.
  16. present: Coded: branded signature TUalertEMER identifies the sender.
  17. present: Coded: source is clear via TUalertEMER.
  18. present: Coded: TUalertEMER brands the alert.
  19. present: Coded: sender identity is branded.
  20. present: Coded: tUalertEMER identifies who is transmitting.
  21. present: Coded: branded sender TUalertEMER appears.
  22. present: Coded: alert system signature TUalertEMER is named.
  23. present: Coded: official alert signature TUalertEMER is present.
  24. present: Coded: source tag is present.
  25. present: Coded: branding TUalertEMER counts as source.
• 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: Specific threat Shooting is stated.
  2. present: Coded: threat type present.
  3. present: Coded: specific hazard is named.
  4. present: Hazard named as Shooting.
  5. present: Hazard is concrete: Shooting.
  6. present: Coded: offense type Shooting is named.
  7. present: Threat type Shooting appears in the text.
  8. present: Specific crime Shooting is identified.
  9. present: The message names Shooting as the event.
  10. present: Coded: crime type present.
  11. present: Offense is stated as Shooting.
  12. present: Coded: incident type named.
  13. present: Coded: hazard is concrete.
  14. present: Incident type Shooting is explicit.
  15. present: Coded: hazard wording is present.
  16. present: Coded: specific threat Shooting is stated.
  17. present: Coded: threat type present.
  18. present: Coded: specific hazard is named.
  19. present: Coded: hazard named as Shooting.
  20. present: Coded: hazard is concrete: Shooting.
  21. present: Coded: offense type Shooting is named.
  22. present: Coded: threat type Shooting appears in the text.
  23. present: Coded: specific crime Shooting is identified.
  24. present: Coded: the message names Shooting as the event.
  25. present: Coded: crime type present.
• 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: Block/street 2000 block of N.10th Street anchors location.
  2. present: Coded: street location is named.
  3. present: Location given as 2000 block of N.10th Street.
  4. present: Coded: location is concrete.
  5. present: Coded: place reference 2000 block of N.10th Street appears.
  6. present: Coded: location cue is present.
  7. present: Coded: geo reference present.
  8. present: Street block 2000 block of N.10th Street is named.
  9. present: Place is identified as 2000 block of N.10th Street.
  10. present: Where is stated via 2000 block of N.10th Street.
  11. present: Coded: area is given.
  12. present: Area is specified: 2000 block of N.10th Street.
  13. present: The message places the event at 2000 block of N.10th Street.
  14. present: Location is concrete: 2000 block of N.10th Street.
  15. present: Coded: geographic detail present.
  16. present: Coded: block/street 2000 block of N.10th Street anchors location.
  17. present: Coded: street location is named.
  18. present: Coded: location given as 2000 block of N.10th Street.
  19. present: Coded: location is concrete.
  20. present: Coded: place reference 2000 block of N.10th Street appears.
  21. present: Coded: location cue is present.
  22. present: Coded: geo reference present.
  23. present: Coded: street block 2000 block of N.10th Street is named.
  24. present: Coded: place is identified as 2000 block of N.10th Street.
  25. present: Coded: where is stated via 2000 block of N.10th Street.
• 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: Recipients get action cue Avoid the area.
  2. present: Protective instruction: Avoid the area.
  3. present: Coded: what-to-do language present.
  4. present: Coded: avoid/caution guidance given.
  5. present: Coded: safety guidance present.
  6. present: Recipients are told to Avoid the area.
  7. present: Audience is directed: Avoid the area.
  8. present: Guidance is present via Avoid the area.
  9. present: Instruction appears: Avoid the area.
  10. present: Coded: audience instructions appear.
  11. present: The text tells people to Avoid the area.
  12. present: Coded: guidance Avoid the area is present.
  13. present: Coded: protective action stated.
  14. present: Protective action Avoid the area is explicit.
  15. present: Coded: protective guidance present.
  16. present: Coded: recipients get action cue Avoid the area.
  17. present: Coded: protective instruction: Avoid the area.
  18. present: Coded: what-to-do language present.
  19. present: Coded: avoid/caution guidance given.
  20. present: Coded: safety guidance present.
  21. present: Coded: recipients are told to Avoid the area.
  22. present: Coded: audience is directed: Avoid the area.
  23. present: Coded: guidance is present via Avoid the area.
  24. present: Coded: instruction appears: Avoid the area.
  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: Coded: timing not stated.
  2. absent: Coded: no when cue.
  3. absent: Temporal detail is absent.
  4. absent: Nothing marks time or recency.
  5. absent: No date or clock time is stated.
  6. absent: No clock time, date, or recency word such as now appears.
  7. absent: Coded: when-information is absent.
  8. absent: No recency language is present.
  9. absent: Coded: time element absent.
  10. absent: No clock time or date is given.
  11. absent: The message does not say when the event occurred.
  12. absent: Coded: no temporal cue.
  13. absent: Timing is not anchored in the text.
  14. absent: Coded: temporal anchor missing.
  15. absent: Coded: no time reference.
  16. absent: Coded: timing not stated.
  17. absent: Coded: no when cue.
  18. absent: Coded: temporal detail is absent.
  19. absent: Coded: nothing marks time or recency.
  20. absent: Coded: no date or clock time is stated.
  21. absent: Coded: no clock time, date, or recency word such as now appears.
  22. absent: Coded: when-information is absent.
  23. absent: Coded: no recency language is present.
  24. absent: Coded: time element absent.
  25. absent: Coded: no clock time or date is given.
• 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: No harm or severity phrase appears.
  2. absent: Coded: no impact cue.
  3. absent: Impact remains unstated.
  4. absent: Coded: no consequence wording.
  5. absent: Coded: impact element absent.
  6. absent: The text does not state what the hazard could do.
  7. absent: Hazard name alone does not satisfy impact.
  8. absent: No life-threat or injury consequence is named.
  9. absent: No explicit consequence is present.
  10. absent: Coded: severity not indicated.
  11. absent: No consequence or severity language is stated.
  12. absent: Coded: severity language missing.
  13. absent: Coded: impact language absent.
  14. absent: Impact is not conveyed beyond the hazard name.
  15. absent: Coded: outcome not stated.
  16. absent: Coded: no harm or severity phrase appears.
  17. absent: Coded: no impact cue.
  18. absent: Coded: impact remains unstated.
  19. absent: Coded: no consequence wording.
  20. absent: Coded: impact element absent.
  21. absent: Coded: the text does not state what the hazard could do.
  22. absent: Coded: hazard name alone does not satisfy impact.
  23. absent: Coded: no life-threat or injury consequence is named.
  24. absent: Coded: no explicit consequence is present.
  25. absent: Coded: severity not indicated.