Storm's AI Templates feature helps teams generate structured Dashpivot templates from natural language instructions instead of manually building them from scratch. This is ideal for quickly creating inspections, checklists, permits, reports, toolbox talks, and custom operational workflows while maintaining consistent structure across your workspace.
Prerequisites
Before you begin make sure you have the following:
Plan: Paid accounts only
Permission: Org Controller, Project Controller, or Team Controller.
Subscription: Dashpivot
Step-by-Step Instructions
Step 1: Open the Templates Area
Navigate to your Workspace and open either the Home Folder or a specific Team Folder.
Select Templates from the menu.
Click Add Template.
Step 2: Access Storm AI Templates
Select Build with AI to open the Storm AI Templates canvas.
Choose Generate.
Step 3: Define Your Template
Enter clear instructions describing the exact template you want to create — you can type your instructions, record a voice note, or combine both. Your voice note is transcribed and merged with any typed text before being passed to Storm.
Examples: “Create a daily site diary for civil construction projects”, “Build a toolbox talk template with attendance and action items”, or “Create an inspection checklist for scaffolding works”.
Tip: The more context you provide, the better Storm can structure the fields, sections, tables, and dropdowns.
Select a Document Type: Choose a specific category from the available document type generators (such as SWMS, AHA, ITP, PTW, QA Checklist, Safety Checklist, Toolbox Talk, Take 5, and more).
📓 Note: If your prompt doesn't match a supported generator type, Storm retries automatically and builds a template using its own built-in knowledge. You will always land in the editor with a template to work from.
Select a Location: Choose the relevant country or region. Storm uses this regional context to apply local terminology and structure workflows appropriately.
Step 4: Adjust Optional Preferences
You can customize how Storm structures your template by adjusting the following settings:
Checklist Handling: Choose Let Agent Decide, Yes/No Fields, or Table.
Page Orientation: Choose Portrait, Landscape, or Let AI decide.
Required Fields: Choose Important Fields Only, None, or All.
Template Type: Choose Timeline, Workflow, or Let AI decide.
Step 5: Build and Process
Click Build. Storm will begin generating your template in the background.
Processing Time: Generation may take several seconds to several minutes depending on the template complexity and prompt detail.
Background Multi-tasking: You do not need to wait on the screen. You can continue working elsewhere in Dashpivot while processing occurs. A new template will appear in your list showing a "processing" state until it is complete.
Completion State: When generation finishes, the card shows a green Complete badge and stays visible in the "Storm is building templates" section with a Review button — it won't clear until you've reviewed it. Clicking Review opens the template editor with the Build with Storm panel already active and ready for your next prompt.
Step 6: Review and Refine
Once processing finishes, clicking Review opens the template editor with the Build with Storm panel already active. The panel starts empty — it does not replay your generation chat history — so you can immediately continue refining your template using new prompts, or make manual adjustments, update workflows, modify layouts, add custom logic, or configure specific team permissions directly in the editor.
📓 Note:
Clicking Preview in Editor on the generation canvas also opens the template editor with the Build with Storm panel pre-loaded and ready for prompting.
Where Build with Storm is not available — for example, on a free trial or when working with Action Templates — clicking Review opens the regular field editor instead.
💡 Tips for Better Results
To get the most accurate structure from Storm on your first try, follow these prompt guidelines:
Provide highly clear, explicit instructions.
Include the wider workflow context.
Describe required sections and specific field types.
Mention where tables, dropdowns, or approval sign-offs are needed.
Specify the exact intended operational use case.
Select the correct country or region — Storm uses this to apply local terminology and relevant regulatory structure (e.g. SWMS in AU/NZ, RAMS in UK/IE, JSA in US/CA).
Use a voice note when your instructions are complex or lengthy — talking through what you need is often faster than typing it out. The same prompt-quality principles apply: be specific, name the document type, and include industry context.
Current Limitations
AI Templates currently does not fully support the automatic generation of:
Conditional logic rules
Highly complex custom layouts
Some generated templates may require manual refinement in the editor after Storm finishes the initial build. Additional capabilities may be introduced in future Storm releases.
If a prompt doesn't match a supported generator type, Storm retries and builds from its own built-in knowledge — so you will always land in the editor with something to refine.
Formula fields are supported for a range of document types. Storm can generate formula logic for common use cases — the table below shows what's currently covered by document type. Review and adjust formula logic in the template editor after generation.
Document Type | Formulas Covered |
Timesheet | TIMEDIF, overtime cap, weekly SUM, day-of-week via CHOOSE(WEEKDAY()), SUMIF cross-table totals |
Dayworks Sheet | Qty × Rate, 3-way labour cost, cross-table SUM, SUMIF by trade |
Diary | Cross-table SUM for labour/equipment/delivery totals |
Risk Assessment | IFS multiply (Mode A), cross-table IFS lookup (Mode B), risk level classification |
Method Statement | Same as Risk Assessment, plus step auto-numbering with ROW() |
Incident | Risk scoring, DATEDIF(date,TODAY()) for days since incident, corrective action % |
Checklist | COUNTIF pass/fail/NA counts, compliance %, any-fail-means-fail, AVERAGEIF excluding N/A |
Inspection Test Plan | Pass/fail %, multi-section cross-table COUNTIF, ROW() auto-numbering |
Shift Report | Cross-table SUM for labour/equipment/production |
NCR | Risk score C1*D1, days open via DATEDIF |
Variation | Line total Qty × Rate, days impact DATEDIF |
Defect | Days open via DATEDIF(date,TODAY()) |
Permit | Days remaining via IFERROR(DATEDIF(TODAY(),expiry),0) |
Machine Pre-Start | Days since service, defect count COUNTIF, next service via EDATE |
Crew Pre-Start | Attendee count via COUNTA |
Lot | AVERAGE, COUNTIF for pass count |
⚠️ Storm cannot handle complex formula expressions such as INDEX/MATCH and VLOOKUP. For these, build the formula manually in the template editor after generation.
Formula cells in Storm-built and Storm-edited tables update independently. Editing one formula cell via the Dashpivot formula bar only changes that cell — other formula cells in the same table are not affected.
📓 Note: Storm always produces a template for every generation request. If a prompt doesn't match a supported generator type, Storm retries and builds from its own built-in knowledge — so you will always land in the editor with something to refine.
Frequently Asked Questions (FAQ)
Can I edit generated templates?
Yes. All templates generated by Storm are fully editable using the standard Dashpivot template editor.
Can I generate multiple templates at once?
Yes. As soon as a template request begins processing, you are free to start another template generation request.
Does AI Templates use customer data to train AI models?
No. Storm does not use customer data or prompts submitted through AI Templates to train AI models.
Do generated templates require review?
Yes. Safety workflows, compliance processes, and approval-heavy forms should always be reviewed before operational use. All generated templates should be checked and refined as needed before deployment.