Skip to content
Campus Alert Archive
UMD

Monthly Alert emergency system test notice

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

University of Maryland published an alert on or about 2026-07-01. Full text is preserved from the official UMD Alerts archive.

Alerts
1
Response
—
Killed
0
Injured
0
Institution
University of Maryland, College Park
Public R1 · MD
All UMD cases →
~40,000 studentsUMD Alerts
Official alert policy
Read when and how UMD says it will use UMD Alerts: 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 verbatim585 chars
First Wednesday of each month at 11:55 a.m., the campus tests the UMD Alert Emergency Notification System, Alertus System and Early Warning Sirens. These are only tests. In the event of an emergency, you will receive text and email notifications with information regarding the nature of the emergency and necessary protective actions. UMD affiliates may edit their mobile device settings at alert.umd.edu. Contact Information: University of Maryland Police Emergency Number 301-405-3333/ 911 Prince George's County Police 911 from mobile phone / 301-352-1200 (non-emergency) / 911
Transcribed from official alert.umd.edu page body.
Confirmed-verbatim recovery from live institutional source.
2026-09-21 second deep audit b42 P3 partial: P3 partial scrape-cut. Recapture full test notice including contact block; listing ellipsis restored. Dual html.parser+regex. Cap-exempt R1.
Message elements

How the first alert is built

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

First Wednesday of each month at 11:55 a.m., the campus tests the UMD Alert Emergency Notification System, Alertus System and Early Warning Sirens. These are only tests. In the event of an emergency, you will receive text and email notifications with information regarding the nature of the emergency and necessary protective actions. UMD affiliates may edit their mobile device settings at alert.umd.edu. Contact Information: University of Maryland Police Emergency Number 301-405-3333/ 911 Prince George's County Police 911 from mobile phone / 301-352-1200 (non-emergency) / 911

  • Sourcepresent25/25

    Final assessment

    All 25 reads agree the source is present: the text names the "UMD Alert Emergency Notification System" and University of Maryland Police contacts.

    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: It names the "UMD Alert Emergency Notification System" and University of Maryland Police contacts.
    2. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police contacts.
    3. present: It names the "UMD Alert Emergency Notification System" and lists University of Maryland Police contacts.
    4. present: It names the 'UMD Alert Emergency Notification System' and lists University of Maryland Police contacts.
    5. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police.
    6. present: It names 'the UMD Alert Emergency Notification System' and lists the University of Maryland Police.
    7. present: It says 'the campus tests the UMD Alert Emergency Notification System' and lists University of Maryland Police as a contact.
    8. present: It names the UMD Alert Emergency Notification System and University of Maryland Police.
    9. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police, identifying the sender.
    10. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police as the source.
    11. present: It names the 'UMD Alert Emergency Notification System' and lists University of Maryland Police contacts, identifying the source.
    12. present: It names the 'UMD Alert Emergency Notification System' and lists University of Maryland Police.
    13. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police, identifying the sender.
    14. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police as the source.
    15. present: It says "the campus tests the UMD Alert Emergency Notification System" and lists University of Maryland Police.
    16. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police as the sending authority.
    17. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police, identifying the source.
    18. present: It describes the 'UMD Alert Emergency Notification System' and lists University of Maryland Police contacts.
    19. present: It describes the UMD Alert system test and lists University of Maryland Police contacts, identifying the sender.
    20. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police contacts.
    21. present: It refers to 'the UMD Alert Emergency Notification System' and lists University of Maryland Police contacts.
    22. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police, identifying the sender.
    23. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police as the source.
    24. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police, identifying the sender.
    25. present: It names the 'UMD Alert Emergency Notification System' and University of Maryland Police as the sources.
  • Hazardabsent0/25

    Final assessment

    All 25 reads agree hazard is absent: it describes routine tests of alert systems and sirens, and "These are only tests".

    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: It describes routine tests of alert systems and sirens, with no actual threat named.
    2. absent: It says 'These are only tests', so no threat is named.
    3. absent: It describes monthly tests that "are only tests", so no actual threat is named.
    4. absent: It describes routine tests that 'are only tests' and names no actual threat.
    5. absent: It says 'These are only tests', so no real hazard is named.
    6. absent: It explains monthly system tests and says 'These are only tests', naming no real threat.
    7. absent: It explicitly states 'These are only tests', so no actual hazard is named.
    8. absent: It describes routine monthly tests, which 'are only tests', and names no threat.
    9. absent: It describes routine monthly tests that 'are only tests', naming no actual threat.
    10. absent: It explains routine monthly tests, saying 'These are only tests', so no hazard is named.
    11. absent: It says 'These are only tests', so no actual threat or hazard is named.
    12. absent: It describes monthly tests and says 'These are only tests', naming no actual threat.
    13. absent: It explains monthly tests and says 'These are only tests', naming no threat.
    14. absent: The message describes routine tests, 'These are only tests', and names no threat.
    15. absent: It states "These are only tests", so no actual hazard is named.
    16. absent: It says the monthly sirens and alerts 'are only tests', so no actual threat is named.
    17. absent: It says 'These are only tests' about the sirens and alert system, naming no actual threat.
    18. absent: It explains that the monthly tests 'are only tests', so no actual hazard is named.
    19. absent: It describes monthly tests of the UMD Alert system and sirens, naming no actual threat.
    20. absent: It describes monthly tests and says 'These are only tests', with no hazard named.
    21. absent: It explains that monthly siren and alert tests 'are only tests' and names no actual threat.
    22. absent: It describes routine system tests that 'are only tests', so no actual hazard is named.
    23. absent: It describes routine tests that 'are only tests', naming no real threat.
    24. absent: It describes routine tests that 'are only tests' and names no real threat.
    25. absent: It describes monthly system tests that 'are only tests' and names no actual threat.
  • Locationpresent20/25

    Final assessment

    Present by majority (20 of 25): "the campus tests" places the tests on campus; a minority argued campus is only the party running the tests, not an incident location.

    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 says "the campus tests" its systems, referring to the campus as the location.
    2. present: It says 'the campus tests' the system and sirens, referring to campus.
    3. present: It says "the campus tests" its systems and early warning sirens, naming the campus as the place.
    4. present: It says 'the campus tests' its alert systems and sirens, referring to the campus.
    5. present: It says 'the campus tests' its systems and sirens, naming the campus.
    6. present: It says 'the campus tests' its systems, indicating the campus as the place.
    7. absent: The campus is mentioned only as the entity running tests, with no location for any incident.
    8. present: It says 'the campus tests' the systems and early warning sirens, naming the campus as the place.
    9. present: It says 'the campus tests' the system and sirens, naming the campus as the place involved.
    10. present: It states that 'the campus tests' the systems and sirens, identifying the campus as the place.
    11. present: It says 'the campus tests' the alert system and sirens, locating the activity on campus.
    12. present: It says 'the campus tests' its sirens and alert systems, referencing the campus.
    13. present: It says 'the campus tests' the system and sirens, referring to the campus as the place.
    14. present: It says 'the campus tests' the system and sirens, referring to campus as the location.
    15. present: It refers to "the campus" where the systems and sirens are tested.
    16. present: It says 'the campus tests' the systems, identifying the campus as the place involved.
    17. absent: It refers to 'the campus' testing generally without naming any place affected by a hazard.
    18. absent: It refers to 'the campus' only as the party running the tests, with no incident location.
    19. absent: It mentions the campus only as conducting tests and gives no location of any hazard.
    20. present: It says 'the campus tests' its sirens and systems, naming the campus.
    21. present: It says 'the campus tests' the alert system and sirens, which refers to campus as the place.
    22. present: It says 'the campus tests' its systems, which places the activity on campus.
    23. present: It says 'the campus tests' the systems and sirens, referring to the campus.
    24. absent: It says the campus tests its systems but names no specific place affected by a hazard.
    25. present: It says 'the campus tests' its sirens, naming the campus as the setting.
  • Guidanceabsent0/25

    Final assessment

    All 25 reads agree guidance is absent: editing device settings at alert.umd.edu is not a protective action against a hazard.

    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: It tells readers they may edit device settings, which is not a protective action against a hazard.
    2. absent: Telling affiliates they 'may edit their mobile device settings' is optional preparedness, not protective action.
    3. absent: It notes affiliates "may edit their mobile device settings", which is optional housekeeping rather than a protective action.
    4. absent: It notes that affiliates 'may edit their mobile device settings', which is not a protective action.
    5. absent: It only says affiliates 'may edit their mobile device settings', not a protective action.
    6. absent: Noting that affiliates 'may edit their mobile device settings' is optional housekeeping, not protective guidance.
    7. absent: It explains that users may edit device settings but gives no protective action to take.
    8. absent: It tells affiliates they may edit device settings, which is not a protective action.
    9. absent: It notes affiliates 'may edit their mobile device settings', an optional setting, not a protective action.
    10. absent: It only mentions editing device settings, which is not a protective action against a threat.
    11. absent: It notes affiliates 'may edit their mobile device settings', an administrative option rather than a protective action.
    12. absent: It notes affiliates 'may edit their mobile device settings', which is not a protective action.
    13. absent: It only notes that affiliates 'may edit their mobile device settings', which is not a protective action.
    14. absent: Saying affiliates 'may edit their mobile device settings' is optional housekeeping, not a protective action.
    15. absent: It mentions editing mobile device settings at alert.umd.edu but gives no protective action instruction.
    16. absent: It notes affiliates 'may edit their mobile device settings', which is optional housekeeping rather than a protective instruction.
    17. absent: It explains monthly tests and settings but gives no protective action to recipients.
    18. absent: It notes that affiliates 'may edit their mobile device settings', which is not a protective action.
    19. absent: It says affiliates may edit device settings, which is optional and not a protective action.
    20. absent: It notes affiliates 'may edit their mobile device settings', not a protective action.
    21. absent: It notes affiliates 'may edit their mobile device settings', which is optional administration, not a protective action.
    22. absent: It notes affiliates 'may edit their mobile device settings', which is not a protective action.
    23. absent: It mentions editing device settings, which is not a protective action against a hazard.
    24. absent: It says affiliates 'may edit their mobile device settings', which is not a protective action against a hazard.
    25. absent: It only notes that affiliates 'may edit their mobile device settings', not a protective action.
  • Timepresent25/25

    Final assessment

    All 25 reads agree time is present: tests occur on the "First Wednesday of each month at 11:55 a.m.".

    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 specifies tests on the "First Wednesday of each month at 11:55 a.m.".
    2. present: It gives the schedule 'First Wednesday of each month at 11:55 a.m.'.
    3. present: It states the tests occur on the "First Wednesday of each month at 11:55 a.m."
    4. present: It gives the schedule 'First Wednesday of each month at 11:55 a.m.' for the tests.
    5. present: It gives the schedule 'First Wednesday of each month at 11:55 a.m.'.
    6. present: It specifies that tests happen on the 'First Wednesday of each month at 11:55 a.m.'.
    7. present: It says tests occur the 'First Wednesday of each month at 11:55 a.m.'.
    8. present: It gives the schedule as the 'First Wednesday of each month at 11:55 a.m.'
    9. present: It gives the schedule as 'First Wednesday of each month at 11:55 a.m.', a time reference.
    10. present: It specifies 'First Wednesday of each month at 11:55 a.m.' as the test time.
    11. present: It says tests occur the 'First Wednesday of each month at 11:55 a.m.', giving timing.
    12. present: It says tests occur the 'First Wednesday of each month at 11:55 a.m.'.
    13. present: It states tests occur the 'First Wednesday of each month at 11:55 a.m.'.
    14. present: It specifies the 'First Wednesday of each month at 11:55 a.m.' as the test time.
    15. present: It gives a recurring schedule, "First Wednesday of each month at 11:55 a.m.", for the tests.
    16. present: It gives the schedule 'First Wednesday of each month at 11:55 a.m.', a time reference.
    17. present: It states tests happen the 'First Wednesday of each month at 11:55 a.m.'.
    18. present: It states tests occur the 'First Wednesday of each month at 11:55 a.m.'
    19. present: It says tests occur on the first Wednesday of each month at 11:55 a.m.
    20. present: It gives 'First Wednesday of each month at 11:55 a.m.' as the test time.
    21. present: It gives the test schedule as the 'First Wednesday of each month at 11:55 a.m.'.
    22. present: It gives the schedule 'First Wednesday of each month at 11:55 a.m.', a time reference.
    23. present: It gives 'First Wednesday of each month at 11:55 a.m.' as the test schedule.
    24. present: It gives the schedule 'First Wednesday of each month at 11:55 a.m.', a clear time reference.
    25. present: It gives the schedule 'First Wednesday of each month at 11:55 a.m.'.
  • Impactabsent0/25

    Final assessment

    All 25 reads agree impact is absent: "These are only tests" and no consequence or severity 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: It states "These are only tests" and conveys no consequence or severity.
    2. absent: No consequence or severity of any hazard is stated in this test notice.
    3. absent: The message is about routine testing and conveys no consequence or severity of any hazard.
    4. absent: As a test notice, it states no consequence or severity of any hazard.
    5. absent: As a notice about scheduled tests, it states no consequence or severity of any real hazard.
    6. absent: As a test notice, it conveys no consequence or severity of a hazard.
    7. absent: As a routine test notice it conveys no consequence or severity of any hazard.
    8. absent: No consequence or severity of any hazard is conveyed in this test notice.
    9. absent: It conveys no consequence or severity because it concerns routine testing only.
    10. absent: As a test notice, it conveys no consequence or severity of any hazard.
    11. absent: As a routine test notice, it conveys no consequence or severity of any hazard.
    12. absent: As a test notice it states no consequence or severity of any hazard.
    13. absent: As a test explanation, it conveys no consequence or severity of any hazard.
    14. absent: No consequence or severity of any hazard is conveyed since only tests are described.
    15. absent: No hazard consequence or severity is described in this routine monthly UMD Alert test notice.
    16. absent: The test notice describes no hazard and thus no consequence or severity.
    17. absent: As a test notice, it conveys no consequence or severity of any hazard.
    18. absent: The test notice conveys no consequence or severity of any hazard.
    19. absent: As a test notice it conveys no consequence or severity of any hazard.
    20. absent: No consequence or severity of any hazard is conveyed in this test notice.
    21. absent: It describes tests only and conveys no consequence or severity of any hazard.
    22. absent: It explains the tests but conveys no consequence or severity of any hazard.
    23. absent: As a test notice, it conveys no consequence or severity of any hazard.
    24. absent: It conveys no potential harm or severity, since only tests are described.
    25. absent: It conveys no potential consequence or severity of any hazard in this test notice.

Coded by Claude Opus 5.5

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

About this analysis
Context

Background

University of Maryland official UMD Alerts archive.
Analysis

Key Findings

Official UMD Alerts page preserves complete notice 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
Cite this case

Campus Alert Archive. "University of Maryland, College Park: Monthly Alert emergency system test notice." Incident of July 1, 2026. Added July 2026; last updated September 2026. https://campusalertarchive.com/case/university-of-maryland-umd-alert-test-41-2026-07-01/

Download case JSON

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

Tags
marylandumdumd-alertstest
Added July 2026Updated September 2026Via ingestion