What goes in a lube oil analysis failure report for the customer?

This answer covers a written report that a lubricant supplier, distributor or service provider sends to the customer after investigating a lubricant-related failure or complaint. It does not cover the laboratory's own analysis certificate, warranty claim forms set by an equipment maker, or reports for electrical insulating oils and heat transfer oils, which ISO 14830-1 places outside its scope (ISO, 2019).

Which equipment and sample details must a lubricant failure report include?

A lubricant failure report must include the equipment identity, its operating conditions, the oil in service and the sample details, because the customer cannot read any oil analysis result without them. ASTM D4378-24 says that "for proper interpretation of the results, many factors, such as type of equipment, operation workload, design of the lubricating oil circuit, and top-up level, should be taken into account" (ASTM, 2024).

For the equipment, give the asset ID the customer uses, the machine type, operating hours, the load or duty at the time of failure, and recent maintenance. For the oil, give the product and viscosity grade in service, hours on the oil, the last oil change date and recent top-up quantities. A marine guide to lube oil analysis lists the same items for the sample form: machinery identification, oil type, operating hours, oil-change date, recent topping-up quantity and any observed abnormality (Merchant Navy Decoded, 2026).

For the sample, give the sample point, date, method and laboratory report number. Sample quality decides whether a lubricant failure report can be trusted. The same guide advises sampling from a representative circulating-oil point, flushing the sampling line first, and avoiding a sample taken right after new oil is added (Merchant Navy Decoded, 2026). If a sample broke one of these rules, say so in the lubricant failure report next to the result it affects.

How should oil analysis results be shown in a customer failure report?

Oil analysis results in a customer failure report should show each test with its method, unit, current value, baseline and the limit used, with the source of that limit named. A value without a baseline or a limit gives the customer a number but no meaning.

Group the oil analysis results the way the customer will act on them: oil condition (viscosity, acid number, base number, oxidation, additive elements), contamination (water, particle count, contaminant metals, fuel or coolant), and wear (wear metals and their pattern). For particle counts in hydraulic systems, report the ISO 4406:2021 code, the standard for coding solid particle contamination in hydraulic fluids (ISO, 2021).

State the baseline for every result. A lab report on lube oil compares the oil with the manufacturer's limits, previous sample results and the normal operating condition of the equipment, and viscosity "should always be compared with the fresh-oil value and the equipment manufacturer's limit" (Merchant Navy Decoded, 2026). Name which limit you used: the equipment maker's, the oil supplier's, or a site limit set from the customer's own data. ASTM D7720-21(2025) gives statistical methods to evaluate alarm limits and states that its techniques do not supersede limits established and validated by an original equipment manufacturer (ASTM, 2025). Show at least the previous samples beside the current one, because a series of reports often reveals a developing problem before an absolute alarm limit is reached (Merchant Navy Decoded, 2026).

How do you separate confirmed conclusions from likely causes in the report?

Separate confirmed conclusions from likely causes in a lubricant failure report by labeling each conclusion: confirmed when a test or inspection shows the cause directly, likely when the oil analysis pattern fits the cause but nothing has confirmed it yet, and not determined when the evidence does not point either way.

A confirmed conclusion names the evidence. Water above the limit plus a cooler that failed a pressure test is confirmed water ingress through the cooler. A likely conclusion names the test that would confirm it. Rising iron and chromium together may require investigation of piston-ring and liner condition, and rising copper and lead may indicate bearing distress (Merchant Navy Decoded, 2026), but each needs an inspection before it is confirmed. Write "likely cause: ring and liner wear; confirm by borescope inspection of cylinders 2 and 4" rather than "cause: ring wear".

Oil analysis results alone rarely confirm a mechanical cause. The marine guide notes that a "normal" report does not guarantee that the machinery is free from defects, and that oil analysis should be evaluated together with alarms, temperatures, filter condition, vibration data and inspection findings (Merchant Navy Decoded, 2026). If the investigation looked at the lubricant itself, say what was tested: a retained sample of the same batch, the batch certificate, or neither. A customer reads "the lubricant met specification" as confirmed, so write it only when a retained sample or certificate supports it.

Which internal notes, scores, costs and stock data stay out of the customer report?

Internal review notes, reviewer comments, confidence scores, internal case history, cost, margin and stock data stay out of the customer lubricant failure report, unless the recommendation depends on one of them. The table below decides, item by item, what goes in the customer report and what stays in the internal record.

The key row is the last one. If the recommendation is an oil changeover, the customer needs the date the replacement oil can be delivered, but not the stock quantity, the cost or the margin behind it. Review history and confidence scores stay out because the customer acts on the conclusion and its label, not on how the team reached it. Internal case notes that refer to other customers' failures also stay out, because they describe accounts this reader has no right to see; restate the finding they support in the customer's own equipment terms instead. The broader rules for any customer document are in what to leave out of a technical report for a customer.

What recommendations should a customer lubricant failure report make?

A customer lubricant failure report should make recommendations that each name one action, who owns it, when it is due, and the check that shows it worked, usually a follow-up oil sample. A recommendation without an owner and a date tends to stay open.

Order the recommendations by the conclusions they answer. For a confirmed cause, recommend the corrective action, for example repair the cooler, change the breather or correct the relubrication amount. For a likely cause, recommend the confirming test first. For every case, recommend a follow-up sample after the corrective action; the marine guide lists a confirmation sample after corrective action among the chief engineer's actions on a report (Merchant Navy Decoded, 2026).

Tie sampling and testing intervals to the practice for the equipment. ASTM D6224-23 covers in-service oil monitoring for auxiliary power plant equipment, such as gears, hydraulic systems, diesel engines, pumps and compressors, and includes sampling and testing schedules and recommended action steps (ASTM, 2023). It does not cover steam and gas turbines, which ASTM D4378-24 covers (ASTM, 2023).

If a recommendation includes draining, flushing or changing the oil, write the safety and disposal step into the recommendation itself: handle the drained oil and any flushing fluid as its safety data sheet (SDS) directs, and dispose of it under the used oil rules of the site's jurisdiction, which in the United States are the used oil management standards in 40 CFR part 279 (US EPA, 2026).

How do you check a lubricant failure report before it goes to the customer?

Check a lubricant failure report before it goes to the customer by confirming that the reader was set before writing, that every result and conclusion can be traced to evidence, and that nothing from the internal record column reached the customer version.

Use this checklist:

1. The sample ID on every result matches the asset ID and sample date in the equipment section.

2. Every oil analysis result shows a method, a unit, a baseline and a limit with its source.

3. Every conclusion carries a label: confirmed, likely or not determined.

4. Every likely conclusion names the test or inspection that would confirm it.

5. Every recommendation has an owner, a date and a follow-up check.

6. No review history, reviewer comments, confidence scores or internal case notes appear.

7. Cost, margin and stock appear only where a recommendation depends on them.

8. The laboratory's own report is attached unchanged, so the customer can see the raw values.

A second person who did not write the report should run the checklist. Lubinpla, an applied AI company for specialty chemicals technical work, sets the reader of a document when the task is proposed and confirms it on the approval card; for a customer reader it leaves out the work history, confidence scores and internal record sources, and keeps cost, margin and stock only as far as the document's purpose needs them. A person still reviews and approves the report before it is sent.