A field service report form creates a closeout record for a site visit: what was found, what was completed, what remains, and the proof needed to approve the work. Copy this field set into a paper, mobile, or operational form and adjust it to the service agreement.
Quick answer
Use the form after every visit to capture the work-order reference, site and technician details, diagnosis, work performed, time and materials, completion evidence, customer acknowledgement, and next action. Do not close a job with missing required evidence.
Copy-ready field service report form
| Field | Type | Requiredness and rule |
|---|---|---|
| Report ID; work order ID; service date | Text/date | Required; unique visit reference |
| Customer, site, and contact | Text/address | Required |
| Technician or crew; service type; priority | Selector | Required |
| Reported issue; diagnosis; work performed | Long text | Required; describe outcome |
| Parts/materials and time on site | Repeating items/timestamps | Required when used |
| Job result | Resolved / partial / unable / return visit | Required |
| Photos, readings, checklist, or deliverable | Attachment | Required when specified by work order |
| Follow-up owner, due date, and dependency | Conditional fields | Required when result is partial, blocked, or return visit |
| Customer acknowledgement and reviewer decision | Confirmation | Required for exceptions |
Validation and closeout logic
- Resolved: require work performed and required evidence, then route to review.
- Partially resolved or return visit: require a follow-up task, owner, due date, and reason.
- Safety or access issue: require incident notes and escalation owner; block closeout.
- Missing evidence: return the report for clarification instead of closing it.
Completed illustrative example
Work order: WO-1048, planned HVAC inspection. Finding: condensate drain partially blocked. Work performed: cleared line and tested flow. Result: resolved. Evidence: before/after photos and test reading. This example is illustrative; use the evidence your agreement requires.
Operating workflow
- Dispatcher pre-fills work-order and site context.
- Technician submits the report and evidence.
- The form validates conditional fields and routes exceptions.
- A service owner approves, reopens, or assigns follow-up.
- Only approved work moves to billing or payment review.
Related resources
- Field service scheduling workflow
- Work order template for service teams
- Shift handover checklist for field teams
Where Workhint fits
Workhint can make this form a connected field service workflow: intake creates a work order, dispatch assigns the visit, technicians submit evidence, and exceptions route to an owner before approved work is visible for billing or payment review.
FAQ
Is a work order the same as a service report?
No. A work order defines requested work before dispatch; a service report records what happened during and after the visit.
Leave a Reply