Storm's AI Templates Import feature converts your existing documents into structured, editable Dashpivot templates. The quality of the output depends largely on the quality of the source file and how you set up the import. This article covers how to prepare your files, configure your import, and what the Import feature currently cannot do.
📸 Images and Diagrams Are Preserved
Storm extracts images, diagrams, and photos from source documents and places them in the generated template at the correct position. Smart filtering automatically removes logos, signatures, and stamps — no manual re-upload required. This includes images inside table cells — they carry through correctly during import.
Best Practices for Better Results
1. Use digital source files where possible
Clean digital files produce the most accurate imports. In order of preference:
Exported PDFs from Word, Excel, or similar tools
Original .docx or .xlsx files
Clear, flat scans of paper documents (.png, .jpg, or .jpeg)
Avoid uploading files that are heavily annotated, watermarked, or exported from CAD or engineering drawing software — these produce text-extraction results rather than actionable form templates.
2. For scanned or photographed documents
If you're uploading a photo or scan of a paper form:
Shoot flat and square-on — avoid angled or shadowed shots
Use good, even lighting
Ensure text is legible and not obscured
Use the highest resolution available on your device
Angled or low-quality scans significantly reduce OCR accuracy and may result in missing fields or incorrect structure.
3. Group similar documents together in one batch
Preferences are applied to all files in the same import batch. For consistent results, import similar document types together:
Import checklists together in one batch
Import SWMS documents together in a separate batch
Import permits together in another batch
Mixing document types in the same batch may cause Storm to apply inconsistent structure or formatting across generated templates.
4. Configure preferences before you build
Set your preferences before clicking Build — they cannot be changed after processing starts. Match your preferences to the document type you're importing:
Page Orientation — choose Let Storm Decide (default) to let Storm determine the best fit; choose Landscape for documents with wide tables (e.g. ITPs — see ITP-Specific Import Behaviour below — SWMS hazard tables); or Portrait for standard forms
Checklist Handling — choose Let Storm Decide (default) to let Storm determine the format; or choose Yes/No Fields or Table if you know which format the source document uses
Required Fields — choose Important Fields Only (default) for most imports; All to mark every field required; or None to mark no fields required
📓 Note:
If no preferences have been previously configured for your workspace, Storm will surface the preferences prompt automatically before proceeding with the import — so your settings are always applied intentionally.
When importing an inspection document, Storm will prompt you to choose a template type explicitly — for example, Workflow or Inspection — rather than applying a default. Select the template type that matches your intended use before building.
5. Avoid long, complex multi-section documents in a single file
Very long documents (16+ pages) may produce incomplete or redundant output. Where possible, split large documents into logical sections before importing. For example, import the hazard table separately from the general information section.
📓 Note:
For Excel files, splitting by column count or row volume is not necessary — upload your full Excel file directly.
Section headings are reliably preserved with their corresponding sections during import, even in long or multi-section documents.
Long tables — including ITPs (see ITP-Specific Import Behaviour below) and checklists now import with all rows intact. You do not need to split documents based on table length.
6. Always review before deploying
Imported templates are a starting point, not a finished product. Always review in the template editor before making a template live — particularly for:
Safety and compliance workflows
Approval-heavy processes
Templates that require conditional logic or formulas
📓 Note: If your source document contains a form or reference number — such as "Permit No.", "Form No.", or a numbered prefix like "NCR-001" — Storm automatically generates a read-only Counter field with the correct prefix. You do not need to add a Counter field manually after import. For example, a permit to work document referencing "PTW-001" will produce a Counter that auto-numbers records as PTW-1, PTW-2, PTW-3, and so on.
7. Use the optional prompt to guide the output (single-file import only)
When importing a single file, you can add an optional prompt to give Storm specific instructions about how to structure the output. You can type the prompt, record a voice note, or combine both — Storm accepts spoken and written input in the same session. This is useful when you want to:
Exclude pages or sections that aren't needed in the template
Change how a section is formatted (e.g. as a table rather than a list)
Emphasise specific parts of the document or reduce focus on others
What works well:
Keep the prompt focused and specific — reference sections or page numbers from the source file
Give one or two clear structural instructions rather than a lengthy description
Use direct language that describes the output format you want
The same principles apply to voice input: speak clearly and be specific — vague spoken instructions produce the same generic results as vague typed prompts
Example prompts:
"Omit page 3"
"Make section 2 a table"
"Only include the hazard register section"
"Convert the checklist items in section 4 to Yes/No fields"
📓 Note: The optional prompt — whether typed, spoken, or both — is only available for single-file import. It is not supported when importing multiple files in a bulk batch.
8. For Excel (XLSX) files: column widths and date types are preserved
When importing an XLSX file, Storm reads column width proportions from the source spreadsheet and applies them to the generated Dashpivot table — so the imported layout reflects the relative column sizing of the original. Cells formatted as dates in Excel are also detected and mapped to the Dashpivot date column type automatically, so you do not need to manually change column types after import.
📓 Note: This applies to standard date-formatted cells. If a cell contains both a date and a time component, it will be mapped to the timezone-aware date-time column type instead.
ITP-Specific Import Behaviour 🆕
When Storm detects that your source document is an Inspection Test Plan (ITP), it applies a set of additional rules to ensure the imported template accurately reflects the ITP’s structure and field types. These rules apply automatically — you do not need to configure them manually.
📓 Note: For best results when importing ITPs, select Landscape page orientation in your import preferences before clicking Build, as ITP documents typically contain wide tables. See step 4 above for details.
Control-point codes
If a control-point code cell (e.g. HP, WP, RP) is filled in the source document, Storm copies the code exactly into the template. If a control-point code cell is blank, Storm generates a dropdown field in its place so you can select the appropriate code when completing a record.Document number field
If the document number field is blank in the source document, Storm generates a Counter field so records are auto-numbered in sequence. If the document number field is already filled, Storm uses that value as the template code.Section structure
Storm only generates structure that is present in the source document. Page breaks and sections that do not contain real ITP content — such as sign-off blocks, NCR sections, and comment areas — are not included in the generated template.Evidence column
If a cell in the evidence column contains the text “To be attached”, Storm maps that cell to an attachment column type in the generated template, so users can upload supporting files directly against that inspection point.
Current Limitations
Limitation | Workaround |
Formulas are not automatically generated | Add formulas manually in the template editor after import, or use Build with Storm to add them conversationally |
Complex multi-column layouts may not render correctly | Refine the layout manually in the template editor after import |
Visual engineering drawings (CAD layouts, drainage plans) produce text-extraction shells rather than actionable site records | Open in the template editor and manually add the appropriate field types (e.g. inspection checkboxes, completion sign-offs) |
Password-protected or encrypted files are not supported | Remove encryption before uploading and re-export the file |
Maximum file size is 100MB per file | Split large files into smaller sections before importing |
Maximum 10 files per batch | Run multiple import batches for larger document sets |
Long Word documents (16+ pages) may produce incomplete output | Split the document into logical sections and import separately |
Excel formulas may not be detected during import | Add Excel formulas manually in the template editor after import. |
Image import in template editor | Adding or editing images directly in the Storm template editor is not yet supported. Use the Import flow to bring images into a template from a source document. |
Frequently Asked Questions (FAQ)
Will my imported template perfectly match the original document?
Not always. Storm preserves structure, layout, headings, field groupings, tables — including all rows and images in table cells — workflow logic, and images, diagrams, and photos from the source document.
Can I change preferences after import starts?
No. Preferences are applied at the start of processing. If you want different settings, start a new import with the correct preferences selected.
Can I import multiple documents at once?
Yes. You can import up to 10 files in a single batch. For best results, group similar document types together.
What file types are supported?
.pdf, .docx, .xlsx, .csv, .png, .jpg, and .jpeg. Password-protected or encrypted files are not supported.
Does Storm apply special rules when it detects an ITP document?
Yes. When Storm detects an ITP (Inspection Test Plan), it automatically applies ITP-specific rules for control-point codes, document number fields, section structure, and evidence columns. See the ITP-Specific Import Behaviour section above for full details.
Do imported templates require review before use?
Yes. Always review imported templates before operational use — particularly safety, compliance, and approval-heavy workflows.
Is my uploaded data used to train AI models?
No. Storm does not use customer data or uploaded documents to train AI models.
Will Storm generate a Counter field from my imported document?
Yes. If your document contains a form or reference number pattern — such as "Permit No.", "Form No.", or a numbered prefix like "NCR-001" or "PTW-001" — Storm automatically detects the prefix and generates a read-only Counter field. Records are then auto-numbered in sequence (e.g. PTW-1, PTW-2 or NCR-1, NCR-2). You do not need to add a Counter field manually after import. The generated Counter field is identical to one added manually in the Dashpivot template editor.
Will my images, diagrams, and photos be imported?
Yes. Storm extracts images, diagrams, and photos from source documents and places them at the correct position in the generated template. Logos, signatures, and stamps are filtered out automatically — no manual re-upload is required.
Can I use a prompt during import?
Yes — but only when importing a single file. When you upload one file, you can add an optional prompt to guide how Storm structures the output. For example, you can tell Storm to omit certain pages, reformat a section as a table, or focus on a specific part of the document.
👉 The optional prompt is not available for bulk import. If you are importing multiple files at once, Storm will process each file without a prompt using your selected preferences.