Describe your tanks and inspection procedure. Makeform builds a tank inspection form with asset details, condition checks, defect evidence, follow-up, and sign-off.
Route inspection records to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your procedure, and review the generated structure before use.
Audience
Facilities inspectors checking exterior tank condition
Format
Routine checklist with defect photos and action routing
Prompt size
397 chars
Example form structure
Routine checklist with defect photos and action routing
Tank ID, location, service, and operating status
Exterior component condition
Where is the defect located?
Upload overview and close-up photos
Overall disposition and inspector sign-off
Suggested routing tags
No defect observed
Monitor condition
Action required
Require tank ID, location, and service before inspectors record observations.
Step 1
Identify
tank, service, location, and inspection scope
Step 2
Inspect
component results, readings, and observations
Step 3
Document
defect location, notes, and photos
Step 4
Route
immediate response, owner, and follow-up date
Inspection records that stay usable
Connect each observation to one asset, component, and next step so exceptions stay reviewable.
Use consistent results for each component, including not applicable.
Capture component, location, observation, severity, and photos.
Record controls, notification, owner, target date, and maintenance reference.
Adapt the inspection scope
Replace generic checkpoints with your procedure's terminology and decision rules.
Check identity, leakage, corrosion, fittings, labels, access, and surroundings.
Document walls, floor, drains, liquid, debris, and exceptions.
Add readings, units, locations, and instrument identifiers.
Summarize disposition, exceptions, ownership, and review.
Build the workflow
Describe the asset and logic, then review the form against your procedure.
Name the tank, service, frequency, inspector, checkpoints, and results.
Require critical items and reveal defect fields only for exceptions.
Test normal and defect results, including IDs, units, photos, and ownership.
Share the form and configure destinations for review and follow-up.
Choose the right record
A structured form supports repeatable rounds, measurements, and exception notes.
Field guide
Align these six sections with your tank design and site procedure.
Inspection context
Identify the event and distinguish a routine round from a follow-up or detailed visit.
Tank identity
Use the displayed asset identifier plus location, service, construction, and status.
Component condition
Give each component a result. Keep not inspected and not applicable separate from a pass.
Defect evidence
For each exception, record location and orientation so photos remain useful to reviewers.
Response and ownership
Use your approved priority definitions and keep decisions within the inspector's role.
Completion and review
Summarize component answers and identify inaccessible areas or unresolved defects before sign-off.
Related tools
Connect tank records with focused safety and maintenance forms.
Create repeatable checks for pumps, machinery, and other site assets.
Open toolRecord workplace observations, exceptions, and follow-up assignments.
Open toolInspect storage areas, access routes, equipment zones, and housekeeping.
Open toolCapture asset condition, access observations, defects, and field photos.
Open toolDocument maintenance activity, parts, status, and the next service step.
Open toolSend inspection findings into a focused repair or assessment request.
Open toolFAQ
Answers for teams creating a repeatable inspection record.
It identifies a tank, records defined component checks, documents conditions or measurements, and assigns defect follow-up. Match its scope to the tank, inspection type, inspector role, and site procedure.
Include date, inspector, tank ID, location, service, status, and applicable component results. Add defect location, description, photos, readings with units, immediate response, action owner, due date, overall result, and sign-off.
For each exception, capture component, location, condition, reading with units, severity under your definitions, photos, and immediate response. Add notification, owner, target date, and maintenance reference.
Yes. Use conditional logic to reveal defect description, location, severity, photo, and follow-up fields after an exception. Keep not inspected separate from acceptable.
Add uploads for an identifying overview, affected component, and close-up. Ask for a location reference, and follow site photography rules and device permissions.
Keep shared identity and action fields, then branch checks by tank type, service, material, or scope. Use only the components and measurement locations defined for that inspection.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge. Review and tailor the form before use.
Not automatically. Use it only for the assigned inspection scope. It can route observations for engineering assessment, testing, or a specialist report without presenting a routine checklist as that evaluation.
Make every tank round easier to review.
