Telling a heat transfer fluid supplier that “performance is poor” may refer to slower heating, temperature fluctuations, changing energy use or an unexpected laboratory result. These issues require different evidence. A clear report helps the supplier and equipment specialists investigate; it does not require the customer to prove the cause first.
For a leak, fire, injury or other urgent risk, follow the site's emergency procedures first. Do not wait for a complete information package.
1. Describe an observable change, not an assumed cause
State the previous condition, what has changed and the records used for comparison. “This batch took longer to reach the same product temperature” is more precise than “the fluid no longer transfers heat.” The first describes an observation; the second already assumes an unverified explanation.
Include any changes in batch size, starting temperature or process steps. Where original records are unavailable, identify statements as observations, recollections or estimates. Do not present an estimate as an instrument measurement.
2. Preserve the timeline without assuming causation
An issue appearing after a top-up, fluid change, maintenance activity or process adjustment deserves attention. However, “after” does not prove “because of.”
Record when the issue was first noticed, relevant changes and what happened subsequently. If several conditions changed together, retain all of them rather than selecting only the event that supports one hypothesis. Mark gaps as missing; do not invent entries to complete the timeline. A cause still requires supporting evidence.
3. Identify the fluid actually in the system
Provide the exact grade, batch or delivery identification, top-up and replacement records, and known mixing history where available. A brand name alone usually cannot identify the applicable product documentation.
Label unknown information as unknown. If the identity of residual fluid has not been confirmed, do not describe the entire system charge as the newly supplied product. Purchasing, warehouse and operating personnel can contribute the records they hold; one person should not be expected to reconstruct everything from memory.
4. Select evidence for the issue—not just an isolated screenshot
For temperature-response concerns, start with time–temperature records, measurement locations and batch conditions. For an unexpected test result, provide the complete laboratory report, sample identity and test method. Evidence requirements vary; collecting every possible record at the outset is not always useful.
Existing alarm, equipment-status and operating-change records can be reviewed by responsible technical personnel. Information gathering does not authorize site work. Do not undertake unapproved hot or pressurized sampling, dismantling or operating changes merely to fill a data gap. Retain original files instead of sending only cropped images without timestamps, units or explanatory notes.
5. Separate facts, hypotheses and unresolved conclusions
Observed fact: a temperature at a specified point fluctuated, supported by the original record.
Hypothesis to verify: the change may relate to load or flow, but this has not been established.
Conclusion requiring evidence: “the fluid has failed” or “the equipment is faulty” cannot follow automatically from the observation.
A supplier's preliminary response should also state the evidence available. A photograph or short description may support a request for further information, but it does not justify remotely declaring the product fault-free or the equipment safe to continue operating.
6. Agree the next action for each exchange
When contacting SCHULTZ or another supplier, prepare a one-page issue summary with the original records attached:
The specific change: previous versus current condition;
The timeline: first observation, related changes and subsequent behavior;
Fluid identity: grade, batch, top-ups, replacements and known mixtures;
Relevant conditions: equipment, operating state and comparison basis;
Existing evidence: original trends, complete reports and site records;
Open items: missing information, responsible person and agreed return date.
The summary does not replace the evidence. Agree who will provide each item, when it is expected, and where equipment specialists or a laboratory need to participate. Record technical cause analysis, commercial responsibility and the proposed response separately. Accepting an investigation is not an admission of liability, and offering a hypothesis is not a completed finding.
Conclusion
A useful support report makes known facts clearer rather than making a problem sound more serious. Preserve the timeline and original records, identify unknowns and verify possible explanations in turn. Customers need not prove the cause before asking for help, but neither party should assign blame without adequate evidence.
Reference and scope
Methodological reference: OSHA, Incident Investigation. This source supports the general approach of gathering facts, organizing events and considering multiple causes. This article is not a statutory incident-investigation procedure.
This is practical guidance on organizing support information, not a diagnosis, a brand response-time commitment, a compensation rule or permission to operate equipment. It does not promise that any manufacturer already provides all services described. Actual abnormal conditions must be handled under site procedures and the judgment of the appropriate qualified personnel.
