Questioning the customer and confirming the fault – Motor Vehicle Theory motor mechanics lesson
Lesson 109 of 131 in the Motor Vehicle Theory course (ages 16+)
US version. US spelling and words (tire, gasoline, hood) and US rules such as state inspections. · UK version
Find out how technicians turn a customer's description such as "it makes a funny noise" into a clear, testable fault, using good questions and careful confirmation.
- Time
- 35 minutes + 10 min homework
- Course
- Motor Vehicle Theory (ages 16+)
- You need
- Paper, a pencil and this page. No tools and no vehicle
- Graded
- Instantly, with explanations
Education and interest only. Classfern teaches motor mechanics as a school subject. It is not a training program or a certification, and nothing here replaces an accredited automotive program, ASE certification or a qualified technician. Never work on a real vehicle without a qualified adult, the right protective equipment and safe equipment. High-voltage parts of electric and hybrid vehicles are for trained technicians only. Rules and values on this page are given as of November 2026. Always check the current official source (NHTSA and your own state’s rules) before relying on them.
How to use this lesson
This lesson develops questioning, listening and recording skills that are used in every workshop, with simple percentage work. It involves no practical work on a vehicle. Every answer is graded straight away with a worked explanation.
- Read what you will learn and the big ideas.
- Press Start the lesson below for the teaching, worked examples and practice (Getting started, On track or Challenge).
- Finish with the exit ticket and the talk question: “A customer is sure the fault is "definitely the transmission". How would you respond politely while still testing with an open mind?”
- Later: the homework, then the practice test.
Watch out for
- Asking only yes-or-no questions. Closed questions can miss important clues. Start open and let the customer describe the fault in their own words.
- Starting tests before confirming the fault. Without confirmation you may test the wrong system, or "fix" a fault the car never had.
- Writing vague notes such as "makes noise". Record what, when, where, how often and since when, so anyone can understand the fault.
Hands-on: Role-play with a friend: one person is a customer with a made-up fault (for example "a squeak from the front when braking, only in the mornings"), the other is the technician. The technician may ask up to ten questions and must start with at least two open questions. Then write the fault on a pretend job card in one clear sentence. Swap roles and compare. No vehicle needed.
What you will learn
- I can explain the difference between open and closed questions and when to use each.
- I can list the key facts to find out about any fault: what, when, where, how often and since when.
- I can explain why a fault must be confirmed, and how conditions such as temperature and speed matter.
- I can work out how often an intermittent fault occurs from a customer's record.
Key words
- open question
- A question that invites a full answer, such as "What happens when you start the car?"
- closed question
- A question with a short answer, often yes or no, such as "Does it happen when the engine is cold?"
- intermittent fault
- A fault that comes and goes, often only under particular conditions.
- reproduce the fault
- Make the fault happen again, under the same conditions, so it can be observed and tested.
The big ideas
The customer knows things about the fault that no tester can tell you: when it started, what the car was doing at the time, and whether it is getting worse. A few minutes of careful questioning at the start of a job can save hours of testing later.
But customers are not technicians. They describe what they hear, feel and smell in their own words – "a knocking", "it feels wobbly", "it smells hot". The technician's job is to turn those words into facts: what exactly happens, under what conditions, how often, and since when. In the US this first step is often written on the repair order as the customer's "concern".
Then comes confirmation. Until the technician has seen, heard or measured the fault for themselves, it is a report, not a diagnosis. This lesson is about communication and reasoning; any road test or check on a vehicle is done by a qualified person.
Read-through: the teaching steps
Open questions first
Start with open questions that let the customer tell the story:
- "Tell me what happens."
- "What were you doing when you first noticed it?"
- "What does it sound like to you?"
Listen without interrupting, and write down their words. People often mention something important in passing – "it's worse after I've filled up" – that they would never think to say if asked only yes-or-no questions.
Then closed questions to pin down the facts
Next, use closed questions to fill gaps:
- What? – Exactly what is the symptom: a noise, a smell, a warning light, a vibration, poor starting?
- When? – Cold or hot engine? At what speed? Braking, accelerating, turning, idling?
- Where? – Front or back? Left or right? Inside or outside?
- How often? – Every time, once a day, once a month?
- Since when? – Did it start suddenly, gradually, or after some recent work or an event such as hitting a pothole?
Each answer narrows down the possible causes.
Conditions matter
Many faults only appear under particular conditions:
- Temperature – a fault that happens only on cold mornings points to different causes from one that appears after a long run.
- Load and speed – a vibration at 50 mph but not at 30 mph suggests something that rotates.
- Weather – a fault in the rain may be water getting into a connector.
- Road surface – knocks over bumps point to suspension or steering parts.
Recording the conditions lets the technician recreate them.
Confirming the fault
Before any testing, the technician tries to confirm the fault:
- check it in the conditions described, for example with a cold engine;
- a road test by a qualified person, with the customer's permission, sometimes with the customer as a passenger to point out the symptom;
- read stored fault codes and look at warning lights.
If the fault cannot be reproduced, the technician records that, may ask the customer to note exactly when it next happens, and avoids replacing parts on a guess.
Writing it down
The concern is written on the repair order in clear, specific words – not "noise", but "knock from front left over bumps at low speed, since last week, cold or hot". Clear records help the technician, any colleague who picks up the job, and the customer.
Good communication continues through the job: explain what will be checked, how long diagnosis may take and what it may cost, and ask permission before any extra work.
The lesson, step by step
| Part | Time | How it is checked |
|---|---|---|
| Starter: warm up | 4 min | Graded by Classfern |
| Teaching and hands-on task | 11 min | Not assessed, self-checked |
| Worked examples and guided practice | 7 min | Graded by Classfern |
| Independent practice (three levels) | 8 min | Graded by Classfern |
| Exit ticket and talk question | 5 min | Graded by Classfern, self-checked |
Make my lesson plan Opens this lesson in the free Lesson Plan Maker, filled in and ready to change, print or save.
The lesson
It runs here on the page. No sign-up and no names – progress is kept only in this browser.
Homework
About 10 minutes: 6 questions and a one-line reflection, all graded instantly.
More practice
More Fault-finding lessons · Motor Vehicle Theory course · All motor mechanics practice tests · Motor Mechanics Department
Sources and curriculum
Facts in this lesson were checked against:
Our lessons and questions are our own. They are not written or endorsed by ASE, NHTSA, any state agency, any college, testing agency or exam board.