
The drive is full, technicians have work, and advisors are answering status calls between write-ups. From the counter, the department looks productive. Then you look at the vehicles that were supposed to leave, and too many still need diagnosis, authorization, parts, or a final check. Everyone has been working. The completion promises have drifted anyway. When that happens, the useful question is where the department committed capacity it didn’t actually have—and where a job stopped moving without someone taking responsibility for its next step.
NADA’s May service-management explainer names poor scheduling and loading, ineffective dispatching, and inaccurate capacity calculations among the reasons busy technicians can remain unproductive. That’s a useful starting point, but it doesn’t supply a dispatch method. You still have to connect the appointment, the available technician, the bay, and the handoff. The operating approach below is a practical framework for making those connections, not a published industry standard. It starts with a simple discipline: before you promise completion, know what the shop has actually committed to do and what must be ready for that work to move.
Give the appointment a clear operational meaning
An appointment can mean the customer may arrive, an advisor will be available, or a technician can begin evaluating the vehicle. Those are different commitments, and your customer may hear a completion promise even when your scheduler intended only an arrival time. Listen to how your team describes appointments on the phone and at write-up. Ask whether the same language reaches dispatch. If the customer expects a diagnosis while the shop has reserved only counter time, the job begins with a gap that the advisor will eventually have to explain.
WardsAuto’s September reporting on Pied Piper’s service-scheduling study examines appointment access, including reaching an advisor and obtaining an available appointment. It also distinguishes routine maintenance from complicated concerns for which customers prefer speaking with someone. That makes access worth reviewing, but the study doesn’t establish whether an appointment reserves usable repair capacity. In your department, pair the access conversation with an operational question: what kind of work is coming, and what can you responsibly promise before anyone has inspected the vehicle? An easy booking experience needs a clear explanation of what happens after arrival.
Agree on language your schedulers and advisors can use consistently. A known maintenance visit may support a completion estimate based on the work reserved. An unresolved concern may require a diagnostic commitment before a repair completion time is possible. For those visits, tell the customer when they should expect an update and who will provide it. Carry that distinction into the repair order so dispatch sees the same commitment the customer heard. You’re giving the advisor a promise that reflects the actual state of the job rather than an assumption about what diagnosis will reveal.
- Arrival, diagnostic start, and completion distinguished
- Customer expectations visible to dispatch
- Update commitments for unresolved concerns
Load the available skills before accepting more work
A department can have open calendar space and no practical capacity for the next concern. The available technician may not have the required skill, the necessary equipment may already be committed, or an unfinished repair may still own that technician’s attention. Build your loading discussion around usable capacity by work type rather than the appearance of open slots. Review who is present, what work they can perform, what support they need, and what is already in progress. The point is to expose constraints before the advisor turns an opening into a customer commitment.
Carryover belongs in that discussion before new arrivals. Look at unfinished work according to what it still needs: active repair, diagnosis, parts, authorization, or verification. A vehicle waiting for approval may not consume wrench time now, but it can create a claim on capacity when the customer responds. Don’t treat all waiting work as available capacity, and don’t assume every open repair order needs immediate technician time. Ask the dispatcher to identify what could return to production and what resource it will need. That gives you a more honest picture of the load you’re about to accept.
Choose who can approve work beyond the planned load and what they must consider before doing it. An urgent customer concern may deserve an exception, but the exception should include a decision about the work it displaces. Otherwise, advisors can make individually reasonable promises that the shop cannot honor together. When capacity changes because of an absence, a difficult diagnosis, or newly authorized work, revisit the remaining commitments. Your loading plan needs room for judgment. It also needs someone accountable for reconciling that judgment with the promises already made to customers.
- Capacity matched to skills and equipment
- Carryover reviewed before new commitments
- Named authority for load exceptions
Make the advisor–technician handoff ready for work
A technician shouldn’t have to reconstruct the customer’s concern before beginning the assigned work. NADA’s earlier discussion of technician time drains identifies inefficient write-ups and poor communication among the problems. Use that framing to review the information your shop needs at dispatch. For a concern that requires diagnosis, the write-up should describe what the customer experiences, when it occurs, and any conditions that help reproduce it. Keep the customer’s description separate from an assumed cause. A clear symptom gives the technician a starting point without turning the advisor’s guess into the repair instruction.
The handoff also needs the customer’s authorization boundaries, contact preference, waiting or transportation arrangement, and the commitment already made. Make those details available where the technician and dispatcher actually look. Then agree on what happens when a necessary detail is missing. The advisor should own resolving the customer question, while dispatch decides whether another ready job should move ahead. That keeps the technician from becoming the message carrier and prevents an incomplete repair order from quietly holding its place as though work could begin. Urgency still matters, but readiness needs to be visible.
The return handoff deserves the same care. Findings should let the advisor explain the condition, the recommended work, the supporting evidence, and what remains uncertain. If additional diagnosis is needed, say so before the advisor presents a repair as settled. Agree on who watches for the customer’s response and who tells dispatch when authorization arrives. While the customer is unreachable, the job needs an owner even if no technician is actively assigned. That ownership connects the technical finding to the next production decision instead of leaving each person to assume someone else is following up.
- Symptoms documented without assumed causes
- Authorization boundaries and promises included
- Clear ownership of customer responses
Treat the bay as a production resource
An occupied bay tells you where a vehicle is, not whether useful work is happening. A vehicle may be under repair, waiting for parts, awaiting approval, or sitting after the technician has moved to another assignment. Those conditions need different responses. During your shop walk, ask what prevents each stationary job from moving and whether the bay is necessary for its current condition. You don’t need to challenge every pause. You need enough visibility to distinguish a legitimate production requirement from waiting that could occur somewhere else without creating extra risk or handling.
Parts readiness is part of that decision. NADA’s fixed-operations discussion connects incomplete parts availability with technician waiting and lost billed hours. Before dispatching a known repair, establish who verifies that the required parts are available and ready for the job. A status such as ordered or received may still leave questions about completeness. Where inspection or disassembly is necessary to identify everything required, acknowledge that uncertainty in the load and the customer conversation. The goal is to avoid assigning a repair as fully ready when the department already knows a necessary input is missing.
Moving a waiting vehicle out of a bay can help, but movement has a cost and may be unsafe or impractical after disassembly. Have the technician and dispatcher decide whether the vehicle can be moved safely, what protection it needs, and what work can use the released space. If it must remain, show the reason and the person responsible for the next action. Then review the completion promise. A blocked bay becomes a larger service problem when its production effect stays invisible while advisors continue making commitments against capacity that is no longer available.
- Active work separated from bay occupancy
- Parts completeness checked before dispatch
- Safe movement decisions with clear ownership
Review the transitions that make promises slip
Your reports may show labor performance without explaining why a particular vehicle finished late. To investigate the flow, follow the transitions: arrival to a complete write-up, ready for dispatch to technician start, findings to customer contact, authorization to resumed work, and repair completion to final release. Use whatever reliable records you already have. Where a timestamp is unavailable, acknowledge the gap rather than filling it with an estimate that looks precise. The purpose is to locate a delay well enough to act on it, not to create a reporting burden that takes attention away from the drive.
Take a manageable sample of late jobs and reconstruct what happened with the advisor, dispatcher, technician, and parts staff involved. Ask where the job stopped, what information or resource was missing, and who could authorize its next move. Keep the review focused on the process rather than judging someone with information they didn’t have at the time. You may find that a supposedly slow repair spent much of its elapsed time waiting for a decision. You may also find a legitimate diagnostic difficulty. Those situations call for different management responses, even when the customer experienced the same late delivery.
Use what you learn to change a specific operating rule. Missing concern details may call for a stronger write-up handoff. Repeated delays after authorization may mean dispatch isn’t receiving the approval promptly. Parts-related interruptions may require a clearer readiness check before the vehicle enters the bay. Review the change against the same transition that exposed the problem, while keeping work mix and unusual circumstances in view. Over time, this gives your production conversations a useful center: which jobs are ready, which are blocked, who owns the next action, and whether the remaining promises still fit the shop.
- Transitions tracked with reliable records
- Late jobs reviewed without hindsight blame
- Process changes tied to observed delays
Questions managers ask
Should we leave room in the schedule for unexpected work?
Leave room according to the uncertainty your shop actually encounters, rather than adopting an unsupported capacity allowance. Review where diagnostic work, additional authorizations, and carryover compete with scheduled repairs. Then decide which commitments can be firm and which need a later confirmation. Protecting flexibility only works if someone controls its use; otherwise, the available room can disappear through unrelated promises. Tell advisors who can release that capacity and what customer commitment they may make when it becomes available. Revisit the approach as you learn more about your work mix.
What should we use to track waiting if our current reports don’t show it?
Start with a shared record your team can maintain reliably, whether that’s a board, a worksheet, or a field in an existing system. Show the job’s current state, what is preventing progress, who owns the next action, and the customer commitment. Record transition times where practical, but don’t let perfect measurement delay basic visibility. Keep customer information appropriately protected. During production reviews, update the record from the people doing the work so it remains a useful operating reference rather than another list that everyone assumes someone else maintains.
Who should tell the customer when the completion promise changes?
Assign the customer conversation to the advisor responsible for the visit, with a clear backup when that advisor is unavailable. The technician or dispatcher should flag the production change promptly and provide enough information for an accurate explanation. The advisor can then explain what changed, what is known, and when the next update will come. If a new completion estimate isn’t supportable, don’t replace the old promise with another guess. Make sure the revised commitment returns to dispatch so the customer conversation and shop plan stay connected.
What to do with this
A dependable completion promise rests on connected decisions: what the appointment reserves, which technician can do the work, whether the job is ready, and who acts when it stops. Your team can be working hard while those decisions remain disconnected. Bringing them together gives advisors a firmer basis for customer conversations and gives dispatch a clearer view of what the shop can finish. It also makes exceptions easier to discuss because you can see which existing commitment an added job may affect.
At your next production meeting, put the unfinished work beside the incoming appointments. Identify the required skills, missing inputs, blocked bays, and customer promises. Agree on who owns each unresolved handoff, then adjust commitments that no longer fit the available capacity. Follow the affected jobs through the day and review where they stopped. Start there, with the work already in your department. You’ll have a concrete basis for deciding what to change next—and a clearer answer when an advisor asks what the shop can honestly promise.
Sources
Related topics
More for service managers
Service Department Efficiency: Keep the Shop Load Moving
The drive is full, your technicians have work, and the afternoon promises are already getting uncomfortable. An advisor needs an answer on a diagnosis. A vehicle is occupying…
Service Department Efficiency: Find the Waiting Behind the Work
The drive can look healthy while the shop falls behind. Advisors are writing, technicians are moving, and vehicles keep coming through the doors. Yet the afternoon brings…
Turbocharge Your Service Bay: Harnessing Innovative Practices for Maximum Efficiency
In today's fast-evolving automotive landscape, dealership service departments are under immense pressure to boost efficiency while maintaining high standards of customer…