When a mechanic types a fault description into our diagnostic platform, the median length is exactly 40 characters. That is about five words. We looked at 2,800 diagnostics from our own data where a written description was provided, and the results show a massive disconnect between how software designers think technicians write and what actually happens on the shop floor.
The reality is that technicians write short, concrete, symptom-first descriptions in their own language. Any tool that expects textbook phrasing or highly structured inputs is going to fail at the very first input box.
The reality of the one-line complaint
Out of 3,564 total diagnostics run through our platform, 79 percent included a written description. The average length of these descriptions is 92 characters, with an average word count of just 15 words.
Technicians are busy, and they write exactly what they need to convey the problem and nothing more. We found that 16 percent of all descriptions are just one or two words. These are barely a prompt, consisting of terms like “motorlampa”, “airbag”, or “misfire”. Another 43 percent are a single sentence of 26 to 80 characters, providing a symptom and a tiny amount of context.
If a diagnostic system requires a detailed narrative to function properly, it will struggle in a real workshop. Only 6 percent of the descriptions we analyzed contained a full case history of 300 characters or more. The vast majority of the time, the input is brief and to the point.
Symptoms over systems
When we look at what the complaint actually is, the technician’s framing is almost always rooted in the immediate, visible symptom.
By far the most common entry is the warning lamp. In 22 percent of cases, an engine or dashboard lamp is named as the primary reason for the visit. The most repeated two-word phrase across all languages is “motorlampa lyser”, appearing 71 times, followed by “check engine” at 52 times.
The next most common complaints are classic driveability issues. Misfires, rough running, juddering, or uneven idle account for 9 percent of the descriptions. Another 6 percent simply state that a function or component does not work, while power loss or limp mode makes up another 6 percent. Crank no start situations account for 5 percent.
Very few technicians use the diagnostic box to paste in scan tool definitions. Only 3 percent of descriptions are pasted fault-code definitions, and another 3 percent are just raw fault codes with no accompanying text.
Speaking the workshop language
Technicians describe faults in the language they actually speak in the bay. In our dataset, 52 percent of the descriptions were in Swedish, 31 percent in English, and the rest split across German, Romanian, Russian, Italian, Finnish, and Bulgarian.
They use abbreviations, local slang, and shorthand. They type “Crank no start no injector pulse” or “AC Kompressor ur funktion”. They do not write “The vehicle exhibits an intermittent misfire under heavy load conditions”.
Diagnostic tools need to meet technicians where they are. If a platform cannot understand a localized, five-word symptom paired with a raw fault code, it is not built for a modern independent workshop. It has to understand the context behind “motorlampa” just as well as a 300-word essay on fuel trims.
Take a look at the job cards in your own workshop this week. Are your technicians writing essays, or are they getting straight to the point with five words and a fault code?
