Call identity
Anchor the report to the assignment.
Use identifiers shared by dispatch and the customer so no note becomes orphaned.
- Work order number and service type.
- Customer, site, contact, and asset location.
- Technician and visit timestamps.
Describe your workflow and Makeform turns it into a service report form with structured fields for the asset, diagnosis, labor, parts, test results, photos, and customer acknowledgment.
Route service reports to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a scenario, adapt its details, and send the editable example to the Makeform builder.
Audience
Heating and cooling technicians
Format
Mobile report with readings and customer sign-off
Prompt size
267 chars
Example form structure
Mobile report with readings and customer sign-off
Work order, customer, site, and technician
Unit details and initial readings
Diagnosis and work performed
Parts used and quantities
Final status and customer signature
Suggested routing tags
Completed
Return visit
Parts required
Ask for readings before and after service. A final status alone cannot show what changed during the visit.
Step 1
Identify
ticket, customer, site, asset, and technician
Step 2
Diagnose
complaint, readings, tests, and cause
Step 3
Document
labor, parts, photos, and outcomes
Step 4
Route
completion, follow-up, or parts required
A usable record from every call
Connect the original request to completed work so managers can distinguish a repair from a temporary fix, locate parts usage, and see the next action.
Require the ticket, asset, location, technician, and timestamps so each record stays attached to the correct call.
Separate symptoms, tests, cause, and corrective work so managers understand why a repair was chosen.
Choose completed, restricted, return visit, or awaiting parts, then reveal the matching follow-up fields.
Fit the field workflow
Keep the common visit record and adapt measurements, checklists, and outcomes to the equipment your technicians actually service.
Record unit identity, pressures, temperatures, filters, refrigerant or consumables, final readings, and operating status.
Connect work orders to building assets, isolation checks, repairs, downtime, tests, and unresolved safety observations.
Summarize the complaint, explain the completed work, list charges or recommendations, and collect customer acknowledgment.
Run scheduled checklists, branch failed items into defect details, and schedule the next visit from the same submission.
Build the report
Describe what each team needs, then refine the generated form around decisions made during a real call.
Name the equipment, visit types, readings, outcomes, and report recipients.
Require asset and outcome fields, standardize statuses, and reveal follow-up questions only when needed.
Try a routine repair and an awaiting-parts path, keeping taps simple and explanations short.
Notify dispatch about return visits, purchasing about parts, and operations about completions.
Choose the right record
Requests and work orders define the assignment. The service report records what the technician found, changed, tested, consumed, and left for follow-up.
Field guide
Follow the call from identification through resolution with sections every receiving team can understand.
Call identity
Use identifiers shared by dispatch and the customer so no note becomes orphaned.
Asset identity
Link the asset to its history and capture details needed to identify parts.
Diagnosis
Separate the complaint from observations and structure readings for later comparison.
Work and labor
List corrective steps and labor without hiding a temporary workaround behind a completion box.
Parts and materials
Repeatable rows make part usage useful to inventory and billing teams.
Outcome and handoff
Combine final tests, condition, recommendations, acknowledgment, and a defined follow-up.
Related tools
Connect intake, work assignment, inspection, maintenance history, inventory movement, and incident follow-up with forms designed for each distinct job.
Assign assets, priorities, technicians, and planned tasks before field work begins.
Open toolCreate a broader maintenance record for recurring facility and equipment work.
Open toolStandardize condition checks and route failed items into corrective work.
Open toolKeep a chronological history of service activities for individual assets.
Open toolCollect the issue, location, contact, and requested timing before dispatch.
Open toolDocument an injury, damage event, or unusual occurrence discovered during service.
Open toolFAQ
Practical answers for field-service managers building a consistent record of every call.
It is the completion record for a visit: ticket, asset, technician, diagnosis, work, labor, parts, tests, and final status. A work order assigns the job; the report documents its outcome.
Include the work order, asset, visit times, problem, diagnosis, corrective steps, labor, parts, photos, final readings, operating status, recommendations, and follow-up owner. Add customer acknowledgment when needed.
Use one repeatable row per item with part number, description, quantity, unit, and disposition. Structured rows route cleanly to inventory or billing and distinguish similar parts.
Yes. Conditional logic can reveal the reason, required parts, next action, owner, priority, and date when a technician selects awaiting parts or return visit required.
Yes. Add file uploads and label each purpose: nameplate, before-work condition, failed component, completed repair, or final reading. Specific labels help offsite reviewers interpret each image.
Lead with ticket, asset, and status. Prefer dropdowns, checkboxes, numbers, and short repeating groups. Use conditional sections and test both routine and exception paths on a phone.
Yes. Makeform offers unlimited free forms and responses, including generating, editing, publishing, and collecting reports. The paid tier only removes the Makeform badge.
Review submissions in Makeform or route workflows through Google Sheets, Slack, or Zapier. Use outcome fields to separate completions, part requests, urgent exceptions, and return visits.
Close every service call with a usable record.