Calibration and the Service Log: The Invisible Part of a Stable Result

Calibration is easy to ignore precisely because good calibration produces no drama. A value appears on the screen, the platform behaves as expected, and the operator can concentrate on the client. That quiet routine depends on a chain of measurement, maintenance, software, delivery components, cooling, and authorised checks. When one link changes, the displayed value may no longer tell the same story.

The operator is part of this chain but is not the service engineer. Their role is not to open a panel, adjust an internal component, defeat an interlock, or perform an improvised output test. It is to complete the checks permitted by the exact IFU, recognise observable deviation, stop use, label the equipment accurately, and create a record that an authorised person can act on. A service log turns “something felt odd” into traceable information.

Separate routine observation from calibration and repair

Calibration connects an indicated or intended output with a verified measurement under a defined procedure. It requires authorised methods, suitable test equipment, traceability, acceptance criteria, and competent personnel. Pressing a built-in button may begin a manufacturer-defined check, but it does not give the operator permission to reinterpret limits or create a substitute procedure.

The useful analogy is a weighing scale. Looking at an intact display, stable base, and a system error is an everyday check. Deciding whether the scale measures accurately requires a controlled reference and documented method. The analogy has a limit because a laser has optical delivery, pulse timing, cooling, interlocks, software, and multiple accessories. The practical point remains: observation and metrology are not the same job.

Before a shift, the operator inspects only what the IFU and clinic procedure assign to them. This may include the external condition of the handpiece, cable, connector, contact window, pedal, cooling path, warning indicators, eyewear identification, interlocks, and system messages. The exact list comes from the model documentation, not from a generic blog checklist copied across platforms.

Observable does not mean trivial. A crack, pitting, clouding, residue that cannot be removed by the authorised cleaning process, a fluid leak, a damaged cable, an unusual sound, unstable airflow, missing cooling, unexpected resistance at a connector, or a recurring error can all change the safe state.

The operator records what was seen, heard, or displayed without guessing which internal part failed.

Cleaning is not repair. If a reusable contact surface is cleaned according to manufacturer instructions and remains marked, damaged, or unclear, repeating harsher cleaning or polishing it is not persistence. It is an unauthorised change to an optical path. The device or affected handpiece is removed from use and passed to the defined technical route.

The US Food and Drug Administration’s medical-laser overview distinguishes medical lasers as regulated devices with hazards that require appropriate controls. For the clinic, that means the model’s documentation and service arrangements matter more than a staff member’s confidence with tools. Familiarity is not calibration authority.

Record the deviation in a form that can be investigated

A useful service entry starts with identity: date and time, device model, serial or internal asset number, installed handpiece, software version when relevant, operator, room, and current status. Without device identity, “laser error again” cannot be connected to previous maintenance, another handpiece, or a later incident.

Next comes the observation in ordinary, precise language. Record the exact error code or message, when it appeared, whether the system completed its permitted startup check, what cooling indicator showed, and what changed from normal. “Stopped after the third activation with code shown in the attached approved record” is useful. “Machine was weird” makes the service engineer perform archaeology.

Context matters, but it should not become a repair theory. Note whether the change appeared at startup or during delivery, which authorised mode and handpiece were selected, whether there was a smell, smoke, sparking, loss of cooling, unstable sound, unexpected display behaviour, or a sudden change in client sensation. Do not open the housing to find a cause or repeatedly trigger the fault to obtain a better video.

When a deviation appears during a procedure, treatment stops. The operator preserves the displayed configuration, time, anatomical location, observed tissue response, client feedback, and areas not treated. If severe or escalating pain, blistering, abnormal colour change, suspected burn, eye exposure, smoke, fire, or another adverse response is present, the clinic also opens its clinical adverse-event route.

Equipment investigation and client care are linked, but neither should disappear inside one vague note.

The device status must be visible. A verbal message to the next shift is not isolation. Clinic procedure should identify the unit or handpiece as unavailable, prevent accidental booking or use, and name the responsible person who receives the escalation. The operator does not test it on another client, a neighbouring area, or a colleague to see whether the fault “comes back.”

The log should also include what the operator did within authority: stopped delivery, placed the system in the prescribed safe state, isolated it according to clinic procedure, notified the named role, preserved records, and submitted a service request. Avoid “fixed,” “reset,” or “calibrated” unless the documented authorised action genuinely supports that word.

Patterns become visible only when entries use consistent identities and language. A cooling warning that appears after several services, repeated damage to one handpiece, or errors following a software update may not be obvious from separate messages. A single service history allows the responsible lead and authorised service provider to see recurrence without relying on memory.

Return to use is a documented decision, not a successful restart

Powering on without an error is not proof that the original deviation has been resolved. A fault may be intermittent, linked to one mode or handpiece, or absent until load is applied. The device remains unavailable until the person authorised by clinic policy has the service documentation, required verification, and a defined basis for return.

The service record should state what was inspected, what component or software was changed when disclosure is appropriate, what authorised tests were completed, their outcome, any new limitation, and who released the system.

“Engineer came” is not a return-to-use record. It provides neither scope nor acceptance.

Software updates, handpiece replacement, calibration, and preventive maintenance belong in the same history even when no fault occurred. A new version can change interface labels, stored presets, pulse delivery, warnings, or required checks. The team should not assume that familiar screen values or workflows survived unchanged. Current documentation and any required retraining come before use.

The first authorised operational check after service follows the manufacturer and clinic procedure. It is not an opportunity for staff to invent a more convincing stress test. If the required check is uncertain, work waits for clarification. An operator’s desire to be helpful should not become an undocumented validation protocol.

Treatment records also need the correct equipment identity after return. If a handpiece or unit was replaced with another of the same model, the internal asset changes. The old clinical history does not automatically describe the replacement. The link between client record and service history must remain specific enough to reconstruct which system delivered each exposure.

The BMLA treatment guidelines place equipment maintenance, local rules, training, and documented safety controls inside the treatment system. The practical lesson is not that every operator becomes a maintenance department. It is that everyday observation, formal service, and clinical documentation must meet in one traceable record.

A stable result does not come only from repeating the same technique. It also depends on the same screen value continuing to mean what the verified system says it means. The operator protects that continuity by noticing change early and refusing to improvise. Calibration remains the service specialist’s work. Making a deviation impossible to ignore is the operator’s.