Lesson 13 of 19 · ~7 min
Run a WeatherCall decision
You'll learn: How to author a weather ruleset, watch it move clear → armed → triggered, log a hold-or-go decision (including "considered, not actioned"), dispatch operator comms, and seal a tamper-evident insurer binder.
WeatherCall is a per-organization capability. If you don't see the WeatherCall panel on your event or org profile, ask your admin to enable it for your org.
01 Author a ruleset
A WeatherCall ruleset is the set of thresholds that decide when a call is warranted — lightning distance, sustained wind and gusts, and the other weather signals SignalGuard already scores. You author it in one of two places:
- Per event — on the event page (
/event), in the WeatherCall section. Use this to tune the thresholds for a specific show or venue. - Org default — on your org profile (
/org-profile). Every event inherits this unless it has its own ruleset.
Rulesets are versioned: when you edit one, the prior version is kept, so a decision always records exactly which thresholds were in force when it was made.
02 Watch the live state — clear, armed, triggered
Once a ruleset is attached and the event is live, the WeatherCall status shows on the Live Monitor. It moves through three states as conditions evolve:
- Clear — nothing in the ruleset is close to firing.
- Armed — a decision window is open and conditions are approaching a threshold; this is your cue to stage the decision group.
- Triggered — a rule has fired. The panel shows exactly which rule and the reading behind it.
The state is driven by the same live weather signals as the brief, so it stays in step with what the map and Threats log show.
weathercall-states.png
03 Log the decision
When the group makes a call, log it from the WeatherCall panel. A decision records the action — hold, evacuate, cancel, or downgrade — a confidence level, and the rule that prompted it. Crucially, you can also log considered, not actioned: a record that the group saw the condition and deliberately chose not to act. That "we looked and decided to continue" entry is often the most important one to have on file afterward.
Decisions are append-only — you add new entries, you don't overwrite old ones — so the timeline is a faithful audit of what was known and decided, and when.
04 Dispatch operator comms
A decision usually needs to reach people. From the panel you can draft the operator communication tied to the decision and dispatch it, so the message and the call it belongs to are recorded together rather than living in a separate group chat. The dispatched comms become part of the same WeatherCall record.
05 Seal the insurer binder
After the event, seal the binder. It assembles the ruleset version that was in force, the live readings, every decision (including the "considered, not actioned" entries), and the dispatched comms into one tamper-evident record, and gives you a read-only shareable link for your broker or insurer. It's the artifact that answers "what did you know, and what did you do about it?" without you having to reconstruct the night from memory.
Tips
- Set an org default ruleset once so new events are covered automatically, then override per event only where the venue calls for it.
- Armed is the moment to pull the decision group together — don't wait for triggered.
- Log considered, not actioned every time you review and continue. An empty record isn't the same as a documented decision to proceed.
- The binder link is read-only and safe to share externally — it exposes the decision record, not your account.