Describe your sites and monthly routine. Makeform creates a mobile checklist for unit results, defects, photos, and follow-up work.
Send inspection records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the Makeform builder. Examples show form structure, not completed inspections.
Audience
Technicians inspecting one building
Format
Mobile checklist with repeatable unit records
Prompt size
274 chars
Example form structure
Mobile checklist with repeatable unit records
Site, date, technician, zone
Unit ID and exact location
Indicator and visible condition
Functional-test result
Defect photo and action
Suggested routing tags
Passed
Defect found
Follow-up due
Give every fitting a stable unit ID and exact location so teams can find it again.
Step 1
Identify
site, route, technician, and unit ID
Step 2
Inspect
indicator, condition, access, and function
Step 3
Flag
defect, photo, priority, and immediate action
Step 4
Follow up
owner, work order, target date, and status
A clearer monthly inspection record
Keep each unit's location, result, and next action together during the inspection.
Asset IDs, locations, and unit records keep failed or inaccessible fittings visible.
Request defect details, photos, priority, and an owner only for failed or incomplete results.
Capture a work order, owner, target date, and status for maintenance follow-up.
Adapt it to the route
Add your team's locations and routing labels.
Organize units by building, floor, room, stair, corridor, and exit route.
Route records by property and zone.
Add access, obstruction, contamination, damage, and mounting notes.
Record scope, exclusions, completed work, parts, and the next visit.
Build the monthly workflow
Describe the route, refine the questions, and publish a phone-ready form.
Name the buildings, locations, fitting types, result choices, and required test details.
Add site lists, unit IDs, defect categories, and instructions; require essential identifiers.
Submit pass, fail, and inaccessible examples; confirm the right conditional fields appear.
Send records to the team, notify owners, and distinguish open actions from completed repairs.
Choosing a record format
An online form connects each exception to its location, image, assignee, and follow-up date.
Field guide
Use these six sections as a backbone, then adapt them to your equipment, procedures, guidance, and local requirements.
Inspection context
Identify the round and its scope. A route or zone choice keeps location descriptions consistent each month.
Unit identity
Pair a stable asset ID with a plain-language location so later technicians can find the correct fitting.
Visual check
Keep observations consistent by recording the indicator plus damage, dirt, labels, stock, or building changes affecting the unit.
Functional test
Record the test method and outcome. Keep pass, fail, and not tested distinct, and require a reason when no test occurred.
Defect evidence
For failures, collect a sortable defect category plus images showing the problem and its location.
Corrective action
Give each unresolved defect an owner and target date. Status fields distinguish reported issues from closed work.
Related tools
Build broader safety checks, equipment records, maintenance logs, and repair requests.
Build broader site checks with photos and assigned actions.
Open toolDocument dampers, findings, access issues, and follow-up work.
Open toolCreate asset checks with results and exception evidence.
Open toolKeep service dates, work performed, parts, technicians, and future actions together.
Open toolTurn a discovered defect into a repair request with location, priority, and supporting photos.
Open toolCover access, storage, equipment, housekeeping, and other warehouse inspection points.
Open toolFAQ
Practical answers for facilities and fire-safety teams replacing printed monthly check sheets.
It records who checked each emergency light, where and when they checked it, the visible condition and test result, plus defects, photos, and follow-up actions. Adapt the method and review process to your equipment and requirements.
Include site, route, date, technician, unit ID, location, fitting type, indicator, visible condition, test method, and result. For exceptions, add a reason, photos, priority, immediate action, work order, owner, target date, and status.
Yes. Use a repeatable section for each fitting while recording visit details once. For large routes, separate submissions by building, floor, or zone so omitted areas stay visible.
Keep fail and not tested separate. Fail can reveal defect, photo, priority, action, and assignee fields. Not tested can require an access reason and revisit date, avoiding treatment of a skipped fitting as a pass.
Yes. Add uploads to the failure branch for a defect image and wider location image. Keep the unit ID in the same record so each image stays connected to its fitting.
Yes. Route records to a maintenance inbox, team channel, or spreadsheet. Include result and priority fields, then capture an owner and target date instead of relying on the alert alone.
Yes. Makeform provides unlimited free forms and responses. You can generate, edit, publish, and reuse the checklist. The paid tier removes the Makeform badge.
No. It organizes an inspection record; it does not certify the work or determine applicable tests, intervals, qualifications, or retention rules. Review it against equipment instructions, your procedure, and local requirements.
Replace loose monthly notes with an actionable record.
