Describe the site, system, and inspection scope. Makeform creates a digital electrical inspection form for checks, readings, photos, code-reference notes, corrective actions, and sign-off.
Send inspection records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the builder. Each question list previews a form structure, not an inspection result.
Audience
Electricians documenting a dwelling service and panel review
Format
Mobile checklist with readings and photos
Prompt size
354 chars
Example form structure
Mobile checklist with readings and photos
Property, inspector, and service details
Panel, grounding, and bonding checks
Record voltage and test readings
Upload panel and deficiency photos
Inspector notes and sign-off
Suggested routing tags
No deficiency observed
Correction recommended
Follow-up required
Collect value, unit, test method, and permitted range separately; pass or fail alone hides the evidence.
Step 1
Identify
site, asset, circuit, scope, and inspection stage
Step 2
Inspect
repeatable observations, readings, and test status
Step 3
Document
locations, photos, references, and recommended work
Step 4
Follow up
owner, target date, correction, and reinspection result
Structured field records
Keep inspection identity, evidence, and follow-up connected without forcing every observation into one notes box.
Use acceptable, deficiency observed, not applicable, and not tested. Require a reason for skipped tests.
Store location, asset, measurement, unit, method, photo, and inspector-entered reference with each observation.
When action is recommended, collect priority, owner, requested work, target date, and reinspection outcome.
Adaptable inspection scope
Generate for the property, system, and stage, then edit every item to match your procedure and local requirements.
Capture service rating, disconnects, panels, directories, conductors, grounding, bonding, access, and clearances.
Organize circuit identification, receptacles, protection, controls, connections, covers, and condition by area or circuit.
Record method, value, unit, inspector-entered range, result, and reason when testing is not performed.
Give each issue a record, then append correction and verification details without overwriting the finding.
Form-building workflow
Makeform provides the structure; your qualified team chooses the scope, methods, criteria, code edition, and review process.
Name the property, system, stage, checks, readings, evidence, handoff, and status choices.
Replace generic items with your procedure, current references, ranges, assets, terms, and escalation rules.
Show photo, location, severity, citation, and action fields after a deficient or untested selection.
Notify a reviewer, send rows to a sheet, and record correction evidence and reinspection results.
Digital form vs paper checklist
A digital submission keeps photos, readings, deficiencies, and follow-up ownership together.
Field guide
Use these six sections as a starting point. The form records work; it does not determine code conformity or replace inspector judgment.
Inspection identity
Tie every submission to the job, exact area, stage, people, and governing references.
System details
Give reviewers the equipment identity, rating, circuit, location, and supply context behind each status.
Checklist outcomes
Give every row a controlled outcome, with explanations for not applicable and not tested.
Tests and readings
Preserve value, unit, method, inspector-entered range, and conditions behind each test outcome.
Finding evidence
Open a finding block for the location, observation, image, and inspector-selected reference.
Correction and review
Preserve the finding, then add responsibility, correction evidence, and reinspection as separate steps.
Related tools
Build forms for safety checks, equipment records, work requests, and property inspections.
Record condition, function, and evidence for individual assets.
Open toolDocument workplace safety observations beyond electrical systems.
Open toolCapture building-area and property condition observations.
Open toolTurn approved corrections into scoped work requests.
Open toolKeep dated service and repair records for assets.
Open toolFAQ
Practical answers for electricians, inspectors, contractors, and facility teams replacing paper checklists.
It records the system reviewed, checklist outcomes, readings, deficiencies, photos, inspector-entered references, and follow-up. It documents the inspection but does not decide code conformity or certify work.
Include location, equipment or circuit, stage, scope, inspector, date, outcomes, readings with units and methods, photos, and comments. For deficiencies, add the observation, inspector-cited reference, priority, action, owner, correction evidence, and reinspection result.
Yes. Use separate forms or reveal fields by stage. Rough-in can cover boxes, raceways, conductors, supports, grounding, and concealed-work photos. Final checks can cover devices, covers, directories, labels, protection tests, connections, and function.
It can record the observed condition, inspector-cited code edition and section, and follow-up. Makeform does not determine code conformity. A qualified reviewer should select current applicable requirements and evaluate the installation for the project and jurisdiction.
Collect the number, unit, test point, instrument or method, inspector-entered range, conditions, and outcome separately. Include not tested with a required reason so reviewers can interpret the result.
Yes. Add uploads and a repeatable finding section with location, captioned photo, observation, reference, priority, and action. If repeatable groups are unavailable, use numbered finding blocks or a linked deficiency form; verify this workflow before field use.
Yes. Makeform provides unlimited free forms and responses. Generate, edit, publish, and collect submissions without a free-plan response cap; the paid tier removes the Makeform badge.
Keep the original finding, then add the owner, requested work, target date, completion details, and evidence. Record reinspection separately. Submissions can also flow to Google Sheets, Slack, or Zapier.
Replace the field notebook with a structured record.
