Cycle time is the single most-watched KPI in collision, and CCC's native report is the worst-suited way to see it. Slow to render, single-average, no distribution, no carrier split, no touch-vs-calendar breakdown.
Why It Breaks
CCC computes a mean cycle time over the window you select and shows one number. At MSO scale, that number is almost never useful — a few outlier ROs pull the mean in a direction that doesn't reflect the typical repair. We wrote up exactly why the average lies.
What MSOs Actually Need
- Median and p90 cycle time, not just the mean.
- Touch time vs calendar time — is the delay in the bay or waiting? See touch vs cycle.
- Cycle time per carrier, because DRP scorecards are carrier-specific.
- A histogram or distribution view, not a single number.
The Fix
Build cycle-time properly in the warehouse — median, p90, distribution, segmented by shop, carrier, estimator, severity band. Render in 2 seconds across any window. Typical build: 1–2 weeks once CCC data is flowing.