Skip to content
Campus Alert Archive
UW

Other incident - disregard advisory

AI-generated · every claim is source-linked
WAotheremergency notificationhigh confidence

University of Washington published a UW Alert Blog update on or about 2020-03-23. Full text is preserved from the official emergency blog.

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

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 verbatim280 chars
Please disregard a UW Advisory message which was erroneously sent at 8:33 p.m. to the entire UW list. The message was intended only for a small group of researchers and staff at Friday Harbor Labs (FHL). We apologize for any confusion and are looking into the cause of the error.
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.

Please disregard a UW Advisory message which was erroneously sent at 8:33 p.m. to the entire UW list. The message was intended only for a small group of researchers and staff at Friday Harbor Labs (FHL). We apologize for any confusion and are looking into the cause of the error.

  • Sourcepresent25/25

    Final assessment

    Present, unanimously at 25 of 25: the notice speaks in the university voice about "a UW Advisory message" and closes "We apologize for any confusion", so the alerting office is plainly 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: The University signs the correction, apologizing for its own "UW Advisory message".
    2. present: The message identifies itself as being about a UW Advisory and apologizes in the university voice.
    3. present: It speaks as the sender of "a UW Advisory message" and apologizes in the institution's voice.
    4. present: The University speaks as sender, referring to "a UW Advisory message" and apologizing on its own behalf.
    5. present: It references "a UW Advisory message" and the UW voice apologizing, identifying the sender.
    6. present: The message identifies itself as coming from the UW Advisory system, apologizing for its own error.
    7. present: The message identifies itself as coming from the "UW Advisory" system and apologizes in the institution's voice.
    8. present: The sender identifies itself as the source of "a UW Advisory message" and apologizes in the first person.
    9. present: Sent in the institutional voice as a "UW Advisory" with "We apologize", identifying the sender.
    10. present: It is written in the institution's voice about "a UW Advisory message" and says "We apologize", identifying the sender.
    11. present: The sender writes as the University, apologizing for a mistaken "UW Advisory message".
    12. present: The sender speaks as the UW Advisory operator: "We apologize" for the erroneous message.
    13. present: The sender speaks for the university, referring to "a UW Advisory message" and apologizing on its behalf.
    14. present: The university speaks as sender, referring to "a UW Advisory message" and apologizing on its own behalf.
    15. present: The sender speaks for the university about "a UW Advisory message" and apologizes as "we".
    16. present: The University writes in the first person, apologizing for its own erroneous "UW Advisory message".
    17. present: It speaks as the sender of "a UW Advisory message" and apologizes in the institution's voice.
    18. present: It speaks for the sender of "a UW Advisory message" and apologizes in the first person.
    19. present: The sender is the UW, apologizing for its own erroneous "UW Advisory message".
    20. present: The sender writes as the alert office: "a UW Advisory message which was erroneously sent".
    21. present: The sender speaks as the UW Advisory operator, apologizing for its own erroneous message.
    22. present: The sender speaks as the UW, apologizing for an erroneous "UW Advisory message".
    23. present: The sender speaks as the University about "a UW Advisory message" and apologizes in the first person.
    24. present: The branded "UW Advisory" system and the apologizing institution identify the sender.
    25. present: "UW Advisory" branding plus "We apologize" identify the university alerting office as sender.
  • Hazardabsent0/25

    Final assessment

    Absent, with 0 of 25 finding a hazard: the entire subject is an advisory "erroneously sent at 8:33 p.m. to the entire UW list", a mailing mistake rather than any threat to people.

    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: The subject is a misdirected email, not any named threat or hazard.
    2. absent: The subject is an erroneous message send, not a specific physical threat.
    3. absent: The subject is an email sent in error, not any named threat.
    4. absent: The subject is a misdirected email, not any named threat or hazard.
    5. absent: The subject is an erroneous send, not any named threat to safety.
    6. absent: The subject is an erroneously sent message, not any specific threat.
    7. absent: The subject is an email sent in error, not any named hazard or threat.
    8. absent: No threat is described: the subject is an erroneously broadcast message, not a hazard.
    9. absent: The subject is a misdirected email, not a threat, so no hazard is named.
    10. absent: The subject is a mistaken mass email, not any named threat.
    11. absent: The subject is an email sent in error, not any specific threat or hazard.
    12. absent: The subject is a mistaken mailing, not any named threat or hazard.
    13. absent: The subject is a misdirected email, not a specific threat to anyone.
    14. absent: The subject is a misdirected email, and no hazard or threat is named.
    15. absent: The subject is a misdirected email, and no threat or hazard is named at all.
    16. absent: The subject is a misdirected email, not any named threat such as fire, weapon or weather.
    17. absent: The subject is a misdirected email, not any named threat or hazard.
    18. absent: The subject is a misdirected email, not any specific threat.
    19. absent: The subject is a messaging error, not a threat to safety.
    20. absent: The subject is an email sent in error, not any named threat to people.
    21. absent: The subject is a misdirected email, not any named physical or criminal threat.
    22. absent: The subject is a misdirected message, not any named threat.
    23. absent: The subject is a mistakenly sent email, not any named threat or hazard.
    24. absent: The subject is a misdirected message, not any specific threat to anyone.
    25. absent: The only subject is an erroneous message send, not any specific physical threat.
  • Locationpresent25/25

    Final assessment

    Present at 25 of 25: the text names "Friday Harbor Labs (FHL)" as the site of the small group of researchers and staff the message was actually meant for.

    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: It names "Friday Harbor Labs (FHL)" as the intended recipients' location.
    2. present: It names Friday Harbor Labs as the intended audience location.
    3. present: It identifies "Friday Harbor Labs (FHL)" as the intended recipient group's site.
    4. present: It identifies "Friday Harbor Labs (FHL)" as the intended recipients' location.
    5. present: It names "Friday Harbor Labs (FHL)" as the intended recipient site.
    6. present: It names "Friday Harbor Labs (FHL)" as the intended audience's location.
    7. present: It names "Friday Harbor Labs (FHL)" as the intended recipient group's location.
    8. present: It names "Friday Harbor Labs (FHL)" as the intended recipients' location.
    9. present: Refers to "Friday Harbor Labs (FHL)", a specific UW facility.
    10. present: It identifies "Friday Harbor Labs (FHL)" as the intended recipients' location.
    11. present: It identifies "Friday Harbor Labs (FHL)" as the intended recipient group's location.
    12. present: It names "Friday Harbor Labs (FHL)" as the intended recipient group's location.
    13. present: It names "Friday Harbor Labs (FHL)" as the group the message was meant for.
    14. present: It identifies "Friday Harbor Labs (FHL)" as the intended audience's location.
    15. present: It identifies "Friday Harbor Labs (FHL)" as the intended recipients' location.
    16. present: It identifies the intended recipients at "Friday Harbor Labs (FHL)", a specific UW facility.
    17. present: It identifies "Friday Harbor Labs (FHL)" as the intended recipients' location.
    18. present: It identifies "Friday Harbor Labs (FHL)" as the intended recipients' site.
    19. present: It identifies "Friday Harbor Labs (FHL)" as the intended audience's location.
    20. present: It names "Friday Harbor Labs (FHL)" as the group the message was meant for.
    21. present: It identifies Friday Harbor Labs as the intended recipient group location.
    22. present: It refers to "Friday Harbor Labs (FHL)", a named UW facility.
    23. present: It identifies the intended audience at "Friday Harbor Labs (FHL)", a named place.
    24. present: It names "Friday Harbor Labs (FHL)" as the intended recipients' location.
    25. present: It names "Friday Harbor Labs (FHL)" as the intended recipient site.
  • Guidanceabsent11/25

    Final assessment

    Absent on an 11 of 25 split: "Please disregard" is an instruction, but the minority is right that retracting a stray email asks no protective action, and the fourteen dissenting reads carry the call.

    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: The core instruction to readers is "Please disregard" the erroneous message.
    2. present: It gives a direct instruction to recipients: please disregard the message.
    3. absent: "Please disregard" tells readers to ignore something, which is not a protective action.
    4. absent: "Please disregard" corrects a message rather than directing any protective action.
    5. absent: "Please disregard" retracts a message rather than directing any protective action.
    6. present: "Please disregard" is a direct instruction to the recipient about what to do.
    7. absent: "Please disregard" is a housekeeping instruction, not a protective action against any hazard.
    8. absent: "Please disregard" corrects the record but is not a protective action for recipients to take.
    9. absent: Asking readers to disregard a message is not a protective action for their safety.
    10. present: The opening instruction is "Please disregard", telling recipients exactly what to do.
    11. absent: "Please disregard" tells readers to ignore something, which is not a protective action.
    12. present: "Please disregard a UW Advisory message" is a clear instruction to the reader.
    13. present: The instruction "Please disregard" tells recipients exactly what to do with the message.
    14. absent: "Please disregard" is a housekeeping instruction, not a protective action for safety.
    15. absent: "Please disregard" corrects an error but asks for no protective action.
    16. present: The recipient is given a clear instruction: "Please disregard" the erroneous message.
    17. absent: "Please disregard" corrects a message but is not a protective action for safety.
    18. present: "Please disregard" is a direct instruction about what recipients should do.
    19. present: Recipients are directly instructed: "Please disregard a UW Advisory message."
    20. absent: "Please disregard" corrects an error rather than telling recipients any protective action.
    21. present: It explicitly tells recipients to disregard the message that was sent.
    22. absent: "Please disregard" tells readers to ignore, which is not a protective action against a hazard.
    23. absent: "Please disregard" is an administrative correction, not a protective action for recipients to take.
    24. absent: "Please disregard" retracts a message rather than directing any protective action.
    25. present: Recipients are given a direct instruction: "Please disregard a UW Advisory message".
  • Timepresent25/25

    Final assessment

    Present at 25 of 25: the erroneous advisory is pinned to a precise clock time, "erroneously sent at 8:33 p.m.", so the message states when the event happened.

    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 says the message was "erroneously sent at 8:33 p.m.".
    2. present: It specifies the message was sent at 8:33 p.m.
    3. present: The erroneous message is timed "at 8:33 p.m.".
    4. present: It pins the error to a message "erroneously sent at 8:33 p.m.".
    5. present: The erroneous message is timed precisely: "erroneously sent at 8:33 p.m."
    6. present: The erroneous message was "erroneously sent at 8:33 p.m.", a clock time.
    7. present: It states the message "was erroneously sent at 8:33 p.m.", a precise time.
    8. present: The erroneous message is timestamped as "erroneously sent at 8:33 p.m."
    9. present: Pinpoints the erroneous message as "erroneously sent at 8:33 p.m."
    10. present: The erroneous message is pinned to "8:33 p.m." that evening.
    11. present: The erroneous message is timed as "erroneously sent at 8:33 p.m."
    12. present: The erroneous message is timed precisely at "8:33 p.m."
    13. present: It specifies the message was "erroneously sent at 8:33 p.m.".
    14. present: The erroneous message is timed precisely, "erroneously sent at 8:33 p.m."
    15. present: The erroneous message is timed "at 8:33 p.m." in the text.
    16. present: The erroneous message is timestamped as "erroneously sent at 8:33 p.m."
    17. present: The erroneous message is timed precisely, "erroneously sent at 8:33 p.m."
    18. present: The erroneous message is pinned to "8:33 p.m." that evening.
    19. present: The erroneous message is timed "at 8:33 p.m." on a stated date.
    20. present: It pins the erroneous message to "8:33 p.m.", a specific clock time.
    21. present: It fixes the error at 8:33 p.m. on the stated date.
    22. present: The message was "erroneously sent at 8:33 p.m.", a clock time.
    23. present: The erroneous message is pinned to "8:33 p.m." that evening.
    24. present: The erroneous message is timed precisely at "8:33 p.m.".
    25. present: The erroneous message is timed precisely at "8:33 p.m."
  • Impactabsent0/25

    Final assessment

    Absent, 0 of 25: the only effect named is "any confusion" the misdirected email caused, which conveys no harm, danger or severity from any hazard.

    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: Beyond possible confusion, no consequence or severity is stated.
    2. absent: Beyond possible confusion, no harm or severity is described.
    3. absent: Only "confusion" is mentioned, not any harm or severity.
    4. absent: Beyond possible confusion, no consequence or severity is conveyed.
    5. absent: No consequence beyond possible confusion is described, and no severity is stated.
    6. absent: No harm or severity is conveyed, only apology for confusion.
    7. absent: Nothing describes harm or severity beyond possible confusion being regretted.
    8. absent: The only stated effect is possible confusion, not a consequence of any hazard.
    9. absent: Only possible "confusion" is mentioned, with no harm or severity.
    10. absent: It mentions only possible confusion, not any consequence of a hazard.
    11. absent: Nothing is said about harm or seriousness beyond possible confusion.
    12. absent: No harm or severity is conveyed, only confusion, which is not a hazard consequence.
    13. absent: Only "confusion" is mentioned; no harm or severity from any hazard is described.
    14. absent: The only effect mentioned is confusion, with no harm or severity conveyed.
    15. absent: No harm or severity is described, only possible confusion from the error.
    16. absent: Beyond possible confusion, the text states no harm, danger or severity of any kind.
    17. absent: Beyond possible "confusion", no consequence or severity is conveyed.
    18. absent: Only confusion is mentioned; no hazard consequence or severity is stated.
    19. absent: Beyond possible confusion, no harm or severity is conveyed.
    20. absent: Only "confusion" is mentioned; no physical consequence or severity is stated.
    21. absent: The only effect mentioned is confusion, with no hazard consequence or severity.
    22. absent: Only possible "confusion" is mentioned, not any harm from a hazard.
    23. absent: The only stated effect is "confusion", with no harm or severity to people or property.
    24. absent: Only "confusion" is mentioned, with no physical consequence or severity.
    25. absent: Beyond "any confusion", no consequence or severity is stated.

Coded by Claude Opus 5

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

About this analysis
Context

Background

University of Washington UW Alert Blog multi-update emergency archive.
Analysis

Key Findings

Official Alert Blog page preserves complete multi-update alert text.
Outcome
See official update page 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
Cite this case

Campus Alert Archive. "University of Washington: Other incident - disregard advisory." Incident of March 23, 2020. Added July 2026; last updated August 2026. https://campusalertarchive.com/case/university-of-washington-disregard-uw-advisory-sent-at-8-33-p-m-march-23-20-2020-03-23/

Download case JSON

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

Tags
washingtonuwuw-alertother
Added July 2026Updated August 2026Via ingestion