How do you write a technical service report the customer acts on?
Summary
A technical service visit report needs 5 sections: conclusion first, scope and standard, deviations with evidence, areas not observed, and actions with owners and dates. The order works when the visit compares the customer's process against a standard both sides agreed in advance, and the reader must act without a follow-up call.
Who reads a technical service visit report, and what do they decide?
A technical service visit report is read by the customer's process owner, who decides whether anything needs action, by whom and by when, and by the engineer or operator who must carry out the change. The process owner usually reads the first page only. The engineer reads the deviations and decides whether the evidence is strong enough to change a setting, a dosing rate or a maintenance routine. A third reader arrives later: whoever opens the report at the next visit, the next complaint or the next audit, and needs to know what was actually checked and what was not.
Each reader needs a different part of the technical service report, which is why the order of sections matters. A report written as a diary of the day, in the sequence the engineer walked the plant, makes the process owner hunt for the decision and gives the later reader no way to tell an observed fact from an impression.
Inspection practice draws the same line between a finding and the requirement behind it. ISO/IEC 17020:2026, the third edition, published in March 2026, describes inspection as the examination of an item, such as a product, plant or process, and the determination of its conformity with requirements that can come from standards, regulations, contracts or internal specifications (ISO/IEC 17020:2026). A supplier's technical service visit is rarely an accredited inspection, but the same logic carries over: a deviation only means something against a named requirement (inference from the ISO definition).
Which sections does a technical service visit report need, in what order?
A technical service visit report needs five sections in this order: conclusion and actions, scope and standard, deviations with evidence, areas not observed, and the action list with owners and dates. The conclusion comes first because the process owner decides from it; the evidence follows because the engineer and the later reader check from it. The table below decides whether the customer can act on the report without a follow-up call.
Section | What it must show | Evidence behind it |
|---|---|---|
1. Conclusion and actions | Overall finding in two or three sentences, then the actions by owner | The deviations in section 3 that drive each action |
2. Scope and standard | What was checked, where, on which date, against which agreed limits | The document that sets each limit, with its revision |
3. Deviations with evidence | Each observation against its limit, with observer, time and location | Readings, sample IDs, photos, log entries |
4. Areas not observed | Each planned check not done, and why | Visit plan versus what was done |
5. Action list | One owner, one due date and one side (customer or supplier) per action | The deviation or gap each action closes |
The row that most reports skip is section 4, areas not observed. Without it, a reader assumes that everything in scope was checked and found in order. A US EPA regional field procedure asks reports to identify and explain any deviations from, additions to or exclusions from the planned sampling or measurement, where necessary for interpreting the results (US EPA Region 4, FSBPROC-003-R7, 2024). That procedure was written for EPA's own field investigations and says it may not apply directly to other organizations, but the habit transfers: what you did not do belongs in the report, next to what you did.
How should a technical service report record each deviation from the standard?
A technical service report should record each deviation as one observation set against one agreed limit, with who observed it, when, where, and the evidence a later reader can check. A deviation without its limit is an opinion, and a limit without its source cannot be defended when the customer's own engineer disagrees.
Write each deviation in the same order every time. Name the point: the machine, tank, line or sample tap. State the agreed limit and the document it comes from, such as the product data sheet, the customer's fluid management plan or a contract specification, with its revision. Give the value or condition you observed, the method or instrument, the time and the observer. Then say whether it is inside or outside the limit, and by how much.
Field record rules from regulators show why each element matters. The US EPA Region 4 logbook procedure requires that observations, data collection and calculations be recorded at the time they are made, and that entries be dated and signed or initialed by staff (US EPA Region 4, LSASDPROC-1002-R1, 2021). The same procedure tells staff writing field and lab audit reports to stick to the facts of the observation and give a regulatory or procedure reference where it applies (US EPA Region 4, LSASDPROC-1002-R1, 2021). If an observation rests on a sample sent to a laboratory, keep the sample's custody record with it. ASTM D4840-99(2018)e1, a guide, describes chain-of-custody procedures that document sample possession during collection, shipment, storage and analysis (ASTM D4840-99(2018)e1). Keep interpretation separate from observation: when you add a judgment, label it as one and give its basis, which the EPA reporting procedure also asks for opinions and interpretations (US EPA Region 4, FSBPROC-003-R7, 2024).
How do you report areas a technical service visit could not observe?
A technical service visit report should list every area the visit planned to check but could not observe, give the reason, and turn each one into a named data request or a check on the next visit instead of a conclusion. An area not observed supports no finding, good or bad.
Typical gaps on a chemical technical service visit are a machine that was down for maintenance, a tank that could not be sampled safely while running, a shift that was not present, records the customer could not find, or a laboratory result still pending. Each is a fact about the visit, not about the process. Writing "system in good condition" over a gap turns a missing check into a claim, and the claim travels: the next reader, or the customer's auditor, cannot tell it from a measured result.
Report each gap on one line with four parts: the area, what was planned, why it was not done, and what will close it. The closing step should name who collects the missing data, by when, and what result would change the conclusion. A pending laboratory result, for example, is listed with the sample ID and the expected report date, and the conclusion states that it may change once the result arrives.
Keep areas not observed in their own section rather than scattered through the deviations. The process owner can then see the coverage of the visit at a glance, and the engineer knows which parts of the conclusion are provisional. A visit that covered 70% of its plan and says so (illustrative) gives the customer more to act on than one that covered everything in prose and nothing in records.
How should a technical service visit report split actions between customer and supplier?
A technical service visit report should give every action one owner, one due date and one side, customer or supplier, and tie it to the deviation or gap it closes. An action with two owners, or owned by "the team", usually has none, and an action without a date cannot be followed up at the next visit.
Split the action list by side before writing it. Customer actions are changes the plant makes itself: adjust a concentration, clean a filter, change a top-up routine, send a sample. Supplier actions are what your company owes: a laboratory analysis, a revised dosing recommendation, a product data question answered by your technical team, a return visit. Mixing the two lets each side assume the other is acting.
Customer quality systems already work this way in their own complaint forms. The SEW-EURODRIVE 8D form for suppliers lists each immediate measure and each corrective measure with a column for the responsible person, the date of introduction and a status that starts as open (SEW-EURODRIVE, 8D process specification, accessed 2026). A technical service report that uses the same columns is easier for the customer to load into its own tracking.
Write each action as a verb and an object with a measurable end: "Reduce sump concentration on machine 14 to the agreed 6 to 8% and record a refractometer reading after 24 hours" (illustrative) rather than "monitor concentration". The end condition is what the next visit checks. If an action depends on a pending result, say so and give the date the decision will be made.
What does an illustrative technical service report findings section look like?
An illustrative technical service report findings section for a metalworking fluid visit at a machining plant shows each observation against its agreed limit, with the observer, time and location, and keeps the area not observed on its own row. All limits, readings, machine numbers and names in this example are illustrative and do not come from a real visit. The table below shows how the findings decide which actions follow (illustrative).
Point and agreed limit | Observed (who, when) | Result |
|---|---|---|
Machine 14 sump, concentration 6 to 8% per fluid management plan rev. 3 | 4.5% by refractometer, factor 1.0 (J. Lee, 10:20) | Deviation, 1.5 points below limit |
Machine 14 sump, pH 8.8 to 9.4 per product data sheet rev. 5 | 8.6 by calibrated meter (J. Lee, 10:25) | Deviation, 0.2 below limit |
Central system, tramp oil below 2% per plan rev. 3 | 1.0% by settling test (J. Lee, 11:05) | Within limit |
Machines 21 to 24 | Not observed: line down for maintenance | No finding; sample on next visit |
The key row in this illustrative findings section is machine 14: concentration and pH are both low at the same point and time, which points to over-dilution at top-up rather than two separate problems (illustrative inference). The action list then reads, in this example: customer, maintenance lead, check the top-up mixer ratio on machine 14 by 2026-11-06; supplier, technical service engineer, return to sample machines 21 to 24 when the line restarts. The conclusion on page one says that the central system is within limits, machine 14 is not, and machines 21 to 24 were not checked. That sentence is shorter than a page of narrative and lets the process owner decide in one read (illustrative).
Why do technical service visit reports fail to get customer action?
Technical service visit reports fail to get customer action for five reasons: no conclusion on the first page, deviations without a stated limit, unobserved areas reported as good, actions with no single owner or date, and opinion mixed with observation. Each one makes the reader do work the writer should have done.
The first is the buried conclusion. A process owner who has to read four pages to find out whether anything is wrong will often forward the report rather than act on it.
The second is a deviation without its basis. "Concentration low" invites the reply "low against what?" Naming the limit and the document that sets it, with its revision, closes that question before it is asked.
The third is the silent gap. When an area was not observed but the report says nothing, the customer reads full coverage. If a failure later appears in that area, the report becomes evidence against the supplier.
The fourth is the shared action. "Supplier and customer to review dosing" has no owner, and it will still be open at the next visit.
The fifth is opinion written as fact. The EPA reporting procedure asks that opinions and interpretations be clearly identified as such and state the basis on which they were made (US EPA Region 4, FSBPROC-003-R7, 2024). A customer engineer who finds one unlabeled guess in a report tends to discount the measured findings next to it.
What should a technical service visit report checklist cover?
A technical service visit report checklist should cover the first page, the scope, each deviation, the gaps and each action, and every line should be true of the final report before it goes to the customer.
Page one states the overall conclusion in two or three sentences and lists the actions by owner.
The scope names the site, the equipment or areas covered, the visit date and the people present.
Each agreed limit names the document it comes from and its revision.
Each deviation gives the point, the limit, the observed value, the method or instrument, the time and the observer.
Each observation that depends on a sample carries the sample ID and its custody record.
Opinions and interpretations are labeled as such and give their basis.
Every planned check not done is listed with the reason and the step that will close it.
No conclusion covers an area that was not observed.
Every action has one owner, one due date and one side, customer or supplier.
Every action names the deviation or gap it closes and the condition that ends it.
Pending laboratory results are listed with the sample ID and the expected date.
The report says which findings may change when pending data arrives.
Lubinpla's field inspection task follows this order from your own documents and site history: it sets the scope and deviation criteria from the agreed standard first, attaches observer, time and location to each observation, gives each action an owner, and sends an area not observed to further collection instead of a conclusion, returning one cited document for your review.