Describe your workflow and Makeform builds a mobile-friendly field service report form. Capture the job, labor, parts, readings, photos, unresolved issues, and customer acknowledgment before the technician leaves.
Send completed service reports to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the Makeform builder. Each example is editable.
Audience
HVAC technicians completing maintenance and repair calls
Format
Mobile report with readings, parts, photos, and sign-off
Prompt size
260 chars
Example form structure
Mobile report with readings, parts, photos, and sign-off
Work order, customer, and site
Equipment model and serial number
Diagnostic readings and work completed
Parts used and quantities
Customer acknowledgment
Suggested routing tags
Completed
Return visit needed
Parts follow-up
Use repeatable parts rows with quantity and part number instead of one notes field, so inventory receives structured details.
Step 1
Identify
job, customer, site, asset, and technician
Step 2
Document
diagnosis, work, labor, parts, and readings
Step 3
Verify
tests, photos, status, and customer acknowledgment
Step 4
Route
completed jobs and unresolved issues to the right queue
Built for work in the field
A structured mobile report prompts technicians for the details dispatch, billing, inventory, and follow-up need.
Keep the work order, customer, asset, technician, timestamps, and status in one submission.
Repeatable rows for part number, description, and quantity support replenishment and billing.
Conditional questions capture the reason, priority, resources, approval, and timing for unresolved work.
Flexible service workflows
Start with a use case, then replace its assets, checks, readings, and statuses with your team's language.
Record asset condition, checks, measurements, adjustments, consumables, and next service date.
Capture symptoms, tests, diagnosis, repair, result, and unresolved faults.
Log components, serial numbers, configuration, tests, photos, and handoff.
Log conditions, failed checks, corrections, photos, severity, and pending authorization.
Report setup
Describe required closeout details, inspect the structure, and publish a clear mobile path.
Name the assets, readings, statuses, evidence, and conditions that require follow-up.
Use quick selections, repeatable parts rows, camera uploads, and focused diagnosis fields.
Show escalation questions only for incomplete jobs, failed tests, unavailable parts, or return visits.
Share the form link, then route completed records and flagged issues for review.
Reporting options
The best method is the one a technician can finish at the job site while asset details, readings, materials, and unresolved conditions are still clear.
Field guide
Build around closeout decisions: what is complete, what was used, and what happens next.
Job identity
Lead with identifiers dispatch recognizes so every report matches the correct customer, asset, and request.
Asset & diagnosis
Identify the asset before asking for narrative. Equipment details and symptoms give the diagnosis useful context.
Work completed
Separate diagnosis from action. Record what was repaired, adjusted, cleaned, configured, installed, or tested.
Parts & materials
A repeating section gives each component its own part number, description, quantity, and status for review.
Evidence & acknowledgment
Photos and confirmations support quick review. Collect customer acknowledgment where it fits the closeout process.
Status & follow-up
Conditional questions should define the blocker, urgency, required resource, owner, and timing for unresolved work.
Related tools
Connect closeout reporting with work requests, inspections, maintenance records, and repair follow-up using related Makeform generators.
Create structured work orders that give technicians the customer, site, asset, problem, and priority before dispatch.
Open toolDocument scheduled and corrective maintenance with service details, findings, actions, and equipment status.
Open toolBuild condition checks for equipment, readings, failed items, photos, and corrective-action recommendations.
Open toolCollect reported problems, locations, assets, priority, and supporting photos before work is scheduled.
Open toolCreate consistent maintenance log entries for recurring service history and work performed on each asset.
Open toolLet staff or customers submit repair needs with issue details, timing, contact information, and evidence.
Open toolFAQ
Practical answers for service managers replacing paper tickets and inconsistent technician summaries.
It is the closeout record for an on-site job. It connects the work order and asset to the diagnosis, completed work, labor, parts, readings, photos, status, unresolved issues, and customer acknowledgment.
Include the work order, customer, site, technician, times, asset, issue, diagnosis, completed work, labor, parts, readings, photos, status, and follow-up requirements. Add acknowledgment when needed.
Yes. Publish a mobile-friendly link. Use dropdowns for common results, repeatable parts rows, camera uploads, and conditional questions that appear only when an issue needs detail.
Use one repeatable row per item with part number, description, and quantity. For unavailable parts, ask for the required item, order status, timing, and whether equipment can operate until return.
Yes. Branch from completion status or test result. For incomplete work, ask for the blocker, severity, temporary action, resources, approval, restriction, owner, and return window.
Yes. Add upload fields for before-and-after or nameplate photos, with captions. You can also add customer comments, an acknowledgment checkbox, or an on-screen signature.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect reports without a response cap. The paid tier removes the Makeform badge.
Each report is stored as a submission. You can also route information to Google Sheets, Slack, and Zapier, with separate paths for completed work and flagged follow-up.
Replace the paper service ticket.
