Think about the last file request that went wrong. Maybe a dealer sent "Audi A4 2.0 TDI remap" with no year, no ECU details, no read file. Maybe they sent a Bosch EDC17C46 read but forgot to mention they wanted EGR and DPF off as well as the stage 1. Maybe you processed it, sent it back, and then got "oh actually that was a bench read not OBD."
Every one of those problems comes from the same root cause: the request process didn't capture the right information.
The Minimum a Request Should Include
Before you even open a file to work on it, you need:
- Vehicle registration or VIN for a definitive ID
- ECU make and type (Bosch EDC17, Siemens SID, Delphi DCM, Denso, etc.)
- Read method — OBD, bench, or boot
- Tool used (Autotuner, KESSv2, Alientech, CMD, etc.)
- The original read file attached and verified
- Exactly what modifications are needed — stage 1, stage 2, DPF off, EGR off, AdBlue, pops and bangs, whatever the request is
If any of that is missing, you're going to waste time chasing it. And if you're handling 15-20 requests a day, those five-minute chases add up to an hour or more of pure admin work.
Why Forms Beat Messages
The problem with WhatsApp or email is that there's no structure. A dealer can send you whatever they want in whatever format they feel like. A structured form — the kind you get in a proper file portal — forces the right information upfront. No reg? Can't submit. No file attached? Can't submit. Didn't select a read method? Can't submit.
It sounds rigid, but dealers love it. They know exactly what's expected, they don't have to guess, and they don't get a reply at midnight saying "what ECU is that?" They fill it in, submit it, and check back later for the completed file.
Status Tracking Stops the Chasing
A great process doesn't just capture information — it keeps people informed. When a dealer can log in and see that their request is "in progress" or "ready for download," they don't need to message you asking for updates. That's another 30 messages a day you don't have to deal with.
SMS or email notifications when a file is ready are even better. The dealer gets a ping, logs in, downloads, done. No chasing, no waiting, no "did you get that?"
The Process Should Work Without You
The ultimate test of a great file request process is this: can it run while you're working on a file, eating lunch, or taking a day off? If every request relies on you reading a message, extracting the info, and manually tracking it, you are the bottleneck.
A portal-based process means requests come in structured, your team (or just you) can see everything at a glance, and the dealer is updated automatically. You just focus on the actual file work.
If your current process involves a lot of "can you resend that?" and "what ECU is it?", it might be time to look at something better. RemappingWebsite.com offers a file portal designed around how tuning businesses actually work — structured requests, automated tracking, and proper dealer management.