Strong winds with PSPS risk and avoid-campus-if-possible guidance
AI-generated · every claim is source-linkedCU Boulder @cuboulderalerts advised strong winds with Xcel PSPS earlier under Red Flag conditions, no sustained campus outages, and avoid campus if possible.
- Alerts
- 1
- Response
- —
- Killed
- —
- Injured
- —
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.
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.
CU Advisory: Strong winds continue in Boulder this evening. No sustained outages have been reported on the CU Boulder campus. Xcel implemented a PSPS earlier due to Red Flag conditions. Outages remain possible overnight. Avoid campus if possible. Updates: https://alerts.colorado.edu/
Sourcepresent25/25
Final assessment
Majority 25/25 present. Institutional branding appears via "CU Advisory: Strong winds continue in B…", which marks the 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
- present: Institutional branding appears via "CU Advisory: Strong winds continue in B…", which marks the sender.
- present: The notice identifies who is speaking through "CU Advisory: Strong winds continue in B…".
- present: Source is present because "CU Advisory: Strong winds continue in B…" names the issuing campus or alert brand.
- present: A campus or alert signature ("CU Advisory: Strong winds continue in B…") supplies the authority line.
- present: Sender identity is clear from the wording "CU Advisory: Strong winds continue in B…".
- present: The alert tags an official issuer with "CU Advisory: Strong winds continue in B…".
- present: Who is sending this is stated through "CU Advisory: Strong winds continue in B…".
- present: Branded language "CU Advisory: Strong winds continue in B…" functions as the source element.
- present: Campus naming in "CU Advisory: Strong winds continue in B…" tells recipients the origin of the message.
- present: An official voice is established by "CU Advisory: Strong winds continue in B…".
- present: The opening or body includes "CU Advisory: Strong winds continue in B…" as institutional source.
- present: "CU Advisory: Strong winds continue in B…" is enough to code source present under the branding rule.
- present: Recipients can tell the sender from "CU Advisory: Strong winds continue in B…".
- present: Source scores present: "CU Advisory: Strong winds continue in B…" is an authority marker.
- present: The university or college is referenced as "CU Advisory: Strong winds continue in B…".
- present: Alert-system or school labeling ("CU Advisory: Strong winds continue in B…") covers source.
- present: Issuing body is identifiable from "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" operates as a branded signature for source.
- present: The text attributes the message via "CU Advisory: Strong winds continue in B…".
- present: Source present: campus authority language "CU Advisory: Strong winds continue in B…".
- present: Readers see "CU Advisory: Strong winds continue in B…" and know which campus is speaking.
- present: Official sender cue "CU Advisory: Strong winds continue in B…" is explicit in the text.
- present: Source is coded yes based on "CU Advisory: Strong winds continue in B…".
- present: The phrase "CU Advisory: Strong winds continue in B…" identifies the responding institution.
- present: Authority is named through the fragment "CU Advisory: Strong winds continue in B…".
Hazardpresent25/25
Final assessment
Majority 25/25 present. Hazard is specific: the text names "CU Advisory: Strong winds continue in B…".
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
- present: Hazard is specific: the text names "CU Advisory: Strong winds continue in B…".
- present: A concrete threat appears as "CU Advisory: Strong winds continue in B…".
- present: The what of the emergency is "CU Advisory: Strong winds continue in B…", not a vague incident label.
- present: "CU Advisory: Strong winds continue in B…" satisfies hazard by naming the condition or threat.
- present: Readers learn the hazard type from "CU Advisory: Strong winds continue in B…".
- present: Hazard present via the explicit phrase "CU Advisory: Strong winds continue in B…".
- present: The threat is particularized as "CU Advisory: Strong winds continue in B…".
- present: Coding H=1 because "CU Advisory: Strong winds continue in B…" is a named hazard.
- present: Specific danger language: "CU Advisory: Strong winds continue in B…".
- present: The alert states the problem as "CU Advisory: Strong winds continue in B…".
- present: Hazard element met by "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" is more than a generic emergency word.
- present: Threat identity is clear from "CU Advisory: Strong winds continue in B…".
- present: The message pins the hazard to "CU Advisory: Strong winds continue in B…".
- present: Named condition "CU Advisory: Strong winds continue in B…" counts as hazard.
- present: H is present: "CU Advisory: Strong winds continue in B…" tells what is wrong.
- present: Concrete hazard wording includes "CU Advisory: Strong winds continue in B…".
- present: The incident type is given as "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" is the stated threat or weather/system hazard.
- present: Hazard codes yes on "CU Advisory: Strong winds continue in B…".
- present: Specifics beat generics here: "CU Advisory: Strong winds continue in B…".
- present: The text's hazard signal is "CU Advisory: Strong winds continue in B…".
- present: What happened is labeled "CU Advisory: Strong winds continue in B…".
- present: Hazard present with the phrase "CU Advisory: Strong winds continue in B…".
- present: Threat naming succeeds through "CU Advisory: Strong winds continue in B…".
Locationpresent25/25
Final assessment
Majority 25/25 present. Location is given through "CU Advisory: Strong winds continue in B…".
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
- present: Location is given through "CU Advisory: Strong winds continue in B…".
- present: Place is specified as "CU Advisory: Strong winds continue in B…".
- present: Where is answered by "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" functions as the location element.
- present: The alert situates the event with "CU Advisory: Strong winds continue in B…".
- present: Geographic or campus place: "CU Advisory: Strong winds continue in B…".
- present: L=1 because "CU Advisory: Strong winds continue in B…" names where this applies.
- present: Recipients are told the place via "CU Advisory: Strong winds continue in B…".
- present: Location present in the phrase "CU Advisory: Strong winds continue in B…".
- present: A campus or building reference "CU Advisory: Strong winds continue in B…" covers location.
- present: The where cue is "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" identifies the affected area.
- present: Place naming succeeds with "CU Advisory: Strong winds continue in B…".
- present: Location codes yes on "CU Advisory: Strong winds continue in B…".
- present: Site detail appears as "CU Advisory: Strong winds continue in B…".
- present: The message anchors place with "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" is enough location under the rubric.
- present: Affected place language: "CU Advisory: Strong winds continue in B…".
- present: L is present via "CU Advisory: Strong winds continue in B…".
- present: Campus geography is marked by "CU Advisory: Strong winds continue in B…".
- present: Where this matters is "CU Advisory: Strong winds continue in B…".
- present: The text localizes to "CU Advisory: Strong winds continue in B…".
- present: Location element met by "CU Advisory: Strong winds continue in B…".
- present: Place is not left blank: "CU Advisory: Strong winds continue in B…".
- present: Spatial reference "CU Advisory: Strong winds continue in B…" supports L=1.
Guidancepresent25/25
Final assessment
Majority 25/25 present. Guidance is the instruction "CU Advisory: Strong winds continue in B…".
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
- present: Guidance is the instruction "CU Advisory: Strong winds continue in B…".
- present: Protective action appears as "CU Advisory: Strong winds continue in B…".
- present: Recipients are told to act via "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" is a direct what-to-do line.
- present: G=1 because "CU Advisory: Strong winds continue in B…" instructs the audience.
- present: The alert directs action with "CU Advisory: Strong winds continue in B…".
- present: Guidance present: "CU Advisory: Strong winds continue in B…".
- present: A clear instruction is "CU Advisory: Strong winds continue in B…".
- present: What to do is stated as "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" counts as protective guidance.
- present: Action language "CU Advisory: Strong winds continue in B…" meets guidance.
- present: The message tells people "CU Advisory: Strong winds continue in B…".
- present: Guidance codes yes on "CU Advisory: Strong winds continue in B…".
- present: Operational direction: "CU Advisory: Strong winds continue in B…".
- present: Instructional content includes "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" is audience-facing guidance.
- present: G is present via the cue "CU Advisory: Strong winds continue in B…".
- present: Protective or operational order "CU Advisory: Strong winds continue in B…" is explicit.
- present: The text's guidance signal is "CU Advisory: Strong winds continue in B…".
- present: Recipients receive the directive "CU Advisory: Strong winds continue in B…".
- present: What-to-do element satisfied by "CU Advisory: Strong winds continue in B…".
- present: "CU Advisory: Strong winds continue in B…" tells the public how to respond or operate.
- present: Guidance met through "CU Advisory: Strong winds continue in B…".
- present: Action instruction present: "CU Advisory: Strong winds continue in B…".
- present: The alert's order to the audience is "CU Advisory: Strong winds continue in B…".
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
- absent: No clock time, date, or recency word such as now or today appears.
- absent: Time is absent from the alert text.
- absent: Nothing tells recipients when this applies.
- absent: T=0 because temporal cues are missing.
- absent: No day, hour, or immediate language is stated.
- absent: The message omits timing entirely.
- absent: Time element fails on this wording.
- absent: When is left unspecified.
- absent: No calendar or clock reference is present.
- absent: Temporal information cannot be found.
- absent: Without a time cue, T is zero.
- absent: The alert is silent on schedule.
- absent: Time codes absent here.
- absent: Recency language is missing.
- absent: T fails the when test.
- absent: No today/now/clock marker appears.
- absent: Timing is not established by the text.
- absent: Date and hour are both omitted.
- absent: Temporal element is not satisfied.
- absent: The body lacks any when cue.
- absent: Time not present under the rubric.
- absent: Schedule detail is blank.
- absent: No temporal anchor is given.
- absent: T is absent on timeless wording.
- 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
- absent: No consequence or severity language appears beyond naming a hazard.
- absent: Impact is absent: the text does not say what the threat could do.
- absent: Nothing states danger level, injuries, or disruptive effect.
- absent: I=0 because severity or harm is not conveyed.
- absent: Hazard may be named, but impact language is missing.
- absent: The alert omits consequence wording.
- absent: Impact fails the harm-or-severity test.
- absent: Readers are not told stakes or effects.
- absent: No life-safety or operational impact phrase is present.
- absent: Impact element codes absent.
- absent: Without consequence language, I is zero.
- absent: Severity is left unstated.
- absent: The text stops short of impact.
- absent: Harm potential is not described.
- absent: I fails on bare description without effects.
- absent: No dangerous/closed/injury-style impact cue appears.
- absent: Impact not established by the wording.
- absent: Consequence detail is missing.
- absent: The message lacks severity framing.
- absent: I is absent under the impact rule.
- absent: Stakes for people or property are not stated.
- absent: No disruption or harm language is included.
- absent: Impact cannot be coded present here.
- absent: Effect-on-campus language is omitted.
- absent: Severity/consequence element fails.
Coded by SuperGrok Heavy 4.5
Systematic AI judgments with visible reasoning, not human-validated codings.
Background
Key Findings
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.
- Social
Campus Alert Archive. "University of Colorado Boulder: Strong winds with PSPS risk and avoid-campus-if-possible guidance." Incident of March 14, 2026. Added August 2026. https://campusalertarchive.com/case/university-of-colorado-boulder-psps-winds-avoid-campus-2026-03-14/
Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.