Service report: what to put on it so nobody has to call you back

A service report is what the engineer leaves behind: the record of what was found, what was done and what still needs doing. It has three audiences with different needs — the customer who signs it, the office that invoices from it, and whoever attends the same equipment next time. Most reports serve the first audience adequately and the third not at all, which is why the next visit starts from scratch.

What belongs on a service report

• Who attended, when they arrived and when they left — actual times, not the booked slot.
• The asset: what it is, where it is, and its identifier or serial number.
• Reported symptom in the customer's words, alongside what you actually found.
• Work performed, in enough detail that a different engineer could follow it.
• Readings taken, with units — pressures, temperatures, currents, hours run.
• Parts fitted, with part numbers, and parts used from van stock as distinct from ordered.
• Outcome: resolved, temporarily mitigated, or requires a return visit.
• Recommendations and anything left unsafe or non-compliant, stated plainly.
• Customer signature, or a note that nobody was available to sign.

The fields that stop disputes

Three in particular. Arrival and departure times settle labour arguments. The distinction between "found" and "reported" settles the "I told you it was the other thing" conversation. And a recommendation recorded but declined — with the date and who declined it — is what protects you when the same fault returns as an emergency. Everything else on the report is documentation; those three are protection.

Write recommendations as work, not as worry. "Compressor contactor pitted, recommend replacement within one month, quote to follow" is actionable; "compressor seems tired" is a liability that helps nobody.

Capture it on the job, not afterwards

A report written from memory in the evening loses the readings. Use a form that the engineer completes on site, with required fields and photographs attached where they were taken — Ettex Forms is built for that, and the submissions arrive timestamped rather than as a photograph of a paper docket. Where the same customer contract generates dozens of reports, keeping them on the asset's row in Ettex Records means the next engineer sees the last three visits before they set off.

From report to invoice

1. Check the report is complete before it leaves the site — a missing signature costs more later than five minutes now.
2. Reconcile labour time on the report against the rates in the agreement rather than against the booked slot.
3. Match parts fitted to what was taken from stock, so van stock stays credible.
4. Raise the invoice from the report, quoting its reference, so the customer can reconcile without a call.
5. Turn every recommendation into a quote or a logged decision within the week, while the visit is still recent.
6. File the report against the asset, not against the month.

Getting the engineer there in the first place is its own problem. Service dispatch software handles intake, skills matching and travel time, then captures completion on site so the paperwork is finished before the van leaves.

Emergency trades rebuild the day several times over. Plumbing dispatch software is judged on reassignment speed and on whether van stock is visible, because the second visit is where the margin disappears.

What to leave off

Anything the office already knows — the customer address block repeated three times, the contract number the system holds, a checklist of items the engineer did not inspect. Long templates get completed by pattern rather than by observation, and a tick against something nobody looked at is worse than a blank. A shorter report honestly completed beats a thorough one filled in from habit.

The same discipline applies to the wider queue: a service report closes a work order, and work order tracking is what tells you the visit happened at all. Reports without the queue behind them are a pile of paper that agrees with nothing.