What is a car diagnostic check?

A garage tells you it needs to run a diagnostic before it can price the job, and quotes you forty or fifty pounds to do it. From the outside that sounds like being charged for plugging a machine in. The machine does most of the work, the read takes half an hour, so what exactly is the money for?

The honest answer is that you are not paying for the read. You are paying for what happens after it. A fault code names a circuit or a system, not the part that has failed, and the gap between those two things is where most wasted car repair money in this country goes. This guide covers what a diagnostic check actually is, what the tool can see and what it cannot, how to read the code yourself if you want to, how long the job takes, what it costs, and the one thing you should not do before the garage sees your car.

It also covers something almost every guide on this subject gets wrong: what the MOT does with your engine warning light. The test does not read your fault codes at all. It looks at one lamp, and it can fail you whether that lamp is lit or dead.

What you are actually paying for

Every car built this century runs on a network of small computers, called control units or modules. One manages the engine, another the gearbox, others the brakes, the airbags, the climate control, the locks and the instrument cluster. Each of them watches a set of sensors and each of them knows what a normal reading looks like.

When a reading falls outside its expected range, the module stores a fault code, and in many cases lights a lamp on the dashboard. That storage happens whether anyone is looking or not. The car has been keeping notes on itself since the day it left the factory.

A diagnostic check is a technician connecting a scan tool to those modules, downloading the notes, and then working out which of them is telling the truth. The download is the cheap part. The working out is the job.

Put it another way. The scan tool turns a car that is generally unwell into a specific question. Answering that question is what the fee covers, and a garage that simply reads you the code and reaches for the parts catalogue has done the first half and charged you for both.

What happens when the tool goes on, step by step

A proper diagnostic follows the same shape at almost every competent garage.

1. They ask you what it does. A good technician starts with your description, not the tool. When did the light appear, was the engine hot or cold, was it raining, does it happen every time or once a fortnight. An intermittent fault that only appears on a cold start is a completely different search from one that is present right now.

2. They plug into the diagnostic port. It is a trapezoid shaped socket with sixteen pins, almost always within reach of the driver's seat: under the dashboard, behind a flap in the lower trim, or occasionally inside the fuse box cover or the centre console. If you have never seen yours, it is there.

3. They scan every module, not just the engine. This is a real difference between a workshop tool and a cheap reader, and it is covered properly further down.

4. They record the codes and the freeze frame data before touching anything. The freeze frame is the snapshot the car saved at the moment the fault was logged, and it is often more useful than the code itself.

5. They watch live data. With the engine running, the tool streams real sensor values: fuel trims, air mass, coolant temperature, oxygen sensor voltages, rail pressure. This is where a technician sees a sensor reading plausibly but wrongly, which no stored code will ever tell them.

6. They test the physical thing. Wiring, connectors, vacuum lines, the component itself. Many faults are found here with a multimeter and a torch rather than on a screen.

7. Only then do they quote. By this point they are telling you what has failed, not what the car suspects.

Steps one, five and six are the ones that separate a diagnosis from a code read. If a garage skips straight from step two to a quote, that is worth a question.

What a fault code can and cannot tell you

This is the part that catches drivers out, and it costs people real money every week.

A code points at an area, not a part. Take the most familiar example. A code reporting that an oxygen sensor is reading outside its expected range does not mean the oxygen sensor has failed. The sensor may be working perfectly and reporting, correctly, that the exhaust gas reaching it is wrong. The actual fault could be a split intake hose, a leaking injector, a misfire on one cylinder, or a hole in the exhaust ahead of the sensor letting air in.

Replace the sensor and you have bought a part, fitted it, cleared the code, and driven away with the same fault. Three weeks later the light returns and the garage that did it has the awkward conversation. This is the single most common way drivers spend money without fixing the car, and it is why the testing after the read is the bit that matters.

Read that left column again. Every line is genuinely valuable, and not one of them is a diagnosis. That is the correct way to think about the fee.

Reading the code itself: P, B, C and U

Fault codes follow a standard format, so you can get a surprising amount from the code before anyone explains it to you. A code looks like P0301 or C1234. The first character says which part of the car is complaining.

The second character is worth knowing too. A zero usually means a standard code shared across manufacturers, so any tool can translate it and any garage will recognise it. A one usually means a manufacturer specific code, which needs either manufacturer level software or a technician who knows that make. This is why a generic reader sometimes returns a number with no description next to it, or a description that reads like nonsense.

The last three digits identify the specific condition. In the well known P03xx family, for instance, the final digit is the cylinder: P0301 is a misfire detected on cylinder one, P0302 on cylinder two, and P0300 is a misfire the car cannot pin to any single cylinder. That last one usually points at something shared by all of them, such as fuel delivery or an air leak, rather than one dead coil.

Knowing this much before you ring round is genuinely useful. It lets you describe the problem precisely, and it makes it much harder for anyone to be vague with you. Our guide on what to ask a garage before booking covers the rest of that conversation.

Freeze frame, the most useful thing on the screen

When a module logs a fault, most also save a snapshot of what the car was doing at that exact moment. It is called freeze frame data, and it typically records engine speed, road speed, engine load, coolant temperature, intake air temperature and the fuel trim values.

That snapshot answers questions the code cannot. Did this happen at seventy on the motorway or pulling off a driveway? Was the engine stone cold or fully warm? Was it under load or idling? A misfire logged at 900rpm on a cold engine is a different search from one logged at 3,000rpm under hard acceleration, even though both produce the same code.

Here is the practical consequence, and it is the most useful single instruction on this page. Do not clear the code before the garage sees the car. Clearing it deletes the freeze frame along with the code. You have thrown away the evidence and the light will come back anyway, because clearing a code does not repair anything. If you have already read the code yourself with a plug in reader, write it down, photograph the freeze frame screen if your reader shows it, and leave everything else alone.

The same goes for disconnecting the battery, which is sometimes suggested as a way to reset a light. On older cars it may clear stored codes. On modern ones it can also lose radio codes, steering angle calibration, window and sunroof settings and adaptive gearbox learning, and it still will not fix the fault.

Why your plug in reader said no faults found

Cheap plug in readers are genuinely worth owning, and this is not an argument against them. But a lot of drivers have the same confusing experience: the ABS light is lit, the dongle is plugged in, and the app cheerfully reports no fault codes. The car is clearly unwell and the tool says everything is fine.

The explanation is in the history of the socket. The standard diagnostic port exists mostly because of emissions law: regulators wanted a common way to check that a car's emissions controls were working, so manufacturers were required to expose that information in a common format on a common connector. Everything else in the car remained the manufacturer's own business.

So a basic reader typically talks to the powertrain side in the standard language, and often nothing else. The ABS module, the airbag module, the body modules and the gearbox may all be sitting there with stored codes that the reader either cannot request or cannot interpret. A workshop tool, or a good manufacturer specific one, interrogates every module on the network and reads the manufacturer codes as well as the standard ones.

Two practical rules follow from that. First, a clean scan from a cheap reader is not proof there are no faults, particularly when a non engine warning lamp is lit. If your ABS light is on and the dongle says nothing, believe the light. Second, when you ring round, it is fair to ask whether the garage can read all modules on your make, especially on a car with a lot of electronics.

If you are not sure which lamp you are looking at in the first place, our guide to dashboard warning lights sorts them by colour and urgency, and why the engine management light comes on covers that specific lamp and its common causes in depth.

Pending, stored, and the light that goes out on its own

Not every fault lights a lamp immediately. Many conditions have to be seen more than once, on separate journeys, before the module is confident enough to warn you. Until then the code sits as a pending code: recorded, but not yet promoted to a warning light.

This is deliberate, and it is why a car can log something without ever telling you. It also means a scan tool can show a fault brewing before you have noticed anything, which is one of the few genuinely useful reasons to scan a car with no light on.

The reverse happens too, and it causes a lot of confusion. A light comes on for two days, then goes out by itself, and the natural conclusion is that the problem has fixed itself. Usually the module has simply gone several journeys without seeing the fault again and has switched the lamp off, while keeping the code stored as history. The record is still in there, and a garage scanning the car will find it.

That is worth knowing because it changes what you should do. A light that came and went is still worth mentioning when you book, and an intermittent fault with a stored history is much easier to chase than one with no trace at all. Do not assume a dark dashboard means a clean bill of health, particularly if the car has felt different, or has dropped into a reduced power mode at any point.

What the MOT checks, and why it is not a diagnostic

Almost everyone assumes the MOT plugs into the car and reads its codes. For an ordinary car test in Great Britain, it does not. This is worth understanding properly, because it changes what the test can and cannot catch, and because the rule that does apply is stricter than most drivers realise.

What the tester inspects is the lamp. Under the emissions sections of the DVSA MOT inspection manual, section 8, the tester turns on the ignition and checks that the engine malfunction indicator lamp, the MIL, illuminates and then goes off. On some cars the engine has to be started before it goes out. That is the whole of it: one lamp, watched through one sequence.

The defect it produces is the interesting part. The manual lists, for petrol engines at 8.2.1.2 and for diesel engines at 8.2.2.2, the defect engine MIL inoperative or indicating a malfunction, graded Major. A Major defect is a fail.

Read that defect wording again, because it runs in both directions. A lamp that stays on fails, which everybody expects. A lamp that never lights at all is inoperative, and that fails too. So the oldest trick in the book, removing the bulb, taping over the symbol, or presenting a car whose cluster has lost that segment, is not a way round the test. It is the failure.

There is a date test as well, and it is one of the few genuinely useful things to know about your own car. The manual requires the tester to inspect a MIL fitted to petrol vehicles, hybrids included, with four or more wheels and not more than eight passenger seats, first used on or after 1 July 2003. For diesels, hybrids included, the date is 1 July 2008. Before those dates, the tester is not inspecting an engine MIL on that vehicle at all. Kit cars, amateur built vehicles and American pickups are not required to have one.

So the contrast is clean, and it is the reason a pass certificate is not a clean bill of electronic health.

Other warning lamps are graded elsewhere in the manual, in the sections for the systems they belong to rather than the emissions one, so an ABS or tyre pressure warning is judged on its own terms. Our guide on dashboard warning lights sets out which lamps carry an MOT consequence.

For scale, DVSA testing data for Great Britain puts emissions and leaks at 5.8% of all car MOT defects in 2024 to 2025. It is not the biggest category by a distance, lamps and electrics lead on 25%, but it is the one that a warning light on the way to the test will land you in.

The practical advice is simple. If the engine light is on and your test is due, get it diagnosed first rather than paying for a test you already expect to fail. Clearing the code in the car park is a gamble rather than a trick: the tester checks the lamp rather than your codes, so a light that stays out may well pass on the day, but many faults re trigger within a few miles, sometimes before the test has finished, and the underlying problem is unchanged and still yours. Our guides on preparing for your MOT, what a pre MOT check covers and why cars fail their MOT cover the rest, and what an MOT advisory means explains the difference between a fail and a note for next time.

How long does a diagnostic check take?

The read itself is quick. Connecting, scanning the modules and pulling the codes and freeze frames is usually twenty to thirty minutes. What varies enormously is the testing after it, and that is what makes one quote an hour and another three.

Intermittent faults are the honest difficulty here. A fault that appears once a fortnight, on a cold morning, cannot be made to appear on a ramp on demand. A good garage will tell you that up front and agree a time limit with you rather than running an open ended bill. If you are quoted for fault finding rather than a fixed diagnostic fee, ask for the hourly rate and a cap you both agree before they start.

What does a diagnostic check cost in the UK?

A diagnostic check commonly costs somewhere between about £40 and £80 at an independent garage. Franchised dealers usually charge more, partly because their labour rates are higher and partly because they are running manufacturer software and hardware that an independent may not have.

Two things move that number more than anything else.

Your local labour rate. A diagnostic fee is mostly an hour of a technician's time, so it tracks whatever an hour costs where you live. The same job is genuinely a different price in central London and in a market town, and neither garage is doing anything wrong.

Whether it is a fixed fee or fault finding time. Some garages charge a flat diagnostic fee that covers the read and a first look. Others charge by the hour from the start. Neither is unreasonable, but they are not the same product, and comparing one against the other is where people conclude they are being overcharged when they are not.

The question worth asking on the phone is the one most people forget: do you put the diagnostic fee towards the repair if I go ahead with you? Many independents do exactly that, which changes the real cost to nothing if you have the work done there. It also quietly tells you something about the garage, because a business confident in its diagnosis is happier to stake the fee on winning the repair.

If a quote that follows a diagnostic feels wrong, our guides on the signs of being overcharged and how to complain about a garage cover what to do about it, and main dealer against independent garage is worth reading if your car is still in warranty.

Why free diagnostics is usually something else

Free diagnostic offers are common and they are not automatically a con. But the phrase covers at least four different things, and only one of them is what you probably picture.

• A genuine full scan, given free. It happens, usually as a goodwill gesture, at a quiet time of year, or from a garage building a local reputation.
• A code read only. Someone plugs in a reader, tells you the code, and stops. Useful, but it is the first thirty minutes of the job, not the job.
• A free quote, not a free diagnosis. The garage will price a job you have already identified. Nothing is being diagnosed at all.
• A loss leader. The read is free on the understanding that the repair happens there, and the fee reappears if you take the car elsewhere.

None of those are dishonest as long as they are described plainly. The thing to do is simply ask what is included: is it a full multi module scan, do I get the codes in writing, and is there any charge if I do not go ahead with the repair. A straight answer to those three questions tells you what you are dealing with.

Be a little more careful with a free read offered alongside an immediate parts recommendation. That is the exact combination, a code and a part with no testing in between, that this guide has spent several sections warning about. How to choose a good garage covers what good practice looks like.

When you need one, and when you do not

A diagnostic check earns its money when the car has told you something and you need to know what. It is close to useless as a routine service item.

Worth booking:

• A warning light has appeared and stayed on, particularly the engine management light.
• The car has gone into limp mode or lost power, which is the engine computer deliberately protecting something.
• A misfire, a hesitation, a stumble at a particular speed or load, or a rough idle.
• Poor starting, or a car that will not start at all despite a healthy battery.
• Fuel economy has fallen noticeably with no change in how you drive.
• The gearbox is shifting oddly, harshly or late on an automatic.
• Something electrical is behaving strangely and intermittently.
• You are buying a used car and want to know what it has stored. This is the best twenty pounds in the whole buying process.

Not worth booking:

• Nothing is lit and the car drives normally. A full service looks after the parts that wear out, which is a better use of the same money.
• The symptom is plainly mechanical: a knock over bumps, a squeal under braking, a fluid puddle. A scan tool has nothing to say about a worn bush. Start with what a knocking noise means or the warning signs of a brake problem instead.
• You already know the fault and just want it priced. Ask for a quote, not a diagnostic.

Some symptoms sit in between, and are worth pairing a scan with a physical inspection: overheating, coloured smoke from the exhaust and a burning smell all have both electronic and mechanical explanations, and the codes narrow it quickly.

What to tell the garage before they plug anything in

Diagnostic time is expensive, and you can genuinely reduce it from your own driveway. A technician spends the first part of any job rebuilding the story of the fault, and you already have it. Turn up with this and you have done some of the work.

• Which lamp, and its exact behaviour. Steady or flashing, and whether it clears on restart. A photograph of the dashboard is ideal.
• When it happens. Cold start, after twenty minutes, at motorway speed, only in the wet, only with a full tank.
• How often. Once, every journey, twice since Christmas.
• What changed just before. New fuel, a new battery, a pothole, a service, a jump start, a car wash, water through a flooded road.
• Anything you can feel. Vibration, hesitation, a change in the noise, different fuel consumption.
• Any code you have already read, written down exactly as it appeared.
• Recent work, and by whom. Including anything you did yourself.

The Highway Code asks drivers, in Annex 6 on vehicle maintenance, to make sure warning lights and instruments are working and to have faults put right without delay. Noticing the detail of what your car is doing is the first half of that, and it costs nothing.

Is a diagnostic check worth the money?

Put the fee against what it prevents and the answer is usually obvious. A diagnostic is forty to eighty pounds. A guessed repair is the price of a part plus the labour to fit it plus, very often, a second attempt when the light returns.

Some of the parts most commonly replaced on the strength of a code alone are not cheap ones. A catalytic converter is a substantial bill, and a P0420 catalyst efficiency code is one of the most frequently misread in the business, because a healthy catalyst reported by a lazy sensor, or poisoned by an unrelated misfire upstream, produces exactly the same number. Fitting the cat without testing for the misfire buys you both bills. Even at the cheaper end, a set of spark plugs or a DPF clean is real money to spend on a hunch.

There is a second value that is easier to miss. A written diagnosis is something you can take elsewhere. Once you know the fault has been tested and named, you can compare quotes on the same job rather than on four different opinions, which is a far more useful comparison than four different guesses at a headline price.

The case against is narrow and honest: if there is no warning light, no symptom and no reason to suspect anything, a scan is unlikely to tell you much you can act on. In that situation the money belongs in a service instead.

The bottom line

A diagnostic check reads what your car has already written down about itself. That read is quick and inexpensive, and on its own it proves very little. The value sits in the hour after it, when a technician uses live data, a wiring diagram and their hands to work out which of the things the code implicates is actually at fault.

Judge a garage on that hour. The right one explains what the codes mean, tells you what they intend to test next and why, and quotes once they have confirmed the cause. The wrong one reads you a number and orders a part. Ask whether the fee comes off the repair, do not clear the code before they see it, and if your MOT is coming up, deal with a lit engine light beforehand rather than paying to be told what you already know.

When you are ready, compare local garages on ratings, services and opening hours, and send a request in about a minute. The garage comes back to you with a price and a time, you pay them directly, and there is no booking fee. If the annual test is also due, our free MOT check points you at the official DVSA record for your car, and booking an MOT and service together looks at whether one visit is worth it.