Emailed threats from a former student close every campus for the afternoon

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

  All 25 reads agree the branded signature 'MC Alert' plus the '@montgomerycoll' reference clearly identifies the sender as Montgomery College.

  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: Signed 'MC Alert' referencing '@montgomerycoll'.
  2. present: 'MC Alert' and '@montgomerycoll' named
  3. present: Branded 'MC Alert' signature.
  4. present: 'MC Alert' branded signature and '@montgomerycoll' identified.
  5. present: 'MC Alert' identifies the sending system.
  6. present: Signed 'MC Alert', names '@montgomerycoll'.
  7. present: 'MC Alert' branded signature identifies sender.
  8. present: 'MC Alert' branded signature and '@montgomerycoll' identify the sender.
  9. present: Branded 'MC Alert' identifies Montgomery College's system.
  10. present: 'MC Alert' branded signature and '@montgomerycoll' named.
  11. present: Labeled 'MC Alert', references @montgomerycoll.
  12. present: 'MC Alert' branded signature and '@montgomerycoll' identify the sender.
  13. present: 'MC Alert' branded signature; '@montgomerycoll' named.
  14. present: Branded 'MC Alert' naming @montgomerycoll.
  15. present: Branded 'MC Alert' and '@montgomerycoll' identify the issuer.
  16. present: Branded 'MC Alert' signature, references '@montgomerycoll'.
  17. present: 'MC Alert' branded signature identifies the sending system (Montgomery College).
  18. present: Signed 'MC Alert' referring to '@montgomerycoll'.
  19. present: Branded 'MC Alert' with '@montgomerycoll' named.
  20. present: 'MC Alert' branded signature and '@montgomerycoll' identify sender.
  21. present: Signed 'MC Alert', '@montgomerycoll'.
  22. present: Branded 'MC Alert' and references '@montgomerycoll'
  23. present: Signed 'MC Alert' referencing '@montgomerycoll'.
  24. present: Branded 'MC Alert' and '@montgomerycoll' identify the sender.
  25. present: Branded 'MC Alert' referencing '@montgomerycoll'.
• Hazardabsent0/25

  Final assessment

  Unanimous: 'Code Red' is only a status code, no specific underlying hazard is ever 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: 'Code Red' is a generic label, no specific threat named.
  2. absent: 'Code Red' is a code label, not a specific hazard type
  3. absent: Only says 'URGENT - Code Red', no specific threat named.
  4. absent: 'Code Red' is a generic code without naming the specific threat.
  5. absent: 'Code Red' is a coded label, not a named specific threat.
  6. absent: 'Code Red' names a status level, not a specific hazard.
  7. absent: 'Code Red' is a generic status code, not a specific hazard type.
  8. absent: Only 'Code Red' is stated without naming the underlying hazard.
  9. absent: Only labeled 'Code Red' without stating the specific underlying threat.
  10. absent: 'Code Red' is a generic code, no specific hazard type named.
  11. absent: Only 'Code Red' given, no specific threat named.
  12. absent: 'Code Red' is a generic status code, not a named hazard.
  13. absent: 'Code Red' is a status label, not a specific named hazard.
  14. absent: 'Code Red' is a generic code, not a named specific threat.
  15. absent: Only 'Code Red' is stated, a generic code without naming a specific hazard.
  16. absent: 'Code Red' given without naming the underlying specific hazard.
  17. absent: 'Code Red' is a generic code, no specific hazard named.
  18. absent: Only 'Code Red' and closure mentioned, no specific hazard named.
  19. absent: Says 'Code Red' but does not specify what the underlying threat is.
  20. absent: 'Code Red' is a generic label, no specific hazard type named.
  21. absent: 'Code Red' is a coded term without naming a specific hazard.
  22. absent: Only 'Code Red' is used without naming a specific hazard
  23. absent: Only 'Code Red' is a code term, not a specific named hazard.
  24. absent: 'Code Red' is a generic code with no specific hazard named.
  25. absent: Only says 'Code Red' without naming the specific threat.
• Locationabsent4/25

  Final assessment

  Overwhelming majority found no specific location beyond generic campus closure; a small minority read the '@montgomerycoll' mention or 'onsite' as location, but that is not a specific place.

  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. absent: No specific location given beyond the college being 'CLOSED onsite'.
  2. absent: no specific campus location named beyond the institution itself
  3. absent: No specific location beyond implied campus-wide closure.
  4. absent: No specific campus location named, only 'onsite' generically.
  5. absent: No specific location is named.
  6. absent: No specific location beyond the college generally.
  7. present: '@montgomerycoll' campus implied.
  8. present: Refers to '@montgomerycoll' campus-wide closure.
  9. absent: No specific building or area named, general campus closure implied.
  10. absent: No specific location beyond the institution name itself.
  11. absent: No specific location named, only 'onsite' operations closed.
  12. absent: No specific campus or building location named, only 'onsite.'
  13. absent: No specific location beyond the institution itself named.
  14. absent: No specific location or campus name is given, only 'onsite'.
  15. present: Implies campus closure ('onsite') as location.
  16. absent: No specific location beyond the whole campus closure.
  17. absent: No specific campus/building named, generic '@montgomerycoll'.
  18. absent: No specific location given beyond the institution being closed generally.
  19. absent: No specific location given, only campus closure generally.
  20. absent: No specific location given beyond the institution itself.
  21. absent: No specific location given beyond 'onsite'.
  22. absent: No specific building or area named
  23. absent: No specific location named beyond general campus closure.
  24. present: Refers to campus closure generally via '@montgomerycoll'.
  25. absent: No specific building or area named, campus-wide closure only.
• Guidancepresent22/25

  Final assessment

  Most reads count the closure directive plus 'check your MC email for further information' as guidance, though a few dissent that this lacks a concrete protective action.

  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: Instructs to 'check your MC email for further information'.
  2. present: 'CLOSED onsite and all remote operations...suspended'
  3. present: Instructs to check MC email and states operations suspended.
  4. present: 'Please check your MC email for further information' is minimal guidance.
  5. present: States campus will be closed and to check email for further information.
  6. present: Instructs to 'check your MC email for further information'.
  7. present: 'Please check your MC email for further information' and closure directive.
  8. present: States campus 'will be CLOSED' and to 'check your MC email'.
  9. present: Instructs to 'check your MC email for further information.'
  10. present: 'CLOSED onsite and all remote operations/instructions/services are suspended.'
  11. absent: Closure announcement gives no protective action instruction.
  12. present: Instructs to 'check your MC email for further information.'
  13. present: 'will be CLOSED onsite...check your MC email.'
  14. present: Instructs to 'check your MC email for further information'.
  15. present: States campus closed and remote operations suspended, check email for info.
  16. absent: States closure but no protective action instruction given.
  17. present: 'CLOSED onsite and all remote operations...suspended. Please check your MC email.'
  18. present: Instructs to 'check your MC email for further information'.
  19. present: Instructs to check MC email for further information; closure order given.
  20. present: 'CLOSED onsite...check your MC email' instructs recipients.
  21. present: Instructs to 'check your MC email for further information'.
  22. absent: States campus is closed but gives no direct protective instruction
  23. present: Instructs to 'check your MC email for further information'.
  24. present: States operations 'CLOSED' and to check email for info.
  25. present: Instructs to 'check your MC email for further information', campus closed.
• Timepresent25/25

  Final assessment

  Unanimous: 'Effective at 1:30 p.m., Friday, October 11' gives an exact date and time.

  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: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  2. present: 'Effective at 1:30 p.m., Friday, October 11'
  3. present: Gives 'Effective at 1:30 p.m., Friday, October 11.'
  4. present: 'Effective at 1:30 p.m., Friday, October 11' given.
  5. present: States 'Effective at 1:30 p.m., Friday, October 11'.
  6. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  7. present: 'Effective at 1:30 p.m., Friday, October 11' given.
  8. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  9. present: States 'Effective at 1:30 p.m., Friday, October 11.'
  10. present: 'Effective at 1:30 p.m., Friday, October 11.'
  11. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  12. present: Gives 'Effective at 1:30 p.m., Friday, October 11.'
  13. present: 'Effective at 1:30 p.m., Friday, October 11.'
  14. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  15. present: Gives 'Effective at 1:30 p.m., Friday, October 11.'
  16. present: States 'Effective at 1:30 p.m., Friday, October 11'.
  17. present: 'Effective at 1:30 p.m., Friday, October 11' given.
  18. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  19. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  20. present: 'Effective at 1:30 p.m., Friday, October 11' gives specific date/time.
  21. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  22. present: Gives 'Effective at 1:30 p.m., Friday, October 11'
  23. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  24. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
  25. present: Gives 'Effective at 1:30 p.m., Friday, October 11'.
• Impactabsent0/25

  Final assessment

  Unanimous: no consequence or severity of the Code Red is ever 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 stated consequence.
  2. absent: no stated consequence or severity
  3. absent: No stated consequence or severity.
  4. absent: No stated potential harm or severity.
  5. absent: No stated potential harm.
  6. absent: No stated harm or severity.
  7. absent: No stated potential harm or severity conveyed.
  8. absent: No explicit statement of danger or severity.
  9. absent: No stated potential harm or severity.
  10. absent: No stated potential harm/severity.
  11. absent: No stated consequence or severity.
  12. absent: No statement of potential harm or severity.
  13. absent: No stated harm or severity.
  14. absent: No explicit statement of potential harm.
  15. absent: No stated consequence or severity.
  16. absent: No stated consequence or severity.
  17. absent: No stated consequence or severity.
  18. absent: No statement of potential harm or severity.
  19. absent: No explicit statement of potential harm or severity.
  20. absent: No stated consequence or severity conveyed.
  21. absent: No stated consequence.
  22. absent: No statement of potential harm or severity
  23. absent: No stated potential harm or severity.
  24. absent: No statement of potential harm.
  25. absent: No stated potential harm.