A remapping workflow that keeps every handover clear.

Record what the customer wants, what is fitted and what is known about previous software work. Include the engine, transmission and fuel. Identify any existing concern that needs investigation before calibration work is considered. Turn that information into a short job brief with a unique workshop reference.

Check the application, tool and requested service with the file provider if support is uncertain. Discuss time-sensitive work before committing a collection time. A manual file-preparation process should be planned as part of the appointment, alongside your own inspection, programming and assessment time.

The responsible technician follows the supported tool procedure and records the ECU identification, protocol and read method. Retain the untouched export and any associated job outputs. Keep a factual note of the vehicle's initial condition and the checks performed.

Use the same workshop reference across the read, notes and submission. If the vehicle specification differs from the booking information, correct the brief before uploading. The person preparing the file should receive the current facts rather than a mixture of appointment assumptions and later discoveries.

Confirm the account has enough credits, select the correct service and upload the intended original file. Review the selected options and total before submission. Stage 1 uses 1 credit, Stage 2 uses 2 credits and standalone options use 0.5 credit each; compatible options selected with either stage are included.

After submission, note the portal reference on the workshop job card. The dashboard tracks pending, in-progress and completed work. If a colleague asks for an update, refer to that status and any specific communication about the job, rather than assuming elapsed time proves it is ready.

When the request is complete, download its prepared file and read the completion notes. Match the delivery to the original job reference and current vehicle specification. Record the version that will be used; do not leave several similarly named downloads for the next technician to guess between.

The workshop performs programming and the appropriate vehicle checks. Document the result against the original customer request and any starting observations. If the vehicle or software changed while the file was being prepared, resolve that change before treating the delivery as suitable for the updated job.

Archive the original read, delivered version, identification and relevant observations together. Keep the credit purchase invoice in the business purchase records, and use the portal's credit history when reconciling service usage. The invoice and file job serve different record-keeping purposes.

If the customer reports a concern later, record what changed since collection and reference the original submission in a support ticket. Include current observations and relevant evidence. For a new hardware project or intervening software update, establish the new specification rather than automatically reusing the earlier delivery.