Describe your inspection workflow. Makeform creates a storm damage assessment form with property details, repeatable findings, severity ratings, photos, safety flags, and follow-up routing.
Route records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a workflow, adjust the prompt, or send it to the builder. These structures are starting points, not completed assessments.
Audience
Adjusters documenting residential property damage
Format
Mobile assessment with repeatable damage entries
Prompt size
328 chars
Example form structure
Mobile assessment with repeatable damage entries
Claim, property, and inspection details
Which area or building component is affected?
Damage type, severity, and measurements
Upload labeled overview and close-up photos
Are urgent safety controls needed?
Suggested routing tags
Urgent safety review
Needs estimate
Assessment complete
Identify each photo by building side, room, or asset so it matches the finding.
Step 1
Identify
event, property, assessor, and access status
Step 2
Inspect
areas, materials, hazards, and measurements
Step 3
Document
labeled photos, notes, and temporary actions
Step 4
Route
priority, owner, estimate, and follow-up date
Clearer field records
Keep location, severity, measurements, photos, and follow-up attached to every finding.
Record each slope, room, exterior side, utility, or asset as its own finding.
Show roof, water-entry, or utility questions only when relevant.
Route safety flags, estimate requests, and completed assessments separately.
Built around the assessor
Start with a field scenario, then apply your categories, ratings, assignments, and instructions.
Connect claim references, affected materials, measurements, photos, and next actions.
Capture trade-specific damage, access, quantities, protection, and estimate follow-up.
Screen parcel condition, hazards, access, infrastructure, and priority.
Document safe entry, operations, systems, vendors, and reinspection dates.
Assessment workflow
Describe the workflow, verify the structure, and publish a consistent path for each property.
Name storm types, properties, teams, ratings, required photos, and follow-up decisions.
Add components and priorities; require flags, images, and skipped-area explanations.
Repeat findings and upload test images to check the field experience.
Connect records to the spreadsheet, inbox, or notifications your team uses.
Field form vs generic notes
Combine sortable fields with room for inspector observations.
Field guide
Connect the event, location, condition, files, safety concerns, and next owner.
Event and assignment
Use the receiving team's identifiers. Separate the reported event date from the inspection date.
Property and scope
List structures, exterior faces, levels, rooms, and systems in scope. Record skipped areas and reasons.
Damage findings
Keep roof, interior, and system observations separate. Ask what the inspector observed, not for unsupported coverage decisions.
Photos and supporting files
Request overview, context, and close-up images with orientation and subject captions.
Safety and temporary action
Flag unstable materials, electrical exposure, gas odor, water, blocked access, or downed lines using your response procedure.
Disposition and handoff
Route by your priorities, while keeping unassigned coverage or authority decisions outside field observations.
Related tools
Build companion forms for inspections, incidents, repairs, approvals, reports, and claim intake.
Create a broader condition inspection for buildings, units, grounds, and systems.
Open toolCapture the initial event, people involved, immediate response, and supporting files.
Open toolTurn documented damage into a scoped request with location, urgency, and attachments.
Open toolRoute proposed work, cost details, reviewer notes, and approval status.
Open toolRecord completed work, materials, unresolved conditions, and the next service date.
Open toolCollect business claim intake details and supporting documents for internal processing.
Open toolFAQ
Practical answers for adjusters, contractors, facility teams, and municipal field coordinators.
It documents a property after a storm, connecting the address and scope to observed damage, measurements, photos, safety flags, actions, and follow-up. It records observations; it does not decide coverage, repair scope, or official building status.
Include assignment, property, storm, inspection, assessor, access, scope, repeatable findings, severity, measurements, labeled photos, safety concerns, temporary actions, skipped areas, follow-up owner, and completion confirmation.
Yes. Use a repeatable section for each slope, room, exterior side, utility, or asset. Each entry keeps its own condition, dimensions, rating, notes, and images under the same property record.
Yes. Conditional logic can require uploads and captions for selected severity or hazard choices. Request overview, context, and close-up images with location or orientation labels.
Give hazards a visible section tied to your stop-work and escalation instructions. Ask about safe entry, utilities, unstable materials, water, access, and restrictions, then route flags promptly.
A shared core can work, but tailor copies for each team. Adjusters need claim details, contractors need quantities and temporary protection, and municipalities need parcel references, rapid categories, infrastructure impact, and priority routing.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses with your form. The paid tier removes the Makeform badge; it does not unlock a usage allowance that the free tier withholds.
Route by safety and follow-up selections. Send hazards to the response queue and routine findings to estimating, repair planning, claim review, or reinspection. Keep observations, files, owner, status, and next date together.
Replace scattered storm notes with one field workflow.
