Repair-order flow
Repair Order Throughput
Direct answer
Repair order throughput is the rate at which repair orders move from write-up through diagnosis, approval, parts, repair, documentation, quality control, and closeout. Throughput improves when the department removes constraints and transition delays while maintaining correct work, complete records, and customer commitments.
Key takeaways
- Throughput counts completed flow, not the amount of work opened or currently busy.
- The active constraint determines the rate of the whole repair-order system.
- More work in process can lengthen queues without increasing completions.
- Stage-level timing and aging reveal where repair orders stop moving.
Throughput is completion-oriented
Opening more repair orders or keeping every bay occupied does not necessarily increase throughput. A repair order contributes to throughput when the required work progresses correctly to completion and closeout. Excess work in process can obscure priorities, increase context switching, and make promised times less predictable. Leaders should compare arrivals, completions, and carryover over a meaningful period and separate work types whose natural cycle times differ.
Transitions govern the flow
Repair time is only part of the lifecycle. The repair order must be dispatched, diagnosed, estimated, authorized, supplied with parts, resumed, documented, inspected when appropriate, and closed. At each transition, the next person needs clear status, information, authority, and system access. A repeated delay at one boundary can set the pace for the entire department, even when other stages have unused time.
Find the constraint without flooding it
Map queues and identify the stage where work consistently accumulates. Protect that constrained resource from incomplete inputs and unnecessary interruption. Do not release more upstream work solely to keep people busy if the constraint cannot absorb it. Improve the quality and timing of information arriving at the stage, then watch whether the queue moves elsewhere. The next constraint may emerge only after the first one is relieved.
Balance speed with completion quality
A repair order moved quickly but returned for missing documentation, an incorrect part, or incomplete repair has not created durable throughput. Track comebacks, corrections, supplementary approvals, and reopened work with cycle time. Standard completion criteria make the metric harder to game. The goal is reliable finished work, not rapid status changes that leave unresolved tasks downstream.
A completed task must become visible before throughput can continue
Repair-order throughput depends on information flow as well as physical repair. A diagnostic conclusion cannot start authorization until the advisor receives it; a parts need cannot enter its queue until the request is complete; finished work cannot close while required documentation remains open. Service Terminal does not accelerate the technical procedure itself. It can shorten the administrative gap between a completed step and the next department's ability to act. Stage-level analysis should pair the task-completion timestamp with the record-update and next-action timestamps.
What to measure
Repair orders entered, completed, and closed per period is the throughput measure, because opening more work is not output. Queue size and age at each lifecycle stage locates the constraint, and cycle time segmented by repair type prevents a change in work mix from being read as a change in performance. Carryover, corrections, and reopened work test whether the completed count is durable. Two intervals isolate the information-flow portion specifically: task-completion-to-record-update time, and record-update-to-next-action time. The first is what closer access can plausibly affect; the second shows whether the next role acted on it.
- Repair orders entered, completed, and closed per period
- Queue size and age at each lifecycle stage
- Cycle time segmented by repair type
- Carryover, corrections, and reopened work
- Task-completion-to-record-update time
- Record-update-to-next-action time
Relevant definitions
Workflow latency
Workflow latency is the time between when work is completed, discovered, measured, diagnosed, or changed and when the next person in the repair process receives enough information to continue.
View glossary entryService capacity
Service capacity is the practical amount of repair-order work a dealership service department can complete within a given period using its available technicians, bays, advisors, parts support, systems, and operating processes.
View glossary entryProduct relevance
How Service Terminal relates
Service Terminal is relevant when repair orders stall because an authorized employee must leave the point of action to reach an existing workstation session. More convenient managed access can shorten documentation, lookup, status, and coordination transitions while dealership systems remain unchanged. It does not make parts arrive, approve work, or perform a repair; it addresses the access-related portion of the flow.
Review the canonical product overview →Related questions
Is throughput the same as repair orders per day?
Repair orders per day can be a throughput measure when counting comparable completed work, but opened repair orders or raw counts without repair-mix context can be misleading. Define the completion event and period.
Why can more work in process reduce throughput?
Additional work creates more queues, priorities, handoffs, and context switches. If the constraint is already full, releasing more work does not raise its output and may make completion less predictable.
What timestamp matters most?
No single timestamp is sufficient. Use a consistent sequence of stage events and focus on the intervals and queues that repeatedly account for the largest avoidable share of elapsed time.
Dealership evaluation
Test this in one representative workflow
Pick a repair-order transition where two measures can be observed under a stable definition: Repair orders entered, completed, and closed per period and Queue size and age at each lifecycle stage. Involve the employees who do the work, plus dealership IT when authorized session access is in scope. Use the result to expand, relocate, narrow, or stop the test.