Skip to content
Campus Alert Archive
UW

active threat emergency update on Alert blog

AI-generated · every claim is source-linked
WAactive threattimely warninghigh confidence
Under Investigation

University of Washington published an official alert update on or about 2022-08-30. Full text is preserved from the official archive.

Alerts
2
Response
—
Killed
0
Injured
0
Institution
University of Washington
Public R1 · WA
All UW cases →
~50,000 studentsUW Alert
Official alert policy
Read when and how UW says it will use UW Alert: 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 verbatim585 chars
UPDATED at 9:35 a.m. Tuesday: The reports of shots fired early Tuesday morning in the area of 18th Ave. NE and NE 50th Street may have come from a cap gun after two men were heard arguing in an alley. Shortly after the reported loud bang, both men were seen walking away from the area in different directions. Officers were unable to find either person when they arrived, and there were no spent casings or other evidence found at the scene. ORIGINAL POST: Re: shots fired at NE 47th and 18th Ave NE. Shooter and victim not found. Scene secured. Info: alert.uw.edu [sent 5:42 Tuesday]
Transcribed from official institutional alert archive page.
Confirmed-verbatim recovery from live institutional source.
INITIAL ALERTMulti-channel
Verified verbatim124 chars
Shooting reported at NE 47th St and 18th Ave NE at 5:12 AM. Shooter at large, traveling west. Avoid area. Info: alert.uw.edu
Transcribed from official emergency.uw.edu Alert Blog entry body.
Confirmed-verbatim recovery from live institutional source.
Message elements

How the first alert is built

To check this alert, Claude Opus 5 (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.

UPDATED at 9:35 a.m. Tuesday: The reports of shots fired early Tuesday morning in the area of 18th Ave. NE and NE 50th Street may have come from a cap gun after two men were heard arguing in an alley. Shortly after the reported loud bang, both men were seen walking away from the area in different directions. Officers were unable to find either person when they arrived, and there were no spent casings or other evidence found at the scene. ORIGINAL POST: Re: shots fired at NE 47th and 18th Ave NE. Shooter and victim not found. Scene secured. Info: alert.uw.edu [sent 5:42 Tuesday]

  • Sourcepresent25/25

    Final assessment

    Present, 25 of 25: "Officers" are described as responding and the message signs itself with the campus channel, "Info: alert.uw.edu".

    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: "Officers" are referenced and the message points to the UW alert address "alert.uw.edu".
    2. present: Officers are referenced and the message signs itself with alert.uw.edu as the alerting channel.
    3. present: Officers are referenced as responding, and alert.uw.edu is given as the alert channel.
    4. present: "Officers" and the branded "alert.uw.edu" signature identify the issuing authority.
    5. present: "Officers were unable to find either person" names police as the source of the account.
    6. present: It names "Officers" investigating and signs with the "alert.uw.edu" alert address.
    7. present: "Officers" are referenced and the message signs off with the branded "alert.uw.edu" pointer.
    8. present: "Officers" are referenced and the post points to the branded address "alert.uw.edu".
    9. present: "Officers" respond and the message signs off with the branded "Info: alert.uw.edu".
    10. present: "Officers" and the "alert.uw.edu" alert-system signature identify the sending authority.
    11. present: "Officers" are named and the message signs off with the alert.uw.edu address.
    12. present: "Officers" are referenced and the message signs off with the branded "Info: alert.uw.edu".
    13. present: Officers are referenced and the original text signs off with the branded "Info: alert.uw.edu".
    14. present: The branded link "alert.uw.edu" plus "Officers" identifies the UW alert system as sender.
    15. present: "Officers" are mentioned and the alert signs off with the UW alert address alert.uw.edu.
    16. present: "Officers were unable to find either person" plus the signature "Info: alert.uw.edu" identify the sender.
    17. present: "Officers" respond and the message signs off with "Info: alert.uw.edu", a branded source.
    18. present: "Officers were unable to find either person" plus the "alert.uw.edu" signature identify the source.
    19. present: "Officers" are mentioned and the message signs off with the branded "Info: alert.uw.edu".
    20. present: "Officers" are referenced and the message points to the branded "alert.uw.edu" source.
    21. present: "Officers" are referenced and the message signs off with the branded pointer "alert.uw.edu".
    22. present: "Officers" are referenced and the message points to "alert.uw.edu", the branded alert channel.
    23. present: "Officers" are named and the message signs off with the branded pointer "Info: alert.uw.edu".
    24. present: "Officers" are named as responding, and the message signs off with "Info: alert.uw.edu".
    25. present: "Officers" are named and the message signs off with the branded "Info: alert.uw.edu".
  • Hazardpresent25/25

    Final assessment

    Present, 25 of 25: the subject line is "shots fired at NE 47th and 18th Ave NE", later reassessed as possibly coming "from a cap gun".

    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: It reports "shots fired", later reassessed as possibly "a cap gun".
    2. present: Shots fired is named, later attributed to a possible cap gun.
    3. present: Shots fired is named, later attributed to a possible cap gun.
    4. present: It reports "shots fired", a specific gunfire threat, later attributed to a possible cap gun.
    5. present: The subject is "shots fired", later attributed to a possible cap gun.
    6. present: The subject line is "shots fired", a specific firearms hazard.
    7. present: The subject line reads "Re: shots fired", naming gunfire as the threat.
    8. present: It reports "shots fired", later reassessed as possibly a cap gun, but gunfire is named.
    9. present: It names "shots fired at NE 47th and 18th Ave NE" as the reported threat.
    10. present: The subject is "shots fired", a specific gunfire threat, later attributed to a cap gun.
    11. present: "Shots fired" is named, though later attributed to a possible cap gun.
    12. present: It names "shots fired", later attributed to a possible cap gun.
    13. present: "Shots fired" is the named hazard, later reassessed as possibly a cap gun.
    14. present: "shots fired" names a specific gunfire threat, later attributed to a possible cap gun.
    15. present: It names "shots fired", a specific gunfire threat, later attributed to a cap gun.
    16. present: "shots fired" is named, later explained as possibly "a cap gun".
    17. present: It reports "shots fired", though later attributed to a possible cap gun.
    18. present: It names "shots fired", a specific gunfire hazard, later reassessed as a possible cap gun.
    19. present: It reports "shots fired", later reassessed as possibly a cap gun, still a named gunfire threat.
    20. present: It reports "shots fired", naming a firearms threat even though a cap gun is later suspected.
    21. present: It names "shots fired", later revised to a possible cap gun, a specific gunfire report.
    22. present: It names "shots fired", a specific firearm hazard, later attributed to a possible cap gun.
    23. present: It names "shots fired", a specific gunfire threat, later attributed to a possible cap gun.
    24. present: It reports "shots fired", later reassessed as possibly "a cap gun", still a named threat.
    25. present: "Shots fired" is the specific hazard, later reassessed as possibly "a cap gun".
  • Locationpresent25/25

    Final assessment

    Present, 25 of 25: two cross streets are given, "NE 47th and 18th Ave NE" in the original and "18th Ave. NE and NE 50th Street" in the update.

    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: The area is "NE 47th and 18th Ave NE" and "18th Ave. NE and NE 50th Street".
    2. present: NE 47th and 18th Ave NE, and 18th Ave. NE at NE 50th Street, locate the reports.
    3. present: NE 47th and 18th Ave NE, and the area of 18th Ave. NE and NE 50th Street, are stated.
    4. present: Places given are "NE 47th and 18th Ave NE" and 18th Ave. NE near NE 50th Street.
    5. present: Locations given are 18th Ave. NE and NE 50th Street, and NE 47th and 18th Ave NE.
    6. present: Locations are given as "NE 47th and 18th Ave NE" and "18th Ave. NE and NE 50th Street".
    7. present: It gives "NE 47th and 18th Ave NE" and the area of 18th Ave. NE and NE 50th Street.
    8. present: Places given are "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE".
    9. present: Places named are "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE".
    10. present: It names "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE".
    11. present: Locations given are NE 47th and 18th Ave NE, and 18th Ave. NE and NE 50th Street.
    12. present: It gives "NE 47th and 18th Ave NE" and the area of 18th Ave. NE and NE 50th Street.
    13. present: Both NE 47th and 18th Ave NE and the area of 18th Ave. NE and NE 50th Street are given.
    14. present: It locates the report at NE 47th and 18th Ave NE.
    15. present: Locations given include "NE 47th and 18th Ave NE" and 18th Ave NE at NE 50th Street.
    16. present: It cites "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE".
    17. present: Places named are "NE 47th and 18th Ave NE" and "18th Ave. NE and NE 50th Street".
    18. present: Places given are "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE".
    19. present: Locations given are "NE 47th and 18th Ave NE" and "18th Ave. NE and NE 50th Street".
    20. present: Locations given are "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE".
    21. present: Locations given are "NE 47th and 18th Ave NE" and "18th Ave. NE and NE 50th Street".
    22. present: It gives "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE".
    23. present: Locations are "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE".
    24. present: Locations "18th Ave. NE and NE 50th Street" and "NE 47th and 18th Ave NE" are given.
    25. present: It cites "NE 47th and 18th Ave NE" and "18th Ave. NE and NE 50th Street".
  • Guidanceabsent1/25

    Final assessment

    Absent on a 1 of 25 vote: the message only reports that the "Scene secured" and asks nothing of recipients; the lone dissenter counted the "Info: alert.uw.edu" pointer, which is a link, 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. absent: No action is requested of readers; the scene is simply described as secured.
    2. absent: Recipients are only pointed to an info page; no protective action is requested.
    3. absent: No protective instruction is given; readers are only pointed to an info page.
    4. absent: The message only reports that the scene is secured and points to a web page, with no instruction to act.
    5. present: "Info: alert.uw.edu" points recipients to the alert page for further updates.
    6. absent: The alert reports only that the scene is secured and points to a webpage, with no protective action.
    7. absent: It reports that the scene is secured and links to info, but directs no protective action.
    8. absent: Readers get only an information link, with no avoid, shelter, or call instruction.
    9. absent: No action is requested of readers, the message reports that the scene was secured.
    10. absent: No protective action is asked of readers; the scene is simply reported secured.
    11. absent: No action is requested of readers; the scene is reported as secured with only a web link offered.
    12. absent: Neither entry tells recipients to do anything; the scene is simply reported secured.
    13. absent: The text says the scene is secured but never asks recipients to take any action.
    14. absent: The message only offers an info link and reports the scene secured, without telling readers to act.
    15. absent: Nothing tells recipients what to do; the scene is simply described as secured.
    16. absent: The message reports that the "Scene secured" but issues no instruction to recipients.
    17. absent: No action is asked of recipients, only that the scene is secured.
    18. absent: No action is requested of readers; the original post only says the scene is secured.
    19. absent: No action is asked of readers, the message only reports that the scene is secured.
    20. absent: The text offers no protective action, only a link for information and a note that the scene is secured.
    21. absent: No action is asked of recipients, the text reports only that the scene is secured.
    22. absent: The text reports scene status only and gives readers no action beyond a link for information.
    23. absent: The message reports that the scene is secured but asks recipients to take no action.
    24. absent: The text reports the scene is secured and points to a web page but asks no action of readers.
    25. absent: No action is requested of recipients; "Scene secured" is a status, not an instruction.
  • Timepresent25/25

    Final assessment

    Present, 25 of 25: the original is marked "sent 5:42 Tuesday" and the revision "UPDATED at 9:35 a.m. Tuesday".

    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: It gives "9:35 a.m. Tuesday" and notes the original was "sent 5:42 Tuesday".
    2. present: It is stamped sent 5:42 Tuesday with a 9:35 a.m. Tuesday update.
    3. present: It was sent 5:42 Tuesday with an update at 9:35 a.m. Tuesday.
    4. present: It is stamped "sent 5:42 Tuesday" with a 9:35 a.m. Tuesday update.
    5. present: It is marked "9:35 a.m. Tuesday" and "sent 5:42 Tuesday".
    6. present: It is timed "sent 5:42 Tuesday" with an update "at 9:35 a.m. Tuesday".
    7. present: It carries "9:35 a.m. Tuesday" and a "[sent 5:42 Tuesday]" stamp.
    8. present: It is stamped "9:35 a.m. Tuesday" and "sent 5:42 Tuesday".
    9. present: Timing is given as "9:35 a.m. Tuesday" and "sent 5:42 Tuesday".
    10. present: "9:35 a.m. Tuesday" and "sent 5:42 Tuesday" provide timing.
    11. present: It carries "9:35 a.m. Tuesday" and a note that it was "sent 5:42 Tuesday".
    12. present: It is stamped "9:35 a.m. Tuesday" and "sent 5:42 Tuesday".
    13. present: It carries "sent 5:42 Tuesday" and an update at 9:35 a.m. Tuesday.
    14. present: It notes "sent 5:42 Tuesday" and an update at "9:35 a.m. Tuesday".
    15. present: It is stamped "sent 5:42 Tuesday" with an update at 9:35 a.m. Tuesday.
    16. present: It gives "9:35 a.m. Tuesday" and the send stamp "sent 5:42 Tuesday".
    17. present: It is stamped "sent 5:42 Tuesday" and updated "at 9:35 a.m. Tuesday".
    18. present: It carries "9:35 a.m. Tuesday" and the note "sent 5:42 Tuesday".
    19. present: It carries "sent 5:42 Tuesday" and an update at "9:35 a.m. Tuesday".
    20. present: It is stamped "9:35 a.m. Tuesday" and "sent 5:42 Tuesday".
    21. present: It carries "9:35 a.m. Tuesday" and a send stamp of "5:42 Tuesday".
    22. present: It is timed "9:35 a.m. Tuesday" and "sent 5:42 Tuesday", with "early Tuesday morning".
    23. present: It is marked "sent 5:42 Tuesday" with an update "at 9:35 a.m. Tuesday".
    24. present: It carries "9:35 a.m. Tuesday" and a send stamp of "5:42 Tuesday".
    25. present: It is marked "sent 5:42 Tuesday" and updated "at 9:35 a.m. Tuesday".
  • Impactabsent0/25

    Final assessment

    Absent, 0 of 25: no harm is claimed anywhere, the post says "Shooter and victim not found", "Scene secured", and "there were no spent casings or other evidence found at the scene".

    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: It reports no casings, no evidence and no injuries, conveying no potential harm.
    2. absent: Scene secured and no casings found leave no statement of harm or severity.
    3. absent: The scene is secured, no casings were found, and no severity or harm is asserted.
    4. absent: No spent casings or evidence were found and no harm or severity is described.
    5. absent: "Scene secured" with no casings found; no harm or severity is conveyed.
    6. absent: It says the sound "may have come from a cap gun" and no casings were found, conveying no severity.
    7. absent: No harm is conveyed; no casings were found and the sound may have been a cap gun.
    8. absent: No injuries or dangers are described: the scene is reported as secured with no casings found.
    9. absent: No harm is described, and the bang may have come from "a cap gun".
    10. absent: With the scene secured and no casings found, no harm or severity is conveyed.
    11. absent: With no casings found and no injury, no consequence or severity is conveyed.
    12. absent: No harm or severity is conveyed; no casings or victims were found.
    13. absent: No injury, damage or danger is described, and no casings or evidence were even found.
    14. absent: No harm is conveyed; no casings or evidence were found and nobody was reported hurt.
    15. absent: No severity or consequence is stated, and no casings or evidence were found.
    16. absent: No casings, no injuries and no severity statement; the sound may have been a toy.
    17. absent: No harm or severity is conveyed, and no evidence of a real shooting was found.
    18. absent: No harm or severity is conveyed; no casings or evidence were found and no injury is mentioned.
    19. absent: No injury or severity is stated, and no casings or evidence were found.
    20. absent: No injury or danger is conveyed; no casings or evidence were found.
    21. absent: No consequence is described, and it notes no casings or evidence and no victim found.
    22. absent: Severity is discounted: no casings, no evidence, and the bang may have been a cap gun.
    23. absent: No harm is conveyed; no casings or evidence were found and no injury is mentioned.
    24. absent: It notes no casings or evidence were found and states no potential harm.
    25. absent: No harm or severity is conveyed; no casings or evidence were even found.

Coded by Claude Opus 5

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

About this analysis
Context

Background

Official UW Alert archive entry.
Analysis

Key Findings

Official archive page preserves complete alert text.
Outcome
See official notice for status.
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
  2. Official
Cite this case

Campus Alert Archive. "University of Washington: active threat emergency update on Alert blog." Incident of August 30, 2022. Added July 2026; last updated August 2026. https://campusalertarchive.com/case/university-of-washington-uw-alert-seattle-52-2022-08-30/

Download case JSON

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

Tags
washingtonuwuw-alertactive-threatUnder Investigation
Added July 2026Updated August 2026Via ingestion