You don't need to know what's wrong with your car to give a workshop something useful to work with. Say "the steering wheel shook between these speeds," and a workshop has a concrete starting point to investigate. Say "the wheel bearing is faulty," and you've turned a guess into a fact — which skips the step where someone goes and checks it.
This article gives you one copyable report you can fill in for almost any car problem, plus two rewritten examples that show the difference between an observation and a suspected cause in practice. The framework organises what you already know. It doesn't diagnose anything, and it doesn't tell you the car is safe to drive.
Facts first, guesses second
An observation is something you saw, heard, smelled, felt, or read off a display. A suspected cause is an explanation for that observation — and it still needs someone to check it.
Go back to the steering wheel. "The steering wheel shook between these speeds" is what you observed: a specific, repeatable fact with a speed range attached. "The wheel bearing is faulty" skips past that straight to naming a part, and there's no way to know whether the guess is right. The first sentence gives a workshop something to investigate directly. The second states a suspected cause as if it were already confirmed, before anyone has looked.
The report below asks for what you observed first, and keeps guesses separate, in a field of their own, clearly labelled as a guess.
Check safety first
Before you write anything down, there's one question that comes before the report: does your current owner manual tell you to stop, avoid driving, or get assistance? If it does, follow that instruction. Documenting the problem carefully is useful, but it never comes before an instruction your vehicle is already giving you.
If you're uncertain whether the vehicle can be operated safely, treat that uncertainty seriously. The report you're about to write isn't permission to drive. Consult your current owner manual for the specific warning or symptom, and if anything is unclear, seek qualified help rather than guessing.
Everything in this report comes from what you can safely see, hear, or read. Nothing here asks you to test brakes, steering, restraints, fuel or high-voltage systems, or anything underneath the car. A professional handles those checks; this report only asks you to observe and record what you notice.
Copy this problem report
What follows is an Autonelio editorial framework, not a universal intake form. A useful starting report can include the fields below, and you don't need to fill in every one. Unknown details may be left blank, and fields that don't apply to your situation don't need an answer.
Think of it as a starting point for the conversation. It doesn't guarantee an outcome — not a faster appointment, not a lower bill, not a successful repair. What it does is give whoever's diagnosing your car a clearer place to start than "it's making a noise."
VEHICLE
Registration or ID used for booking:
Make / model / approximate year:
Engine or powertrain (if known):
Current mileage (if readily available):
WHAT YOU OBSERVED
Sound, smell, vibration, loss of function, changed
behaviour, visible leak (seen from a safe position),
or displayed information:
TIMING AND CONDITIONS
First occurrence:
Most recent occurrence:
Journey stage / speed or stationary / weather /
road type / load / controls in use / cold or
warmed up (only the fields relevant to your event):
REPEATABILITY
Every time / sometimes / once / not yet reproduced:
Simplest safe description of the circumstances:
EXACT DISPLAYED INFORMATION
Symbol, indicator, warning text, or fault code —
and whether it was photographed, recorded,
copied exactly, or recalled from memory:
CHANGES AND RECENT EVENTS
New or worsening?
Recent service or repair, impact, refuelling or
charging, tyre or battery work, or other relevant
event:
SUSPECTED CAUSE, IF ANY
(Optional. Keep guesses separate from the facts above.)
BOOKING SUMMARY
One or two sentences for the phone call or booking form.
NOTES
Anything else the workshop might ask about.
Copying a warning message or a fault code exactly is worth handing to the workshop. Copying it accurately doesn't settle the diagnosis or whether the car's safe to drive — that still depends on your current owner manual and, where anything's unclear, on qualified help.
Two examples, rewritten
Here are two hypothetical examples that turn a diagnostic-sounding guess into a bounded observation. Neither one names a fault or tells you what to do about the car — they just show how the fields above get filled in.
An intermittent symptom
Imagine an owner tells a workshop, "the brakes are broken." That single sentence names a system and implies a conclusion, but gives the technician almost nothing to work with.
Rewritten as an observation, it looks different: a grinding sound, noticed twice this week, both times on the first hard stop after starting the car cold. The pedal felt about the same, though the owner isn't certain. The sound hasn't happened on every stop — only some of them — and hasn't been reproduced on purpose. That's it: no cause named, no test suggested, no claim about whether the car's safe to keep driving. It just preserves what the owner noticed, with the timing and the pattern attached, so the workshop starts from real detail instead of a label.
A warning message
Now imagine an owner tells a workshop, "the engine light means something's seriously wrong." That's an alarm — it doesn't say what appeared, or when.
Rewritten as an observation, it reads differently: an amber engine-management symbol appeared while cruising on the motorway, about sixty kilometres into the trip, with the engine already warmed up and no other warning symbols showing. The symbol stayed lit rather than flashing. The owner opened the current manual and checked what it said about that exact symbol before writing anything else down. No cause is named, and no claim is made about how serious the underlying problem is.
This last point matters more than it looks. In the Canadian-market 2016 Volvo V70 example, the response the manual calls for depends on the specific symbol shown, the exact text, and the equipment fitted. It also depends on the engine, the vehicle's condition, and whether more than one warning is displayed at once. That material tells the driver to read and follow whatever message the instrument panel displays, and for the specified red warning symbol, to stop safely and not drive further — one illustration of what following the manual can mean for a particular vehicle. That's why your exact vehicle's current manual governs, not a general impression of what a warning colour usually means. If your manual tells you to stop or seek assistance, follow that first — write down the details afterward, once you're safely able to.
Filling this in for someone else
If you're helping another owner talk to a workshop, the same fields work, with one addition: label what you know first-hand separately from what you were told. "The driver reports that the noise happens on left turns only" is a fair, useful sentence, because it's honest about the source. Folding a driver's account into your own words as if you'd heard it yourself risks turning a secondhand guess into what sounds like a witnessed fact. Mark which category each detail belongs to:
- witnessed details you saw or heard yourself
- driver-reported details you were told
- displayed information the vehicle showed
- remembered wording, recalled rather than copied exactly
- anything you're genuinely unsure about
What supporting information can do
Warning messages, fault codes already displayed, photos or recordings, and notes on recent work are all worth passing along to a workshop. Treat each one as information to hand over. None of it, by itself, settles a finished diagnosis, proves a repair worked, or establishes whether the car is safe or roadworthy — that still depends on further investigation, your current owner manual, and qualified help where anything is unclear.
Follow-up questions from a workshop fall into the same categories: what you saw or felt yourself, what someone else told you, what the vehicle displayed, what you're recalling from memory, and what you're genuinely unsure about. That separation matters for as long as the conversation continues, from the first note onward.
Where to go next
This article sits in Autonelio's diagnostics hub. From there you can read about preparing for a diagnostic appointment, what to record when a fault is intermittent, and why a warning light, a fault code, and a diagnosis are three different things. The wider car-ownership section covers maintenance planning and workshop costs too.
Your next step: if the vehicle is stationary and its current manual doesn't require immediate action, open a note, copy the template above, and write your first observation in plain language.