A servicing record can turn into a complaint

Servicing is a defined activity, not a catch-all for post-sale work

Clause 7.5.4 covers repair and preventive or routine maintenance carried out on a device already in the field, aimed at restoring or maintaining the safety and performance the device was specified to have. It only engages where servicing is itself a specified requirement for the device — some device types are serviced by design, and a single-use or non-serviceable device simply doesn't trigger the clause at all. Where it does apply, the organization has to maintain documented procedures, the instructions needed for the work to be performed correctly, and the reference materials and measurement data used to confirm the device still met specification once the servicing was done — the maintenance-side counterpart to production process documentation, applied after the sale instead of before it.

The screening step is the clause's real requirement

The part of 7.5.4 that does the most work isn't the procedure requirement; it's the instruction to analyze servicing records — the organization's own and any a supplier performs on its behalf — to determine whether the information should be handled as a complaint, and separately, whether it should feed the improvement process. A repair that traces back to ordinary wear generates one kind of record. A repair that traces back to the device failing to perform as intended is a complaint by definition, whatever the technician who logged the work order called it. Clause 7.5.4 doesn't leave that classification to whoever happens to close the ticket.

Not-a-complaint still needs a reason on file

When the analysis concludes a servicing record isn't a complaint, the clause doesn't let that conclusion stand unsupported — it calls for the justification itself to be documented, the same discipline a complaint record has to apply to its own intake decision before a report becomes a CAPA. A servicing log that records only “not a complaint” with nothing behind it has produced a conclusion no one downstream can independently check, which functions, on audit, close to not having made the determination at all.

Where the two records have to meet

Because the screening step feeds the improvement process whichever way it resolves, a servicing program that keeps its own trend data walled off from the complaint-handling function's has broken a loop the rest of Section 8 depends on. An active surveillance system is supposed to catch a device failing repeatedly in the field regardless of which door the first report walked through — a complaint line or a field technician's repair ticket — and a servicing log that never talks to the complaint database can miss a pattern the complaint file alone would have caught two reports sooner.

A supplier's servicing work is still the manufacturer's record

Clause 7.5.4 doesn't stop at work the organization performs itself; it names servicing carried out by a supplier on the organization's behalf as the same kind of record, subject to the same screening step. A manufacturer that contracts field service to a distributor or a third-party technician doesn't get to treat that arrangement as outside the clause's reach — the analysis of whether a given repair belongs in the complaint file still has to happen, whether the person who filled out the work order was on payroll or not. That puts a documented flow-back requirement on the servicing contract itself: a supplier agreement that never specifies how repair records reach the manufacturer for this screening has left a gap the clause doesn't allow, no matter how well the repairs themselves are performed.

Where this meets the rest of the file

A servicing-record template built around Clause 7.5.4's actual screening step — the complaint determination, the documented reason when the answer is no, and a shared trend feed into the same improvement process the complaint file already runs through — is previewed in the launch catalog. If your program routes servicing data differently, the shelf takes that correction directly.