A service visit is useful long after the engineer leaves only when the visit produces a record that another person can understand. A group photo or a statement that the machine is “running well” may document that a visit happened, but it does not tell a buyer which machine was checked, what work was observed, what maintenance was performed or what still needs attention.
Build the visit record around evidence that the customer, supplier and future technician can reuse. The public TRISKEL project record provides one concrete example: MOTI visited the Brazilian customer on 12 May 2026 and discussed operation, maintenance, efficiency and possible upgrades around a MOTI-80-3NC. That documented visit is evidence of one customer interaction. It is not a promise of free on-site service for every order or proof of a universal production result.
Identify the exact machine before describing the visit
Start with the customer site, visit date, machine model, serial number and the supplied configuration. Add the controller or software version when it matters, installed tools, optional stations and any later modification. A model name alone may cover different electrical, control or tooling arrangements.
Photograph the nameplate and overall machine without exposing confidential factory information. Link the record to the original order, packing list, manuals and previous support cases. For the TRISKEL case, the public material identifies the MOTI-80-3NC; a technical service file should preserve the serial number and actual configuration as well.
Separate observed production from general performance claims
Record what was actually present during the visit: material type and size, the representative part or drawing revision, tools installed, operations observed and the inspection method. State whether the engineer watched normal production, a troubleshooting test, a training part or a specially prepared demonstration.
One observed part does not establish the machine’s output for every material, tool or operator. If the customer wants a repeatable production claim, use a defined batch and the sample acceptance record to capture measurements, conditions and approval. Keep customer business results outside the visit report unless the customer provides and authorizes the data.
Write findings, actions and results as three different fields
A useful maintenance entry has a clear sequence. First write the condition or symptom found. Then record the inspection, adjustment, cleaning, lubrication, repair or test performed. Finally state the observed result and the remaining limitation. Do not replace these fields with “checked” or “fixed.”
Include readings, alarm codes, photographs and test files when available. If the visit did not reproduce a reported issue, say so and list the conditions tested. The earlier guide on support information for a busbar machine issue can be used as the incoming record; the visit report should close or update each item rather than start a separate, disconnected story.
Control spare parts and consumables by identity
For every replaced, supplied or recommended item, record the part name, part number or drawing, quantity, compatible machine configuration, reason and installation status. Distinguish a consumable from a repair part and a backup part. If a removed item is retained for analysis, identify who holds it and the follow-up date.
The internal record says parts were given during the TRISKEL visit. That is a case-specific detail and does not mean all parts, freight or service visits are free. Commercial coverage remains subject to the quotation, warranty and service terms. Buyers should use the fixed delivery, installation and support guide to put those responsibilities in writing before the order.
Record training by task, person and evidence
“Operator training completed” is too broad. List the tasks covered, the personnel present, the language and documents used, and the practical check performed. Examples include tool installation, datum setting, safe startup, program selection, first-part inspection, normal shutdown and the approved response to an alarm.
Note any question that requires an engineering answer or a revised document. If an instruction, drawing or parameter sheet changes after the visit, keep the old revision, the approved replacement and the effective date together. The drawing revision control method helps connect the machine file, tool drawing, program and accepted sample.
Treat an upgrade request as a new controlled scope
A visit often reveals a request for different tooling, added positioning, software changes or another handling method. Record the current problem, the desired result and the existing machine interface. Add the representative part, material, volume and acceptance test. Do not describe a discussion as an approved upgrade.
The supplier should then issue a separate scope identifying supplied hardware or software, site work, responsibilities, price, schedule and validation. Compatibility must be checked against the exact serial number and configuration. A feature available on a new model may not be a safe or practical retrofit.
Close the visit with owners, dates and open evidence
End the report with a table of closed items and open items. Each open item needs an owner, next action, due date and the evidence required for closure. Typical evidence includes a replacement-part dispatch record, revised drawing, parameter backup, customer test result or a remote follow-up session.
Both sides should retain the final record and the attachments. This turns one visit into a maintenance history that helps future technicians understand what changed and helps buyers assess the supplier’s support process. It also prevents photographs, chat messages and part numbers from being scattered across unrelated conversations.
Ask for a sample record when evaluating a supplier
Before selecting a supplier, ask how service visits are documented, how machine identity and configuration are controlled, how parts are matched, how confidential customer data is handled and how open actions are followed. A redacted example can show the structure without exposing another customer’s information.
Send MOTI the machine model, serial number, supplied configuration, current symptom or improvement goal, one representative part or drawing and the available maintenance history. We can organize the first technical review and define what evidence is needed before deciding between remote support, parts, training or a site visit.
Sources: MOTI’s public TRISKEL project material and internal case, service-policy, maintenance and evidence records, checked 24 September 2026. The TRISKEL visit is a documented case, not a universal service entitlement or customer-performance claim.