How to document verbal technical advice after a site visit
Summary
Put verbal technical advice on record in four steps: write it the same day, state the question and conditions, note assumptions and limits, and get written confirmation. It fits advice a supplier's engineer gives a customer on a chemical site visit, such as a dosage, a cleaning step or a product change, when no written report was agreed beforehand.
Asked two days after a 30-minute guided tour, participants recalled at best about 25% of it, though the details they did recall were 94% accurate (Diamond, Armson and Levine, 2020, reported by APS, 2021).
The UK MHRA GxP data integrity guidance, Revision 1 of March 2018, lists 5 ALCOA attributes for records: attributable, legible, contemporaneous, original and accurate (MHRA, 2018).
ISO 9001:2026, the sixth edition dated 2026-09, replaced ISO 9001:2015 and keeps clause 8.2.1 Customer communication and clause 7.5 Documented information (ISO 9001:2026).
ISO gives organizations certified to ISO 9001:2015 3 years to move to ISO 9001:2026 (ISO, 2026).
This method covers recording technical advice. It does not decide who is liable when advice goes wrong; that question belongs with your legal or quality function. Advice that changes a hazardous procedure also needs the customer's own change process and the product's safety data sheet (SDS).
When does verbal technical advice from a site visit cause problems later?
Verbal technical advice from a site visit causes trouble later when results differ from what the customer expected and nobody can show what was said, under which conditions, or with which limits. Take an illustrative case. An engineer reads a high dip-slide count at a cooling tower and suggests raising the biocide dose. The customer applies the change to a second system with different water, and three months later the two sides remember the advice differently.
Memory is the weak link. In a controlled study, people asked two days after a 30-minute guided tour recalled at best about 25% of it, even though most details they did recall were correct (APS, 2021). What drops out is exactly what matters here: the conditions, numbers and caveats around the advice.
The problem usually surfaces in one of three ways:
A complaint, where the complaints process asks what the customer was told. ISO 10002:2018, confirmed in 2023, gives guidelines for analysing and evaluating complaints (ISO, 2018).
A handover, where the next engineer inherits a customer along with promises nobody wrote down.
A repeat problem, where the team cannot tell whether the earlier advice was followed, changed or ignored.
Each time, the record that settles the question is the one written close to the visit, with the conditions attached.
What do you need before you document verbal technical advice?
Before you document verbal technical advice, collect the visit notes or photos taken on site, the readings the advice relied on, and the place where your company keeps customer records. Gather them before you write, so the record cites evidence rather than memory.
Your rough notes, voice memos or photos from the visit, each with the time it was taken.
The measured conditions behind the advice: concentration, pH, temperature, dose rate or test results, each with its unit and the person who measured it.
The product identity: trade name, product code, and the SDS and technical data sheet (TDS) revision you referred to.
The names of the customer contacts who heard the advice.
Your company's existing procedure for customer communication, if there is one. A supplier running an ISO 9001 quality management system may already cover this under clause 8.2.1 Customer communication or clause 7.5 Documented information (ISO 9001:2026), so use that form before inventing a new one.
The name of the technical lead who reviews advice before it goes to the customer for confirmation.
If the customer took a reading and you only heard the result, write that down too. A condition you did not measure yourself is an assumption, and the record should say so.
Documenting verbal technical advice step by step
The four steps break down into seven actions, done in this order on the day of the visit.
Write the record the same working day, before your next visit. The AEC guidance on inspector comments recommends writing them down immediately after the inspection, while they are fresh (AEC).
Write the customer's question in one sentence, in their words where you can.
List each condition the advice relied on, with value, unit, method and who measured it, for example "pH 9.1 by handheld meter, measured by the customer's operator" (illustrative).
State the advice in one sentence: the action, the amount and the timing.
Write down the assumptions and limits: what you did not check, which system the advice applies to, and what result would change it.
Send the record to your technical lead for review, and note the reviewer and the date.
Send the reviewed record to the customer contact and ask them to confirm or correct it by a set date.
Attach the photos, readings and documents you cited to the same record, so a reader can check the advice against its evidence. If the advice changes a step involving hazardous chemicals, name the SDS section and the customer's change procedure inside step 4.
What should a record of verbal technical advice include?
A record of verbal technical advice should include the customer's question, the conditions and readings it relied on, the advice itself, its assumptions and limits, and who reviewed and confirmed it, with dates. Each part answers a question someone will ask later.
Question: the problem the customer raised, so the advice is read in context.
Conditions: the measured values with units and source, so a reader can tell whether the advice still holds once conditions change.
Advice: one action with amount and timing, not a summary of the conversation.
Assumptions and limits: the systems it does not cover and the result that would change it.
People and dates: who gave it, who heard it, who reviewed it and who confirmed it.
Regulated record-keeping follows the same logic. The MHRA guidance expects data to be "attributable, legible, contemporaneously recorded, original (or a true copy) and accurate" (MHRA, 2018). Construction sites apply a similar idea to verbal site instructions: confirmation of verbal instruction (CVI) forms record the person issuing the instruction, the recipient and the scope of instructed work (SafetyCulture).
A record built this way is also what lets a colleague find the commitment months later. Searching for past commitments is covered in how to find what was promised to a customer in past visits.
How do you get the customer to confirm verbal technical advice in writing?
To get written confirmation, send the reviewed record to the contact who heard the advice, ask a specific yes-or-correct question, and set a reply date. A short message such as "Please confirm this matches what we agreed on 14 October, or tell us what to change, by 21 October" (illustrative dates) gets more replies than a full report with no question.
Keep the request small: the question, the conditions, the advice and the limits, not your full visit notes. Address it to the person who heard the advice, not to a purchasing contact who was not there.
Regulated practice accepts that confirmation often comes after the record is written. In the MHRA scribe model for GxP work, the record identifies both the person performing the task and the person writing it, and the performer should countersign "wherever possible," with the countersignature accepted as retrospective (MHRA, 2018). For a supplier's advice, the customer's reply does the same job.
If the customer corrects the record, update it and keep the first version, so the change stays visible. If no reply comes by the date, note that the request was sent and went unanswered, then raise it at the next contact. An unanswered request is still evidence that the advice was shared in writing.
How do you check a record of verbal technical advice?
Check a record of verbal technical advice against eight points before you file it. Each point either passes or tells you what to fix, and together they decide whether the record will hold up when someone reads it months later.
Check | Pass | Fail and what to do |
|---|---|---|
Written the same day | Record dated the day of the visit | Write it now and note the delay in the record |
Customer question stated | One sentence, in the customer's terms | Ask the contact what they asked, then add it |
Conditions with units and source | Each value has unit, method and who measured it | Mark unmeasured values as assumptions |
Advice in one sentence | Action, amount and timing stated | Rewrite; split several pieces of advice into items |
Assumptions and limits | Systems not covered and what would change the advice | Add them or mark the advice provisional |
Reviewer named | Technical lead and review date recorded | Send for review before confirming with the customer |
Customer confirmation | Reply filed, or request date and no reply noted | Send the confirmation request with a reply date |
Evidence attached | Photos and readings attached to the record | Attach them or note they do not exist |
The conditions row fails most often, because people remember the advice but not the readings behind it. The confirmation row fails next: a record that was never sent shows only what you believe you said.
A record that passes every row is one a second engineer can act on without calling you. File it where the next person to visit that customer will look first, under the customer's name and the visit date, not in a personal folder or a phone note. Lubinpla work logs can hold this record: write the advice and its assumptions in a work log right after the visit, get the technical lead's review in its comments, and attach the photos and files to the same log.
Frequently asked questions
How soon after a site visit should verbal technical advice be written down?
Write it the same working day, before the next visit. In one controlled study, people asked two days later recalled at best about 25% of a 30-minute tour (APS, 2021). If you write it later, note the delay in the record itself.
What if the customer will not confirm the advice in writing?
Keep the record, note the date you sent the confirmation request and that no reply came, and raise it at the next contact. A dated, reviewed record that was sent to the customer is far more useful than nothing.
Should a passing remark in the hallway be recorded?
Record it if the customer could act on it. A remark such as "you could try a lower concentration" becomes advice once someone changes a process because of it, so treat it like any other advice and add the conditions and limits.