Confirm the job and vehicle
Check the customer’s authorization, exact vehicle identity and agreed technical target. Review the diagnostic findings and any mechanical concerns that could affect the work. Confirm the hardware and fuel assumptions used for the calibration. If the vehicle changed since the file was read, resolve that discrepancy before writing.
Verify the original and selected result
Open the job record and verify the ECU/TCU family, hardware and software identity. Confirm that an independent copy of the original exists and is readable. Select the intended output revision, with a clear connection to the original. Similar names, matching file sizes or a neighbouring folder are not enough to establish that relationship.
Check the programming workflow
Use the current instructions for the exact tool and protocol. Verify the supported connection method, required file format, integrity handling and any documented preparation. Alientech’s workflow explicitly separates importing the modified file from verifying that writing completed. Preserve that separation in your process: receiving a result is not confirmation of a successful write.
Prepare power and recovery
Provide the power support specified for the vehicle and equipment, maintain the required connection and avoid unrelated operations during programming. Know the documented recovery route before starting. Keep the original, identification report and relevant support contact accessible so an interruption can be investigated from evidence rather than memory.
Define the checks after programming
Confirm the tool’s completion result. Carry out the appropriate diagnostic and operational checks for the vehicle and intended work. Record unexpected faults or behaviour and investigate before handing over the vehicle. When measurements are used to assess a target, record their conditions and method rather than presenting an unexplained number.
Know when to stop
An uncertain software identity, unsupported protocol, missing original, unresolved fault or unexplained integrity warning is a reason to pause. Contact the appropriate software or tool support team with specific evidence. Repeated blind writes can compound an unclear problem. A documented stop decision is part of professional delivery.
Further reading
Check ECU & TCU coverage or contact Support about a specific file.