Storm's AI Templates Generate feature produces more accurate, ready-to-deploy templates when given clear, specific prompts. The quality of your output depends largely on the quality of your input. This article covers how to write better prompts, how to use preferences effectively, and what the Generate feature currently cannot do.
Best Practices for Better Results
1. Be specific about the document type and context
Always name the document type and include industry or project context in your prompt. Vague prompts produce generic templates.
Instead of | Try |
"Create a safety form" | "Create a SWMS for steel erection on a commercial high-rise construction project" |
"Build a checklist" | "Build a pre-pour inspection checklist for a 200m³ suspended concrete slab including formwork, reinforcement, and embedments" |
"Make a toolbox talk" | "Create a toolbox talk template with attendance register, action items, and supervisor sign-off for a civil earthworks crew" |
2. Select the right generator type
Storm has 23 specialist generator types covering safety, quality, and environmental workflows. Selecting the correct generator — rather than using a generic prompt — produces templates structured to industry best practice for that document type.
For example, selecting the SWMS generator and describing your task produces a better result than typing "create a SWMS" into a generic prompt field.
See the full list in What Can You Generate With AI Templates?
3. Select the correct country or region
Storm uses your region selection to apply local terminology, regulatory references, and document structure. Getting this right avoids needing to manually rename fields after generation.
AU/NZ → SWMS, WHS references
UK/IE → RAMS, HSE references
US/CA → JHA/JSA, OSHA references
4. Describe required sections and field types explicitly
Storm can generate tables, dropdowns, counter fields, approval sign-offs, and linked lists — but only if you indicate they're needed. If your prompt doesn't mention them, Storm may omit them.
Useful things to include in your prompt:
Section headings you want included
Where tables or checklists are needed
Whether approval signatures or sign-offs are required
Any specific fields like date, time, location, or crew details
📓 Note: If your prompt contains a form or reference number pattern — such as "Form No.", "Permit No.", or a numbered prefix like "NCR-001" — Storm automatically detects this and generates a read-only Counter field with the correct prefix. You do not need to request a Counter field explicitly when the pattern is clear in your prompt.
5. Use preferences to guide structure
Before clicking Build, configure your preferences to match the output you want:
Checklist Handling — choose Yes/No Fields or Table if you know which format you need, rather than letting the agent decide
Template Type — choose Timeline or Workflow if your process has a defined structure; use Let AI Decide only if you're unsure
Page Orientation — choose Landscape for templates with wide tables (e.g. ITPs, SWMS hazard tables); Portrait for simpler forms
Required Fields — choose Important Fields Only for most use cases; use All only if every field must be completed before submission
6. Answer clarifying questions when prompted
When Storm hits something ambiguous in your prompt or preferences, it will ask you a quick question before continuing — rather than guessing and producing the wrong output. Answer each question to help Storm generate a more accurate result. You can set your preferences upfront to reduce the number of clarifying questions.
7. Use voice note input for more natural, detailed prompts
Both the Generate and File Import flows support voice note recording. This can be especially useful when you need to describe a complex structure quickly, or when typing out a detailed prompt would be slow or awkward. The same principles apply to spoken input as typed — be specific, name the document type, and include industry or project context. Storm combines voice and text, so you can speak part of your instructions and type the rest in the same session.
Storm combines your voice and text input, so you don't need to choose one exclusively. You can speak part of your instructions and type the rest in the same session.
8. Review and refine before deploying
Generated templates are a starting point, not a finished product. Always review before making a template live — particularly for:
Safety and compliance workflows
Approval-heavy processes
Templates with conditional logic or formulas (these must be added manually)
Current Limitations
Limitation | Workaround |
Conditional logic rules are not automatically generated | Add conditional logic manually in Dashpivot's template editor after generation |
Formulas are not automatically generated | Add formulas manually in the template editor after generation |
Highly complex multi-column layouts may not render as expected | Simplify the layout in the template editor after generation |
Visual engineering drawings (CAD layouts, drainage plans) produce text-extraction templates rather than actionable site records | Use the Import flow and add field types manually in the editor |
Generator type cannot be changed after generation begins | Start a new generation request with the correct generator selected |
Only 23 generator types are currently available | Use the Import flow to upload an existing document for document types not yet supported |
Frequently Asked Questions (FAQ)
Will Storm always produce a perfect template on the first try?
Not always. Complex workflows, unusual document structures, or vague prompts may require manual refinement. The more specific your prompt and preferences, the closer the output will be to ready-to-deploy.
Can I change preferences after generation starts?
No. Preferences are applied at the start of generation. If you want different settings, start a new generation request.
Does Storm generate Counter fields automatically?
Yes. When your prompt contains a form or reference number pattern — such as "Form No.", "Permit No.", or a numbered prefix like "PTW-001" or "TOOLBOX-001" — Storm automatically generates a read-only Counter field with the correct prefix. Records are then auto-numbered in sequence (e.g. PTW-1, PTW-2 or TOOLBOX-1, TOOLBOX-2). You do not need to request a Counter field explicitly when the pattern is clear in your prompt.
Why did Storm use the wrong generator structure?
If you enter a prompt that doesn't match the selected generator type — for example, describing a toolbox talk in an AHA generator — Storm will process the prompt using the selected generator's structure. Always match your prompt to the generator type for best results.
Can I queue multiple generation requests?
Yes. As soon as a generation request begins processing, you can start a new one immediately.
Do generated templates require review before use?
Yes. Safety workflows, compliance processes, and approval-heavy forms should always be reviewed and refined before operational deployment.