Skip to content
Campus Alert Archive
Georgetown

Fire investigation in progress at Henle 75

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

Georgetown HOYAlert reported a fire investigation at Henle 75 and later ended the notification.

Alerts
2
Response
Killed
Injured
Institution
Georgetown University
Private R1 · DC
All Georgetown cases →
~19,000 studentsRaveHOYAlert
Official alert policy
Read when and how Georgetown says it will use HOYAlert: 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 ALERTTwitter/X
Verified verbatim109 chars
HOYAlert: There is a fire investigation in progress in Henle 75. Please avoid the area until further notice.
Dual independent X fetch match 2026-08-03 (keyword_search family + second fetch). SPN 523.
EXPANSION continuation batch 492 residual.
ALL CLEARTwitter/X+26 min
Verified verbatim114 chars
HOYAlert: The Fire Investigation notification at Henle 75 has now ended. This message is the official "all clear."
Dual independent X fetch match 2026-08-03 (keyword_search family + second fetch). SPN 523.
EXPANSION continuation batch 492 residual.
Message elements

How the first alert is built

To check this alert, SuperGrok Heavy 4.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.

HOYAlert: There is a fire investigation in progress in Henle 75. Please avoid the area until further notice.

  • Sourcepresent25/25

    Final assessment

    Majority 25/25 present. HOYAlert branding identifies 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: HOYAlert branding identifies the sender.
    2. present: the HOYAlert signature names the system in the message.
    3. present: source is the HOYAlert product label on a full read.
    4. present: Verdict rests on branded HOYAlert header is present.
    5. present: Coding finds the opening HOYAlert tag is the source mark.
    6. present: Element call: HOYAlert branding identifies the sender.
    7. present: Text supports that the HOYAlert signature names the system.
    8. present: Independent read: source is the HOYAlert product label.
    9. present: Pass judgment: branded HOYAlert header is present.
    10. present: From the wording, the opening HOYAlert tag is the source mark.
    11. present: Alert text shows HOYAlert branding identifies the sender.
    12. present: Reader notes the HOYAlert signature names the system.
    13. present: Decision basis: source is the HOYAlert product label.
    14. present: Justified because branded HOYAlert header is present.
    15. present: The deciding point is the opening HOYAlert tag is the source mark.
    16. present: Clear that HOYAlert branding identifies the sender.
    17. present: Evidence is that the HOYAlert signature names the system.
    18. present: Marked as such since source is the HOYAlert product label.
    19. present: Based on text, branded HOYAlert header is present.
    20. present: Reasoning: the opening HOYAlert tag is the source mark.
    21. present: Call follows from HOYAlert branding identifies the sender.
    22. present: Supported by the HOYAlert signature names the system.
    23. present: Observation: source is the HOYAlert product label.
    24. present: Finding: branded HOYAlert header is present.
    25. present: Conclusion: the opening HOYAlert tag is the source mark.
  • Hazardpresent25/25

    Final assessment

    Majority 25/25 present. hazard is a fire investigation.

    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: hazard is a fire investigation.
    2. present: fire investigation is the named threat in the message.
    3. present: hazard coding met by fire investigation language on a full read.
    4. present: Verdict rests on the text states a fire investigation in progress.
    5. present: Coding finds named hazard is fire investigation.
    6. present: Element call: hazard is a fire investigation.
    7. present: Text supports that fire investigation is the named threat.
    8. present: Independent read: hazard coding met by fire investigation language.
    9. present: Pass judgment: the text states a fire investigation in progress.
    10. present: From the wording, named hazard is fire investigation.
    11. present: Alert text shows hazard is a fire investigation.
    12. present: Reader notes fire investigation is the named threat.
    13. present: Decision basis: hazard coding met by fire investigation language.
    14. present: Justified because the text states a fire investigation in progress.
    15. present: The deciding point is named hazard is fire investigation.
    16. present: Clear that hazard is a fire investigation.
    17. present: Evidence is that fire investigation is the named threat.
    18. present: Marked as such since hazard coding met by fire investigation language.
    19. present: Based on text, the text states a fire investigation in progress.
    20. present: Reasoning: named hazard is fire investigation.
    21. present: Call follows from hazard is a fire investigation.
    22. present: Supported by fire investigation is the named threat.
    23. present: Observation: hazard coding met by fire investigation language.
    24. present: Finding: the text states a fire investigation in progress.
    25. present: Conclusion: named hazard is fire investigation.
  • Locationpresent25/25

    Final assessment

    Majority 25/25 present. location is Henle 75.

    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: location is Henle 75.
    2. present: place is Henle 75 in the message.
    3. present: location coding met by Henle 75 wording on a full read.
    4. present: Verdict rests on the event is at Henle 75.
    5. present: Coding finds named place is Henle 75.
    6. present: Element call: location is Henle 75.
    7. present: Text supports that place is Henle 75.
    8. present: Independent read: location coding met by Henle 75 wording.
    9. present: Pass judgment: the event is at Henle 75.
    10. present: From the wording, named place is Henle 75.
    11. present: Alert text shows location is Henle 75.
    12. present: Reader notes place is Henle 75.
    13. present: Decision basis: location coding met by Henle 75 wording.
    14. present: Justified because the event is at Henle 75.
    15. present: The deciding point is named place is Henle 75.
    16. present: Clear that location is Henle 75.
    17. present: Evidence is that place is Henle 75.
    18. present: Marked as such since location coding met by Henle 75 wording.
    19. present: Based on text, the event is at Henle 75.
    20. present: Reasoning: named place is Henle 75.
    21. present: Call follows from location is Henle 75.
    22. present: Supported by place is Henle 75.
    23. present: Observation: location coding met by Henle 75 wording.
    24. present: Finding: the event is at Henle 75.
    25. present: Conclusion: named place is Henle 75.
  • Guidancepresent25/25

    Final assessment

    Majority 25/25 present. guidance is Please avoid the area.

    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: guidance is Please avoid the area.
    2. present: recipients are told to avoid the area in the message.
    3. present: protective action is area avoidance on a full read.
    4. present: Verdict rests on instruction to avoid the area is present.
    5. present: Coding finds guidance coding met by avoid-area language.
    6. present: Element call: guidance is Please avoid the area.
    7. present: Text supports that recipients are told to avoid the area.
    8. present: Independent read: protective action is area avoidance.
    9. present: Pass judgment: instruction to avoid the area is present.
    10. present: From the wording, guidance coding met by avoid-area language.
    11. present: Alert text shows guidance is Please avoid the area.
    12. present: Reader notes recipients are told to avoid the area.
    13. present: Decision basis: protective action is area avoidance.
    14. present: Justified because instruction to avoid the area is present.
    15. present: The deciding point is guidance coding met by avoid-area language.
    16. present: Clear that guidance is Please avoid the area.
    17. present: Evidence is that recipients are told to avoid the area.
    18. present: Marked as such since protective action is area avoidance.
    19. present: Based on text, instruction to avoid the area is present.
    20. present: Reasoning: guidance coding met by avoid-area language.
    21. present: Call follows from guidance is Please avoid the area.
    22. present: Supported by recipients are told to avoid the area.
    23. present: Observation: protective action is area avoidance.
    24. present: Finding: instruction to avoid the area is present.
    25. present: Conclusion: guidance coding met by avoid-area language.
  • Timepresent25/25

    Final assessment

    Majority 25/25 present. time is present via until further notice.

    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: time is present via until further notice.
    2. present: temporal cue is until further notice in the message.
    3. present: time coding met by until further notice on a full read.
    4. present: Verdict rests on recency language includes until further notice.
    5. present: Coding finds when-language is until further notice.
    6. present: Element call: time is present via until further notice.
    7. present: Text supports that temporal cue is until further notice.
    8. present: Independent read: time coding met by until further notice.
    9. present: Pass judgment: recency language includes until further notice.
    10. present: From the wording, when-language is until further notice.
    11. present: Alert text shows time is present via until further notice.
    12. present: Reader notes temporal cue is until further notice.
    13. present: Decision basis: time coding met by until further notice.
    14. present: Justified because recency language includes until further notice.
    15. present: The deciding point is when-language is until further notice.
    16. present: Clear that time is present via until further notice.
    17. present: Evidence is that temporal cue is until further notice.
    18. present: Marked as such since time coding met by until further notice.
    19. present: Based on text, recency language includes until further notice.
    20. present: Reasoning: when-language is until further notice.
    21. present: Call follows from time is present via until further notice.
    22. present: Supported by temporal cue is until further notice.
    23. present: Observation: time coding met by until further notice.
    24. present: Finding: recency language includes until further notice.
    25. present: Conclusion: when-language is until further notice.
  • Impactabsent0/25

    Final assessment

    Majority 25/25 absent. no consequence severity beyond naming the fire investigation.

    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 consequence severity beyond naming the fire investigation.
    2. absent: impact is absent without severity language in the message.
    3. absent: avoid the area is guidance not stated harm severity on a full read.
    4. absent: Verdict rests on no deadly or injury consequence is stated.
    5. absent: Coding finds impact coding fails for lack of severity wording.
    6. absent: Element call: no consequence severity beyond naming the fire investigation.
    7. absent: Text supports that impact is absent without severity language.
    8. absent: Independent read: avoid the area is guidance not stated harm severity.
    9. absent: Pass judgment: no deadly or injury consequence is stated.
    10. absent: From the wording, impact coding fails for lack of severity wording.
    11. absent: Alert text shows no consequence severity beyond naming the fire investigation.
    12. absent: Reader notes impact is absent without severity language.
    13. absent: Decision basis: avoid the area is guidance not stated harm severity.
    14. absent: Justified because no deadly or injury consequence is stated.
    15. absent: The deciding point is impact coding fails for lack of severity wording.
    16. absent: Clear that no consequence severity beyond naming the fire investigation.
    17. absent: Evidence is that impact is absent without severity language.
    18. absent: Marked as such since avoid the area is guidance not stated harm severity.
    19. absent: Based on text, no deadly or injury consequence is stated.
    20. absent: Reasoning: impact coding fails for lack of severity wording.
    21. absent: Call follows from no consequence severity beyond naming the fire investigation.
    22. absent: Supported by impact is absent without severity language.
    23. absent: Observation: avoid the area is guidance not stated harm severity.
    24. absent: Finding: no deadly or injury consequence is stated.
    25. absent: Conclusion: impact coding fails for lack of severity wording.

Coded by SuperGrok Heavy 4.5

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

About this analysis
Context

Background

Georgetown posts HOYAlert notices on @HOYAlert.
Analysis

Key Findings

Official residual product with complete short-form text.
Outcome
Fire investigation notification ended.
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. Social
  2. Social
Cite this case

Campus Alert Archive. "Georgetown University: Fire investigation in progress at Henle 75." Incident of May 25, 2022. Added August 2026. https://campusalertarchive.com/case/georgetown-university-henle-75-fire-investigation-2022-05-25/

Download case JSON

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

Tags
private-r1district-of-columbiageorgetownhoyalertfire
Added August 2026Updated August 2026Via ingestion