Describe your assets and condition standards. Makeform creates a mobile manhole inspection form with asset identification, component ratings, defect photos, measurements, and maintenance routing.
Send inspection records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a workflow, adapt the prompt, or send it into the builder. Each example is editable.
Audience
Municipal wastewater inspectors completing scheduled rounds
Format
Mobile checklist with condition ratings and photos
Prompt size
266 chars
Example form structure
Mobile checklist with condition ratings and photos
Manhole asset ID and location
Cover, frame, and structure condition
Sediment depth and gas readings
Defect and context photos
Recommended action and priority
Suggested routing tags
Routine
Maintenance needed
Urgent review
Require an asset ID and fixed defect choices so repeat inspections can be compared.
Step 1
Identify
asset ID, location, access, and inspection context
Step 2
Observe
cover, frame, structure, channel, and connections
Step 3
Document
ratings, measurements, defects, notes, and photos
Step 4
Route
priority, maintenance action, owner, and follow-up
Field records that stay useful
Capture the structure, finding, and action in fields operations teams can sort.
Give every inspector the same component choices instead of uneven narrative notes.
Pair defect category and severity with measurements and photos for review.
Capture recommended work, priority, owner, and work order only when action is needed.
Adapted to the inspection
Edit component lists, rating scales, and routing rules to match your asset program.
Component ratings, access notes, photos, and maintenance recommendations.
Weather, leakage sources, joints, penetrations, severity, and evidence.
Work orders, sediment measurements, methods, material removed, and photos.
Plans, elevations, connections, punch-list items, corrections, and reinspection.
Build the workflow
Shape the form around data reviewers and maintenance crews need.
Name the inspection, identifiers, components, rating scale, and review team.
Use your defect vocabulary, units, priorities, and evidence requirements.
Show severity, measurements, photos, and work questions only for defects.
Test routine and urgent examples, then route records to reviewers.
Choose the record format
Keep asset IDs, ratings, evidence, and maintenance decisions connected.
Field guide
Use six groups to identify the asset, explain findings, and plan maintenance.
Asset and context
Start with an asset identifier and location context. Add purpose and conditions so reviewers interpret observations correctly.
Access and safety
Record surface conditions and whether the inspection was completed. The form does not replace procedures, training, or field judgment.
Components
Separate ratings reveal where deterioration occurs. Define repeatable choices such as acceptable, monitor, repair, and not visible.
Flow and defects
Pair each defect with its component or position, extent, severity, and whether it was active during inspection.
Measurements and evidence
Photos add context and measurements define scope. Label views so reviewers can identify components and defects.
Decision and follow-up
End with an overall assessment and next step. Request repair scope only for records needing attention.
Related tools
Build companion forms for equipment checks, safety observations, maintenance requests, incidents, work orders, and broader property inspections.
Document the condition and readiness of field equipment used by inspection and maintenance crews.
Open toolCreate structured site safety observations for recurring field checks and follow-up actions.
Open toolTurn a reported defect into a request with location, priority, evidence, and repair details.
Open toolDefine assigned work, labor, materials, completion notes, and asset references for maintenance tasks.
Open toolCapture event details, people involved, observations, attachments, and internal follow-up after an incident.
Open toolBuild a broader inspection checklist for sites, structures, utilities, and corrective items.
Open toolFAQ
Practical answers for utility inspectors, public works teams, contractors, and maintenance coordinators.
It is a structured field record for identifying a manhole, rating accessible components, documenting defects and flow conditions, attaching evidence, and recommending follow-up.
Include asset ID and location, inspector and date, access conditions, cover and frame, chimney, cone or slab, barrel, bench, channel, steps, seals, joints, pipe connections, flow, debris, sediment, inflow or infiltration evidence, photos, an overall condition rating, priority, and recommended action. Add measurements and project references when the workflow requires them.
Yes. Use a short mobile path: identification, component ratings, then conditional detail for defects. Test it on the devices and in the conditions crews encounter.
Add location and file-upload fields for coordinates, context, and defect photos. Require the asset ID too, because location alone may not distinguish nearby structures.
Use scales your organization defines and trains inspectors to apply. Keep component condition separate from response priority: a defect rating describes what was observed, while priority reflects factors such as service impact, access, progression, and the maintenance program's decision rules. Add help text with observable examples for each choice.
Yes. Conditional logic can reveal defect type, location, extent, severity, photos, recommended action, and work-order details after an inspector selects a problem rating. Routine records stay short while exceptional findings still collect enough detail for review.
Yes. Makeform offers unlimited free form creation, editing, publishing, and responses. The paid tier removes the Makeform badge, so inspectors and operations teams can build and use the core inspection workflow without a usage limit.
No. It organizes the questions and evidence your team chooses to collect. Your utility or project team should supply the applicable procedures, terminology, rating definitions, access rules, and review process, then test the form with field staff before relying on it for operational decisions.
Build a clearer field record.
