A customer pulls up and says the car "feels a bit off", but cannot say when it started, what makes it better, or whether a light was involved. Where does your workshop begin? For many teams, the answer is a baseline vehicle scan: a short, structured capture of the vehicle's reported condition before anyone opens a parts catalogue or quotes a repair. Used well, that baseline becomes the anchor for every conversation that follows, from the first phone call to the final invoice.
This article explains what a baseline scan is and what it is not, which details are worth recording, how to turn the record into a clearer customer conversation, and where the limits lie. The guiding principle throughout is simple: scan data is information that supports diagnosis. It is not a diagnosis by itself, and presenting it that way protects both the customer's trust and your team's credibility.
What a Baseline Scan Is, and What It Is Not
A baseline scan is a record of what the vehicle reports before any repair work is approved. It typically covers stored fault codes, the live values relevant to the customer's symptoms, the vehicle's identification details and the conditions under which the scan was taken. Its purpose is documentary. It answers the question "what did the vehicle say on this day, in this state?" so that later readings have something to be compared against.
What it is not is a verdict. A stored fault code describes an observation the vehicle made, not the component that must be replaced. A clean scan does not prove the car is healthy, and a long list of codes does not prove it is expensive to fix. Workshops that frame the baseline honestly, as a snapshot to be interpreted by a technician, tend to avoid the two most common communication failures: overpromising on the strength of one reading, and dismissing data that later turns out to matter.
What to Record in a Baseline Report
The value of a baseline comes from its completeness. A useful record includes the vehicle's make, model, model year and VIN, the odometer reading, and the date and time of the scan. It also includes the conditions: was the engine or drive system warm or cold, had the customer just driven the car, were any warning lights on at the time? A code that appears only after a cold start, or a value that only drifts when the car is fully warmed up, means little without that context.
Beyond the codes themselves, note the freeze-frame data attached to each fault and the live values that relate to the symptom the customer described. If the customer reported an intermittent concern, record that it was not present during the scan. A documented absence is genuinely useful information, both for the technician who picks the job up later and for the customer who wants to understand why the team wants the car back for a longer observation.
Turning the Record into a Customer Conversation
Most customers do not speak in fault codes, and a report full of five-digit identifiers can feel like a wall. The baseline works best when it is translated. Start from what the customer already told you: the symptom, in their words. Then explain what the vehicle reported, what a technician thinks it may mean, and what the next step is designed to find out. "The car flagged a sensor reading outside its expected range" invites a different, calmer conversation than "we found a code".
It also helps to show the record rather than describe it. A printed or on-screen summary of the baseline, with the codes and readings you consider relevant, gives the customer something concrete to take away. Owners who keep their own scan records make this easier; a customer who arrives with a saved report from an earlier scan gives your team a comparison point before the car is even on the ramp. The habit of keeping scan reports before repairs is useful on both sides of the counter, which is why we wrote a separate guide on why you should save a scan report before any vehicle repair.
Repair Approvals and Shared Expectations
The baseline also earns its keep at the approval stage. When the recommended repair follows directly from the recorded findings, the customer can see the chain: symptom, recorded data, technician's interpretation, proposed work. When the repair is exploratory, for example because an intermittent fault did not reproduce during the visit, the baseline documents why the team is recommending monitoring rather than parts. That transparency reduces the two classic disputes: work the customer did not understand, and a "fixed" car whose original concern returns a fortnight later.
After the repair, a second scan provides the closure. Recording the vehicle's reported state after the work, and sharing the comparison with the customer, turns "we think it is sorted" into "here is what the car reported before, and here is what it reports now". If the concern later returns, both sides also have a dated record of what was and was not present at handover, which protects the workshop as much as the customer.
Where Baseline Scans Reach Their Limits
A baseline is only as useful as the tool and the interpretation behind it. Generic code readers vary widely in what they can access, particularly on vehicles that report much of their data through brand-specific channels. Workshops that regularly service particular marques often choose vehicle-specific tools for this reason. A workshop focused on selected Chinese brands, for instance, might use a tool such as the Fcar CW700, which according to the store's published information supports OBD2 plus DoIP diagnosis across systems including engine, transmission, ABS, SRS, TPMS, BMS and SAS for published brands including Geely, Haval/GWM, Chery and Changan. Whatever the tool, coverage is specific to brand and model, never universal, and the compatibility list should be checked before ordering.
The second limit is human. A scan report tells the team what the vehicle reported; deciding what it means still requires a qualified technician, and some concerns will need road testing, physical inspection or specialist equipment that no scan tool replaces. Writing "baseline recorded, interpretation pending" into the job file is not an admission of ignorance. It is an accurate description of the diagnostic process, and it sets the customer's expectations for how the next stage will proceed.
Making Baselines a Workshop Habit
Processes stick when they are short enough to follow on a busy day. A practical version of the baseline habit fits on one page: capture the vehicle details, record codes and relevant live values, note the conditions, translate the findings into plain language for the customer, and file the report where the next technician can find it. Teams that review these records together, even briefly, tend to spot patterns across similar vehicles sooner and to onboard newer technicians faster, because the reasoning behind each job is written down rather than carried in one person's memory.
None of this requires new equipment to start. It requires agreement that every job begins with a recorded starting point, and a shared understanding that the record supports diagnosis rather than replacing it. Workshops that build that habit usually find the payoff in fewer disputes, clearer approvals and customers who return because they understood what was done and why.
Frequently asked questions
Does a baseline scan replace a technician's diagnosis?
No. The baseline captures what the vehicle reported at a moment in time. A qualified technician interprets that information alongside symptoms, history and physical inspection. The record supports the diagnosis; it is not the diagnosis itself.
What if the scan shows no fault codes?
Record that the scan was clean, along with the conditions and the live values you checked. A documented clean scan under known conditions is useful evidence, especially for intermittent concerns, and it helps the customer understand why further observation may be needed.
Should customers be given a copy of the baseline report?
Offering a summary of the recorded findings, in plain language alongside the technical detail, builds trust and gives the customer a reference for future visits. Many customers also appreciate knowing how to keep their own scan records between services.