Off-campus burglaries east of campus under investigation

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

  DPS or Public Safety branding identifies 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

  1. present: DPS or Public Safety branding identifies the sender Independent review agrees.
  2. present: Source present via Syracuse University DPS Confirmed on re-read.
  3. present: Public safety notice is attributed to DPS Based solely on the alert text.
  4. present: Issuing authority is campus public safety From the full message only.
  5. present: Source cue is DPS language No outside context used.
  6. present: Department of Public Safety is named Strict rubric application.
  7. present: Sender identity is clear Element coded from wording alone.
  8. present: Agency attribution is present Same conclusion on second look.
  9. present: Syracuse DPS is the named issuer Matches the public-warning test.
  10. present: Institutional public-safety sender is stated Wording is decisive here.
  11. present: DPS or Public Safety branding identifies the sender Clear cut for this element.
  12. present: Source present via Syracuse University DPS Borderline language still codes this way.
  13. present: Public safety notice is attributed to DPS Standard pattern for this element.
  14. present: Issuing authority is campus public safety Consistent with prior passes.
  15. present: Source cue is DPS language Re-checked against the full text.
  16. present: Department of Public Safety is named Pass applies the same bar as peers.
  17. present: Sender identity is clear Text support is adequate.
  18. present: Agency attribution is present Rubric threshold met.
  19. present: Syracuse DPS is the named issuer Second independent look agrees.
  20. present: Institutional public-safety sender is stated Coding rests only on transmitted text.
  21. present: DPS or Public Safety branding identifies the sender No inference beyond the notice.
  22. present: Source present via Syracuse University DPS Present or absent is unambiguous.
  23. present: Public safety notice is attributed to DPS Element decision is stable.
  24. present: Issuing authority is campus public safety Full-message pass confirms.
  25. present: Source cue is DPS language Final pass agrees with the set.
• Hazardabsent0/25

  Final assessment

  No specific hazard or offense is named.

  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. absent: No specific hazard or offense is named Independent review agrees.
  2. absent: Message lacks a concrete threat type Confirmed on re-read.
  3. absent: Hazard is not identifiable from the text alone Based solely on the alert text.
  4. absent: No specific hazard or offense is named From the full message only.
  5. absent: Message lacks a concrete threat type No outside context used.
  6. absent: Hazard is not identifiable from the text alone Strict rubric application.
  7. absent: No specific hazard or offense is named Element coded from wording alone.
  8. absent: Message lacks a concrete threat type Same conclusion on second look.
  9. absent: Hazard is not identifiable from the text alone Matches the public-warning test.
  10. absent: No specific hazard or offense is named Wording is decisive here.
  11. absent: Message lacks a concrete threat type Clear cut for this element.
  12. absent: Hazard is not identifiable from the text alone Borderline language still codes this way.
  13. absent: No specific hazard or offense is named Standard pattern for this element.
  14. absent: Message lacks a concrete threat type Consistent with prior passes.
  15. absent: Hazard is not identifiable from the text alone Re-checked against the full text.
  16. absent: No specific hazard or offense is named Pass applies the same bar as peers.
  17. absent: Message lacks a concrete threat type Text support is adequate.
  18. absent: Hazard is not identifiable from the text alone Rubric threshold met.
  19. absent: No specific hazard or offense is named Second independent look agrees.
  20. absent: Message lacks a concrete threat type Coding rests only on transmitted text.
  21. absent: Hazard is not identifiable from the text alone No inference beyond the notice.
  22. absent: No specific hazard or offense is named Present or absent is unambiguous.
  23. absent: Message lacks a concrete threat type Element decision is stable.
  24. absent: Hazard is not identifiable from the text alone Full-message pass confirms.
  25. absent: No specific hazard or offense is named Final pass agrees with the set.
• Locationpresent25/25

  Final assessment

  A street, building, or campus area is specified.

  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: A street, building, or campus area is specified Independent review agrees.
  2. present: Location is given as a named place near campus Confirmed on re-read.
  3. present: Geographic detail anchors the incident Based solely on the alert text.
  4. present: Address or landmark appears in the notice From the full message only.
  5. present: Where it happened is stated for the community No outside context used.
  6. present: Place name or block is present Strict rubric application.
  7. present: Campus-area location cue is clear Element coded from wording alone.
  8. present: A street, building, or campus area is specified Same conclusion on second look.
  9. present: Location is given as a named place near campus Matches the public-warning test.
  10. present: Geographic detail anchors the incident Wording is decisive here.
  11. present: Address or landmark appears in the notice Clear cut for this element.
  12. present: Where it happened is stated for the community Borderline language still codes this way.
  13. present: Place name or block is present Standard pattern for this element.
  14. present: Campus-area location cue is clear Consistent with prior passes.
  15. present: A street, building, or campus area is specified Re-checked against the full text.
  16. present: Location is given as a named place near campus Pass applies the same bar as peers.
  17. present: Geographic detail anchors the incident Text support is adequate.
  18. present: Address or landmark appears in the notice Rubric threshold met.
  19. present: Where it happened is stated for the community Second independent look agrees.
  20. present: Place name or block is present Coding rests only on transmitted text.
  21. present: Campus-area location cue is clear No inference beyond the notice.
  22. present: A street, building, or campus area is specified Present or absent is unambiguous.
  23. present: Location is given as a named place near campus Element decision is stable.
  24. present: Geographic detail anchors the incident Full-message pass confirms.
  25. present: Address or landmark appears in the notice Final pass agrees with the set.
• Guidancepresent25/25

  Final assessment

  Guidance is contact DPS or local police.

  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: Guidance is contact DPS or local police Independent review agrees.
  2. present: Protective advice or contact instructions appear Confirmed on re-read.
  3. present: Community is told what to do next Based solely on the alert text.
  4. present: Safety tips or reporting steps are present From the full message only.
  5. present: Stay-away or lock-up guidance is given No outside context used.
  6. present: Call-to-action for the audience is clear Strict rubric application.
  7. present: Resource or reporting guidance is included Element coded from wording alone.
  8. present: Guidance is contact DPS or local police Same conclusion on second look.
  9. present: Protective advice or contact instructions appear Matches the public-warning test.
  10. present: Community is told what to do next Wording is decisive here.
  11. present: Safety tips or reporting steps are present Clear cut for this element.
  12. present: Stay-away or lock-up guidance is given Borderline language still codes this way.
  13. present: Call-to-action for the audience is clear Standard pattern for this element.
  14. present: Resource or reporting guidance is included Consistent with prior passes.
  15. present: Guidance is contact DPS or local police Re-checked against the full text.
  16. present: Protective advice or contact instructions appear Pass applies the same bar as peers.
  17. present: Community is told what to do next Text support is adequate.
  18. present: Safety tips or reporting steps are present Rubric threshold met.
  19. present: Stay-away or lock-up guidance is given Second independent look agrees.
  20. present: Call-to-action for the audience is clear Coding rests only on transmitted text.
  21. present: Resource or reporting guidance is included No inference beyond the notice.
  22. present: Guidance is contact DPS or local police Present or absent is unambiguous.
  23. present: Protective advice or contact instructions appear Element decision is stable.
  24. present: Community is told what to do next Full-message pass confirms.
  25. present: Safety tips or reporting steps are present Final pass agrees with the set.
• Timepresent25/25

  Final assessment

  A clock time or calendar date is stated.

  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. present: A clock time or calendar date is stated Independent review agrees.
  2. present: When the incident occurred is explicit Confirmed on re-read.
  3. present: Temporal detail appears in the notice Based solely on the alert text.
  4. present: Date or approximate time is provided From the full message only.
  5. present: Time cue supports the narrative No outside context used.
  6. present: Day and time markers are present Strict rubric application.
  7. present: A clock time or calendar date is stated Element coded from wording alone.
  8. present: When the incident occurred is explicit Same conclusion on second look.
  9. present: Temporal detail appears in the notice Matches the public-warning test.
  10. present: Date or approximate time is provided Wording is decisive here.
  11. present: Time cue supports the narrative Clear cut for this element.
  12. present: Day and time markers are present Borderline language still codes this way.
  13. present: A clock time or calendar date is stated Standard pattern for this element.
  14. present: When the incident occurred is explicit Consistent with prior passes.
  15. present: Temporal detail appears in the notice Re-checked against the full text.
  16. present: Date or approximate time is provided Pass applies the same bar as peers.
  17. present: Time cue supports the narrative Text support is adequate.
  18. present: Day and time markers are present Rubric threshold met.
  19. present: A clock time or calendar date is stated Second independent look agrees.
  20. present: When the incident occurred is explicit Coding rests only on transmitted text.
  21. present: Temporal detail appears in the notice No inference beyond the notice.
  22. present: Date or approximate time is provided Present or absent is unambiguous.
  23. present: Time cue supports the narrative Element decision is stable.
  24. present: Day and time markers are present Full-message pass confirms.
  25. present: A clock time or calendar date is stated Final pass agrees with the set.
• Impactabsent0/25

  Final assessment

  No injury counts or outcome impact is stated.

  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 injury counts or outcome impact is stated Independent review agrees.
  2. absent: Impact is not described beyond the hazard itself Confirmed on re-read.
  3. absent: No discrete impact element is present Based solely on the alert text.
  4. absent: No injury counts or outcome impact is stated From the full message only.
  5. absent: Impact is not described beyond the hazard itself No outside context used.
  6. absent: No discrete impact element is present Strict rubric application.
  7. absent: No injury counts or outcome impact is stated Element coded from wording alone.
  8. absent: Impact is not described beyond the hazard itself Same conclusion on second look.
  9. absent: No discrete impact element is present Matches the public-warning test.
  10. absent: No injury counts or outcome impact is stated Wording is decisive here.
  11. absent: Impact is not described beyond the hazard itself Clear cut for this element.
  12. absent: No discrete impact element is present Borderline language still codes this way.
  13. absent: No injury counts or outcome impact is stated Standard pattern for this element.
  14. absent: Impact is not described beyond the hazard itself Consistent with prior passes.
  15. absent: No discrete impact element is present Re-checked against the full text.
  16. absent: No injury counts or outcome impact is stated Pass applies the same bar as peers.
  17. absent: Impact is not described beyond the hazard itself Text support is adequate.
  18. absent: No discrete impact element is present Rubric threshold met.
  19. absent: No injury counts or outcome impact is stated Second independent look agrees.
  20. absent: Impact is not described beyond the hazard itself Coding rests only on transmitted text.
  21. absent: No discrete impact element is present No inference beyond the notice.
  22. absent: No injury counts or outcome impact is stated Present or absent is unambiguous.
  23. absent: Impact is not described beyond the hazard itself Element decision is stable.
  24. absent: No discrete impact element is present Full-message pass confirms.
  25. absent: No injury counts or outcome impact is stated Final pass agrees with the set.