A field service report is a post-visit record of what happened at a customer site. It gives the business, technician, and customer a consistent summary of the reported issue, work completed, current job status, and any follow-up still needed.
Use the copyable field service report template below for repair, maintenance, installation, and follow-up visits. The field set is a practical starting point rather than a universal requirement: adapt it to your trade, customer process, and recordkeeping needs.
Digital field service platforms can generate reports from related work orders or service appointments and use reusable templates, which supports carrying a single job reference through the completed-visit record. See Salesforce’s documentation on field service report templates for that workflow context.
Copyable field service report template
Copy this structure into a paper form, document, spreadsheet, PDF, or digital form. Record what happened during or after the visit; do not use it as a booking, dispatch, pricing, or payment form.
| Section | Field | Use |
|---|---|---|
| Report reference | Report number; work order or job reference | Core — connects the report to the related job record. |
| Customer and site | Customer name; contact details; service location | Core — identifies who and where the visit concerned. |
| Visit details | Technician name; visit date; arrival and departure time | Technician and date are Core. Times are Optional where useful to your workflow. |
| Reported issue | Customer-reported concern or reason for visit | Core — a concise starting point for the visit record. |
| Findings and work performed | Observations; work completed; customer-facing summary | Core — state what occurred in plain language. |
| Materials or parts | Materials used; parts installed; items still needed | Optional — include when it helps explain completed or paused work. |
| Photos or attachments | Before, during, or after photos; related documents | Optional — attach only when relevant to the visit. |
| Current status | Complete; follow-up needed; return work needed | Core — make the outcome clear. |
| Customer acknowledgement | Name; date; acknowledgement that work or findings were discussed | Optional — keep this separate from internal notes. |
| Internal notes | Office handoff; information needed; parts-pending detail; follow-up owner | Internal-only — not intended for the customer-facing summary. |
| Next action | Required follow-up and responsible role or team | Core when incomplete — state what needs to happen next without turning the report into a scheduling document. |
Copyable form wording
Report reference: ____________________
Customer: ____________________
Customer contact: ____________________
Service location: ____________________
Technician: ____________________
Visit date: ____________________
Arrival time (optional): ____________________
Departure time (optional): ____________________
Reported issue or visit purpose:
____________________________________________________________
Findings and work performed:
____________________________________________________________
____________________________________________________________
Materials or parts used / still needed (optional):
____________________________________________________________
Photos or attachments included (optional):
____________________________________________________________
Current status: Complete / Follow-up needed / Return work needed
Customer acknowledgement, if used:
I confirm that the work completed or findings from this visit were discussed with me.
Name: ____________________ Date: ____________________
Internal notes:
____________________________________________________________
Next action, if needed:
____________________________________________________________
What each section should capture
Who and where
Start with a report reference, customer name, contact details, and service location. Reusing the related work-order or job reference reduces ambiguity when a customer has multiple visits or locations.
When and by whom
Record the technician and visit date on every report. Arrival and departure times can be useful where they support the business’s internal process, but they do not need to appear on every simple report.
What happened at the visit
Keep the reported issue separate from findings and work performed. The first explains why the visit happened; the second records what the technician observed and completed. A short, factual summary is usually more useful than a long narrative.
Supporting evidence and customer-facing information
Photos can support the job record when they add useful context, but they are not necessary for every visit. If the business uses a customer-facing report, keep its wording concise and separate it from internal handoff notes. Salesforce documents workflows that can create customer reports from related service records, including reports saved with the related record.
Current status and next action
Every report should make the present outcome easy to understand. For completed work, mark the job complete. For paused work, state what was completed so far, what remains open, and the next required action. This avoids a report that describes the visit but leaves the office or technician unclear about what follows.
Core, optional, and internal-only fields
Keeping every possible field on every form makes completion slower and can bury the important information. A simpler approach is to divide fields by purpose.
- Core fields: job reference, customer or site details, technician, visit date, reported issue, work summary, and current status.
- Core when work is not complete: a clear next action and enough context for the follow-up record.
- Optional fields: visit times, materials or parts, photos, attachments, and customer acknowledgement.
- Internal-only fields: technician handoff notes, office follow-up ownership, or detail that is useful to the business but not suitable for a customer-facing summary.
Customer acknowledgement can be useful when appropriate to confirm that completed work or findings were discussed. It should not be presented as legal approval, acceptance, waiver, or proof of a legal, warranty, safety, or compliance outcome. Salesforce’s signature guidance for service reports similarly notes that customers remain responsible for lawful use of signature capture.
Completed examples: finished job and return work needed
Example 1: One-visit completion
Reported issue: Customer requested service for an identified problem at the site.
Findings and work performed: Technician reviewed the reported concern, completed the agreed service work, and discussed the completed work with the customer.
Materials or photos: Included only if relevant to the visit.
Status: Complete.
Next action: None recorded.
Example 2: Return work needed
Reported issue: Customer requested service for an identified problem at the site.
Findings and work performed: Technician documented the condition observed and the work completed during this visit.
Materials or parts: Additional item or information needed before the remaining work can be completed.
Status: Return work needed.
Internal note: Record the detail needed for the follow-up record and who should review it.
Next action: Follow up on the outstanding item and create or update the related job record as appropriate.
For businesses that regularly handle parts-pending jobs or connected return visits, this broader guide to a multi-visit repair workflow provides additional operational context without changing the purpose of the report itself.
Service report vs work order, booking form, and invoice
| Document | Primary purpose | When it is used |
|---|---|---|
| Booking form | Captures the incoming service request. | Before scheduling and the site visit. Use a field service booking template for that earlier stage. |
| Work order or assigned-job summary | Provides job context before work starts. | Before or during the visit. |
| Field service report | Records what happened during or after the visit. | After a completed or paused visit. |
| Estimate, quote, or invoice | Handles pricing approval or a payment request. | Separate commercial documents. See estimate, quote, and invoice differences. |
A work order may provide the reference and initial job context, while the service report records the completed-visit outcome. The two documents can be linked, but they serve different stages of the workflow.
Move from paper to a digital form without changing the workflow
Start by standardizing the field structure, not by changing every tool at once. A solo operator may begin with a printed form or PDF. An office-managed team may place the same headings in a shared spreadsheet or document. A digital form can later preserve the same report reference, customer-facing summary, internal notes, attachments, status, and next action.
- Choose one shared set of core fields for every completed or paused visit.
- Use the same job or work-order reference on the report and related records.
- Keep customer-facing acknowledgement separate from internal notes.
- Store the finished report with the related job record where the workflow supports it.
- Review a small sample of completed reports to remove fields that are rarely useful and clarify fields technicians interpret differently.
Checked August 1, 2026. The digital-report examples referenced in this article support templates, related service records, report summaries, images, and signatures; they do not establish a universal required field list. Use this template as a practical operational format and adapt it to your business.
Frequently asked questions
What should a field service report include?
A practical field service report includes a job reference, customer and site details, technician, visit date, reported issue, work performed, and current status. Add a next action when work remains open. Materials, photos, visit times, and customer acknowledgement are useful conditional fields rather than universal requirements.
Is a field service report the same as a work order?
No. A work order or assigned-job summary provides context for the job before or during the visit. A field service report records what happened at the visit, including work completed, current status, and any follow-up needed.
Should customers sign a service report?
Customer acknowledgement may be useful when appropriate to confirm that work completed or findings were discussed. Keep the wording narrow and do not present a signature as legal approval, a waiver, or proof of compliance.