← Blog

Note

How to write a field service report

The structure that works for an inspection, maintenance or service report, how to write a finding the client understands, the most common mistakes and a checklist to review it before sending it.

By the BITA team · 5 min read · Published

The 8 parts of a field service report, drawn as a report with a number, a signature and a QR code: identification, purpose and scope, conditions, work carried out, findings with photos, measurements, conclusions, and signatures and verification.

What is a field service report?

A field service report is the document that tells what was done in a field job, what was found and what is recommended, with the evidence behind it and the signature of whoever is accountable.

It is issued by the company that did the work —an inspection, a maintenance job, a service— and read by someone who was not there: the client, their management, an auditor or the company doing the next job. So it has to stand on its own, with nobody there to explain it.

The structure of a field service report

Eight parts, in this order. If the client has its own format, use it; if not, this one works for almost any service:

  1. IdentificationThe report number, the client, the place (the farm site, the plant, the job site), the exact asset (the pen, the equipment, the line), the date and time of the work and who did it.
  2. Purpose and scopeWhat was requested and what was left out. «Inspection of the nets of pens 101 to 112» says more than «net inspection».
  3. ConditionsWhat affected the work: weather, visibility, tide, a piece of equipment that failed. It explains why something could not be checked.
  4. Work carried outWhat was done, in order, with the equipment or instruments used.
  5. FindingsEach observation on its own, with its location, its severity and its evidence. It is the part the client reads first.
  6. MeasurementsThe values with their units, the instrument and, where relevant, the reference value.
  7. Conclusions and recommendationsWhat the findings mean and what needs to be done, with deadlines where relevant.
  8. Signatures and verificationWho did the work and who received it, and how to check that the document is the original: a report number and, better still, a verification code.

How to write a finding people understand

A good finding says what was seen, exactly where, how serious it is and what evidence supports it, in one or two sentences.

Compare two ways of saying the same thing:

  • Poor: «Damage observed on the net.»
  • Good: «10 cm tear on the outer face of the net of pen 104, at 12 m depth. High severity: escape risk. Photo 7.»

The second can be located, repaired and checked; the first means calling to ask. Always use the same words for the same thing —a fixed severity scale, the same names for the faces of a net or for the equipment— and put the photo next to the finding, not in an appendix.

The most common mistakes

  • Copying the previous reportThe date is changed and the name of last time's site or pen stays. It is the most common mistake and the one that damages trust the most.
  • Photos without contextAn appendix of twenty photos that do not say what they show supports nothing.
  • «All OK»If nothing was found, say so with the scope: what was checked and under what conditions. «No observations in the 12 pens inspected» is a result.
  • The report date instead of the work dateWhat matters is when the work was done and seen, not when it was written up.
  • Versions circulating by emailIf something has to be corrected, the new version should say so and the previous one should be identified. Otherwise the client ends up with three different PDFs and none of them is reliable.

Checklist before sending

  • Does it have a report number and the date of the work?
  • Is the scope clear: what was checked and what was not?
  • Does each finding say where, how serious and which photo?
  • Do the measurements have their units?
  • Do the recommendations say what to do and when?
  • Is it signed by whoever did the work and whoever received it?
  • Can the recipient check that it is the original?

For the last point, see what makes a report traceable and verifiable.

The report nobody has to write

The way to avoid almost all these mistakes is not to write the report afterwards: record each finding on site, with its photo and its location, and let the report be built from that data in a fixed format. Then there is nothing to copy from the previous one and no photos to sort. It is what we do at BITA, and we tell the story in the hours lost after the job.

Questions

Questions about field service reports.

What should a field service report contain?

Identification (report number, client, place, asset, date and people responsible), purpose and scope, conditions, work carried out, findings with their evidence, measurements, conclusions and recommendations, and the signatures with a way to verify the document.

What is the difference between a technical report and a service report?

They are used almost as synonyms. A service report is usually shorter and tells what was done on a visit —a maintenance job, a repair— and who received it; a technical report focuses on what was found and what is recommended. The structure in this article works for both.

Do photos go in an appendix or next to the finding?

Next to the finding they support, with a caption saying what they show. An appendix of loose photos forces the reader to guess what each one proves.

Is a Word or Excel template good enough?

It is good for getting started, because it fixes the structure. The problem comes later: each report is copied from the previous one, photos are pasted by hand and the data cannot be searched or compared between reports.

For companies that stand behind every job.

Book a presentation and we'll walk you through the full traceability of a job from your own industry.

14-day trial · no credit card · nothing to install