Driver Procedures

Unusual noises in a company car — how should the driver describe them?

Short and precise — that is how a report of a sound from a company car should look. This text will show what to enter, which recordings to make and when to stop driving.

9 September 2026 Redakcja FleetPoint

Why an accurate description of the sound is important

The clearer and more orderly the description, the faster the workshop will know where to look for the fault. A precise description speeds up diagnosis and reduces repair costs — after receiving a well completed report, a mechanic is less likely to immediately schedule extra inspection visits.

Remember, however, that the driver’s description does not replace a workshop inspection. Your report is meant to help set priority and identify the most likely areas to check — the final diagnosis is always made by the mechanic.

What must be included in the report — quick checklist

The report should be short but complete. Below is a list of fields that will significantly facilitate handling the case and decision-making by the workshop or repair coordinator.

  • Basic vehicle data: make, model, year, registration number.
  • Odometer reading (km) and fuel level, if relevant.
  • Date and time of the event and exact location (address or GPS link).
  • Description of the sound: type (from the list – see the “Vocabulary” section), intensity (quiet/medium/loud), whether it is continuous or intermittent.
  • When it occurs: on acceleration from standstill, when accelerating, when braking, during turning, at constant speed, only on bumps, etc.
  • Conditions: vehicle speed, road surface, load (cargo/passengers), temperature (cold/warm engine).
  • Accompanying symptoms: vibrations, pulsation in the brake pedal, dashboard warning lights, smell of burning, fluid leaks.
  • Attachments: short audio/video recording, photos of the source area, photo of the dashboard with warning lights.

Vocabulary — how to describe the sound to be understood

Use simple, commonly understood words. The terms below will facilitate communication with the workshop and should be included in the company’s report form.

  • Knocking / knock (e.g., “knock when passing over bumps”): short, distinct impacts — often associated with suspension or loose components.
  • Squeal / squeaking (e.g., “squeal when braking”): a high, whistling sound — may come from the brakes or a belt (orientation only).
  • Hum / whir / drone (e.g., “hum at 90 km/h”): a steady, low-frequency sound — can be related to wheel bearings, tires or the drivetrain.
  • Vibration / shaking: felt in the steering wheel or seat, often accompanies sounds and helps locate their source.
  • Rattling / clattering: repetitive, metallic sounds — may indicate play in axles, the exhaust system or moving parts.
  • Metallic cracks / snaps: short, sharp sounds when load changes, for example.
  • Thudding / jolts: low impacts that can be felt in the bodywork.
  • Hissing: a high sound resembling gas/air escaping — check seals or hoses.

How to record and take photos — practical rules

Recordings and photos greatly help the workshop. Make sure they are useful: short, focused and taken safely.

  • Record only when the vehicle is parked and it is safe to do so — do not record while driving.
  • Make a short audio clip (10–30 s) presenting the sound while simulating the conditions in which it occurs (e.g., braking while stationary — if possible and safe).
  • If the sound occurs only while driving, record an exterior video (someone else holding the phone) or capture playback from inside the car after stopping — it is important that the clip conveys context (e.g., speed on the speedometer).
  • Take a photo of the area where you think the sound originates (wheel, wheel arch, underside, engine) and a photo of the dashboard with the warning lights on.
  • Label the recording: date, time, mileage (km) and a short summary — this will help match it to the report.

Priorities — when to stop immediately

Not all sounds require an immediate stop, but some signals are dangerous and must not be ignored. The appearance of these symptoms means you should safely pull over and call for help.

  • Loss of engine power or sudden change in vehicle behavior (e.g., the engine stalls).
  • Smoke, strong smell of burning or visible flames.
  • Severe steering vibrations, wheel locking or sudden difficulty braking.
  • Visible fluid leaks (oil, brake fluid, fuel) or dripping from an unknown location.
  • Loud metallic cracks indicating a fracture of a load-bearing part (if present, stop immediately).

Ready-made report templates — copy and paste

The short templates below can be used in the company form, in an e-mail or in the app. Insert your details where marked by brackets.

  • Template 1 — knock over bumps: “Date: [DD.MM.YYYY], time: [HH:MM]. Vehicle: [make/model, reg. no.]. Mileage: [km]. Location: [address/GPS]. Symptom: knocking when passing over bumps, short ‘knock’ at the front on the right side. Occurs at 30–50 km/h, continuously. No warning lights, no smoke. Attachment: short video with sound.”
  • Template 2 — squeal when braking: “Date: [DD.MM], time: [HH:MM]. Vehicle: [make/model, reg. no.]. Mileage: [km]. Symptom: high-pitched squeal during braking, audible with every brake, increases at low speeds. Noticeable slight vibration in the brake pedal. ABS warning light is not on. Attachment: audio recording + photo of the dashboard.”
  • Template 3 — hum at speed: “Date/time: [..]. Vehicle: [..]. Mileage: [..]. Symptom: steady hum/drone at 80–100 km/h, increasing with speed. No other symptoms, no smoke. Road surface asphalt, full load. Attachment: exterior video + description of conditions.”

What next — how to submit the report and what to expect

Send the report via the company form, fleet app or e-mail to the repair coordinator. Attach recordings and photos. If the company has a repair coordination service, the report will go to them and priority and a workshop appointment will be scheduled.

Keep a copy of the report and attachments. If the situation changes (the sound intensifies or other symptoms appear), update the report — this helps determine whether the fault is progressing and whether vehicle use should be stopped.

Summary

A precise description of the sound, a short recording and a few basic data points (location, mileage, when it occurs) significantly speed up handling the report. Do not diagnose on your own; report quickly and safely — if there are signs of immediate danger, stop and call for help. If you need assistance organizing the repair, use repair coordination or the company car service.

Keep reading

More from the FleetPoint knowledge base

Browse the full knowledge base
Fleet Costs

What should be included in a company car repair summary?

A list of elements that a company car repair report should contain — practical tips for a small-fleet administrator to settle costs, secure warranty claims and plan vehicle availability.

Read article