Campus Alert Archive
UMN

Assault with a dangerous weapon occurred yesterday, 10/22/24, at 2:06 AM, near the

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

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

Alerts
2
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

2 messages in sequence · 2 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 verbatim625 chars
U of M Twin Cities: Assault with a dangerous weapon occurred yesterday, 10/22/24, at 2:06 AM, near the intersection of Riverside Ave and 19th Ave S. UMPD learned of the incident today. Victims were being followed by another vehicle when they heard multiple shots fired towards their vehicle. No injuries were reported. There is no suspect information or suspect vehicle information. This occurred off campus and did involve campus community members. This is a MPD case. If you have any information about this incident, contact Minneapolis Police at 612-673-3000. Updates and safety tips at: z.umn.edu/alerts. Previous page ‹‹
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.
UPDATEMulti-channel+9 min
Verified verbatim607 chars
U of M Twin Cities: Assault with a dangerous weapon occurred yesterday, 10/22/24, at 2:06 AM, near the intersection of Riverside Ave and 19th Ave S. UMPD learned of the incident today. Victims were being followed by another vehicle when they heard multiple shots fired towards their vehicle. No injuries were reported. There is no suspect information or suspect vehicle information. This occurred off campus and did involve campus community members. This is a MPD case. If you have any information about this incident, contact Minneapolis Police at 612-673-3000. Updates and safety tips at: z.umn.edu/alerts
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: Assault with a dangerous weapon occurred yesterday, 10/22/24, at 2:06 AM, near the intersection of Riverside Ave and 19th Ave S. UMPD learned of the incident today. Victims were being followed by another vehicle when they heard multiple shots fired towards their vehicle. No injuries were reported. There is no suspect information or suspect vehicle information. This occurred off campus and did involve campus community members. This is a MPD case. If you have any information about this incident, contact Minneapolis Police at 612-673-3000. Updates and safety tips at: z.umn.edu/alerts. Previous page ‹‹

  • Sourcepresent25/25

    Final assessment

    Unanimous: signed 'U of M Twin Cities' with 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'.
    2. present: 'U of M Twin Cities' plus UMPD case reference.
    3. present: 'U of M Twin Cities' and 'UMPD' identified.
    4. present: Signed 'U of M Twin Cities'
    5. present: Signed "U of M Twin Cities"
    6. present: Signed "U of M Twin Cities".
    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" / UMPD named
    10. present: Signed 'U of M Twin Cities'.
    11. present: Signed 'U of M Twin Cities'.
    12. present: Signed 'U of M Twin Cities'
    13. present: Signed 'U of M Twin Cities.'
    14. present: Branded "U of M Twin Cities" signature.
    15. present: Signed 'U of M Twin Cities', mentions UMPD/MPD.
    16. present: Signed 'U of M Twin Cities'.
    17. present: 'U of M Twin Cities' identified as sender.
    18. present: Signed 'U of M Twin Cities' with UMPD noted
    19. present: Signed 'U of M Twin Cities'.
    20. present: Signed "U of M Twin Cities".
    21. present: Signed 'U of M Twin Cities'.
    22. present: 'U of M Twin Cities' and 'UMPD' identify the issuer.
    23. present: Signature 'U of M Twin Cities'.
    24. present: References 'UMPD' and 'Minneapolis Police', signed 'U of M Twin Cities'.
    25. present: "U of M Twin Cities"
  • Hazardpresent25/25

    Final assessment

    Unanimous: 'Assault with a dangerous weapon' involving 'multiple shots fired' toward the victims' vehicle 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: 'Assault with a dangerous weapon... shots fired towards their vehicle'.
    2. present: 'Assault with a dangerous weapon' and shots fired at vehicle named.
    3. present: 'Assault with a dangerous weapon... multiple shots fired.'
    4. present: 'Assault with a dangerous weapon' and shots fired named
    5. present: Names "Assault with a dangerous weapon" and "multiple shots fired"
    6. present: "Assault with a dangerous weapon" (shots fired towards their vehicle) specifically named.
    7. present: 'Assault with a dangerous weapon... heard multiple shots fired'.
    8. present: Names 'Assault with a dangerous weapon' where victims 'heard multiple shots fired'.
    9. present: "Assault with a dangerous weapon...multiple shots fired"
    10. present: 'Assault with a dangerous weapon' and 'multiple shots fired'.
    11. present: States an assault with a dangerous weapon involving shots fired at a vehicle.
    12. present: States 'Assault with a dangerous weapon' and shots fired at vehicle
    13. present: 'Assault with a dangerous weapon... multiple shots fired towards their vehicle.'
    14. present: States "Assault with a dangerous weapon" with shots fired at vehicle.
    15. present: 'Assault with a dangerous weapon' with shots fired.
    16. present: 'Assault with a dangerous weapon' and 'multiple shots fired'.
    17. present: 'Assault with a dangerous weapon... multiple shots fired'.
    18. present: 'Assault with a dangerous weapon...multiple shots fired'
    19. present: 'heard multiple shots fired towards their vehicle'.
    20. present: "Assault with a dangerous weapon," with "multiple shots fired".
    21. present: States 'Assault with a dangerous weapon' and 'multiple shots fired'.
    22. present: States 'Assault with a dangerous weapon' with shots fired.
    23. present: 'Assault with a dangerous weapon...heard multiple shots fired'.
    24. present: Names 'Assault with a dangerous weapon' involving 'multiple shots fired'.
    25. present: "Assault with a dangerous weapon" and shots fired towards vehicle
  • Locationpresent25/25

    Final assessment

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

    Final assessment

    Narrow majority (14 of 25) counted the instruction to 'contact Minneapolis Police' with information as guidance; a substantial minority felt this is purely a reporting request rather than a protective action, reflecting genuine ambiguity in the message.

    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. absent: No direct protective action instructed, only report contact for info.
    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. absent: Only asks to contact police with information, not protective action
    6. present: "If you have any information about this incident, contact Minneapolis Police at 612-673-3000."
    7. absent: No direct protective-action instruction given, only case referral to police.
    8. present: Instructs to 'contact Minneapolis Police' with information.
    9. absent: no direct protective action instructed, only asks for info
    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 directive.
    14. present: Instructs to "contact Minneapolis Police" with information.
    15. absent: No direct protective instruction, only asks to contact police with info.
    16. present: 'contact Minneapolis Police at 612-673-3000' if information.
    17. absent: No instruction given beyond 'contact Minneapolis Police' for tips, which is informational not protective.
    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 Minneapolis Police, not protective action.
    22. present: Instructs to 'contact Minneapolis Police at 612-673-3000'.
    23. absent: No specific instruction beyond contacting police if info known, which is reporting not protective action.
    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/22/24, at 2:06 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/22/24, at 2:06 AM'.
    2. present: 'yesterday, 10/22/24, at 2:06 AM' given.
    3. present: 'yesterday, 10/22/24, at 2:06 AM.'
    4. present: 'yesterday, 10/22/24, at 2:06 AM' given
    5. present: States "yesterday, 10/22/24, at 2:06 AM"
    6. present: "yesterday, 10/22/24, at 2:06 AM" given.
    7. present: 'yesterday, 10/22/24, at 2:06 AM'.
    8. present: States 'yesterday, 10/22/24, at 2:06 AM'.
    9. present: "yesterday, 10/22/24, at 2:06 AM"
    10. present: 'yesterday, 10/22/24, at 2:06 AM'.
    11. present: States '10/22/24, at 2:06 AM'.
    12. present: Gives 'yesterday, 10/22/24, at 2:06 AM'
    13. present: 'yesterday, 10/22/24, at 2:06 AM.'
    14. present: Gives "10/22/24, at 2:06 AM".
    15. present: 'yesterday, 10/22/24, at 2:06 AM' given.
    16. present: 'yesterday, 10/22/24, at 2:06 AM'.
    17. present: 'yesterday, 10/22/24, at 2:06 AM'.
    18. present: 'yesterday, 10/22/24, at 2:06 AM'
    19. present: 'yesterday, 10/22/24, at 2:06 AM'.
    20. present: "yesterday, 10/22/24, at 2:06 AM".
    21. present: 'occurred yesterday, 10/22/24, at 2:06 AM'.
    22. present: States 'yesterday, 10/22/24, at 2:06 AM'.
    23. present: 'yesterday, 10/22/24, at 2:06 AM'.
    24. present: Gives 'yesterday, 10/22/24, at 2:06 AM'.
    25. present: "yesterday, 10/22/24, at 2:06 AM"
  • Impactabsent0/25

    Final assessment

    Unanimous: the message states 'No injuries were reported,' which negates rather than states potential harm, so no impact is conveyed.

    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: States 'no injuries were reported', not a stated potential harm.
    2. absent: 'No injuries were reported' explicitly negates impact stated.
    3. absent: 'No injuries were reported' negates rather than states impact.
    4. absent: 'No injuries were reported' negates rather than states impact
    5. absent: States "No injuries were reported", not a stated potential harm
    6. absent: "No injuries were reported" states absence of harm, not potential impact.
    7. absent: States 'No injuries were reported', not a stated potential harm.
    8. absent: No stated consequence or severity.
    9. absent: states "No injuries were reported", no stated potential harm
    10. absent: No stated harm or severity; notes 'no injuries were reported'.
    11. absent: No stated potential harm; notes no injuries.
    12. absent: No stated potential harm or severity
    13. absent: States 'No injuries were reported,' not a stated potential harm.
    14. absent: States "No injuries were reported", not potential harm.
    15. absent: States 'No injuries were reported', not a stated potential harm.
    16. absent: States 'No injuries were reported', not a forward-looking harm statement.
    17. absent: 'No injuries were reported' negates rather than states impact.
    18. absent: States 'No injuries were reported', not a stated potential harm
    19. absent: States 'No injuries were reported', not a stated harm.
    20. absent: "No injuries were reported" negates rather than states impact.
    21. absent: No stated consequence or severity, notes 'No injuries were reported'.
    22. absent: States 'No injuries were reported', not a forward-looking severity statement.
    23. absent: States 'No injuries were reported', no stated potential harm/severity.
    24. absent: States 'No injuries were reported', not a stated potential harm.
    25. absent: states "No injuries were reported", no stated potential harm

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-23: 2 transmitted notice(s).
Analysis

Key Findings

Verbatim from publicsafety.umn.edu/alerts.
2 confirmed message(s).
Outcome
Official SAFE-U/Dinkytown sequence of 2 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: Assault with a dangerous weapon occurred yesterday, 10/22/24, at 2:06 AM, near the." Incident of October 23, 2024. Added July 2026. https://campusalertarchive.com/case/university-of-minnesota-assault-dangerous-weapon-2024-10-23/

Download case JSON

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

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