Petrol tuning files with fuel and hardware in the brief.

Write down the fuel grade as it is sold to the customer, and identify the country or labelling system where relevant. If a request crosses borders, a bare number can leave unnecessary uncertainty. Include any relevant information about the fuel actually in the vehicle, rather than listing a grade the customer only plans to use later.

If the intended fuel changes while the request is open, update the specification before using the delivery. The same principle applies to a change of hardware or a revised target: the file brief needs to reflect the vehicle that will be programmed, not the original appointment notes.

Include the engine designation, transmission and ECU hardware/software identification. State whether the hardware is standard or modified, then list the relevant installed components. The words turbocharged or naturally aspirated are useful context, but they do not replace the full vehicle specification or establish a particular achievable gain.

Record any previous tuning and explain where the submitted file came from. If the car arrived already modified, say what is known and what remains uncertain. Preserving that distinction is more helpful than labelling an unfamiliar file as original because it was read before your workshop made a change.

Stage 1 costs 1 credit and is the starting category for a standard-hardware request. Stage 2 costs 2 credits and needs the modified hardware to be specified. Compatible additional options are included when selected with either stage; standalone options cost 0.5 credit each. The current catalogue shows the services available to select.

Tell us what matters to the customer in use, such as a particular response preference or consistency in an identified operating condition. Avoid treating a peak-output claim from a different vehicle as the specification for this one. The exact application and supporting information should guide the discussion.

Track the request in the dashboard and use the completed submission for the download and notes. Record which version was written and retain the original file under the same workshop job reference. This gives you a practical starting point if the customer later changes hardware or returns after other software work.

For follow-up, explain the observation, when it occurs and whether the fuel or configuration has changed. Provide diagnostic information or logs if requested. A clear sequence of what was fitted, what was written and what was observed lets the support conversation address a specific question.