Skip to content
Campus Alert Archive
Georgia Tech

Back-to-back lightning holds delay a football game; fans sheltered in stadium concourses

AI-generated · every claim is source-linked
GAsevere stormadvisoryhigh confidence
Confirmed Threat

Georgia Tech's home opener against South Carolina State on September 9, 2023, was delayed more than two hours after back-to-back lightning holds forced fans at Bobby Dodd Stadium to take shelter in the concourses before a scheduled 1 PM EDT kickoff. 11Alive reported that fans who left the stadium to shelter in their cars were later allowed to re-enter with their tickets; Georgia Tech ultimately defeated South Carolina State 48-13.

Alerts
7
Response
Killed
Injured
Institution
Georgia Institute of Technology
Public R1 · GA
All Georgia Tech cases →
~21,916 studentsGT Emergency Notification
Official alert policy
Read when and how Georgia Tech says it will use GTENS: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

7 messages in sequence · 3 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.

Some messages in this sequence are documented (their existence, timing, and channel are sourced) but their exact wording is not preserved in the public record. Those entries appear as placeholders; only confirmed text is displayed.

INITIAL ALERTTwitter/X
Verified verbatim196 chars
We are currently in a pregame hold due to potential severe weather in the area. New approximate kickoff time for @GeorgiaTechFB vs South Carolina State is 1:22 pm ET. Please stay tune for updates.
Exact text from official @GTAthletics status 1700554806144962570
UPDATETwitter/X
Wording not preserved

This message is documented at this point in the sequence, but its exact wording is not preserved in the public record. The public edition displays only confirmed alert text.

@GTAthletics on X (official, verbatim)
UPDATETwitter/X
Wording not preserved

This message is documented at this point in the sequence, but its exact wording is not preserved in the public record. The public edition displays only confirmed alert text.

@GTAthletics on X (official, verbatim)
UPDATETwitter/X
Verified verbatim132 chars
IMPORTANT UPDATE: Fans inside Bobby Dodd Stadium at Hyundai Field are asked to please take shelter in the concourses of the stadium.
11Alive reported this shelter instruction was tweeted out around 1:50 PM EDT, just moments after teams had taken the field for a 1:42 PM EDT kickoff attempt, the second lightning hold of the afternoon, which reset the mandatory 30-minute clock and extended the total delay to more than two hours.
The message directs fans to the concourses rather than out of the stadium entirely, reflecting Bobby Dodd Stadium's covered-concourse shelter plan for lightning events.
UPDATETwitter/X
Wording not preserved

This message is documented at this point in the sequence, but its exact wording is not preserved in the public record. The public edition displays only confirmed alert text.

@GTAthletics on X (verbatim raw t.co)
UPDATETwitter/X
Wording not preserved

This message is documented at this point in the sequence, but its exact wording is not preserved in the public record. The public edition displays only confirmed alert text.

@GTAthletics on X (official, verbatim)
ALL CLEARTwitter/X
Verified verbatim231 chars
UPDATE TO THE UPDATE: Severe weather is no longer a threat to Bobby Dodd Stadium at Hyundai Field. Fans may return to their seats. As a reminder, if you left the stadium, you may re-enter with your original game ticket. #StingEm 🐝
Exact text from official @GTAthletics status 1700584266130972832
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.

We are currently in a pregame hold due to potential severe weather in the area. New approximate kickoff time for @GeorgiaTechFB vs South Carolina State is 1:22 pm ET. Please stay tune for updates.

  • Sourcepresent17/25

    Final assessment

    Most reads (17 of 25) counted the '@GeorgiaTechFB' tag as identifying the issuing account; a notable minority felt this game-status post lacks a clear institutional or safety authority, but the majority treats the tagged account as the identifiable source.

    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 sender or authority identified in this game-status update.
    2. present: References "@GeorgiaTechFB" as the account/team issuing the update.
    3. present: '@GeorgiaTechFB' identifies the posting account.
    4. absent: No sender or agency identified, only references the football team account tone.
    5. absent: No sender or authority named in this weather hold update.
    6. absent: No sender or issuing authority named, just a game-status update.
    7. present: References '@GeorgiaTechFB', a team-branded account.
    8. present: References "@GeorgiaTechFB" as the source of the update.
    9. absent: No sender name or agency identified, references a football game account
    10. present: References '@GeorgiaTechFB' as the sending account.
    11. present: References '@GeorgiaTechFB' as the identifiable sender.
    12. present: '@GeorgiaTechFB' referenced as identifying source of the update.
    13. present: References '@GeorgiaTechFB' identifying the team/institution.
    14. present: References '@GeorgiaTechFB' identifying the team/institution.
    15. absent: No sender or authority identified, only references the football team by tag.
    16. absent: No sender identity or agency named, only tags a football team.
    17. present: References '@GeorgiaTechFB' as the issuing account
    18. absent: No sender/authority identified, only mentions the football team hashtag.
    19. present: Tags @GeorgiaTechFB as the account communicating the update.
    20. present: References '@GeorgiaTechFB', implying the team/athletics as sender.
    21. present: References '@GeorgiaTechFB' as the issuing account.
    22. present: References '@GeorgiaTechFB' as the issuing account.
    23. present: References '@GeorgiaTechFB' tagging the team's account.
    24. present: References '@GeorgiaTechFB' as the issuing account.
    25. present: References '@GeorgiaTechFB' as the issuing account.
  • Hazardpresent25/25

    Final assessment

    Unanimous: the message names 'potential severe weather in the area' as the hazard prompting the hold.

    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: States 'potential severe weather in the area'.
    2. present: States "potential severe weather in the area".
    3. present: 'potential severe weather in the area'.
    4. present: 'potential severe weather in the area' names the hazard.
    5. present: References 'potential severe weather'.
    6. present: Names "potential severe weather."
    7. present: Names 'potential severe weather'.
    8. present: States "potential severe weather".
    9. present: 'potential severe weather' names the hazard
    10. present: States 'potential severe weather in the area'.
    11. present: States 'potential severe weather'.
    12. present: 'potential severe weather' named.
    13. present: 'potential severe weather' names hazard.
    14. present: 'potential severe weather' specifically named.
    15. present: States 'potential severe weather in the area'.
    16. present: References 'potential severe weather in the area'.
    17. present: States 'potential severe weather in the area'
    18. present: 'potential severe weather in the area' names the hazard.
    19. present: References "potential severe weather" as the reason for the hold.
    20. present: States 'potential severe weather' specifically.
    21. present: States 'potential severe weather in the area'.
    22. present: 'Potential severe weather' named as hazard.
    23. present: Names 'potential severe weather'.
    24. present: States 'potential severe weather in the area'.
    25. present: Names 'potential severe weather'.
  • Locationabsent12/25

    Final assessment

    A narrow majority (13 of 25) found no specific location beyond the general game context; a close minority counted 'in the area' as sufficient, but the majority view is that no real place 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. present: Names the area of the game, implying stadium location.
    2. present: States "in the area" of the game/stadium.
    3. absent: No specific location beyond the game context.
    4. absent: No specific location beyond the game/stadium context, not stated explicitly.
    5. absent: No specific location given beyond the game.
    6. present: Implies the stadium/game location for Georgia Tech vs South Carolina State.
    7. absent: No specific location, only general game venue context.
    8. present: Implies stadium location via kickoff/game context.
    9. present: 'in the area' referring to the game location
    10. present: Says 'in the area' referencing the game venue.
    11. absent: No specific location, only general game context.
    12. absent: No specific location beyond the game context.
    13. absent: No specific location, only the game context.
    14. absent: No specific location given beyond the game context.
    15. present: Implies the stadium/game location via 'the area'.
    16. present: States 'in the area' referring to the game venue.
    17. present: References 'the area' at the game location
    18. present: 'in the area' referring to the game venue.
    19. absent: No specific place beyond the game context is mentioned.
    20. absent: No specific location given beyond the game context.
    21. present: References game location implicitly via team names; 'in the area'.
    22. absent: No specific location beyond the game venue implied.
    23. absent: No specific location, only game venue implied.
    24. present: References 'in the area' of the game.
    25. absent: No specific location beyond the game venue implied.
  • Guidanceabsent12/25

    Final assessment

    A narrow majority (13 of 25) found no protective action instructed, just a request to stay tuned; a close minority counted 'please stay tune for updates' as an instruction, but the majority sees it as informational rather than protective.

    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: No protective action instructed, just a kickoff delay update.
    2. present: Implicitly instructs to "stay tune for updates" during the "pregame hold".
    3. absent: 'Please stay tune for updates' is not a protective action.
    4. present: 'Please stay tune for updates' instructs recipients to monitor.
    5. present: Instructs to 'stay tune for updates', implying a hold in place.
    6. absent: No protective action instructed, just stay tuned.
    7. absent: No protective action instructed, just informs of hold and kickoff delay.
    8. present: Instructs to "please stay tune for updates".
    9. absent: No protective action instructed, only informs of delay
    10. present: Instructs to 'stay tune for updates', an implicit monitoring instruction.
    11. absent: No protective action instructed, only informs of delay and to stay tuned.
    12. absent: No protective action instructed, just a hold notice.
    13. present: Instructs to 'stay tune for updates'.
    14. present: Instructs to 'stay tune for updates', a monitoring instruction.
    15. present: Instructs to 'stay tune for updates', a monitoring instruction.
    16. present: Instructs to 'stay tune for updates'.
    17. present: Instructs to 'stay tune for updates', implying a hold in place
    18. absent: No protective action instructed, just a hold/delay notice.
    19. absent: Only asks fans to "stay tune for updates", not a protective action.
    20. absent: No protective action instructed, just informs of a delay.
    21. present: Instructs to 'stay tune for updates' during the hold.
    22. absent: No protective instruction, just a hold and time update.
    23. absent: No protective action, just informs of kickoff delay.
    24. absent: No protective action instructed, only kickoff delay information.
    25. present: Instructs to 'stay tune for updates'.
  • Timepresent25/25

    Final assessment

    Unanimous: the message gives a specific new approximate kickoff time, 1:22 pm ET.

    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: Gives 'New approximate kickoff time...is 1:22 pm ET'.
    2. present: Gives "New approximate kickoff time... is 1:22 pm ET".
    3. present: 'New approximate kickoff time... is 1:22 pm ET'.
    4. present: 'New approximate kickoff time...1:22 pm ET' gives specific time.
    5. present: Gives 'New approximate kickoff time...1:22 pm ET'.
    6. present: Gives "approximate kickoff time...1:22 pm ET."
    7. present: States 'New approximate kickoff time...1:22 pm ET'.
    8. present: Gives "approximate kickoff time... is 1:22 pm ET".
    9. present: 'New approximate kickoff time...is 1:22 pm ET' gives clock time
    10. present: Gives 'New approximate kickoff time... is 1:22 pm ET'.
    11. present: Gives 'New approximate kickoff time... 1:22 pm ET'.
    12. present: 'New approximate kickoff time... 1:22 pm ET' given.
    13. present: 'New approximate kickoff time...1:22 pm ET'.
    14. present: 'New approximate kickoff time...1:22 pm ET' given.
    15. present: Gives 'New approximate kickoff time... 1:22 pm ET'.
    16. present: Gives 'new approximate kickoff time...1:22 pm ET'.
    17. present: Gives 'New approximate kickoff time... 1:22 pm ET'
    18. present: 'New approximate kickoff time... is 1:22 pm ET'.
    19. present: States "New approximate kickoff time...is 1:22 pm ET".
    20. present: 'New approximate kickoff time...is 1:22 pm ET' gives specific time.
    21. present: Gives 'New approximate kickoff time... 1:22 pm ET'.
    22. present: 'New approximate kickoff time...1:22 pm ET' given.
    23. present: States 'New approximate kickoff time...is 1:22 pm ET'.
    24. present: Gives 'New approximate kickoff time... 1:22 pm ET'.
    25. present: Gives 'new approximate kickoff time... 1:22 pm ET'.
  • Impactabsent0/25

    Final assessment

    Unanimous: no consequence or severity of the weather itself is stated.

    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 stated consequence or severity of the weather.
    2. absent: No stated consequence or severity of the weather described.
    3. absent: No stated consequence of the severe weather.
    4. absent: No stated potential harm or severity of the weather.
    5. absent: No stated potential harm from the severe weather.
    6. absent: No stated harm severity of the weather.
    7. absent: No stated consequence or severity.
    8. absent: No stated potential harm or severity of the weather.
    9. absent: No stated consequence of the weather
    10. absent: No stated harm or severity from the weather.
    11. absent: No stated consequence or severity of the weather.
    12. absent: No statement of potential harm or severity.
    13. absent: No stated consequence or severity.
    14. absent: No stated consequence or severity conveyed.
    15. absent: No statement of potential harm from the severe weather.
    16. absent: No stated harm or severity of the weather.
    17. absent: No stated potential harm from the severe weather
    18. absent: No statement of potential harm.
    19. absent: No stated consequence or severity of the weather.
    20. absent: No stated consequence or severity of the weather.
    21. absent: No stated potential harm or severity.
    22. absent: No stated severity or potential harm.
    23. absent: No stated potential harm of the weather.
    24. absent: No stated potential harm or severity.
    25. absent: No stated harm or severity from the weather.

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

About this analysis
Context

Background

Georgia Tech's 2023 home opener against South Carolina State was set for a 1 PM EDT kickoff at Bobby Dodd Stadium in midtown Atlanta, but a series of Atlanta-area thunderstorm cells repeatedly blocked play. The game experienced two separate lightning holds before kickoff could occur, with fans instructed to shelter in the concourses throughout. After the first delay, teams came onto the field at approximately 1:42 PM EDT for warm-ups but lightning was detected again, sending everyone back indoors and resetting the 30-minute clock. Georgia Tech explicitly communicated that fans who left to wait in their cars would be re-admitted with their tickets, a fan-friendly policy that acknowledged the extended and uncertain timeline. The game ultimately began at 3:23 PM EDT, more than two hours and twenty minutes late. Georgia Tech won 48-13.
Analysis

Key Findings

Two separate lightning holds before kickoff pushed the game's start more than two hours past the scheduled 1 PM EDT time
Georgia Tech allowed fans who sheltered in their cars to re-enter with their tickets, a documented fan-policy decision made during the extended delay
Bobby Dodd Stadium concourses served as the primary in-stadium shelter; teams returned to locker rooms for both delays
The back-to-back delay pattern reflects the multi-cell nature of major Atlanta metro summer thunderstorm systems
Outcome
Georgia Tech defeated South Carolina State 48-13; kickoff finally occurred at approximately 3:23 PM EDT after a 2-hour 23-minute delay.
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. News
  2. News
  3. News
  4. News
  5. News
  6. Social
  7. Social
  8. Social
  9. Social
  10. Social
  11. Official
  12. Official
Cite this case

Campus Alert Archive. "Georgia Institute of Technology: Back-to-back lightning holds delay a football game; fans sheltered in stadium concourses." Incident of September 9, 2023. Added June 2026; last updated July 2026. https://campusalertarchive.com/case/georgia-tech-bobby-dodd-sc-state-lightning-delay-2023-09-09/

Download case JSON

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

Tags
severe-stormlightningweather-delaystadiumgeorgia-techbobby-dodd-stadiumgame-dayfootballpre-game-delay
Added June 2026Updated July 2026Via ingestion