Guide 

Standardize the decision process before the treatment routine

The useful distinction is between a common management process and a common exposure protocol. All locations can use the same record fields, document approval steps and fault-escalation route. Exposure time, positioning, mode, eye protection and cleaning instructions must remain tied to the exact device and the service permitted at that location.

The UK Medicines and Healthcare products Regulatory Agency (MHRA) describes identity, maintenance and training records as foundations of medical-device management. Its checklists address health and social care; they are a reference for this article’s management approach, not a declaration that every salon LED is a medical device or that every checklist is a salon legal requirement. [1]

For a salon network, organize the information into three linked records:

• Unit record: the physical asset, its configuration and its history.
• Device document pack: the instructions, manufacturer communications and technical evidence that apply to that configuration.
• Site decision record: who reviewed the local service, operator requirements and unresolved questions, and what the review actually established.

Use “not verified” when evidence is missing. A blank field, a supplier’s verbal assurance or another branch’s approval should not become a positive permission in the receiving branch’s records. This article provides a documentation framework; an actual operating procedure needs the models, instructions and local requirements in question.

Build an inventory that identifies the actual unit

Give each physical device a stable internal asset ID, separate from its room or branch. The ID should follow the unit when it moves. Keep the original serial number alongside it; an internal label should not replace the manufacturer’s identity.

The following is a suggested salon record design, not a prescribed regulatory form. Its purpose is to make mismatches visible before staff rely on an inherited workflow.

A QR code can point to this record, but the underlying file needs controlled access and an accessible fallback. If the code opens an obsolete IFU or the wrong serial number, it has made a documentation error easier to repeat.

Keep product identity separate from local permission

For US device verification, FDA establishment registration and device listing do not mean approval, clearance or authorization. A registration certificate is not a substitute for a matching regulatory record. [2]

An official record can also describe a narrower or different purpose than a salon’s service label suggests. FDA record K223544 names Guangdong Newdermo’s FM-01, FM-02 and FM-03 and gives mode-specific indications, including an infrared heating purpose. The summary describes a home-use wearable device. It is an example of why the model, mode and intended setting matter—not evidence that these units are suitable for shared salon use, or that any SaintQueen device has the same identity or status. [3]

For each branch, keep product documentation and the local operating review as separate evidence entries. Record the relevant authority or adviser and the question answered. Neither a manufacturer document nor a central SOP should be presented as proof that all branches or operators are legally permitted to offer the service.

Control workflow versions without mixing device protocols

A useful central standard operating procedure (SOP) explains how the network handles documents, discrepancies, training and release decisions. Attach separate device-specific instructions rather than combining incompatible settings into one “LED routine.”

Give each local workflow an identifiable revision and link it to the relevant device document pack. Distinguish the manufacturer’s IFU revision from the salon’s own document revision: changing a salon form does not change the manufacturer’s instructions.

Make every document change traceable

Use a short change record: what changed, where the information came from, which units and locations are affected, who reviewed it, and what remains unresolved. Preserve the superseded version for history while clearly identifying the version intended for current use.

For example, if a new IFU arrives, ask whether it applies to all units or only a specified configuration. Do not automatically replace every branch’s instructions because the filename looks newer. If applicability is unclear, retain the uncertainty and obtain written clarification rather than filling the gap from memory.

Give staff a way to report a discrepancy between the physical device, its display and the controlled instructions. A signature confirming that a file was read should not be the only evidence that an operator understands a changed workflow.

Use a transfer review, not automatic inheritance

When a unit moves, the receiving branch should be able to answer: Is this the expected serial number and configuration? Does its history include unresolved faults? Are the applicable instructions available? Has the receiving site reviewed its own requirements and staff readiness?

Keep transport, installation and cleaning methods within the relevant manufacturer documentation and local requirements. This management checklist does not supply packing instructions, electrical compatibility assumptions, cleaning agents or disinfectant contact times.

Treat a repair as a change with evidence to review

MHRA’s medical-device management guidance addresses device/software version records and testing before a repaired device returns to service. It also calls for maintenance providers to have appropriate test equipment. These are general management principles within that guidance’s scope; they do not supply an LED-specific test method or acceptance limit. [4]

For the salon record, separate three decisions: the provider completed work; the relevant checks were documented; the designated person accepted the unit for the intended local use. Avoid a single “fixed” checkbox that hides which decision is still pending.

What to ask about a replacement light source or controller

A suggested service-review note should identify the reported fault, work performed, changed parts or software, supporting report, unresolved restrictions and the person responsible for reviewing the result. Keep observations separate from a technician’s confirmed diagnosis.

If an output check is relevant to the repair, ask the manufacturer or qualified technical provider which check is required for that model and what its result establishes. Request enough detail to interpret the report: the tested configuration and mode, measurement method and conditions, instrument suitability and calibration information where applicable, units, and the source of any acceptance criteria.

Do not invent a network-wide output tolerance, calibration interval or test geometry. If the applicable criteria or method are missing, the record should say that performance acceptance remains unresolved. A visual impression that the unit is bright, or a number without its measurement conditions, should not close that question.

Make records comparable without claiming equal exposure

Branches can compare whether required fields and evidence are complete. Comparing technical readings needs a separate review of whether the methods and configurations are comparable. Keep administrative consistency distinct from an assertion of equivalent delivered exposure or clinical results.

A replacement or loan unit also needs its own asset and document review. Copying the unavailable unit’s service name into a booking system does not establish that the substitute supports the same workflow.

Name the people who resolve exceptions

For each branch, assign a local custodian and an alternate. At network level, name the document owner, the person who coordinates technical questions and the person who reviews local operating requirements. One person may hold several roles, but the record should make those responsibilities explicit.

Build the escalation route around a question that needs an answer, not simply a department name. Who decides whether an IFU applies? Who contacts the service provider? Who determines which branches are affected by a manufacturer notice? Who can authorize return to use within the applicable requirements?

Audit the chain of evidence

Use a selected unit or event to test whether another reviewer can reconstruct what happened:

• Find the unit and confirm that its record matches its location and identity.
• Retrieve the document revision that applied at the time of the event.
• Follow a repair or change through to its supporting evidence and review decision.
• Check that an unresolved action has an owner and a visible status.
• For a notice affecting several branches, distinguish “message sent” from “applicability checked and action recorded.”

Set the review schedule using the applicable requirements and risks of the actual fleet. This article does not establish a universal monthly or annual audit interval, or a record-retention period. When reviewing events involving clients, link to appropriately protected client records rather than exposing personal information in a widely shared equipment list.

Common assumptions that weaken a multi-site system

• “Same brand means interchangeable.” A brand label does not identify the model, configuration or applicable instructions.
• “The central SOP makes every branch compliant.” A common process still needs a documented local review.
• “A service invoice closes the fault.” Work completion and acceptance for return to use should be distinguishable.
• “Matching records guarantee matching results.” Complete records improve traceability; they are not evidence of equivalent exposure or outcomes.

Practical questions

What if a device has no readable serial number?

Record the identification problem and use a temporary internal reference to track it. Ask the manufacturer or service provider how the unit can be identified reliably. Do not infer the model or serial number from its appearance or a nearby unit’s paperwork, and do not treat the temporary reference as resolving suitability for use.

Can the salon use one spreadsheet for the whole network?

A shared spreadsheet can support the proposed framework if it preserves changes, links each unit to the right documents and makes responsibility and availability clear. Evaluate whether staff can retrieve the applicable record at the point of use, including when normal access fails. The choice of software does not itself verify the equipment.

What should happen if the manufacturer’s answer is only verbal?

Log who answered, when, the question and what was said, then request written, model-specific clarification. Label the note as an unconfirmed communication until its authority and applicability are resolved. Do not silently promote it into an approved protocol.

How can branches review service complaints without asserting device equivalence?

Retain the asset identity, relevant configuration and event context. Review whether documentation or escalation failures recur across sites. Similar complaint wording alone does not establish the same cause, and a difference in complaints does not prove one model is safer or more effective.

Start with the units whose status is unclear

Reconcile the physical inventory with the records, identify missing or mismatched documents and assign each open question to a named person. Expand the system from verified unit and site decisions. That gives the network a consistent way to manage differences without pretending those differences have disappeared.