GUPD phone line outage with alternate contact numbers
AI-generated · every claim is source-linkedGeorgetown HOYAlert reported GUPD and campus phone issues and issued restoration updates.
- Alerts
- 4
- Response
- —
- Killed
- —
- Injured
- —
Alert Sequence
4 messages in sequence · 4 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.
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 no network outage on the main campus; there are cell phone issues being reported. Use 202-384-3358 or 202-295-9019 to reach GUPD.
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
- present: HOYAlert branding identifies the sender.
- present: GUPD is named as the contact authority in the message.
- present: source is the HOYAlert product label on a full read.
- present: Verdict rests on branded HOYAlert header is present.
- present: Coding finds the opening HOYAlert tag is the source mark.
- present: Element call: HOYAlert branding identifies the sender.
- present: Text supports that GUPD is named as the contact authority.
- present: Independent read: source is the HOYAlert product label.
- present: Pass judgment: branded HOYAlert header is present.
- present: From the wording, the opening HOYAlert tag is the source mark.
- present: Alert text shows HOYAlert branding identifies the sender.
- present: Reader notes GUPD is named as the contact authority.
- present: Decision basis: source is the HOYAlert product label.
- present: Justified because branded HOYAlert header is present.
- present: The deciding point is the opening HOYAlert tag is the source mark.
- present: Clear that HOYAlert branding identifies the sender.
- present: Evidence is that GUPD is named as the contact authority.
- present: Marked as such since source is the HOYAlert product label.
- present: Based on text, branded HOYAlert header is present.
- present: Reasoning: the opening HOYAlert tag is the source mark.
- present: Call follows from HOYAlert branding identifies the sender.
- present: Supported by GUPD is named as the contact authority.
- present: Observation: source is the HOYAlert product label.
- present: Finding: branded HOYAlert header is present.
- present: Conclusion: the opening HOYAlert tag is the source mark.
Hazardpresent25/25
Final assessment
Majority 25/25 present. hazard is cell phone and phone line issues.
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
- present: hazard is cell phone and phone line issues.
- present: phone outage is the named disruption in the message.
- present: hazard coding met by phone line issue language on a full read.
- present: Verdict rests on the text states cell phone issues and phone line problems.
- present: Coding finds named hazard is GUPD phone line outage context.
- present: Element call: hazard is cell phone and phone line issues.
- present: Text supports that phone outage is the named disruption.
- present: Independent read: hazard coding met by phone line issue language.
- present: Pass judgment: the text states cell phone issues and phone line problems.
- present: From the wording, named hazard is GUPD phone line outage context.
- present: Alert text shows hazard is cell phone and phone line issues.
- present: Reader notes phone outage is the named disruption.
- present: Decision basis: hazard coding met by phone line issue language.
- present: Justified because the text states cell phone issues and phone line problems.
- present: The deciding point is named hazard is GUPD phone line outage context.
- present: Clear that hazard is cell phone and phone line issues.
- present: Evidence is that phone outage is the named disruption.
- present: Marked as such since hazard coding met by phone line issue language.
- present: Based on text, the text states cell phone issues and phone line problems.
- present: Reasoning: named hazard is GUPD phone line outage context.
- present: Call follows from hazard is cell phone and phone line issues.
- present: Supported by phone outage is the named disruption.
- present: Observation: hazard coding met by phone line issue language.
- present: Finding: the text states cell phone issues and phone line problems.
- present: Conclusion: named hazard is GUPD phone line outage context.
Locationpresent25/25
Final assessment
Majority 25/25 present. location is the main campus.
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
- present: location is the main campus.
- present: place is main campus in the message.
- present: location coding met by main campus wording on a full read.
- present: Verdict rests on the issue is on the main campus.
- present: Coding finds named place is main campus.
- present: Element call: location is the main campus.
- present: Text supports that place is main campus.
- present: Independent read: location coding met by main campus wording.
- present: Pass judgment: the issue is on the main campus.
- present: From the wording, named place is main campus.
- present: Alert text shows location is the main campus.
- present: Reader notes place is main campus.
- present: Decision basis: location coding met by main campus wording.
- present: Justified because the issue is on the main campus.
- present: The deciding point is named place is main campus.
- present: Clear that location is the main campus.
- present: Evidence is that place is main campus.
- present: Marked as such since location coding met by main campus wording.
- present: Based on text, the issue is on the main campus.
- present: Reasoning: named place is main campus.
- present: Call follows from location is the main campus.
- present: Supported by place is main campus.
- present: Observation: location coding met by main campus wording.
- present: Finding: the issue is on the main campus.
- present: Conclusion: named place is main campus.
Guidancepresent25/25
Final assessment
Majority 25/25 present. guidance is use alternate numbers to reach GUPD.
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
- present: guidance is use alternate numbers to reach GUPD.
- present: recipients are told to call alternate GUPD lines in the message.
- present: protective or operational action is alternate contact numbers on a full read.
- present: Verdict rests on instruction to use 202-384-3358 or 202-295-9019 is present.
- present: Coding finds guidance coding met by alternate contact instructions.
- present: Element call: guidance is use alternate numbers to reach GUPD.
- present: Text supports that recipients are told to call alternate GUPD lines.
- present: Independent read: protective or operational action is alternate contact numbers.
- present: Pass judgment: instruction to use 202-384-3358 or 202-295-9019 is present.
- present: From the wording, guidance coding met by alternate contact instructions.
- present: Alert text shows guidance is use alternate numbers to reach GUPD.
- present: Reader notes recipients are told to call alternate GUPD lines.
- present: Decision basis: protective or operational action is alternate contact numbers.
- present: Justified because instruction to use 202-384-3358 or 202-295-9019 is present.
- present: The deciding point is guidance coding met by alternate contact instructions.
- present: Clear that guidance is use alternate numbers to reach GUPD.
- present: Evidence is that recipients are told to call alternate GUPD lines.
- present: Marked as such since protective or operational action is alternate contact numbers.
- present: Based on text, instruction to use 202-384-3358 or 202-295-9019 is present.
- present: Reasoning: guidance coding met by alternate contact instructions.
- present: Call follows from guidance is use alternate numbers to reach GUPD.
- present: Supported by recipients are told to call alternate GUPD lines.
- present: Observation: protective or operational action is alternate contact numbers.
- present: Finding: instruction to use 202-384-3358 or 202-295-9019 is present.
- present: Conclusion: guidance coding met by alternate contact instructions.
Timeabsent0/25
Final assessment
Majority 25/25 absent. no clock time now or immediately cue appears.
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
- absent: no clock time now or immediately cue appears.
- absent: time is absent without a temporal marker in the message.
- absent: time coding fails for lack of when language on a full read.
- absent: Verdict rests on no until further notice timing is stated in the first alert.
- absent: Coding finds the first alert lacks recency words like now.
- absent: Element call: no clock time now or immediately cue appears.
- absent: Text supports that time is absent without a temporal marker.
- absent: Independent read: time coding fails for lack of when language.
- absent: Pass judgment: no until further notice timing is stated in the first alert.
- absent: From the wording, the first alert lacks recency words like now.
- absent: Alert text shows no clock time now or immediately cue appears.
- absent: Reader notes time is absent without a temporal marker.
- absent: Decision basis: time coding fails for lack of when language.
- absent: Justified because no until further notice timing is stated in the first alert.
- absent: The deciding point is the first alert lacks recency words like now.
- absent: Clear that no clock time now or immediately cue appears.
- absent: Evidence is that time is absent without a temporal marker.
- absent: Marked as such since time coding fails for lack of when language.
- absent: Based on text, no until further notice timing is stated in the first alert.
- absent: Reasoning: the first alert lacks recency words like now.
- absent: Call follows from no clock time now or immediately cue appears.
- absent: Supported by time is absent without a temporal marker.
- absent: Observation: time coding fails for lack of when language.
- absent: Finding: no until further notice timing is stated in the first alert.
- absent: Conclusion: the first alert lacks recency words like now.
Impactabsent0/25
Final assessment
Majority 25/25 absent. phone issues are named without life-safety severity.
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
- absent: phone issues are named without life-safety severity.
- absent: impact is absent beyond naming the outage in the message.
- absent: no injury or danger consequence is stated on a full read.
- absent: Verdict rests on impact coding fails for lack of severity wording.
- absent: Coding finds naming a phone issue alone does not satisfy impact.
- absent: Element call: phone issues are named without life-safety severity.
- absent: Text supports that impact is absent beyond naming the outage.
- absent: Independent read: no injury or danger consequence is stated.
- absent: Pass judgment: impact coding fails for lack of severity wording.
- absent: From the wording, naming a phone issue alone does not satisfy impact.
- absent: Alert text shows phone issues are named without life-safety severity.
- absent: Reader notes impact is absent beyond naming the outage.
- absent: Decision basis: no injury or danger consequence is stated.
- absent: Justified because impact coding fails for lack of severity wording.
- absent: The deciding point is naming a phone issue alone does not satisfy impact.
- absent: Clear that phone issues are named without life-safety severity.
- absent: Evidence is that impact is absent beyond naming the outage.
- absent: Marked as such since no injury or danger consequence is stated.
- absent: Based on text, impact coding fails for lack of severity wording.
- absent: Reasoning: naming a phone issue alone does not satisfy impact.
- absent: Call follows from phone issues are named without life-safety severity.
- absent: Supported by impact is absent beyond naming the outage.
- absent: Observation: no injury or danger consequence is stated.
- absent: Finding: impact coding fails for lack of severity wording.
- absent: Conclusion: naming a phone issue alone does not satisfy impact.
Coded by SuperGrok Heavy 4.5
Systematic AI judgments with visible reasoning, not human-validated codings.
Background
Key Findings
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.
- Social
- Social
- Social
- Social
Campus Alert Archive. "Georgetown University: GUPD phone line outage with alternate contact numbers." Incident of April 13, 2022. Added August 2026. https://campusalertarchive.com/case/georgetown-university-gupd-phone-line-outage-apr-2022-04-13/
Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.