Skip to content
Campus Alert Archive
UF

Cancer and Genetics gas odor evacuation then no leak found

AI-generated · every claim is source-linked
FLgas leakemergency notificationhigh confidence
UnfoundedNo evidence of an actual threat was found. The institutional response is documented because the alert communication is identical to what would occur during a real incident.

UF Alert evacuated the Cancer and Genetics Research Building for a strong gas odor, updated with fire rescue on scene, then cleared that no gas leak was identified.

Alerts
4
Response
Killed
Injured
Institution
University of Florida
Public R1 · FL
All UF cases →
~60,000 studentsUF Alert / @UFAlert
Official alert policy
Read when and how UF says it will use UF Alert: summarized, quoted, and analyzed.
Documented Timeline

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.

INITIAL ALERTTwitter/X
Verified verbatim172 chars
Strong odor of gas located at Cancer and Genetics Research Building on 2033 Mowry Rd. Building being evacuated. Avoid area or shelter in place if nearby; details to follow.
Dual independent X fetch match 2026-08-02. SPN 523.
UPDATETwitter/X+14 min
Verified verbatim164 chars
Update (Mowry Road). Fire rescue is on scene and working to locate the origin of the odor. Continue to avoid the area and follow the directions of first responders.
Dual independent X fetch match 2026-08-02. SPN 523.
UPDATETwitter/X+28 min
Verified verbatim135 chars
UPDATE: (Cancer and Genetics): There has been no change in the situation. Avoid the area and follow the directions of first responders.
EXPANSION 2026-08-02 sequence completion. Dual independent X fetch match. SPN 523.
ALL CLEARTwitter/X+55 min
Verified verbatim126 chars
UPDATE: (Cancer and Genetics): No gas leak identified. Resume normal activities unless directed otherwise by first responders.
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.

Strong odor of gas located at Cancer and Genetics Research Building on 2033 Mowry Rd. Building being evacuated. Avoid area or shelter in place if nearby; details to follow.

  • 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 "Strong odor of gas located at Cancer an…".

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

    Final assessment

    Majority 25/25 present. Location is given through "Research Building".

    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 given through "Research Building".
    2. present: Place is specified as "Research Building".
    3. present: Where is answered by "Research Building".
    4. present: "Research Building" functions as the location element.
    5. present: The alert situates the event with "Research Building".
    6. present: Geographic or campus place: "Research Building".
    7. present: L=1 because "Research Building" names where this applies.
    8. present: Recipients are told the place via "Research Building".
    9. present: Location present in the phrase "Research Building".
    10. present: A campus or building reference "Research Building" covers location.
    11. present: The where cue is "Research Building".
    12. present: "Research Building" identifies the affected area.
    13. present: Place naming succeeds with "Research Building".
    14. present: Location codes yes on "Research Building".
    15. present: Site detail appears as "Research Building".
    16. present: The message anchors place with "Research Building".
    17. present: "Research Building" is enough location under the rubric.
    18. present: Affected place language: "Research Building".
    19. present: L is present via "Research Building".
    20. present: Campus geography is marked by "Research Building".
    21. present: Where this matters is "Research Building".
    22. present: The text localizes to "Research Building".
    23. present: Location element met by "Research Building".
    24. present: Place is not left blank: "Research Building".
    25. present: Spatial reference "Research Building" supports L=1.
  • Guidancepresent25/25

    Final assessment

    Majority 25/25 present. Guidance is the instruction "shelter in place".

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

    Final assessment

    Majority 25/25 absent. No clock time, date, or recency word such as now or today 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
    1. absent: No clock time, date, or recency word such as now or today appears.
    2. absent: Time is absent from the alert text.
    3. absent: Nothing tells recipients when this applies.
    4. absent: T=0 because temporal cues are missing.
    5. absent: No day, hour, or immediate language is stated.
    6. absent: The message omits timing entirely.
    7. absent: Time element fails on this wording.
    8. absent: When is left unspecified.
    9. absent: No calendar or clock reference is present.
    10. absent: Temporal information cannot be found.
    11. absent: Without a time cue, T is zero.
    12. absent: The alert is silent on schedule.
    13. absent: Time codes absent here.
    14. absent: Recency language is missing.
    15. absent: T fails the when test.
    16. absent: No today/now/clock marker appears.
    17. absent: Timing is not established by the text.
    18. absent: Date and hour are both omitted.
    19. absent: Temporal element is not satisfied.
    20. absent: The body lacks any when cue.
    21. absent: Time not present under the rubric.
    22. absent: Schedule detail is blank.
    23. absent: No temporal anchor is given.
    24. absent: T is absent on timeless wording.
    25. absent: When-information is not included.
  • 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

UF posts UF Alert emergency notices on @UFAlert.
Analysis

Key Findings

Evacuate plus avoid/shelter options for gas odor; later unfounded all-clear.
Outcome
No gas leak identified; normal activities resumed.
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
  3. Social
  4. Social
Cite this case

Campus Alert Archive. "University of Florida: Cancer and Genetics gas odor evacuation then no leak found." Incident of March 26, 2026. Added August 2026. https://campusalertarchive.com/case/university-of-florida-cancer-genetics-gas-odor-evacuation-2026-03-26/

Download case JSON

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

Tags
public-r1floridagas-leakuf-alertUnfounded
Added August 2026Updated August 2026Via ingestion