Automotive diagnostic data is what a vehicle’s control modules record and report about their own health: fault codes, a snapshot taken when a fault appeared, and live sensor readings. Technical data is the reference side: wiring diagrams, torque settings, test procedures and repair times. A technician needs both, and the result is only worth anything if it ends up on the job card and in the vehicle’s history. That is why we build Workshop Pulse to keep diagnostic findings, quotes, parts and invoices in one system, rather than on a scrap of paper beside the scan tool.
This guide explains each type of data in plain terms, shows how to read it in a sensible order, and covers the points where a small workshop usually loses time or money.
TL;DR
- Diagnostic data comes in three layers: fault codes (what a module flagged), freeze-frame data (the conditions at that moment) and live data (what the sensors say now).
- A fault code points at a circuit or system. It does not name the failed part, so test before you replace.
- Technical data, such as wiring diagrams, torque figures and test procedures, is what turns a reading into a repair.
- Independent garages have a legal right to manufacturers’ OBD information, though access to some connected services needs the customer’s consent.
- The findings only protect you if they are recorded against the job and the vehicle, which is where connected workshop software earns its place.
Table of Contents
- Where diagnostic data comes from
- The three layers of diagnostic data
- Why a fault code is not a diagnosis
- Technical data: the other half of the job
- A repeatable diagnostic routine
- Recording the data so it earns money
- Access to manufacturer data: your rights and the limits
- Connected diagnostics and AI: what they add
- Putting it all in one workflow
- Habits that keep diagnostics profitable
- FAQ
- Sources
Where diagnostic data comes from
A modern car carries many electronic control units (ECUs), small computers that each manage a system such as the engine, brakes, airbags or gearbox. They read sensors continuously. When a reading falls outside what the software expects, the ECU stores a Diagnostic Trouble Code (DTC) in its fault memory. Gofore’s explanation of the UDS diagnostic protocol describes control units holding readable data points such as sensor values, the VIN and software versions, with trouble codes kept in that fault memory.
You reach all of this through the OBD-II port, the standard diagnostic socket under the dashboard. A scan tool plugged in there can ask each module what it has stored and what it is measuring right now. The depth of access varies by tool and by manufacturer, which is one reason tool choice matters. If you are weighing up handheld and professional options, this overview of OBD2 scanner types for a garage sets out what each class can reach.

The three layers of diagnostic data
Fault codes
A DTC is a short alphanumeric code. The first letter tells you the area: P for powertrain, B for body, C for chassis and U for network communication. A code such as P0302 means a misfire has been detected on cylinder 2. That is a description of what the module observed, not an instruction to fit a new coil.
Codes also have a status. Roughly:
- Stored (confirmed): the fault has been seen enough times to be logged.
- Pending: the module has seen something but has not yet confirmed it.
- Permanent: emissions-related codes that stay in memory until the vehicle itself confirms the repair over a drive cycle.
This breakdown follows Diagnostic Central’s scanner guide, which also warns that clearing codes too early can wipe out evidence and make an intermittent fault harder to catch. Write the codes down, with their status, before you clear anything.
Freeze-frame data
When a fault is logged, the ECU saves a snapshot of conditions at that instant: typically engine speed, vehicle speed, coolant temperature, engine load and fuel trims. It answers the question the customer cannot: what was the car doing when it went wrong? A misfire that only appears at 3,000 rpm under load is a very different job from one that appears on a cold idle.
Live data
Live data is the stream of current sensor readings, often called parameter IDs (PIDs): engine speed, coolant temperature, throttle position, manifold pressure, mass airflow and fuel trims. Where the code says a threshold tripped, live data shows whether the problem is present now and how it behaves as the engine warms up or revs.
Live data can overwhelm anyone. The practical answer, as Diagnostic Central puts it, is to focus on the few values that match the complaint: for a no-start, cranking voltage, rpm signal and rail pressure; for a boost fault, requested against actual boost.
Why a fault code is not a diagnosis
The most expensive mistake in diagnostics is replacing the part named in the code description. Diagnostic Central makes the point directly: a code for an oxygen sensor, a DPF pressure sensor or an EGR circuit does not mean that component has failed, because wiring damage, poor earths, blocked pipes, air leaks and software issues can all trigger the same complaint.
The technician writing in Professional Motor Mechanic recalls that in the early days of modern diagnostics, the common approach was to clear the code and hope, or fit whatever the fault description named. The same writer, who has 25 years in diagnostics, urges garages to move beyond that kind of parts-swapping.
A worked example: fuel trims
Fuel trims are the ECU’s corrections to the fuel mixture. Short-term and long-term trims are added together, and in Auto Technician’s fuel trim analysis Des Davies of Top Gear Motor Services gives the rule of thumb that the total should sit within plus or minus 10%. Beyond +10% the engine is running lean, and beyond -10% rich.
Now take a car with a misfire code. The same article explains that if the trims barely move, a single-digit difference points towards an ignition fault, while a double-digit difference usually indicates an air/fuel ratio problem. Two cars with identical codes, then, can need an ignition coil in one case and a vacuum leak hunt in the other.
The same source adds that trims improving at higher rpm alongside a rough idle suggest checking for vacuum leaks, while trims worsening at higher rpm suggest checking fuel pressure, fuel delivery or the MAF or MAP sensor. The reading becomes useful only when compared with the other readings and a physical test.
Technical data: the other half of the job
Diagnostic data tells you what the car reports. Technical data tells you what it should be doing and how to fix it. For a UK independent, that typically means:
- wiring diagrams and control-module pin data for electrical faults
- component locations and testing procedures
- torque settings, adjustment data and lubricant capacities
- manufacturer service schedules
- repair times, which feed straight into an accurate quote
Without the reference side, a good reading has nowhere to go. A voltage reading from a sensor connector is meaningless until you know what it should be.
Workshop Pulse offers Technical Data and Parts Lookup as part of its platform, and has a page on its HaynesPro WorkshopData and E3 Technical integration for garages that want this reference material alongside the job card instead of in a separate browser tab. Neither Technical Data nor Parts Lookup has a published price, so check the plans page for the current options.
A repeatable diagnostic routine
The order matters more than the tool. Diagnostic Central’s recommended sequence is a good base, and it works for any vehicle:
- Confirm the complaint. Ask when it happens, how often, and what the customer was doing. Note it on the job card.
- Check battery voltage. Low voltage can produce a crop of unrelated communication faults. Diagnostic Central notes that several systems flagging communication errors can point to a power supply or network problem rather than several separate failures.
- Connect the correct tool for the make and system.
- Run a full system scan, not just the engine module.
- Record every code with its status before clearing anything.
- Review freeze-frame data to see the conditions when the fault set.
- Inspect likely causes: wiring, connectors, earths, hoses, obvious mechanical issues.
- Use live data and actuator tests on the values that match the complaint.
- Repair, clear and retest, then confirm the fault does not return on a road test.
Each step produces something worth keeping: codes, readings, photos, test results. On paper, those get lost between the bay and the front desk. In a connected system they attach to the vehicle.
Recording the data so it earns money
The findings matter commercially in three places.
The quote. A customer who is told a part is needed will want to know why. A job card showing the code, the live reading that confirmed it and the test result makes the quote easier to accept and the invoice easier to defend. Repair times from technical data keep the labour figure honest.
The vehicle history. An intermittent fault returns months later. If the earlier codes, freeze-frame data and the work done are linked to the registration, the next technician starts from facts instead of memory.
The customer conversation. Showing the evidence is faster than explaining it. Workshop Pulse’s digital vehicle inspections and customer portal are built around vehicle-linked documentation and proof of work, so what the technician found is visible to the customer as well.
If your findings currently live in a notebook or a spreadsheet, Workshop Pulse’s job card and invoicing software brings them into the same record as the quote, parts and payment.

Access to manufacturer data: your rights and the limits
Independent garages are entitled to the same diagnostic information as franchised dealers. The type-approval regulation (EU) 2018/858, as published on legislation.gov.uk, requires manufacturers to give independent operators unrestricted, standardised and non-discriminatory access to vehicle OBD information, diagnostic equipment and tools, and to the remote diagnosis services used by manufacturers and authorised dealers.
The technician in Professional Motor Mechanic calls the right to use manufacturer tools and data the single most important thing for the future of UK independents. In practice, deeper services, such as manufacturer remote diagnosis, come with conditions. They can require the workshop to be registered with the manufacturer and the vehicle owner to give consent to share their data. Build that consent step into your booking process so it does not hold up the job.
Connected diagnostics and AI: what they add
AI tools do not replace the routine above. They shorten it. A useful tool for a small workshop should interpret codes clearly, keep related codes together, preserve freeze-frame context and link findings to vehicle history. It should also end in a next action, such as a quote, an inspection request or a message to the customer, rather than another screen of numbers.
Workshop Pulse’s AI Diagnostic Assistant is built for independent garages, and the BQM Assistant gives technicians diagnostic support inside the workflow. It costs £79 per month as an add-on. For garages that also run vans and company cars, Fleet Management is £99 per month, keeping repeated faults and maintenance on each vehicle in one place.
Putting it all in one workflow
Workshop Pulse is designed by a technician for independent garages. The Core plan is £149 per month per garage and Core Plus is £299 per month per garage, both with unlimited employees and onboarding support. Core Pro has no published price. Standard onboarding is a one-off £395 for Core and £795 for Core Plus. Every plan starts with a 14-day trial that needs no payment details, and support is by phone and WhatsApp with a real person.

If you want to see how a diagnostic finding travels from the bay to the job card, quote and invoice, start with the 14-day free trial or book a demo. The plans page lists the add-ons.
Habits that keep diagnostics profitable
- Charge for diagnostic time as its own line. It is skilled work, and the evidence on the job card supports it.
- Never clear codes before recording them.
- Compare any reading with related sensors and expected conditions. A plausible number can still be wrong for the engine speed, temperature or load at that moment.
- Prove the repair with a retest and road test, and note the result.
- Keep every scan, reading and test result against the vehicle registration, not the technician’s memory.
FAQ
What is the difference between diagnostic data and technical data?
Diagnostic data is what the vehicle reports: fault codes, freeze-frame snapshots and live sensor readings. Technical data is reference material: wiring diagrams, torque settings, test procedures and repair times. You use diagnostic data to find where the problem is, and technical data to confirm it and carry out the repair.
Does a fault code tell me which part to replace?
No. A code tells you which circuit or system a module flagged. Wiring, earths, air leaks and software can all cause the same code as a failed part. Check the live data and test the component or circuit before ordering anything.
What is freeze-frame data?
It is a snapshot the ECU saves at the moment a fault is logged, usually including engine speed, vehicle speed, coolant temperature, load and fuel trims. It shows the conditions in which the fault appeared, which helps you recreate it on a road test.
Can independent garages access the same data as dealers?
In principle, yes. The type-approval rules require manufacturers to give independent operators non-discriminatory access to OBD information and tools. Some connected services also need registration with the manufacturer and the customer’s consent to share data.
Should I clear the codes after reading them?
Only after you have recorded them, with their status and freeze-frame data. Clearing too early can remove evidence and make an intermittent fault harder to find. Clear and retest after the repair, to confirm the fault does not return.
Sources
- Gofore: UDS, the protocol without which vehicles come to a standstill
- Diagnostic Central: Diagnostic scanner step-by-step guide
- Professional Motor Mechanic: A deep dive into diagnostics
- Auto Technician: Fuel trim analysis
- legislation.gov.uk: Regulation (EU) 2018/858, Article 61
- OBD2 scanner types for a garage
Recommended
- AI Diagnostic Assistant for Garage Technicians
- Digital Vehicle Inspections: A Guide for Independent Garages
- HaynesPro WorkshopData & E3 Technical
Workshop Pulse
Run your whole workshop from one app.
Bookings, job cards, video inspections, invoicing and parts in one place. 14 days free. No card required; £0 today. Your trial starts only when your workshop is ready to use.