Describe the property, roofing system, and inspection workflow you use. Makeform turns that brief into an editable roof inspection form with section-by-section condition fields, defect locations, measurements, photo uploads, urgency ratings, and clear next actions for the office and property owner.
Route inspection records to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a complete starting brief, adjust it to your inspection practice, or send it to the Makeform builder. The structures shown are examples for planning your form.
Prompt ready4 formats
Audience
Roofing contractors inspecting asphalt-shingle homes
Format
Mobile checklist with slope-specific photos
Prompt size
532 chars
Brief qualitySends to builder
Example form structure
Mobile checklist with slope-specific photos
Prompt exampleEditable in builder
Property, customer, inspector, and inspection date
Short answerFirst ask
2
Roof age, pitch, stories, and access method
Dropdown
3
Condition by roof face and component
Multiple choice
4
Photos of each defect and overview
File upload
5
Recommended action and urgency
Long answer
Suggested routing tags
Suggested
No action
Repair estimate
Urgent follow-up
Ask inspectors to pair every defect photo with a roof area, component, severity, and recommended action. A folder of unlabeled images is hard to turn into an estimate or follow-up visit.
Step 1
Identify
property, roof system, area, weather, and access
Step 2
Inspect
surfaces, edges, penetrations, drainage, and interiors
Step 3
Document
location, dimensions, severity, notes, and paired photos
Step 4
Act
priority, recommendation, assignee, and follow-up date
Better field records
Turn a roof walk into an actionable record.
A useful inspection does more than check boxes. It connects each observation to an exact area, a consistent condition scale, visual evidence, and the next decision someone needs to make.
Follow the same inspection path
Organize the form from site details and access through roof surfaces, flashings, penetrations, drainage, edges, and interior indicators. Crews get a repeatable sequence without forcing every roof into identical observations.
Tie defects to roof areas
Use named sections, slopes, elevations, or grid zones before asking what was found. Location fields prevent a note such as open seam from becoming a second search when the repair crew returns.
Pair context with close-ups
Request an overview image that establishes location and a close-up that shows the condition. Add captions for orientation, component, dimensions, and direction so the office can interpret each upload.
Adapt to the inspection
Different roofs need different branches.
Start with property and access details, then reveal questions that match the roof material, inspection purpose, and conditions found onsite.
Material-specific questions
Show shingle questions for tabs and granules, membrane questions for seams and blisters, metal questions for fasteners and corrosion, or tile questions for cracked and displaced units.
Access and stop-work decisions
Record weather, access method, visible hazards, and whether the inspector continued from the roof, ladder, drone, or ground. If access is declined, ask for the reason and the safer follow-up needed.
Findings that create work
Branch from each failed item to location, measurement, photo, severity, temporary action, recommended scope, and owner. Normal items stay compact while real defects receive full detail.
Handoffs the office can sort
Use consistent urgency and disposition choices such as monitor, maintain, estimate repair, or schedule a closer review. Notifications can bring time-sensitive records to the appropriate inbox quickly.
Build your workflow
From inspection brief to a form crews can use.
Describe how your team inspects, refine the generated sections, test the path on a phone, and route the completed record to the people responsible for the next action.
Tell the builder whether this is a sales inspection, routine maintenance visit, leak investigation, storm review, or completion check. Name common roof systems, service areas, and the decisions the submission should support.
02
Edit fields and condition logic
Add your roof-area labels, component list, rating scale, required images, and internal terminology. Use conditional questions so an observed issue opens fields for location, size, urgency, explanation, and action.
03
Test it like an inspector
Open the form on the device crews carry. Walk through safe access, a normal component, multiple defects, several image uploads, a paused visit, and final recommendations before sharing the live link.
04
Route and review submissions
Send records to the office workflow you already use. Sort by property, system, finding, severity, and recommended action, then confirm that repairs, estimates, monitoring items, and reinspections receive owners and dates.
Choose a capture method
Why a generated form works better than scattered field notes.
Paper checklists and generic documents can capture observations, but they often separate the condition, location, image, and next action. A purpose-built online form keeps those details together.
Approach
What the inspector records
What happens after the visit
ApproachPaper checklist and camera roll
What the inspector recordsChecks are on paper while photos remain on the phone, often without matching labels.
What happens after the visitOffice staff rename files, interpret handwriting, and ask which slope appears in each image.
ApproachGeneric document
What the inspector recordsThe inspector types a narrative and manually places images into a file after the visit.
What happens after the visitThe result may read well, but consistent ratings, filtering, assignment, and repeat inspections take extra setup.
Approach
Generated online roof inspection form
What the inspector recordsStructured roof areas, component ratings, defect details, measurements, and uploads are captured in one flow.
What happens after the visitEach submission arrives with consistent fields that the office can review, sort, route, and use to plan follow-up.
Field guide
What a practical roof inspection form should include.
Use these six groups as a starting architecture. Adjust component names, rating choices, and required evidence to match the roofs you inspect and the scope of each visit.
Site context
Identify the property and inspection scope.
Begin with enough context to distinguish this visit from past and future work. Record who requested it, why the roof is being reviewed, what areas are in scope, and any known history without treating owner comments as inspector findings.
Property address, building or unit, owner or contact, and access contact.
Inspector, company, inspection date and time, purpose, and requested scope.
Known roof age, installation or repair history, reported leak areas, and prior record reference.
Conditions & access
Record how the observation was made.
Weather and access affect what an inspector can see. Capture those limits at the start, make a clear continue-or-stop choice, and identify whether observations came from direct roof access, a ladder, the ground, interior spaces, or remote imagery.
Weather, surface condition, visibility, recent precipitation, and inspection start time.
Story count, pitch or slope, access point, ladder setup, and observation method.
Visible hazards, restricted areas, reason access was limited, and recommended return conditions.
Roof map
Give every finding an exact home.
Choose a location convention your crews will use consistently: compass-facing slopes, elevations, roof sections, or a numbered grid. Reuse that choice for observations, photos, repair notes, and return visits so another person can find the same spot.
Roof system and material, section name, slope or orientation, approximate area, and pitch.
Reference points such as ridge, eave, valley, drain, penetration, curb, or parapet.
Location description plus an overview photo that makes the defect position understandable.
Components
Inspect surfaces, details, and drainage consistently.
Use a component list that fits the roof rather than one universal checklist. Give each applicable item a condition choice and notes, then open detailed finding fields only when something requires monitoring or action.
Field material, seams or laps, ridges, valleys, edges, flashing, sealants, and fasteners.
Vents, pipes, skylights, chimneys, curbs, equipment supports, penetrations, and transitions.
Gutters, downspouts, drains, scuppers, ponding indicators, debris, and vegetation.
Findings & evidence
Describe defects so another person can act.
A finding should answer what, where, how much, and how urgent. Combine a controlled defect category with plain-language observations, dimensions, severity, and well-labeled images. Keep observed facts separate from suspected causes when the cause is uncertain.
Condition or severity scale with definitions your team applies the same way.
Overview and close-up photos, image captions, interior indicator photos, and supporting notes.
Actions & closure
End with a decision, owner, and date.
Summaries should distinguish routine upkeep, monitoring, repair estimating, urgent temporary action, and further evaluation. Assignment fields turn the inspection into a handoff, while completion evidence and reinspection status close the loop later.
Overall condition summary, recommended disposition, priority, and supporting explanation.
Practical answers for contractors, inspectors, and property teams replacing paper checklists and disconnected photo folders.
What should a roof inspection form include?
Include property and customer details, inspector and visit date, inspection purpose, weather, access method, roof system, material, age if known, pitch, and named roof areas. For each component, capture condition, observations, defect location, dimensions, severity, overview and close-up photos, and whether action is needed. Finish with an overall summary, recommendation, priority, assignee, target date, and any limits on what could be observed. The exact checklist should change for shingles, tile, metal, and low-slope membranes rather than asking irrelevant questions on every roof.
How do I organize photos in a roof inspection form?
Ask for photos inside the finding they support instead of placing one large upload field at the end. A strong photo set includes an overview that establishes the roof area, a medium view that identifies the component, and a close-up that shows the condition. Add a caption or adjacent fields for slope or zone, reference point, orientation, defect type, and dimensions. Consistent labels make the files usable by estimators, repair crews, property contacts, and anyone comparing the next visit.
Can the form change for shingles, metal, tile, and flat roofs?
Yes. Start with a roof-system or material selection, then use conditional sections for the relevant components. Asphalt-shingle paths can ask about missing tabs, lifting, granule loss, and exposed fasteners. Metal paths can cover panels, seams, coatings, corrosion, fasteners, and movement. Tile paths can cover cracked, slipped, or missing units and visible underlayment. Low-slope paths can cover membrane condition, seams, blisters, flashings, drains, scuppers, and ponding evidence. Shared questions for access, penetrations, edges, photos, and recommendations can remain outside those branches.
How should inspectors rate the severity of a finding?
Use a small scale with written definitions that reflect your workflow, and show those definitions beside the choices. For example, separate an item that is acceptable, one to monitor, one that needs maintenance or an estimate, and one that needs prompt escalation or temporary protection. Do not rely on color or a number alone. Require supporting notes and photos for elevated ratings, and keep severity distinct from the recommended action because a visible condition, its likely progression, access constraints, and the owner's schedule may affect the next step differently.
Can I use one form for an initial inspection and a reinspection?
Yes. Ask for the visit type near the beginning and show a reinspection branch when selected. That branch can request the original submission or work-order reference, prior finding identifier, prior photo, work reportedly completed, current status, and a matching current photo. Include choices for resolved, partially resolved, unchanged, not accessible, or additional issue observed. If your team needs to carry prior findings automatically into a new response, define that as a workflow requirement and test it before relying on the form for recurring maintenance.
How can a roof inspection submission become a repair task?
Give every actionable finding a disposition, priority, owner, and target date. The disposition might be clean during visit, monitor, prepare estimate, schedule repair, apply temporary protection, or request further evaluation. Route the submission to your chosen inbox or connected workflow, then use the property, roof area, finding type, and priority as sorting fields. Include a stable finding reference in the repair record so completion notes and after-work photos can be matched to the original evidence rather than living in a separate conversation.
Is this roof inspection form generator free?
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses with your roof inspection form. The paid tier removes the Makeform badge. You can start with one of the prompts above, revise the generated fields to match your inspection scope and terminology, and test the complete mobile path before sharing it with inspectors.
Can an online form replace an inspector's judgment or a full roof report?
The form structures observations and evidence; it does not decide what an inspector observed, determine a hidden cause, or define the scope of every roof review. The inspector still chooses safe access, records limitations, applies the company's condition definitions, and writes recommendations appropriate to the visit. Whether the submission also serves as your customer-facing report depends on the information, review, layout, and delivery process your business requires. Test the output with the people who inspect, estimate, repair, and communicate with property contacts.
Replace the clipboard and unlabeled camera roll.
Generate a roof inspection form built around how your crew works.
Unlimited freeRoof-area condition fieldsPhotos tied to findings
