Warning lights & faults
A structured route from symptom verification to measured evidence and a repair recommendation.
W / 01 / Diagnostic-first vehicle care
Find the fault.Understand the fix.
A clearer workshop experience starts with the symptom, follows the evidence, and pauses for approval before repair work begins.
01 / VerifyConfirm the concern
02 / ExplainShare the evidence
03 / ApproveAgree the next step
Start with what the vehicle is doing
What brought you here?
Drivers rarely arrive with a part number. Choose the closest concern and start with information that helps the workshop test the right system.
Service map / common needs
Useful work, explained plainly.
Start with the concern rather than a guessed part. Vehicle coverage, timing, and specialist work can then be confirmed before a visit is accepted.
See the full service mapService & maintenance
Planned maintenance built around vehicle condition, service history, and the approved service scope.
Brakes & handling
Inspection and measured assessment for braking, steering, wheel-end, and suspension concerns.
Temperature & climate
Pressure, temperature, airflow, and leak checks before parts are recommended.
Battery & electrical
Battery, charging, starting, wiring, and network checks using measured values rather than assumptions.
Workshop method
Four steps. One clear decision at a time.
A disciplined process makes technical work easier to trust: define the concern, gather evidence, agree the scope, and verify the outcome.
- 01
Listen & verify
Record the symptom, when it happens, and what changed. Reproduce the concern where practical before choosing tests.
A precise problem statement - 02
Test & narrow
Use the right visual, mechanical, electrical, or data checks to separate a symptom from its root cause.
Measured findings, not a parts list - 03
Explain & approve
Share what was found, the recommended next step, and the price or further diagnostic scope before repair work begins.
An informed decision point - 04
Repair & verify
Complete only the approved scope, then repeat the relevant check so the outcome is supported by evidence.
A recorded post-repair check
Example evidence / diagnostic handover
A code points to a system. Testing finds the cause.
This sample handover shows how a finding can be communicated without hiding behind jargon: what was checked, what the evidence suggests, and what happens next.
Diagnostic processMeasured before replacement
Example / charging concern
Evidence snapshot
Example of a plain-language diagnostic handover.
Concern verifiedYES
Battery stateCHECKED
Supply pathWITHIN TEST RANGE
Control-side dropINVESTIGATE
Parts approvalNOT YET
Next step: isolate the control-side connection before recommending a component.
People-first service
Good workshop advice makes the next decision easier.
Technical findings matter when they are connected to the original concern and explained in plain language. A clear handover should leave room for questions, options, and approval.
- 01Concern in contextListen first
- 02Checks that fit the symptomMeasure next
- 03Findings in plain languageExplain clearly
- 04An agreed next stepApprove calmly
Evidence, not guesswork.
A useful recommendation connects the symptom, the test result, the recommended scope, and the check that follows the work.
See how diagnostics works