Describe your system and inspection procedure. Makeform builds a septic inspection form for site details, tanks, measurements, drainfield observations, photos, and follow-up.
Route inspection records to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your procedure, or send it to the builder. The structure is an example, not an inspection result.
Audience
Septic contractors documenting residential systems
Format
Mobile checklist with measurements and photos
Prompt size
279 chars
Example form structure
Mobile checklist with measurements and photos
Property, inspector, and date
Tank access and condition
Liquid, sludge, and scum measurements
Distribution and drainfield
Photos and follow-up
Suggested routing tags
No immediate action
Service recommended
Further evaluation
Separate observed conditions, measurements, and recommended actions so findings remain distinct from follow-up notes.
Step 1
Identify
property, system record, reason, and inspector
Step 2
Observe
access, tanks, components, distribution, and field
Step 3
Document
measurements, conditions, limitations, and photos
Step 4
Route
findings, follow-up, reviewer, and service queue
Consistent field records
Follow the system from site records to disposal area. Structured fields reduce omissions while preserving room for unusual observations.
Order required sections by inspection sequence, with conditional questions for pumps, alarms, filters, and treatment units.
Number fields keep liquid, sludge, scum, counter, and other readings comparable.
Request labeled images beside each tank, distribution, or drainfield finding.
Adaptable inspection scope
Routine service, county review, property transfer, and treatment-system visits need different questions. Choose a workflow and edit its terms.
Capture access, levels, components, field observations, completed service, and next steps.
Organize parcel references, local checklist items, reviewer notes, and status.
Document records, methods, conditions, access limits, photos, and further evaluation.
Reveal pump, float, alarm, filter, and treatment questions only when applicable.
Build your field workflow
Describe the inspection path, review the fields, test conditional branches, and route follow-up records.
Name your system types, components, methods, readings, photos, result categories, and local terminology.
Use your component list and distinguish not present, inaccessible, uninspected, acceptable, and attention needed.
Preview on a phone, test each configuration, and ensure access limitations do not block submission.
Email records, organize submissions, and tag responses for review or scheduling.
Form vs document vs notes
An online form can reveal component sections, require explanations, attach photos, and route results.
Field guide
Scope varies by jurisdiction, system, and purpose. Align these six sections with your procedure and local requirements.
Site and record
Match the submission to the correct site and system. Inspection reason, occupancy, and recent use provide context for observed conditions.
Tank and access
Treat access as a finding. Record known tank details and visible lid, riser, liquid, leakage, corrosion, and structural conditions.
Measurements and internals
Use numeric fields with units, method, or location. Assess baffles, filters, and compartments separately from readings.
Mechanical components
Conditional logic keeps gravity inspections short while opening pumped-system checks. Record the test, response, and limitations.
Distribution and disposal
Check accessible distribution components and walk the disposal area. Photos and a site sketch clarify locations.
Findings and follow-up
Separate observations from interpretation and proposed work. State limitations, uninspected items, and specific next actions.
Related tools
Build companion workflows for property checks, equipment, maintenance, safety, foundations, and work orders.
Request maintenance with location, priority, and photos.
Open toolRecord foundation conditions, measurements, and photos.
Open toolSpecify repair work, materials, assignment, and completion.
Open toolFAQ
Answers for contractors, technicians, and local inspection teams.
It identifies the property and system, records scope, accessible component conditions, measurements, photos, limitations, and follow-up. A consistent sequence reduces omissions while allowing system-specific observations.
Include property, record, inspector, date, reason, system type, tank access, measurements, inlet and outlet components, filters, pumps and alarms when present, distribution, drainfield, photos, limitations, findings, work, and next actions. Adapt fields to local requirements.
Yes. Use the selected configuration to show pump, float, alarm, control-panel, distribution, or treatment sections when applicable. Test each branch, including unknown and inaccessible components.
Offer not present, inaccessible, not inspected, and unknown instead of forcing a rating. Require an explanation and optional photo, and distinguish limitations from observed defects.
Yes. Place uploads beside relevant sections and request the component, location, and view. Ask for overviews, access, visible internals, distribution, disposal area, and finding-specific images as needed.
No. It creates an editable form, not a government-issued approval or certificate. Criteria, terms, submission methods, and signatures vary. Compare it with local instructions and your procedure before use.
Yes. Makeform supports unlimited free forms and responses for generating, editing, publishing, and collecting submissions. The paid tier removes the Makeform badge.
Use consistent result tags while retaining full findings. Route records to an inbox or sheet with property, component, priority, photo, and next action so staff can review or schedule.
Replace scattered field notes with one inspection path.
