Describe your properties and test procedure. Makeform creates an editable smoke detector inspection form for device locations, test results, conditions, battery actions, photos, and follow-up.
Send inspection records to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a starting point, tailor the details, and send the prompt to the Makeform builder.
Audience
Landlords inspecting occupied rental units
Format
One submission per unit with repeating device checks
Prompt size
303 chars
Example form structure
One submission per unit with repeating device checks
Property, unit, date, and inspector
Detector ID, room, and device type
Did the detector respond to the test?
Condition, battery action, and photo
Follow-up owner and due date
Suggested routing tags
Passed
Needs service
Access needed
Give every detector a stable device ID or location label so a failed test can be matched to the right alarm during follow-up.
Step 1
Identify
property, unit, room, and detector ID
Step 2
Test
method, response, indicators, and condition
Step 3
Route
failed or inaccessible devices to follow-up
Step 4
Close
repair, replacement, and retest recorded
Inspection records that stay useful
A unit-level pass box can hide exceptions. Device records preserve each alarm's location, result, evidence, and next action.
Capture a stable device ID, room, type, and test outcome so every answer refers to a specific alarm.
Conditional questions appear after failed, damaged, missing, or inaccessible outcomes to collect priority, assignee, and due date.
Attach a photo, maintenance note, battery action, work-order reference, and retest result to the same inspection submission.
Adapt the route
Start with the inspection context closest to your team, then change labels, device choices, routing, and required evidence in the builder.
Log access status, every room checked, resident-reported issues, and follow-up that needs a return visit.
Organize devices by building, floor, stairwell, corridor, utility room, or other inspection zone.
Compare expected and found counts, document service completed, and leave a clear list of open items.
Use asset IDs, routes, panel references, exception ownership, and scheduled retests across larger sites.
Build the workflow
Define the properties and outcomes once, then give inspectors a consistent path from identification through documented follow-up.
List the properties, rooms, detector types, test outcomes, and evidence your organization wants inspectors to record.
Add real building and unit dropdowns, required device identifiers, outcome choices, and instructions based on your procedure.
Ask for a photo, reason, priority, assignee, and target date only when a device fails, is missing, or cannot be accessed.
Send submissions to the right team, then connect repair, replacement, and retest details to the original finding.
Choose the right record
The useful record is not simply that someone visited. It shows which devices were present, what was observed during each test, and which exceptions still need action.
Field guide
Use six focused sections so inspectors can identify the device, record what they observed, and send exceptions into a clear maintenance path.
Property and visit
Record where and when the visit happened, who performed it, and whether every area was accessible.
Device identity
Combine exact location with an asset ID or consistent label so later work points to the correct alarm.
Test and observation
Record the test method and observed response, then use separate choices for visible or audible exceptions.
Outcome logic
Use clear outcomes, then reveal detailed questions only when an exception needs maintenance attention.
Corrective action
Capture immediate action, remaining work, priority, responsible person, work-order reference, and return date.
Retest and summary
Keep the original finding, then add follow-up work and the retest result without overwriting history.
Related tools
Build companion forms for broader property checks, specialized fire-safety components, resident requests, and unit turnover.
Document broader room, exterior, utility, and property condition checks.
Open toolRecord door location, hardware, closure, condition, labels, and exceptions.
Open toolStructure location-based damper checks and corrective-action records.
Open toolRoute observed defects into an assigned maintenance request workflow.
Open toolCapture unit condition and resident observations at the beginning of occupancy.
Open toolCreate a room-by-room handoff record for apartment turnover and move-in.
Open toolFAQ
Practical answers for landlords, property managers, and facilities teams creating repeatable detector records.
It records a detector check at a specific place and time, including device identity, test observation, condition, evidence, outcome, and follow-up.
Include property, unit, date, inspector, access, detector ID and location, device type, test method and result, condition, service action, photo, outcome, and follow-up owner.
Yes. Repeat the device questions for every alarm while sharing the property, unit, date, inspector, and access details across the submission.
Use distinct outcomes, then conditionally request a reason, photo, immediate action, priority, assignee, target date, and retest plan. Define escalation in your own procedure.
Yes. Place a file-upload field beside the device record and explain when a label, damage, obstruction, installation, or completed-work photo is needed.
Yes. Keep the original exception, then add work completed, technician, completion date, replacement details, retest result, and closing evidence.
Yes. Makeform supports unlimited free forms and responses, including generating, editing, and publishing this inspection form. A paid plan is available to remove Makeform branding.
No. It structures your workflow but does not decide applicable devices, methods, intervals, or records. Use equipment instructions, your procedure, and relevant local guidance.
Replace scattered inspection notes with device-level records.
