Skip to content
Campus Alert Archive
U-M

Gas leak Ellsworth and State avoid area

AI-generated · every claim is source-linked
MIgas leakemergency notificationhigh confidence

UM EAlert reported a gas leak at W Ellsworth Rd / S State Rd at 5:35 p.m. and ordered people to avoid the area.

Alerts
1
Response
Killed
Injured
Institution
University of Michigan
Public R1 · MI
All U-M cases →
~51,000 studentsUM EAlert / @umichdpss
Official alert policy
Read when and how U-M says it will use U-M Emergency 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 ALERTTwitter/X
Verified verbatim115 chars
UM EAlert Ann Arbor: 5:35pm Gas Leak W ELLSWORTH RD / S STATE RD. Avoid the area. Updates: https://dpss.umich.edu/
Dual independent X fetch match 2026-08-02. SPN 523.
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.

UM EAlert Ann Arbor: 5:35pm Gas Leak W ELLSWORTH RD / S STATE RD. Avoid the area. Updates: https://dpss.umich.edu/

  • Sourceabsent0/25

    Final assessment

    Majority 25/25 absent. No campus brand, agency name, or alert signature appears in the text.

    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. absent: No campus brand, agency name, or alert signature appears in the text.
    2. absent: The wording never says who is sending the notice.
    3. absent: Source is absent: no university, police, or alert-system label is stated.
    4. absent: Nothing identifies an issuing authority or branded channel.
    5. absent: No sender tag or institutional self-naming is present.
    6. absent: Recipients cannot tell the source from the body alone.
    7. absent: Source codes zero because authority language is missing.
    8. absent: There is no ALERT brand or school name to credit as source.
    9. absent: The message jumps to content without naming who issued it.
    10. absent: No public-safety or campus office is identified as sender.
    11. absent: Source fails: blank on branded signature and agency.
    12. absent: Issuing body is not stated in any form.
    13. absent: Without a signature or school name, source is absent.
    14. absent: The text omits sender identification entirely.
    15. absent: No authority cue meets the source element rule.
    16. absent: Source not present under the branding or agency tests.
    17. absent: Who authored the alert is left unspecified.
    18. absent: There is no institutional label to treat as source.
    19. absent: Sender identity cannot be read from the message.
    20. absent: Source scores absent on this wording.
    21. absent: No alert header or campus self-reference is included.
    22. absent: The body never attributes the notice to an issuer.
    23. absent: Authority line is missing from start to end.
    24. absent: Source element fails for lack of named sender.
    25. absent: Nothing in the text names a sending organization.
  • Hazardpresent25/25

    Final assessment

    Majority 25/25 present. Hazard is specific: the text names "Gas Leak".

    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 specific: the text names "Gas Leak".
    2. present: A concrete threat appears as "Gas Leak".
    3. present: The what of the emergency is "Gas Leak", not a vague incident label.
    4. present: "Gas Leak" satisfies hazard by naming the condition or threat.
    5. present: Readers learn the hazard type from "Gas Leak".
    6. present: Hazard present via the explicit phrase "Gas Leak".
    7. present: The threat is particularized as "Gas Leak".
    8. present: Coding H=1 because "Gas Leak" is a named hazard.
    9. present: Specific danger language: "Gas Leak".
    10. present: The alert states the problem as "Gas Leak".
    11. present: Hazard element met by "Gas Leak".
    12. present: "Gas Leak" is more than a generic emergency word.
    13. present: Threat identity is clear from "Gas Leak".
    14. present: The message pins the hazard to "Gas Leak".
    15. present: Named condition "Gas Leak" counts as hazard.
    16. present: H is present: "Gas Leak" tells what is wrong.
    17. present: Concrete hazard wording includes "Gas Leak".
    18. present: The incident type is given as "Gas Leak".
    19. present: "Gas Leak" is the stated threat or weather/system hazard.
    20. present: Hazard codes yes on "Gas Leak".
    21. present: Specifics beat generics here: "Gas Leak".
    22. present: The text's hazard signal is "Gas Leak".
    23. present: What happened is labeled "Gas Leak".
    24. present: Hazard present with the phrase "Gas Leak".
    25. present: Threat naming succeeds through "Gas Leak".
  • Locationabsent0/25

    Final assessment

    Majority 25/25 absent. No building, campus, street, or area is named.

    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. absent: No building, campus, street, or area is named.
    2. absent: Location is absent: the text never says where.
    3. absent: There is no place cue for recipients to orient to.
    4. absent: L=0 because spatial reference is missing.
    5. absent: The alert omits campus or site detail.
    6. absent: Where this applies is never stated.
    7. absent: No location language appears in the body.
    8. absent: Place naming fails on this wording.
    9. absent: Readers get no geographic anchor.
    10. absent: Location element is not satisfied.
    11. absent: Without a place name, L is zero.
    12. absent: The message leaves location unspecified.
    13. absent: No hall, campus, or area reference is present.
    14. absent: Spatial information is missing entirely.
    15. absent: L fails the place-naming test.
    16. absent: Affected site is not identified.
    17. absent: Location codes absent here.
    18. absent: The text is silent on where.
    19. absent: No campus geography is given.
    20. absent: Place element cannot be coded present.
    21. absent: Where-cue is blank in this alert.
    22. absent: Location not established by the wording.
    23. absent: Site detail is omitted.
    24. absent: No area or building reference exists.
    25. absent: L is absent on a pure no-place text.
  • Guidancepresent25/25

    Final assessment

    Majority 25/25 present. Guidance is the instruction "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 the instruction "Avoid the area".
    2. present: Protective action appears as "Avoid the area".
    3. present: Recipients are told to act via "Avoid the area".
    4. present: "Avoid the area" is a direct what-to-do line.
    5. present: G=1 because "Avoid the area" instructs the audience.
    6. present: The alert directs action with "Avoid the area".
    7. present: Guidance present: "Avoid the area".
    8. present: A clear instruction is "Avoid the area".
    9. present: What to do is stated as "Avoid the area".
    10. present: "Avoid the area" counts as protective guidance.
    11. present: Action language "Avoid the area" meets guidance.
    12. present: The message tells people "Avoid the area".
    13. present: Guidance codes yes on "Avoid the area".
    14. present: Operational direction: "Avoid the area".
    15. present: Instructional content includes "Avoid the area".
    16. present: "Avoid the area" is audience-facing guidance.
    17. present: G is present via the cue "Avoid the area".
    18. present: Protective or operational order "Avoid the area" is explicit.
    19. present: The text's guidance signal is "Avoid the area".
    20. present: Recipients receive the directive "Avoid the area".
    21. present: What-to-do element satisfied by "Avoid the area".
    22. present: "Avoid the area" tells the public how to respond or operate.
    23. present: Guidance met through "Avoid the area".
    24. present: Action instruction present: "Avoid the area".
    25. present: The alert's order to the audience is "Avoid the area".
  • Timepresent25/25

    Final assessment

    Majority 25/25 present. Time is marked by "5:35pm".

    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 marked by "5:35pm".
    2. present: A temporal cue appears as "5:35pm".
    3. present: When is answered with "5:35pm".
    4. present: "5:35pm" supplies timing or recency.
    5. present: T=1 because "5:35pm" is a time reference.
    6. present: Clock or calendar language: "5:35pm".
    7. present: The alert times the event with "5:35pm".
    8. present: Temporal detail "5:35pm" is present.
    9. present: Time element met by "5:35pm".
    10. present: Recipients see timing via "5:35pm".
    11. present: "5:35pm" counts as the time cue.
    12. present: When-language includes "5:35pm".
    13. present: T codes yes on "5:35pm".
    14. present: A schedule or day marker "5:35pm" appears.
    15. present: Timing is explicit: "5:35pm".
    16. present: The text anchors time with "5:35pm".
    17. present: "5:35pm" is enough for the time element.
    18. present: Recency or clock cue "5:35pm" is stated.
    19. present: T is present via "5:35pm".
    20. present: Date or hour language "5:35pm" supports T=1.
    21. present: Temporal reference: "5:35pm".
    22. present: The when signal is "5:35pm".
    23. present: Time present through "5:35pm".
    24. present: "5:35pm" tells recipients the relevant when.
    25. present: Schedule wording "5:35pm" meets time.
  • Impactabsent0/25

    Final assessment

    Majority 25/25 absent. No consequence or severity language appears beyond naming a 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 consequence or severity language appears beyond naming a hazard.
    2. absent: Impact is absent: the text does not say what the threat could do.
    3. absent: Nothing states danger level, injuries, or disruptive effect.
    4. absent: I=0 because severity or harm is not conveyed.
    5. absent: Hazard may be named, but impact language is missing.
    6. absent: The alert omits consequence wording.
    7. absent: Impact fails the harm-or-severity test.
    8. absent: Readers are not told stakes or effects.
    9. absent: No life-safety or operational impact phrase is present.
    10. absent: Impact element codes absent.
    11. absent: Without consequence language, I is zero.
    12. absent: Severity is left unstated.
    13. absent: The text stops short of impact.
    14. absent: Harm potential is not described.
    15. absent: I fails on bare description without effects.
    16. absent: No dangerous/closed/injury-style impact cue appears.
    17. absent: Impact not established by the wording.
    18. absent: Consequence detail is missing.
    19. absent: The message lacks severity framing.
    20. absent: I is absent under the impact rule.
    21. absent: Stakes for people or property are not stated.
    22. absent: No disruption or harm language is included.
    23. absent: Impact cannot be coded present here.
    24. absent: Effect-on-campus language is omitted.
    25. absent: Severity/consequence element fails.

Coded by SuperGrok Heavy 4.5

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

About this analysis
Context

Background

U-M DPSS posts EAlert notices on @umichdpss.
Analysis

Key Findings

Clock-time gas leak with avoid-area instruction at a named intersection.
Outcome
Avoid-area gas leak notice issued.
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
Cite this case

Campus Alert Archive. "University of Michigan: Gas leak Ellsworth and State avoid area." Incident of February 12, 2026. Added August 2026. https://campusalertarchive.com/case/university-of-michigan-ellsworth-state-gas-leak-2026-02-12/

Download case JSON

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

Tags
public-r1michigangas-leakealert
Added August 2026Updated August 2026Via ingestion