How to audit your current ADAS workflow for bottlenecks

A vehicle comes in for a bumper repair on Tuesday. The body work wraps up by Thursday afternoon. But the car doesn't leave the lot until the following Wednesday, because the forward-facing radar calibration wasn't identified until post-repair scan, the target boards for that specific vehicle weren't in stock, and the calibration bay was already booked for two days. 

A five-day repair just turned into a nine-day repair, even though no one did anything wrong. 

This is what a workflow bottleneck looks like in an ADAS-equipped shop. It's rarely one bad decision, but instead comes down to a sequence of small process gaps that compound into cycle time hits, supplement conversations, and frustrated customers. 

Auditing your workflow can help you identify specific points where work stalls, information gets lost, or handoffs break down so you can fix them before they become ongoing operational bottlenecks. This post walks through how to run that audit, what to look for, and how to prioritize the fixes that will actually move the needle.

Start with where your shop sits on the maturity curve

Before you can audit effectively, you need an honest assessment of your current operational stage. The ADAS Calibration Maturity Curve provides a framework for this. There are five stages ranging from fully outsourced and reactive (Stage 1) to a fully optimized calibration business line that other shops sublet to (Stage 5).

Most shops sit somewhere in the middle, and that's where bottleneck audits matter most. Shops can run into Stage 3 costs with Stage 2 operations, for example, or Stage 4 equipment utilized at Stage 3 capacity. That gap is where many bottlenecks live.

Identifying your stage first matters because the bottlenecks that matter at Stage 2 are different from the ones that matter at Stage 4. A Stage 2 shop might be bottlenecked by calibration identification because they're missing requirements at the estimate stage. Meanwhile, A Stage 4 shop is more likely bottlenecked by scheduling or bay throughput. 

Auditing without context leads to fixing the wrong things, and knowing where you’re at is the first step of the process. 

Want to understand where you sit on the Maturity Curve? Take the self-assessment. 

Map your workflow end-to-end

You can't audit what you haven't mapped, so the first step is documenting what actually happens from the moment a vehicle arrives to the moment it leaves. And keep in mind, this is not what your SOPs say should happen, but what actually happens on a busy Tuesday afternoon.

Walk through a typical ADAS repair and note every handoff, decision point, and waiting period:

• Intake and estimating. When does ADAS identification happen? Is it at the estimate stage, or does it get caught later? Who is responsible for identifying calibration requirements, and what tools are they using?
• Pre-scan and diagnosis. Is the pre-scan happening consistently on every eligible vehicle? Where are the results documented, and who sees them?
• Parts and equipment readiness. How do you know the right targets, scan tools, and OEM procedures are ready before the vehicle hits the calibration bay? How often do technicians start a calibration and discover they're missing something?
• Calibration execution. What's the sequence for static versus dynamic calibrations? Are environmental conditions verified and documented before the procedure begins?
• Post-scan and verification. How is calibration completion confirmed? What documentation is produced, and where does it live?
• Release and invoicing. How quickly does the documentation move from the technician to billing? Where do insurance pushback conversations originate?

Map this on paper or a whiteboard. The goal is to see the whole flow at once, because bottlenecks are almost always created by what happens between steps. 

Identify the most common bottleneck sources

Once you have your workflow mapped, compare it against the bottleneck patterns that show up most often in ADAS operations. These are the places where audits typically surface the biggest opportunities:

Calibration identification happening too late. If calibrations are being added as supplements rather than captured at the estimate stage, you have an identification bottleneck. The benchmark report found that before systematic identification tools, 22% of vehicles requiring calibration left shops without it. That's a front-end workflow gap with downstream consequences — every missed calibration becomes either a comeback or a liability.

OEM procedure confusion. According to our benchmark report, 27% of ADAS jobs involve OEM procedures that changed since the last time a technician performed a similar repair. If your shop is relying on memory or outdated procedure copies, technicians are losing time looking things up or completing calibrations to the wrong specifications.

Scheduling and bay utilization. If calibrations are consistently delayed because the bay is booked, or if technicians are idle waiting for a bay to free up, you have a throughput bottleneck. Our benchmark report found that ADAS work adds roughly an hour to the average cycle time — and that's in shops that have worked out their scheduling. In shops that haven't, it could be significantly more.

Equipment and target board availability. If technicians are discovering mid-calibration that they need a target they don't have, or a scan tool update that wasn't installed, the bottleneck is in your equipment management process. 

Documentation reconstruction. If documentation is being assembled at the end of the repair rather than captured in real time, you're building liability exposure and slowing down invoicing. With our report finding that 77% of shops reporting insurance pushback on ADAS charges at least sometimes, documentation gaps turn into payment delays.

Sublet coordination. If you're outsourcing calibrations, the handoff to and from the sublet provider is a common a bottleneck. Vehicles sit waiting for pickup, sit waiting at the calibration facility, then sit waiting for return while cycle time and storage costs accumulate.

Measure the actual cost of each bottleneck

Once you've identified where bottlenecks occur, the next step is quantifying their impact. Not every bottleneck is worth fixing immediately — the ones that consume the most time or generate the most rework are.

Track these metrics for at least 30 days:

• Average cycle time impact of ADAS work. How many additional days does an ADAS repair take compared to a non-ADAS repair? Where is that time being lost?
• Supplement rate. What percentage of ADAS calibrations appear on the original estimate versus being added later? Each supplement represents a bottleneck in the identification process.
• Rework and comeback rate. How often are vehicles returning for ADAS-related issues after release? Rework is the most expensive symptom of workflow failure — it consumes capacity you could be using for new work.
• Insurance pushback frequency. How often are ADAS charges being questioned or denied? Pushback usually traces back to documentation gaps, which trace back to workflow gaps.

Quantifying these gives you a prioritization framework. A bottleneck that adds two days to cycle time on 40% of repairs is worth more attention than one that adds an hour on 5% of repairs.

Build auditing into your operational rhythm

A one-time audit will surface your current bottlenecks, but it won't prevent the next set of road blocks from forming. ADAS requirements change constantly thanks to new OEM procedures, and vehicle platforms, and workflows that were optimized last year can be obstacles this year without anyone noticing.

The shops that stay ahead build auditing into their operational rhythm. Quarterly reviews of the metrics above, a running log of bottleneck observations from technicians, and scheduled walkthroughs of the workflow map keep the audit from becoming a one-time project that slowly goes stale.

The shops that move up the maturity curve are the ones that treat workflow and processes as a product that gets iterated on, measured, and improved. The ones that stay stuck are the ones that treat it as a given.

Moving from audit to action

Auditing your workflow is only valuable if it leads to changes in how your shop operates. A completed audit sitting in a drawer produces the same results as no audit at all.

Revv helps shops eliminate the most common ADAS bottlenecks — calibration identification, OEM procedure currency, and documentation — by providing VIN-specific calibration requirements at the estimate stage, always-current OEM procedures, and documentation that's generated as the work is performed rather than reconstructed at the end.

Book a demo to see how Revv can help your shop close the workflow gaps your audit surfaces and stay ahead of the ones forming next.

‍