The original-file checklist that makes a request easier to process.

Give the job a short internal reference and keep it consistent in your file names and notes. Then record the make, model, model year, engine and transmission. If the vehicle selector does not fully describe the application, explain the missing information in the request rather than choosing the nearest-looking variant and leaving it unexplained.

Attach or transcribe the ECU identification reported by the tool, including the hardware and software identifiers that are available. These details are more useful for a technical handover than a registration number alone. Do not place unnecessary personal customer information inside a filename that may later be shared for support.

Keep an untouched copy of the tool's output before preparing anything for upload. Record the date, tool, protocol and read method. If there are several exports, explain which is the requested input and retain the others in the job archive. Do not silently substitute a file from a previous visit.

Know whether the file contains the vehicle's current read, a virtual original or a separate backup output. If the vehicle was already tuned, say so. If its history is unknown, write unknown. That is a useful fact; calling the first file your workshop sees original can create a misleading history.

List the installed hardware and identify the fuel that will be used. Include relevant part specifications where available. Separate planned modifications from completed work, and tell us about previous calibration work or software updates. The request needs to describe the vehicle that will receive the delivery.

Record any current running concern and the checks already performed. Keep this factual: symptom, conditions, diagnostic observation and action taken. Avoid presenting an unresolved problem as something a stage selection will automatically fix.

Select the appropriate service, then explain the customer's priorities in plain language. A hardware-specific request should include the complete configuration. Select only the additional options actually required and confirm uncertain availability before submitting.

A useful brief could read: Job W-1042, current ECU identification attached, standard hardware, specified fuel, Stage 1 requested for the stated daily-driving priorities; previous software history unknown. The value is in the concrete details and honest unknowns, not in a long paragraph of tuning terminology.

Compare the uploaded filename with the job reference, vehicle description and read report. Check that the account has enough credits for the selected service. Read the notes as if you were the person receiving the job: do they explain what was read, what is fitted and what work is requested?

After submission, retain the job reference and follow its status in the dashboard. If information changes, reference the existing submission in a support conversation. Opening another nearly identical job without explaining the relationship makes the handover harder to follow and can create unnecessary duplicate work.