Before secure submission
Use a concise workshop checklist to prepare vehicle, ECU or TCU, read-method, service, diagnostic and original-file context before secure submission.
A complete request reduces avoidable clarification and helps the technical review begin with the right controller and service context. The checklist should describe facts the workshop has verified, not assumptions inferred from a vehicle badge or file name.
The public checklist does not upload or analyze a file. It helps prepare the information that will later be submitted through the secure MG AutoTech customer request workflow.
Include the exact codes relevant to the request and the diagnostic context. Do not replace verified codes with a general description such as warning light on.
The request can state that identification is unknown, but support and processing may require clarification before work can continue.
No. It improves request quality, while final support still depends on the submitted file, controller identity, requested service and technical review.