How to map a car dealership service department

How to map a car dealership service department: draw the estimate decision and the revise loop first, then the roles. Live example from vehicle arrival to a job in the workshop.

A service department looks like a line from arrival to handover, but the middle is a decision with three exits. Draw the estimate approval and its revise loop first, and the desk, controller and workshop fall into place around it.

The short version

  • Map the decisions and label every branch before you assign roles.
  • The estimate is a three way decision: approve, wants changes or decline.
  • Send the revise loop back to the estimate so each new scope is priced again.
  • Record condition, mileage, fuel level and existing damage before the job card is raised.
  • End a declined job with its own closing step so the vehicle leaves without work.

The estimate decides everything after it

Most service department charts start with the people: the customer, the service advisor, the workshop controller and the technician. That gives a tidy set of swimlanes and very little understanding. The questions a customer and a workshop actually ask are about outcomes. Was damage found at the walk round? Did the customer approve the estimate? Is a technician with the right skills free today? Each of those is a decision with more than one exit, and the process is the sum of those exits.

The part most charts get wrong is the estimate. A customer who has seen the price is not simply approving or leaving. They may approve, they may want changes, or they may decline. Wanting changes sends the advisor back to rework the scope and prepare a new estimate, which is a loop. Declining ends the job and returns the vehicle without work. A chart that shows only approval hides the loop and the decline, which are the two paths that cost the advisor the most time.

So the method is to map in this order. First list the decisions and label every branch. Second, draw the revise loop so that it returns to the estimate and not to the start. Third, record what must be captured before work begins, such as condition notes, mileage, fuel level and a signature on any existing damage, because those records settle disputes later. Only then put the steps into lanes, so each handoff shows as a lane crossing you can time.

The example below is a vehicle check-in and job card process in QueryChart, built in four stages. Processes differ by brand, workshop and country, so treat the chart as a structure to adapt against your own procedures rather than a statement of what any manufacturer or regulator requires.

From vehicle arrival to a job in the workshop

A vehicle check-in and job card process with a damage check, an estimate decision and a revise loop.

  1. Arrival and the condition record

    The vehicle arrives for the booked service and the advisor greets the customer and confirms the booking. A walk round follows, and the condition notes, mileage and fuel level are recorded with photos. A decision asks whether existing damage or warning lights were found. If so, each finding is added with the customer's signature, and either way the job card is raised with the requested work and concerns.

  2. The estimate and its three exits

    The advisor prepares the estimate for labour and parts. The decision asks whether the customer approves the estimate and has three branches: Yes, Wants changes and Declines. Wants changes leads to revising the scope with the customer and returns to the estimate, which is the loop. Declines ends at "Job closed, vehicle returned without work".

  3. Keys, loan car and technician allocation

    An approved estimate moves on to tagging the keys and logging the vehicle on the tracking board, then arranging a courtesy car, lift or wait. The controller allocates a technician by skill and hours free. If nobody suitable is free today, jobs are reshuffled or the customer is given a new finish time, and the chart returns to the allocation step. When the answer is yes, the technician accepts the job card and collects the keys.

  4. The roles and the handoffs

    The job ends at "Job in the workshop with keys tracked and work approved". With the decisions fixed, the lanes for the customer, service advisor, workshop controller and technician show where each handoff happens and where waiting time collects, most often at the estimate and at the allocation.

How it works

  1. List every decision

    Write down each point where the outcome can differ: damage found or not, estimate approved, changed or declined, and technician free or not. Add each as a decision in QueryChart with labelled branches, before any lanes exist.

  2. Draw the arrival to the estimate

    Connect the greeting, the walk round, the condition record and the job card in a line. Keep it plain. The aim is a spine you can read in one pass, with the exceptions hanging off it.

  3. Draw the three way estimate decision

    Add the estimate step and a decision with the branches Yes, Wants changes and Declines. Give the decline its own closing step so the path has a visible end.

  4. Close the revise loop

    Connect Wants changes to a revise step and return it to the estimate step, not to the walk round. Each new scope is then priced again before it reaches the decision.

  5. Add the allocation check

    After approval, add the key tagging, the loan arrangement and the technician allocation, with a decision on whether a suitable technician is free and a return path to the allocation when not.

  6. Assign lanes and read the handoffs

    Now move the steps into lanes for the customer, the advisor, the controller and the technician. Look at the lane crossings: each is a place where a job can sit unattended.

Mistakes to avoid

  • Showing only approval

    An estimate drawn as a single step to approval hides the loop and the decline. Draw all three exits.

  • A revise loop that returns to the start

    Sending the customer back to the walk round repeats work that was already done. Return to the estimate.

  • Skipping the condition record

    Without condition notes, mileage, fuel level and signed damage, a later dispute has nothing to point to.

  • Starting with the org chart

    Lanes first gives you a picture of departments. Decisions first gives you a picture of the process.

Map your own service department

Open the vehicle check-in example as your own chart, change the estimate exits and the allocation rules to match your workshop, and then assign the lanes.

Map your own service department

Related guides

Frequently asked questions

What is the first thing to draw in a service department process?

The decisions. List the points where the outcome can differ and draw each with labelled branches. Roles can be added as lanes afterwards without changing the logic.

How do I show a customer who wants changes to an estimate?

As a loop. The Wants changes branch leads to a revise step and returns to the estimate step, so the new scope is priced and put to the customer again.

Where does extra work found during the job belong?

It starts a second approval of its own. Read /guides/how-to-handle-additional-work-approval-in-a-workshop and the chart at /templates/workshop-additional-work-authorisation-process. For the step before this one see /templates/vehicle-service-booking-process.

Is the chart a statement of manufacturer policy?

No. Procedures differ by brand, workshop and country. The chart shows the structure; put your own rules in the labels and comments.

The template behind this guide

Vehicle check-in and job card process flowchart — Vehicle check-in and job card process flowchart: walk-round with condition notes, job card, estimate approval, keys and tracking board, and technician allocation in a dealership workshop.