Running a pre-start briefing means covering hazards, permits, SWMS, and crew sign-on — and then writing it all up afterwards. Storm lets you record the entire meeting as it happens and drafts the form for you.
Just hit record, run the briefing as normal, and Storm fills in the details — ready for you to review and submit.
What Storm Can Do With Pre-Start Briefings
Record the entire briefing as it happens and draft the form automatically — no write-up required after
Handle multiple speakers — Storm processes the full group recording and attributes content accordingly
Read attached SWMS and permit documents and use them as context when filling the form
Handle multilingual crews — Storm detects spoken language and outputs in the template's destination language
Reference a previous pre-start in the same folder to carry over recurring hazards or crew details
Before You Start
AI Form Fill must be enabled for your workspace.
For best results, record in a location with minimal background noise.
Make sure your SWMS and permit documents are accessible — you can attach them to the canvas for Storm to cross-reference.
How to Do It
📱 On Dashpivot Mobile
Open your pre-start briefing form in Dashpivot Mobile.
Tap the Storm button at the bottom of the form to open the AI Form Fill canvas.
Tap the microphone and record the entire briefing — Storm can handle multiple speakers.
Optionally, attach relevant SWMS or permit documents to the canvas using the paperclip icon so Storm can reference them when filling the form.
Tap the green arrow to submit.
Review the draft Storm generates, make any corrections, and submit as normal.
💻 On Dashpivot Web
Open your pre-start briefing form in Dashpivot.
In the Storm AI Form Fill canvas at the bottom of the form, record your briefing audio or type your notes.
Attach any relevant SWMS or permit documents using the paperclip icon.
Click Fill ↑.
Review the draft, make any corrections, and save or submit manually.
✏️ Good to Know
Storm handles multiple speakers. You don't need to pause or identify speakers — Storm processes the full group recording. For best results, avoid people talking over each other and identify speakers verbally where possible.
Attach permits and SWMS for better accuracy. Storm can read attached documents and use them as context when filling the form.
Reference a previous pre-start. Mention it in your directive — for example, "same hazards as yesterday's pre-start" — and Storm will draw on that form to help fill recurring fields. Both forms must be in the same Dashpivot folder.
Storm drafts, you decide. Storm never submits forms on your behalf — you always review before saving or submitting.
Action fields are not yet supported. Storm cannot create Dashpivot Actions automatically — these must be added manually after the briefing.
FAQs
Can Storm record a pre-start briefing with multiple people speaking?
Yes. Storm can process group recordings including meetings and briefings where multiple people are speaking. For best results, avoid people talking over each other and identify speakers verbally where possible.
Can I attach SWMS and permit documents for Storm to reference?
Yes. You can attach PDF, DOCX, XLSX, CSV, or EML files to the AI Form Fill canvas using the paperclip icon. Storm extracts text from the documents and uses them as context when filling the form.
Can Storm reference a previous pre-start briefing for recurring hazards or crew details?
Yes. Mention it in your directive — for example, "same hazards as yesterday's pre-start." Storm will draw on that form's content and cite which record it referenced. Both forms must be in the same Dashpivot folder.
Can Storm fill pre-start briefings for multilingual crews?
Yes. Storm detects the spoken language in voice input and outputs content in the template's destination language. Results may vary depending on recording quality and terminology.
Will Storm automatically create actions from the briefing?
Not yet. Storm can fill your pre-start briefing form from the recording, but creating Dashpivot Actions automatically is not yet available. Actions must be added manually.
Related articles: