A Pre and Post Remap Workshop Checklist to Protect the Shop and Car
A workshop remaps a diesel Passat, hands the keys back, and three days later the customer is back with the engine management light on and a complaint that “the remap broke my car”. A quick check shows a stored EGR fault code that was already intermittently present before the car came in, just not illuminated at the time. A five-minute pre-check would have caught it and avoided an awkward conversation and a free diagnostic session.
Before the remap: what to check
- Full fault code scan, stored and pending, not just active codes, using a proper diagnostic tool rather than a generic OBD reader that might miss manufacturer-specific codes
- Service history: cambelt or chain interval, oil service currency, and any known open recalls for that engine code
- A visual check for obvious existing issues: boost leaks, oil leaks near the turbo, a worn or perishing intercooler hose, coolant condition
- Baseline road test noting any existing hesitation, limp mode history, or unusual noises, written down, not just remembered
- Confirming exactly what hardware is fitted, standard or already modified exhaust, intercooler, injectors, so the correct file is written for the car in front of you, not assumed from the model badge
Photographing the VIN, the ECU part number or label, and the odometer reading before starting protects the shop if there’s ever a dispute later about what car the work was done on and when.
During the job
Always take and store a backup of the original file before writing anything, regardless of how routine the job seems. A bench or boot read that fails partway through is far less stressful to recover from with a good original file already saved than without one. On OBD-writable ECUs, checking battery voltage is stable and using a proper power supply rather than trusting the car’s own battery is worth the extra five minutes; a voltage dip mid-write is one of the more common causes of a failed flash that didn’t need to happen.
After the remap: verification, not just a test drive round the block
- Re-scan for fault codes immediately after flashing, before the road test, to catch anything the write process itself may have triggered
- A proper road test covering low-load cruising, hard acceleration and, where relevant, motorway load, not just a five-minute loop around the industrial estate
- Check live data under load: boost pressure against target, fuel trims, EGT if available, and watch for knock correction
- Confirm the transmission, if automatic or DSG, is shifting normally and not hunting or flaring, since torque changes can expose a transmission that was already borderline
- A second fault code scan after the road test, since some faults, particularly EGR or turbo-related, only set once the car has been driven under real load
What protects the shop, not just the car
Writing the pre-existing fault findings on the invoice or job sheet, with the customer’s acknowledgement, is the single biggest thing that prevents a “the remap broke it” dispute two weeks later over a fault that was already there. It costs five minutes and saves arguments that cost far more in goodwill.
Handling a genuine comeback
Sometimes a fault really does relate to the remap, a boost leak that only shows under the higher pressure the new map runs, or a marginal injector that couldn’t quite keep up with the extra fuelling demand. When that happens, the pre and post checklist pays for itself again: it lets the shop show exactly what was working and what wasn’t at handover, rather than arguing from memory a week later. A customer who sees the documented before-and-after data is far more likely to accept a genuine fix under goodwill than one who feels like they’re being fobbed off.
The checklist in one line
Know what the car was doing before you touched it, back up what you’re about to overwrite, and prove what you did afterwards with data, not just a test drive that felt fine.
For guidance on backing up and recovering files safely, see recovering a bricked ECU after a failed flash, and for the request process itself, use the file request form. More workshop process guidance lives under Workshop & Business.
More ECU guides
Remap vs Tuning Box, How Each Works and Why One Is a Compromise
A customer walks in with a plug-in tuning box he bought online, wired into the fuel rail sensor on his Mercedes Sprinter, asking why it feels…
How to Read a Dyno Graph, Correction Factors and What the Numbers Mean
Two customers bring the same model BMW 320d (N47) in for a before/after dyno pull after a remap, a week apart. The power figures come out…
Is Remapping Legal in the EU, and What About Insurance and Warranty
A customer asks a workshop to remap his year-old Golf GTD "but don't tell the dealer", because he's worried about the warranty. Before answering that question,…