Mansfield campus severe thunderstorm warning

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.

• Sourcepresent25/25

  Final assessment

  Majority 25/25 present. Institutional branding appears via "OSU Mansfield Campus - Severe Thunderst…", 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

  1. present: Institutional branding appears via "OSU Mansfield Campus - Severe Thunderst…", which marks the sender.
  2. present: The notice identifies who is speaking through "OSU Mansfield Campus - Severe Thunderst…".
  3. present: Source is present because "OSU Mansfield Campus - Severe Thunderst…" names the issuing campus or alert brand.
  4. present: A campus or alert signature ("OSU Mansfield Campus - Severe Thunderst…") supplies the authority line.
  5. present: Sender identity is clear from the wording "OSU Mansfield Campus - Severe Thunderst…".
  6. present: The alert tags an official issuer with "OSU Mansfield Campus - Severe Thunderst…".
  7. present: Who is sending this is stated through "OSU Mansfield Campus - Severe Thunderst…".
  8. present: Branded language "OSU Mansfield Campus - Severe Thunderst…" functions as the source element.
  9. present: Campus naming in "OSU Mansfield Campus - Severe Thunderst…" tells recipients the origin of the message.
  10. present: An official voice is established by "OSU Mansfield Campus - Severe Thunderst…".
  11. present: The opening or body includes "OSU Mansfield Campus - Severe Thunderst…" as institutional source.
  12. present: "OSU Mansfield Campus - Severe Thunderst…" is enough to code source present under the branding rule.
  13. present: Recipients can tell the sender from "OSU Mansfield Campus - Severe Thunderst…".
  14. present: Source scores present: "OSU Mansfield Campus - Severe Thunderst…" is an authority marker.
  15. present: The university or college is referenced as "OSU Mansfield Campus - Severe Thunderst…".
  16. present: Alert-system or school labeling ("OSU Mansfield Campus - Severe Thunderst…") covers source.
  17. present: Issuing body is identifiable from "OSU Mansfield Campus - Severe Thunderst…".
  18. present: "OSU Mansfield Campus - Severe Thunderst…" operates as a branded signature for source.
  19. present: The text attributes the message via "OSU Mansfield Campus - Severe Thunderst…".
  20. present: Source present: campus authority language "OSU Mansfield Campus - Severe Thunderst…".
  21. present: Readers see "OSU Mansfield Campus - Severe Thunderst…" and know which campus is speaking.
  22. present: Official sender cue "OSU Mansfield Campus - Severe Thunderst…" is explicit in the text.
  23. present: Source is coded yes based on "OSU Mansfield Campus - Severe Thunderst…".
  24. present: The phrase "OSU Mansfield Campus - Severe Thunderst…" identifies the responding institution.
  25. present: Authority is named through the fragment "OSU Mansfield Campus - Severe Thunderst…".
• Hazardpresent25/25

  Final assessment

  Majority 25/25 present. Hazard is specific: the text names "Severe Thunderstorm".

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

  Final assessment

  Majority 25/25 present. Location is given through "Mansfield Campus".

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

  Final assessment

  Majority 25/25 absent. No protective action or operational instruction is given to recipients.

  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 or operational instruction is given to recipients.
  2. absent: Guidance is absent: the text does not tell people what to do.
  3. absent: There is no shelter, avoid, evacuate, remote, or similar directive.
  4. absent: G=0 because audience-facing instructions are missing.
  5. absent: The message reports status without directing action.
  6. absent: No what-to-do language appears.
  7. absent: Guidance fails: pure information without orders.
  8. absent: Recipients are not told a protective step.
  9. absent: Instructional content is not present.
  10. absent: The alert omits guidance to the public.
  11. absent: Without a directive, G is zero.
  12. absent: No action line is addressed to readers.
  13. absent: Guidance element codes absent.
  14. absent: What-to-do is left unstated.
  15. absent: The text does not instruct avoidance, shelter, or closure behavior.
  16. absent: Audience guidance is missing from the body.
  17. absent: G fails the protective-action test.
  18. absent: No operational instruction is issued.
  19. absent: Readers get facts but not orders.
  20. absent: Guidance not established here.
  21. absent: Directive language is absent.
  22. absent: The message never tells recipients how to act.
  23. absent: No shelter/evacuate/remote/close instruction appears.
  24. absent: G is absent on non-directive wording.
  25. absent: Protective guidance cannot be coded present.
• Timepresent25/25

  Final assessment

  Majority 25/25 present. Time is marked by "11:03AM".

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

  Final assessment

  Majority 25/25 present. Impact is conveyed by "OSU Mansfield Campus - Severe Thunderst…".

  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. present: Impact is conveyed by "OSU Mansfield Campus - Severe Thunderst…".
  2. present: Consequence language appears as "OSU Mansfield Campus - Severe Thunderst…".
  3. present: Severity or harm is signaled by "OSU Mansfield Campus - Severe Thunderst…".
  4. present: "OSU Mansfield Campus - Severe Thunderst…" states what the hazard does to people or operations.
  5. present: I=1 because "OSU Mansfield Campus - Severe Thunderst…" implies real-world impact.
  6. present: The alert spells impact through "OSU Mansfield Campus - Severe Thunderst…".
  7. present: Impact present: "OSU Mansfield Campus - Severe Thunderst…".
  8. present: Operational or safety consequence "OSU Mansfield Campus - Severe Thunderst…" is explicit.
  9. present: What could happen is framed as "OSU Mansfield Campus - Severe Thunderst…".
  10. present: "OSU Mansfield Campus - Severe Thunderst…" counts as impact beyond bare hazard naming.
  11. present: Impact element met by "OSU Mansfield Campus - Severe Thunderst…".
  12. present: Severity cue "OSU Mansfield Campus - Severe Thunderst…" supports I=1.
  13. present: I codes yes on "OSU Mansfield Campus - Severe Thunderst…".
  14. present: The text links hazard to effect via "OSU Mansfield Campus - Severe Thunderst…".
  15. present: Consequence wording: "OSU Mansfield Campus - Severe Thunderst…".
  16. present: "OSU Mansfield Campus - Severe Thunderst…" shows stakes for the campus community.
  17. present: Impact is not left implicit only: "OSU Mansfield Campus - Severe Thunderst…".
  18. present: Harm or closure effect appears as "OSU Mansfield Campus - Severe Thunderst…".
  19. present: I is present via "OSU Mansfield Campus - Severe Thunderst…".
  20. present: The message states impact with "OSU Mansfield Campus - Severe Thunderst…".
  21. present: Real-world effect language "OSU Mansfield Campus - Severe Thunderst…" is included.
  22. present: Impact signal: "OSU Mansfield Campus - Severe Thunderst…".
  23. present: "OSU Mansfield Campus - Severe Thunderst…" communicates severity or disruption.
  24. present: Consequence is clear from "OSU Mansfield Campus - Severe Thunderst…".
  25. present: Impact present through the phrase "OSU Mansfield Campus - Severe Thunderst…".