Capturing a Healthy Baseline So a Later Complaint Has Something to Compare Against

Why this matters

Six months from now, a customer calls and says a unit is making a noise it did not used to make. Neither of you can prove what it used to sound like. You are relying on your memory of a piece of equipment you may have seen once, and the customer is relying on a vague impression from someone who was not really listening at the time. Neither memory holds up well, and the whole conversation turns into "does this sound normal to you" with nothing solid behind it. A recorded baseline, captured while the unit was healthy, turns that guesswork into an actual comparison: this is what it sounded like then, this is what it sounds like now, here is what changed. That comparison is worth more than any amount of experience trying to recall a sound from memory.

When to capture a baseline

The right moments are the ones where you are already standing next to the equipment while it is known to be healthy, so capturing a baseline costs you almost nothing extra.

• At commissioning or initial install, while the unit is brand new and running exactly as intended. This is the cleanest possible baseline, because there is no ambiguity about condition.
• At the first service call, even if the unit is not new, as long as nothing currently indicates a problem. A baseline captured on a unit that is running fine today is still useful, even if you do not know its full history.
• Immediately after any repair, once you have confirmed the fix worked. This resets the baseline to the unit's new post-repair condition, which matters because a repaired unit rarely sounds identical to how it did before the failure, and the old baseline (if you have one) is no longer the right reference point.
• On any unit with a history of intermittent or hard-to-pin-down complaints, even outside a scheduled repair. If a customer has already mentioned "sometimes it does this thing" and you cannot catch it today, capturing today's baseline at least gives the next visit a real comparison point.

How to capture one, without special equipment

You do not need a vibration analyzer or lab gear to make this useful. A phone and a habit are enough.

1. Record a short voice memo of the sound itself, taken close to the equipment, in a quiet moment if you can get one. Thirty seconds is plenty. State out loud, on the recording, what unit this is, the date, and the operating condition (running normally, under what load, what speed setting).
2. Write a short note alongside the recording covering what you cannot capture in audio alone: the load the unit was under, the speed or setting, the ambient conditions (hot day, unit had been running a while, just started), and where you had your hand or ear when you assessed it. A sound recorded at idle is not the same reference as one recorded under full load, and the note is what keeps that distinction from getting lost.
3. Note anything already slightly off, honestly, rather than pretending every baseline is perfectly clean. If a unit has a faint, stable hum that has always been there and is not a concern, say so in the note. A baseline is supposed to capture "this is what normal looks like for this specific unit," not an idealized normal that does not match reality.

Where to store it so it is actually findable later

A baseline that lives only on your personal phone, in a folder you will never think to check again, does the customer and the next tech no good at all. Attach it to the unit's record the same way you would attach a photo of a nameplate or a repair note, so anyone pulling up that unit's history six months or two years later finds it without having to ask you personally.

• File it under the unit's own record, not a generic job note, so it survives a change in tech or a change in who answers the phone that day.
• Label the file with the date and a one-line description, not just a filename, so a quick scan of the record tells you which baseline is the current one if there is more than one.
• If the unit gets repaired later, add the new post-repair baseline as a new entry rather than replacing the old one. The history of how the sound changed over the unit's life is itself useful information.

How this changes the actual diagnostic conversation

Without a baseline, a follow-up complaint call goes like this: the customer describes something vague, you try to recall what this specific unit sounded like the last time you were there, and you are essentially guessing at whether this is new or has always been there. The conversation is subjective on both sides.

With a captured baseline, the same call goes differently: you pull up the recording and note from the last known-healthy visit, play it back or read the note, and you have an actual reference to compare the current complaint against. You can tell the customer specifically what changed, not just that something sounds different from your memory. And if the unit turns out fine, you have real evidence to show the customer that nothing has changed since the last healthy check, rather than just your word that it "sounds okay to me."

This does not replace hands-on, in-the-moment listening and feeling at the current visit. It gives that in-the-moment assessment something concrete to measure against, instead of asking you to remember a sound you heard once, months or years ago, on a unit that is one of hundreds you have serviced since.

Recap

1. Capture a short recording and a written note at commissioning, at the first service call, and right after any repair.
2. The note needs load, speed, and ambient conditions, not just the audio, since the same sound means different things under different conditions.
3. Store it on the unit's own record, labeled with date and description, so it is findable without asking you personally.
4. Add a new baseline after every repair rather than overwriting the old one; the change over time is itself useful.
5. A captured baseline turns a later complaint into a real comparison instead of a guess from memory.

References

• ISO 13373-1, Condition monitoring and diagnostics of machines, general procedures for baseline and trend data
• Trade-standard practice for equipment service-history documentation
• See related: The Vibration Signature Reference; A Whine, a Rattle, or a Hum: Which Points Where