The single device file: what you lose every time the same refrigerator is diagnosed twice

A refrigerator arrives at the counter. The clerk writes the serial on a receipt, the technician opens it, finds a failed start relay, replaces it, and the unit goes home. Four months later the same refrigerator is back with the same symptom. A different technician opens it, spends forty minutes finding the start relay, and discovers it is new. He now has a harder question: why did a new relay fail? The answer was in the first technician's head, and the first technician is on leave.

The cost of the second diagnosis

The visible cost is forty minutes of skilled labour. The real cost is larger and spread across people who never see each other. The customer, who has now explained the fault twice. The clerk, who could not tell the customer the unit had been here before. The owner, who may be about to replace a compressor under warranty when the actual fault is a wiring harness the first technician noted but did not have time to fix. And the manufacturer, who will receive a claim for the compressor and, if they are diligent, reject it.

In a center that sees thirty devices a day, repeat visits are not the exception. Depending on the product category, between one in eight and one in five devices will return within a year. Each return that starts from zero repeats part of the first visit's work and loses all of its findings. Over a year, that is weeks of technician time spent rediscovering what the center already knew.

Why the knowledge is lost

It is tempting to blame the technician for not writing things down. He did write them down, on the job card, which was filed, which is in a box. The failure is structural: the information was recorded in a place organized by date and by job, and it was needed in a place organized by device. Nobody converts between the two, because in a paper or spreadsheet system that conversion is a search, and a search under time pressure is a search that does not happen.

The same applies to the photo of the burnt connector, taken on the technician's phone, and the quotation the customer declined, saved as a spreadsheet on the counter computer. Each fact exists. None of them is attached to the device.

There is a second, quieter loss. When findings live with the person rather than the record, the center's knowledge walks out of the door with every resignation. A workshop that has trained three generations of technicians may hold less usable history than one that has kept a single file per device for two years, because the second one can be read by whoever is standing at the bench today.

What a device file is

A device file is not a folder. It is a record whose identity is the serial number, and to which every event in the device's life is attached as it happens: receipt, inspection notes, photos, parts issued, parts reserved, quotation offered, quotation accepted or declined, report sealed, delivery, and the invoice. The end customer is attached, and so is the referring brand or intermediary, because a warranty claim needs both.

Crucially, the file is not assembled afterwards by someone diligent. It is the place where the work is recorded in the first place. The technician does not write a job card and then copy it into the file; the job card is a view of the file. This is the difference between a system that depends on discipline and a system that depends on structure, and in a busy center only structure survives.

What changes on the second visit

When the same refrigerator returns, the clerk scans the serial and the screen shows the previous visit before the customer has finished describing the fault. The technician reads the first finding, sees the photo of the harness, sees that the relay was replaced and the harness was noted, and goes straight to the harness. Forty minutes become ten, the warranty claim is filed for the right part, and the customer hears the words every service center wants to be able to say: "we know this unit."

Here the causal direction should be stated carefully. The device file does not make technicians better diagnosticians. It stops the center from paying for the same diagnosis twice, and it makes the first technician's skill available to the second. The improvement is in retention of knowledge, not in its creation.

Beyond the single device

Once every device has a file, questions that were previously unanswerable become reports. Which model fails most often within warranty? Which fault is most frequently misdiagnosed on first visit? Which intermediary's units arrive with the most incomplete paperwork? A manufacturer will pay attention to a service center that can answer those questions with numbers, because most cannot.

None of that is possible while the knowledge is in job cards and phones. All of it follows naturally once the device, not the day, is the unit of record.

MOSAIC is organized around the device file. Everything else on the platform, from spare parts to sealed reports to invoices, hangs from it.