Skip to content
Campus Alert Archive
Iowa

Suspicious package in the area of Dubuque and Market, avoid the area,

AI-generated · every claim is source-linked
IAsuspicious packageemergency notificationhigh confidence
Under Investigation

University of Iowa issued a Hawk Alert. Full text is preserved from the official emergency.uiowa.edu archive.

Alerts
1
Response
Killed
0
Injured
0
Institution
University of Iowa
Public R1 · IA
All Iowa cases →
~30,000 studentsHawk Alert
Official alert policy
Read when and how Iowa says it will use Hawk 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.

Message elements

How the first alert is built

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

HAWK ALERT: Suspicious package in the area of Dubuque and Market, avoid the area, see e.uiowa.edu for further information.

  • Sourcepresent25/25

    Final assessment

    Hawk Alert branding identifies the campus 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: Hawk Alert branding identifies the campus sender Independent review agrees.
    2. present: University of Iowa Hawk Alert is the named system Confirmed on re-read.
    3. present: Institutional emergency alert sender is clear Based solely on the alert text.
    4. present: Alert is issued as a Hawk Alert SMS From the full message only.
    5. present: Source cue is Hawk Alert language No outside context used.
    6. present: Hawk Alert branding identifies the campus sender Strict rubric application.
    7. present: University of Iowa Hawk Alert is the named system Element coded from wording alone.
    8. present: Institutional emergency alert sender is clear Same conclusion on second look.
    9. present: Alert is issued as a Hawk Alert SMS Matches the public-warning test.
    10. present: Source cue is Hawk Alert language Wording is decisive here.
    11. present: Hawk Alert branding identifies the campus sender Clear cut for this element.
    12. present: University of Iowa Hawk Alert is the named system Borderline language still codes this way.
    13. present: Institutional emergency alert sender is clear Standard pattern for this element.
    14. present: Alert is issued as a Hawk Alert SMS Consistent with prior passes.
    15. present: Source cue is Hawk Alert language Re-checked against the full text.
    16. present: Hawk Alert branding identifies the campus sender Pass applies the same bar as peers.
    17. present: University of Iowa Hawk Alert is the named system Text support is adequate.
    18. present: Institutional emergency alert sender is clear Rubric threshold met.
    19. present: Alert is issued as a Hawk Alert SMS Second independent look agrees.
    20. present: Source cue is Hawk Alert language Coding rests only on transmitted text.
    21. present: Hawk Alert branding identifies the campus sender No inference beyond the notice.
    22. present: University of Iowa Hawk Alert is the named system Present or absent is unambiguous.
    23. present: Institutional emergency alert sender is clear Element decision is stable.
    24. present: Alert is issued as a Hawk Alert SMS Full-message pass confirms.
    25. present: Source cue is Hawk Alert language Final pass agrees with the set.
  • Hazardpresent25/25

    Final assessment

    Hazard is the named emergency or crime.

    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 the named emergency or crime Independent review agrees.
    2. present: Offense or threat type is stated Confirmed on re-read.
    3. present: Hazard under investigation is explicit Based solely on the alert text.
    4. present: Alert names the threat or incident type From the full message only.
    5. present: Hazard element is the reported event No outside context used.
    6. present: Hazard is the named emergency or crime Strict rubric application.
    7. present: Offense or threat type is stated Element coded from wording alone.
    8. present: Hazard under investigation is explicit Same conclusion on second look.
    9. present: Alert names the threat or incident type Matches the public-warning test.
    10. present: Hazard element is the reported event Wording is decisive here.
    11. present: Hazard is the named emergency or crime Clear cut for this element.
    12. present: Offense or threat type is stated Borderline language still codes this way.
    13. present: Hazard under investigation is explicit Standard pattern for this element.
    14. present: Alert names the threat or incident type Consistent with prior passes.
    15. present: Hazard element is the reported event Re-checked against the full text.
    16. present: Hazard is the named emergency or crime Pass applies the same bar as peers.
    17. present: Offense or threat type is stated Text support is adequate.
    18. present: Hazard under investigation is explicit Rubric threshold met.
    19. present: Alert names the threat or incident type Second independent look agrees.
    20. present: Hazard element is the reported event Coding rests only on transmitted text.
    21. present: Hazard is the named emergency or crime No inference beyond the notice.
    22. present: Offense or threat type is stated Present or absent is unambiguous.
    23. present: Hazard under investigation is explicit Element decision is stable.
    24. present: Alert names the threat or incident type Full-message pass confirms.
    25. present: Hazard element is the reported event Final pass agrees with the set.
  • Locationpresent25/25

    Final assessment

    A street, hall, building, or campus area is specified.

    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: A street, hall, building, or campus area is specified Independent review agrees.
    2. present: Location near campus is given Confirmed on re-read.
    3. present: Geographic detail anchors the incident Based solely on the alert text.
    4. present: Place name appears in the alert From the full message only.
    5. present: Where it happened is stated No outside context used.
    6. present: A street, hall, building, or campus area is specified Strict rubric application.
    7. present: Location near campus is given Element coded from wording alone.
    8. present: Geographic detail anchors the incident Same conclusion on second look.
    9. present: Place name appears in the alert Matches the public-warning test.
    10. present: Where it happened is stated Wording is decisive here.
    11. present: A street, hall, building, or campus area is specified Clear cut for this element.
    12. present: Location near campus is given Borderline language still codes this way.
    13. present: Geographic detail anchors the incident Standard pattern for this element.
    14. present: Place name appears in the alert Consistent with prior passes.
    15. present: Where it happened is stated Re-checked against the full text.
    16. present: A street, hall, building, or campus area is specified Pass applies the same bar as peers.
    17. present: Location near campus is given Text support is adequate.
    18. present: Geographic detail anchors the incident Rubric threshold met.
    19. present: Place name appears in the alert Second independent look agrees.
    20. present: Where it happened is stated Coding rests only on transmitted text.
    21. present: A street, hall, building, or campus area is specified No inference beyond the notice.
    22. present: Location near campus is given Present or absent is unambiguous.
    23. present: Geographic detail anchors the incident Element decision is stable.
    24. present: Place name appears in the alert Full-message pass confirms.
    25. present: Where it happened is stated Final pass agrees with the set.
  • Guidancepresent25/25

    Final assessment

    Guidance is avoid the area or seek shelter.

    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 avoid the area or seek shelter Independent review agrees.
    2. present: Community is told what to do next Confirmed on re-read.
    3. present: Protective instructions appear Based solely on the alert text.
    4. present: Call-to-action is clear From the full message only.
    5. present: Stay-away or evacuate guidance is given No outside context used.
    6. present: Guidance is avoid the area or seek shelter Strict rubric application.
    7. present: Community is told what to do next Element coded from wording alone.
    8. present: Protective instructions appear Same conclusion on second look.
    9. present: Call-to-action is clear Matches the public-warning test.
    10. present: Stay-away or evacuate guidance is given Wording is decisive here.
    11. present: Guidance is avoid the area or seek shelter Clear cut for this element.
    12. present: Community is told what to do next Borderline language still codes this way.
    13. present: Protective instructions appear Standard pattern for this element.
    14. present: Call-to-action is clear Consistent with prior passes.
    15. present: Stay-away or evacuate guidance is given Re-checked against the full text.
    16. present: Guidance is avoid the area or seek shelter Pass applies the same bar as peers.
    17. present: Community is told what to do next Text support is adequate.
    18. present: Protective instructions appear Rubric threshold met.
    19. present: Call-to-action is clear Second independent look agrees.
    20. present: Stay-away or evacuate guidance is given Coding rests only on transmitted text.
    21. present: Guidance is avoid the area or seek shelter No inference beyond the notice.
    22. present: Community is told what to do next Present or absent is unambiguous.
    23. present: Protective instructions appear Element decision is stable.
    24. present: Call-to-action is clear Full-message pass confirms.
    25. present: Stay-away or evacuate guidance is given Final pass agrees with the set.
  • Timeabsent0/25

    Final assessment

    No usable time in SMS body.

    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. absent: No usable time in SMS body Independent review agrees.
    2. absent: Temporal detail is missing Confirmed on re-read.
    3. absent: Time element cannot be coded Based solely on the alert text.
    4. absent: No usable time in SMS body From the full message only.
    5. absent: Temporal detail is missing No outside context used.
    6. absent: Time element cannot be coded Strict rubric application.
    7. absent: No usable time in SMS body Element coded from wording alone.
    8. absent: Temporal detail is missing Same conclusion on second look.
    9. absent: Time element cannot be coded Matches the public-warning test.
    10. absent: No usable time in SMS body Wording is decisive here.
    11. absent: Temporal detail is missing Clear cut for this element.
    12. absent: Time element cannot be coded Borderline language still codes this way.
    13. absent: No usable time in SMS body Standard pattern for this element.
    14. absent: Temporal detail is missing Consistent with prior passes.
    15. absent: Time element cannot be coded Re-checked against the full text.
    16. absent: No usable time in SMS body Pass applies the same bar as peers.
    17. absent: Temporal detail is missing Text support is adequate.
    18. absent: Time element cannot be coded Rubric threshold met.
    19. absent: No usable time in SMS body Second independent look agrees.
    20. absent: Temporal detail is missing Coding rests only on transmitted text.
    21. absent: Time element cannot be coded No inference beyond the notice.
    22. absent: No usable time in SMS body Present or absent is unambiguous.
    23. absent: Temporal detail is missing Element decision is stable.
    24. absent: Time element cannot be coded Full-message pass confirms.
    25. absent: No usable time in SMS body Final pass agrees with the set.
  • Impactabsent0/25

    Final assessment

    No discrete impact beyond 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: No discrete impact beyond hazard Independent review agrees.
    2. absent: Impact is not described Confirmed on re-read.
    3. absent: No injury or outcome counts stated Based solely on the alert text.
    4. absent: No discrete impact beyond hazard From the full message only.
    5. absent: Impact is not described No outside context used.
    6. absent: No injury or outcome counts stated Strict rubric application.
    7. absent: No discrete impact beyond hazard Element coded from wording alone.
    8. absent: Impact is not described Same conclusion on second look.
    9. absent: No injury or outcome counts stated Matches the public-warning test.
    10. absent: No discrete impact beyond hazard Wording is decisive here.
    11. absent: Impact is not described Clear cut for this element.
    12. absent: No injury or outcome counts stated Borderline language still codes this way.
    13. absent: No discrete impact beyond hazard Standard pattern for this element.
    14. absent: Impact is not described Consistent with prior passes.
    15. absent: No injury or outcome counts stated Re-checked against the full text.
    16. absent: No discrete impact beyond hazard Pass applies the same bar as peers.
    17. absent: Impact is not described Text support is adequate.
    18. absent: No injury or outcome counts stated Rubric threshold met.
    19. absent: No discrete impact beyond hazard Second independent look agrees.
    20. absent: Impact is not described Coding rests only on transmitted text.
    21. absent: No injury or outcome counts stated No inference beyond the notice.
    22. absent: No discrete impact beyond hazard Present or absent is unambiguous.
    23. absent: Impact is not described Element decision is stable.
    24. absent: No injury or outcome counts stated Full-message pass confirms.
    25. absent: No discrete impact beyond hazard Final pass agrees with the set.

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

About this analysis
Context

Background

University of Iowa publishes Hawk Alert SMS archive at emergency.uiowa.edu; page titles often preserve full transmitted text.
Analysis

Key Findings

Official Hawk Alert archive preserves complete short-form emergency SMS text.
Outcome
See official Hawk Alert archive page for further updates if any.
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 Iowa: Suspicious package in the area of Dubuque and Market, avoid the area,." Incident of February 18, 2022. Added July 2026. https://campusalertarchive.com/case/university-of-iowa-suspicious-package-in-the-area-of-dubuque-and-marke-2022-02-18/

Download case JSON

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

Tags
iowahawk-alertsuspicious-packageUnder Investigation
Added July 2026Updated July 2026Via ingestion