Storm In-Editor can configure the formula layer for four non-timesheet template types — Scoring System, Risk Matrix, Automated Table Summary, and Hand Arm Vibration Record. When prompted correctly, Storm sets up the full calculation logic so you don't have to configure formulas manually.
For timesheet formula configuration (Daily, Single Entry Weekly, Multiple Entry Weekly, Time Sensitive), see How to Use Storm to Configure Timesheet Formulas in AI Templates.
📓 Note: Storm requires specific, detailed instructions to generate the correct formulas. It uses defaults when details are missing, but those defaults may not match your setup. Always specify your exact thresholds, labels, and option values so the output is right the first time.
How do I configure Scoring System formulas with Storm?
Storm configures pass/fail percentage formulas or weighted score totals across your inspection or checklist table. The most important thing to specify is the exact status option values used in your dropdown — Storm matches against these character-for-character.
What Storm needs to configure correctly:
The exact status option values in the dropdown (e.g. "Pass" / "Fail", "Y" / "N", "Compliant" / "Non-Compliant")
Whether the checklist is one table or split across multiple sections (each section with its own table)
Whether scoring is pass/fail percentage or weighted (each item worth a set number of points)
Whether to display the result as a raw number, percentage, or label (e.g. "Pass" / "Fail")
Example prompt (pass/fail percentage, single table):
"Add a scoring summary to this form. The checklist table has a Status column with options: Pass, Fail, N/A. Count the number of Pass and Fail responses (excluding N/A), calculate the compliance percentage (Pass ÷ total answered), and show an overall result label: 'Pass' if 80% or above, 'Fail' if below 80%."
Example prompt (weighted scoring):
"Add a weighted scoring summary to this form. The table has a Maximum Score column and an Achieved Score column. Calculate total achieved, total possible, and overall percentage. Show a result: 'Satisfactory' if 80% or above, 'Unsatisfactory' if below 80%."
Example prompt (multi-section):
"This form has three checklist tables: Site Access, PPE, and Housekeeping. Each has a Status column with options: Yes / No / N/A. Add a summary section that counts Yes and No across all three tables and shows a combined compliance percentage."
How do I configure Risk Matrix formulas with Storm?
Storm configures likelihood × consequence scoring with automatic risk level classification. It supports standard L×C matrices (score = likelihood number × consequence number) and custom-value matrices (where body cell values come from the source document).
What Storm needs to configure correctly:
The matrix size (3×3, 4×4, or 5×5) — Storm uses different band defaults per size
The exact likelihood option labels in the dropdown
The exact consequence option labels in the dropdown
The risk level bands — if your source document states them, share them; otherwise Storm will use defaults and flag them as assumptions
Whether both a pre-controls and post-controls risk score are needed
If you don't specify risk level bands, Storm uses these defaults for a 5×5 matrix: ≥15 = Extreme, ≥10 = High, ≥5 = Moderate, ≥3 = Low, ≥1 = Minimal — and will flag them as assumptions to confirm.
Example prompt:
"Configure the risk scoring formulas in this risk assessment. The table has a Likelihood dropdown (Highly Unlikely, Unlikely, Likely, Very Likely, Almost Certain) and a Consequence dropdown (Insignificant, Minor, Moderate, Critical, Severe). Add a Risk Score column (Likelihood × Consequence, scored 1–5 each) and a Risk Level column. Risk bands: 1–4 = Low, 5–9 = Medium, 10–16 = High, 17–25 = Critical. Apply these formulas to both the Inherent Risk section and the Residual Risk section."
How do I configure Automated Table Summary formulas with Storm?
Storm configures formulas that sum, count, or aggregate values across one or more data tables and display them in a separate summary section. Specify exactly which columns to summarise and which values to count.
What Storm needs to configure correctly:
Which columns to summarise and what operation to apply (sum, count, average, conditional count)
The exact option values to count conditionally (e.g. count rows where Status = "Open")
Whether the data comes from one table or multiple tables that need to be combined
Example prompt:
"Add a summary section to this form that reads from the defect log table. The table has Quantity, Unit Cost, and Status columns (Status options: Open / Closed / In Progress). Show: total quantity (sum), total cost (sum of Quantity × Unit Cost), count of Open items, and count of Closed items."
How do I configure Hand Arm Vibration (HAV) Record formulas with Storm?
Storm configures HAV exposure calculations. There are two paths depending on whether your organisation uses a published exposure points chart or calculates points directly.
Path 1 — Direct formula (no chart needed):
Storm calculates exposure points using the HSE formula: Exposure Points = 2 × magnitude² × hours. It then tracks a running daily total against the Exposure Action Value (EAV) and Exposure Limit Value (ELV).
Example prompt (direct formula):
"Configure the HAV exposure formulas in this table. The table has Tool Name, Vibration Magnitude (m/s², entered as a number), and Exposure Duration (hours, entered as a decimal). Add an Exposure Points column using: 2 × magnitude² × hours. Add a Running Daily Total column (cumulative sum of exposure points down the table). Add a Remaining Allowance column (400 minus running total). Flag rows where the running total reaches 400 points (EAV) or 1,600 points (ELV)."
Path 2 — Chart-based lookup (if you have a published exposure points chart):
If your organisation uses a published HAVS ready-reckoner chart, Storm can transcribe the chart into the template as a hidden reference table and use INDEX-MATCH to look up the correct exposure points for each tool. The dropdown options must match the chart's axis labels exactly.
Example prompt (chart-based):
"Configure the HAV lookup formulas in this table. Add a hidden reference table using our HAVS exposure points chart — rows are vibration magnitude values (2.5, 3, 4, 5, 6, 8, 10, 12 m/s²), columns are exposure durations (15 mins, 30 mins, 1 hour, 2 hours, 4 hours). The main table has Vibration Magnitude and Exposure Duration dropdowns that match the chart axis labels. Add an Exposure Points column that looks up the correct value from the chart, a Running Daily Total column (cumulative sum), and a Remaining Allowance column (400 minus running total)."
Tips for better formula results
Use the exact option values from your dropdowns — Storm matches status tokens like "Pass", "Y", or "Compliant" character-for-character. A mismatch returns zero without erroring.
Specify your thresholds — don't rely on defaults — Storm will use assumptions and flag them, but those defaults may not match your setup.
Reference your existing columns by name — say "the Status column" rather than "the dropdown." This avoids ambiguity when the table has multiple columns.
Iterate if needed — complex templates may need 2–3 prompt refinements. Describe what's wrong and what the correct output should look like.
Use a correction prefix if Storm gets it wrong — say "Correction — " or "Actually, " before your fix. This signals Storm to re-evaluate its last output before responding.
Notes
Formula support is only available in the template types listed in this article and the timesheet article linked above. Other template types do not support formula configuration through Storm.
Storm can add or modify formulas in an existing template — not just templates being built from scratch.
Storm uses default thresholds when details are missing and flags them as assumptions in its response. Always review the assumptions before saving.
For general instructions on using Storm In-Editor, see How to Edit Dashpivot Templates with Storm in the Template Editor.