Insurance and liability every tuning workshop needs before writing an ECU

A customer’s Transit comes in for a DPF solution, the write goes fine, but three weeks later the car won’t start and the customer insists it’s “the remap.” The ECU turns out to have an unrelated wiring fault, but until that’s proven, you’re the one holding the liability conversation. This is the side of tuning work that doesn’t get talked about in forum threads about which tool to buy.

Public liability isn’t enough on its own

Standard public liability covers injury or damage to third-party property in the general sense, but a bricked ECU or a comeback dispute over a remap sits in murkier territory. Ask your broker specifically whether goods-in-trust is included, because that’s what covers the customer’s vehicle while it’s in your possession and under your work, not just the building and the public walking past it.

What actually happens if a write bricks an ECU

Most of the time a failed write is recoverable with a boot/bench connection and the right tool. Occasionally it isn’t, and you’re looking at a replacement ECU, coding, and possibly a dealer visit for anything the aftermarket tool can’t touch. Without goods-in-trust cover, that cost sits entirely with the workshop. With it, you’ve got a route to recovering at least part of that cost rather than absorbing a four-figure bill on one job.

It’s worth asking your broker directly whether the policy distinguishes between OBD writes and bench/boot work, since some policies quietly exclude one or the other, and whether it covers third-party ECUs sent in for remote work as well as vehicles physically on your premises. A policy written for a general repair garage often hasn’t been checked against these specifics at all, and the gap only becomes obvious at claim time, which is the worst possible moment to discover it.

Contracts and disclaimers, done properly

A disclaimer scrawled on an invoice after the fact holds very little weight. What actually protects you is a written job sheet, signed before work starts, that sets out what’s being done (read, backup taken, file type, expected outcome), what the customer has been told about risk, and what happens if something goes wrong during the process. This isn’t about avoiding responsibility for your own mistakes; it’s about having a clear record of what was agreed when a dispute happens six months later and memories differ.

Keep the wording plain rather than copying dense legal text from somewhere online. A customer who’s actually read and understood what they signed is far less likely to dispute it later than one who was handed a page of small print and told to sign at the bottom. A short, clear job sheet also makes life easier for the workshop if a claim does end up going to an insurer or, in rare cases, further than that.

Questions worth asking your insurer directly

• Does the policy cover ECU remapping and file writing specifically, or just general vehicle repair
• Is there a cap on goods-in-trust that would actually cover a full ECU replacement
• Does DPF/EGR removal work affect the policy, given the legal and MOT/TÜV implications
• What documentation does the insurer expect you to keep if a claim is made

Where legality overlaps with liability

Removing emissions equipment or disabling systems can carry inspection and legal implications depending on the country the car’s registered in. A customer asking for this work doesn’t remove your responsibility to be clear about what it means for MOT, TÜV or CT compliance. Being upfront about this in writing protects you as much as it informs them.

If a write does go wrong, knowing the recovery route matters as much as the insurance behind it; it’s worth reading through recovering a bricked ECU after a failed flash so the team knows the steps before it happens for real. Pair that with the right kit from tools and equipment and a solid file request process, and most liability situations never reach the insurer at all.