Campus Alert Archive
UMN

Robbery occurred yesterday, 10/20/24, at 8:30 am near the intersection of Huron Blvd

AI-generated · every claim is source-linked
MNrobberytimely warninghigh confidence
Compare →
Under Investigation

UMN Public Safety posted 1 Safety Notification(s) on 2024-10-21. Verbatim from the official alerts archive.

Alerts
1
Response
—
Killed
0
Injured
0
Institution
University of Minnesota
Public R1 · MN
All UMN cases →
SAFE-U
Official alert policy
Read when and how UMN says it will use SAFE-U: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

1 message in sequence · 1 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.

INITIAL ALERTMulti-channel
Verified verbatim589 chars
U of M Twin Cities: Robbery occurred yesterday, 10/20/24, at 8:30 am near the intersection of Huron Blvd and Washington Ave Se. UMPD learned of the incident today. Victim was assaulted and his groceries were taken. Suspect was described as a male, approx. 30 years old, 5'10", thin build, beard, wearing a grey hooded sweatshirt, dark pants and a black backpack. This occurred off campus and did not involve campus community members. If you have any information about this incident, contact Minneapolis Police at 612-673-3000. Updates and safety tips at: z.umn.edu/alerts. SAFE-U EMERGENCY
Verify this quote
UMN Department of Public Safety Safety Notifications (SAFE-U / Dinkytown)publicsafety.umn.edufind archived copies
Exact text from official publicsafety.umn.edu/alerts archive page.
Message elements

How the first alert is built

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.

U of M Twin Cities: Robbery occurred yesterday, 10/20/24, at 8:30 am near the intersection of Huron Blvd and Washington Ave Se. UMPD learned of the incident today. Victim was assaulted and his groceries were taken. Suspect was described as a male, approx. 30 years old, 5'10", thin build, beard, wearing a grey hooded sweatshirt, dark pants and a black backpack. This occurred off campus and did not involve campus community members. If you have any information about this incident, contact Minneapolis Police at 612-673-3000. Updates and safety tips at: z.umn.edu/alerts. SAFE-U EMERGENCY

  • Sourcepresent25/25

    Final assessment

    Unanimous: signed 'U of M Twin Cities' with 'SAFE-U EMERGENCY' tag and UMPD referenced as the issuing authority.

    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 'U of M Twin Cities' / 'SAFE-U EMERGENCY'.
    2. present: 'U of M Twin Cities' plus 'SAFE-U EMERGENCY' tag.
    3. present: 'U of M Twin Cities' and 'UMPD' identified.
    4. present: Signed 'U of M Twin Cities' and 'SAFE-U EMERGENCY'
    5. present: Signed "U of M Twin Cities" and "SAFE-U EMERGENCY"
    6. present: Signed "U of M Twin Cities" and "SAFE-U EMERGENCY".
    7. present: 'U of M Twin Cities... UMPD learned of the incident'.
    8. present: Signed 'U of M Twin Cities'.
    9. present: "U of M Twin Cities" / SAFE-U EMERGENCY, UMPD mentioned
    10. present: Signed 'U of M Twin Cities' 'SAFE-U EMERGENCY'.
    11. present: Signed 'U of M Twin Cities'.
    12. present: Signed 'U of M Twin Cities' and 'SAFE-U EMERGENCY'
    13. present: Signed 'U of M Twin Cities,' 'SAFE-U EMERGENCY' branding.
    14. present: Branded "U of M Twin Cities" and "SAFE-U EMERGENCY" signatures.
    15. present: Signed 'U of M Twin Cities' and 'SAFE-U EMERGENCY'.
    16. present: Signed 'U of M Twin Cities' and 'SAFE-U EMERGENCY'.
    17. present: 'U of M Twin Cities' identified as sender.
    18. present: Signed 'U of M Twin Cities' with SAFE-U EMERGENCY tag
    19. present: Signed 'U of M Twin Cities'.
    20. present: Signed "U of M Twin Cities...SAFE-U EMERGENCY".
    21. present: Signed 'U of M Twin Cities' / 'SAFE-U EMERGENCY'.
    22. present: 'U of M Twin Cities' and 'UMPD' identify the issuer, tagged 'SAFE-U EMERGENCY'.
    23. present: Signature 'U of M Twin Cities', 'SAFE-U EMERGENCY'.
    24. present: References 'UMPD' and 'Minneapolis Police'.
    25. present: "U of M Twin Cities"
  • Hazardpresent25/25

    Final assessment

    Unanimous: a 'Robbery' with the 'Victim was assaulted' is explicitly 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. present: 'Robbery occurred... Victim was assaulted'.
    2. present: 'Robbery occurred' with victim assaulted, groceries taken.
    3. present: 'Robbery occurred... Victim was assaulted.'
    4. present: 'Robbery occurred' with assault named
    5. present: Names "Robbery" with assault
    6. present: "Robbery occurred" (victim assaulted, groceries taken) specifically named.
    7. present: 'Robbery occurred... Victim was assaulted'.
    8. present: Names a 'Robbery' where 'Victim was assaulted'.
    9. present: "Robbery...Victim was assaulted"
    10. present: 'Victim was assaulted and his groceries were taken.'
    11. present: States a robbery where the victim was assaulted.
    12. present: States 'Robbery occurred' and victim assaulted
    13. present: 'Robbery occurred... Victim was assaulted and his groceries were taken.'
    14. present: States "Robbery" with assault specifically.
    15. present: 'Robbery occurred' and victim assaulted.
    16. present: 'Robbery occurred' and victim 'was assaulted'.
    17. present: 'Robbery occurred... Victim was assaulted'.
    18. present: 'Robbery occurred...Victim was assaulted'
    19. present: 'Victim was assaulted and his groceries were taken'.
    20. present: "Robbery occurred," with the victim assaulted.
    21. present: States 'Victim was assaulted and his groceries were taken'.
    22. present: States 'Robbery occurred' with victim assaulted.
    23. present: 'Victim was assaulted and his groceries were taken.'
    24. present: Names 'Robbery' where 'Victim was assaulted'.
    25. present: "Robbery occurred" with victim assaulted
  • Locationpresent25/25

    Final assessment

    Unanimous: 'near the intersection of Huron Blvd and Washington Ave Se' is specifically given.

    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: 'near the intersection of Huron Blvd and Washington Ave Se'.
    2. present: 'near the intersection of Huron Blvd and Washington Ave Se' given.
    3. present: 'near the intersection of Huron Blvd and Washington Ave Se.'
    4. present: 'near the intersection of Huron Blvd and Washington Ave Se'
    5. present: Names "Huron Blvd and Washington Ave Se"
    6. present: "near the intersection of Huron Blvd and Washington Ave Se" given.
    7. present: 'near the intersection of Huron Blvd and Washington Ave Se'.
    8. present: States 'near the intersection of Huron Blvd and Washington Ave Se'.
    9. present: "near the intersection of Huron Blvd and Washington Ave Se"
    10. present: 'near the intersection of Huron Blvd and Washington Ave Se'.
    11. present: Names the intersection of Huron Blvd and Washington Ave SE.
    12. present: Names 'near the intersection of Huron Blvd and Washington Ave Se'
    13. present: 'near the intersection of Huron Blvd and Washington Ave Se.'
    14. present: Names "Huron Blvd and Washington Ave Se".
    15. present: 'near the intersection of Huron Blvd and Washington Ave Se'.
    16. present: 'near the intersection of Huron Blvd and Washington Ave Se'.
    17. present: 'near the intersection of Huron Blvd and Washington Ave Se'.
    18. present: 'near the intersection of Huron Blvd and Washington Ave Se'
    19. present: 'near the intersection of Huron Blvd and Washington Ave Se'.
    20. present: "near the intersection of Huron Blvd and Washington Ave Se".
    21. present: 'near the intersection of Huron Blvd and Washington Ave Se'.
    22. present: Gives 'near the intersection of Huron Blvd and Washington Ave Se'.
    23. present: 'near the intersection of Huron Blvd and Washington Ave Se'.
    24. present: Names 'near the intersection of Huron Blvd and Washington Ave Se'.
    25. present: "near the intersection of Huron Blvd and Washington Ave Se"
  • Guidancepresent21/25

    Final assessment

    Large majority (21 of 25) counted the instruction to 'contact Minneapolis Police' with information as guidance, though several reads note it is only a reporting request, not 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: 'contact Minneapolis Police at 612-673-3000'.
    2. present: 'contact Minneapolis Police at 612-673-3000' instructs those with information.
    3. present: 'contact Minneapolis Police at 612-673-3000.'
    4. absent: Only asks to contact police with info, no protective action
    5. present: Tells to "contact Minneapolis Police" with information
    6. present: "If you have any information about this incident, contact Minneapolis Police at 612-673-3000."
    7. present: 'If you have any information about this incident, contact Minneapolis Police.'
    8. present: Instructs to 'contact Minneapolis Police' with information.
    9. present: "contact Minneapolis Police" if info available
    10. present: 'contact Minneapolis Police at 612-673-3000.'
    11. present: Instructs to contact Minneapolis Police with information.
    12. absent: Only asks recipients to contact police with information, no protective action
    13. absent: Only 'contact Minneapolis Police,' not a protective action for recipients.
    14. present: Instructs to "contact Minneapolis Police" with information.
    15. present: 'contact Minneapolis Police at 612-673-3000' if info known.
    16. present: 'contact Minneapolis Police at 612-673-3000' if information.
    17. present: 'contact Minneapolis Police at 612-673-3000.'
    18. present: 'contact Minneapolis Police at 612-673-3000'
    19. present: 'contact Minneapolis Police at 612-673-3000'.
    20. present: "Contact Minneapolis Police at 612-673-3000."
    21. absent: Only asks people with info to contact police, not protective action.
    22. present: Instructs to 'contact Minneapolis Police at 612-673-3000'.
    23. present: 'If you have any information about this incident, contact Minneapolis Police'.
    24. present: Instructs to 'contact Minneapolis Police' with information.
    25. present: "contact Minneapolis Police at 612-673-3000"
  • Timepresent25/25

    Final assessment

    Unanimous: 'yesterday, 10/20/24, at 8:30 am' is given.

    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: 'yesterday, 10/20/24, at 8:30 am'.
    2. present: 'yesterday, 10/20/24, at 8:30 am' given.
    3. present: 'yesterday, 10/20/24, at 8:30 am.'
    4. present: 'yesterday, 10/20/24, at 8:30 am' given
    5. present: States "10/20/24, at 8:30 am"
    6. present: "yesterday, 10/20/24, at 8:30 am" given.
    7. present: 'occurred yesterday, 10/20/24, at 8:30 am'.
    8. present: States 'yesterday, 10/20/24, at 8:30 am'.
    9. present: "yesterday, 10/20/24, at 8:30 am"
    10. present: 'yesterday, 10/20/24, at 8:30 am'.
    11. present: States '10/20/24, at 8:30 am'.
    12. present: Gives 'yesterday, 10/20/24, at 8:30 am'
    13. present: 'yesterday, 10/20/24, at 8:30 am.'
    14. present: Gives "10/20/24, at 8:30 am".
    15. present: 'yesterday, 10/20/24, at 8:30 am' given.
    16. present: 'yesterday, 10/20/24, at 8:30 am'.
    17. present: 'yesterday, 10/20/24, at 8:30 am'.
    18. present: 'yesterday, 10/20/24, at 8:30 am'
    19. present: 'yesterday, 10/20/24, at 8:30 am'.
    20. present: "yesterday, 10/20/24, at 8:30 am".
    21. present: 'occurred yesterday, 10/20/24, at 8:30 am'.
    22. present: States 'yesterday, 10/20/24, at 8:30 am'.
    23. present: 'occurred yesterday, 10/20/24, at 8:30 am'.
    24. present: Gives 'yesterday, 10/20/24, at 8:30 am'.
    25. present: "yesterday, 10/20/24, at 8:30 am"
  • Impactabsent1/25

    Final assessment

    Nearly unanimous: no stated harm beyond describing the victim being assaulted; one dissenting read treated the assault mention itself as impact, but the majority correctly treats that as part of the hazard description, not a separate stated consequence.

    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 beyond describing the assault.
    2. absent: No explicit statement of potential harm or severity.
    3. absent: No stated potential harm or severity.
    4. absent: No stated harm or severity
    5. present: States "Victim was assaulted", conveying resulting harm
    6. absent: No stated consequence or severity beyond describing the robbery.
    7. absent: No stated potential harm or severity.
    8. absent: No stated consequence or severity.
    9. absent: no explicit statement of potential harm
    10. absent: No stated harm or severity.
    11. absent: No stated potential harm.
    12. absent: No stated potential harm or severity
    13. absent: No stated harm or severity described.
    14. absent: No statement of potential harm beyond describing the assault.
    15. absent: No stated potential harm or severity described.
    16. absent: No stated potential harm or severity beyond describing the assault.
    17. absent: No stated consequence or severity beyond the assault facts.
    18. absent: No stated consequence or severity beyond the assault description
    19. absent: No stated harm or severity.
    20. absent: No stated consequence beyond the assault fact itself.
    21. absent: No stated consequence or severity.
    22. absent: No explicit statement of potential harm.
    23. absent: No stated harm or severity beyond describing the assault/robbery.
    24. absent: No stated consequence beyond noting victim assaulted.
    25. absent: no stated potential harm or severity

Systematic AI judgments with visible reasoning, not human-validated codings.

About this analysis
Context

Background

From the official UMN Safety Notifications archive on 2024-10-21: 1 transmitted notice(s).
Analysis

Key Findings

Verbatim from publicsafety.umn.edu/alerts.
1 confirmed message(s).
Outcome
Official SAFE-U/Dinkytown sequence of 1 message(s).
Provenance

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.

  1. Official
    UMN Safety Notifications (Alerts)
    publicsafety.umn.edu
    archived copy
  2. Official
    UMN Department of Public Safety
    publicsafety.umn.edu
    archived copy
Cite this case

Campus Alert Archive. "University of Minnesota: Robbery occurred yesterday, 10/20/24, at 8:30 am near the intersection of Huron Blvd." Incident of October 21, 2024. Added July 2026. https://campusalertarchive.com/case/university-of-minnesota-morrill-robbery-same-day-2024-10-21/

Download case JSON

Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.

Tags
robberysafe-uminnesotaumn-alertsUnder Investigation
Added July 2026Updated July 2026Via ingestion