Newark 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 Newark Campus - Severe Thunderstorm…", 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 Newark Campus - Severe Thunderstorm…", which marks the sender.
  2. present: The notice identifies who is speaking through "OSU Newark Campus - Severe Thunderstorm…".
  3. present: Source is present because "OSU Newark Campus - Severe Thunderstorm…" names the issuing campus or alert brand.
  4. present: A campus or alert signature ("OSU Newark Campus - Severe Thunderstorm…") supplies the authority line.
  5. present: Sender identity is clear from the wording "OSU Newark Campus - Severe Thunderstorm…".
  6. present: The alert tags an official issuer with "OSU Newark Campus - Severe Thunderstorm…".
  7. present: Who is sending this is stated through "OSU Newark Campus - Severe Thunderstorm…".
  8. present: Branded language "OSU Newark Campus - Severe Thunderstorm…" functions as the source element.
  9. present: Campus naming in "OSU Newark Campus - Severe Thunderstorm…" tells recipients the origin of the message.
  10. present: An official voice is established by "OSU Newark Campus - Severe Thunderstorm…".
  11. present: The opening or body includes "OSU Newark Campus - Severe Thunderstorm…" as institutional source.
  12. present: "OSU Newark Campus - Severe Thunderstorm…" is enough to code source present under the branding rule.
  13. present: Recipients can tell the sender from "OSU Newark Campus - Severe Thunderstorm…".
  14. present: Source scores present: "OSU Newark Campus - Severe Thunderstorm…" is an authority marker.
  15. present: The university or college is referenced as "OSU Newark Campus - Severe Thunderstorm…".
  16. present: Alert-system or school labeling ("OSU Newark Campus - Severe Thunderstorm…") covers source.
  17. present: Issuing body is identifiable from "OSU Newark Campus - Severe Thunderstorm…".
  18. present: "OSU Newark Campus - Severe Thunderstorm…" operates as a branded signature for source.
  19. present: The text attributes the message via "OSU Newark Campus - Severe Thunderstorm…".
  20. present: Source present: campus authority language "OSU Newark Campus - Severe Thunderstorm…".
  21. present: Readers see "OSU Newark Campus - Severe Thunderstorm…" and know which campus is speaking.
  22. present: Official sender cue "OSU Newark Campus - Severe Thunderstorm…" is explicit in the text.
  23. present: Source is coded yes based on "OSU Newark Campus - Severe Thunderstorm…".
  24. present: The phrase "OSU Newark Campus - Severe Thunderstorm…" identifies the responding institution.
  25. present: Authority is named through the fragment "OSU Newark Campus - Severe Thunderstorm…".
• 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 "Newark 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 "Newark Campus".
  2. present: Place is specified as "Newark Campus".
  3. present: Where is answered by "Newark Campus".
  4. present: "Newark Campus" functions as the location element.
  5. present: The alert situates the event with "Newark Campus".
  6. present: Geographic or campus place: "Newark Campus".
  7. present: L=1 because "Newark Campus" names where this applies.
  8. present: Recipients are told the place via "Newark Campus".
  9. present: Location present in the phrase "Newark Campus".
  10. present: A campus or building reference "Newark Campus" covers location.
  11. present: The where cue is "Newark Campus".
  12. present: "Newark Campus" identifies the affected area.
  13. present: Place naming succeeds with "Newark Campus".
  14. present: Location codes yes on "Newark Campus".
  15. present: Site detail appears as "Newark Campus".
  16. present: The message anchors place with "Newark Campus".
  17. present: "Newark Campus" is enough location under the rubric.
  18. present: Affected place language: "Newark Campus".
  19. present: L is present via "Newark Campus".
  20. present: Campus geography is marked by "Newark Campus".
  21. present: Where this matters is "Newark Campus".
  22. present: The text localizes to "Newark Campus".
  23. present: Location element met by "Newark Campus".
  24. present: Place is not left blank: "Newark Campus".
  25. present: Spatial reference "Newark 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 "2:37PM".

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

  Final assessment

  Majority 25/25 present. Impact is conveyed by "OSU Newark Campus - Severe Thunderstorm…".

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