Industry: ADAS calibration
An ADAS calibration is a compliance record with a physical procedure attached.
Treat it as a repair job and you will staff it wrong. The calibration takes minutes. Proving it was performed to the OE procedure, or could not be, is what the shop sells.
The premise
The exposure is not the labor. It is the assertion.
A lane departure or automatic emergency braking system calibrated against the wrong target position, on an unlevel floor, at the wrong ride height, is a vehicle handed back with a system that may not intervene when it should. That is a safety event and a liability event, because the shop asserted the work was done.
So the deliverable is not only a calibrated vehicle. It is a calibration record: which systems were calibrated, to which procedure, with which conditions confirmed, and with what result. A record showing a pass with no procedure reference is worth very little.
There is a second outcome shops under-document, and it matters most: a vehicle that could not be calibrated, redirected with the reason recorded. A shop that never records a failure is not a shop that never fails. It is a shop whose failures are invisible.
What a calibration record has to carry
- The vehicle, and which systems on it require calibration
- The pre-scan result and the DTCs present before work began
- The OE procedure reference, and whether it was static or dynamic
- The target setup and the conditions confirmed
- The post-scan result, and whether the calibration passed
- If it did not pass: the reason, and where the vehicle went
The calibration queue
Five stages, and the constraint is usually the bay, not the technician.
A calibration shop's throughput is set by target space, rack availability, lighting, and whether the procedure runs static or goes dynamic.
01 INTAKE
Which vehicles need it, and what triggered it
The trigger is a windshield replacement, a repair that moved a camera or radar, a steering or suspension job that changed ride height, or an alignment. The pre-scan establishes which systems are present and which DTCs already exist, because a fault predating your work is not yours to clear.
Prepared: the required calibration list and the pre-scan captured against the job. Human: whether the trigger moved a sensor, and whether the vehicle is safe to release if the calibration cannot finish today.
02 PROCEDURE
The OE procedure and target setup for this vehicle
Every vehicle has its own requirements: target type, target distance, height, angle, ambient light, fuel level, tire pressure, and whether cargo has to come out. Getting this wrong is not a sloppy job. It is an invalid calibration, and the pass it produces means nothing.
Prepared: the procedure and its prerequisite checklist pulled to the job before the vehicle reaches the bay. Human: confirming conditions and running the procedure as written.
03 CONSTRAINTS
Target space, rack, lighting, static versus dynamic
A static procedure needs a dedicated bay with the clearance the target distance requires and controlled lighting. A dynamic procedure needs a straight road, a driver, and conditions that may not exist the day the vehicle is ready. This is where a queue backs up: the vehicle waits on a room, not a person.
Prepared: the calibration scheduled against the bay and equipment it needs, with dynamic runs routed to a slot where road conditions hold. Human: judging when a bay is fit to use and when a dynamic run should be called off.
04 DOCUMENT
The record, built from what was done rather than remembered
The calibration report is what leaves the shop. It goes to the body shop that sublet the vehicle, to the insurer, and sometimes to the owner. Rebuilding it at the end of the day from memory is how references go missing, and it is also where the physical procedure stops being trackable at all.
Prepared: the report assembled from the job record, with both scans, the procedure reference, and the outcome in place. Human: the pass or fail judgment, and the signature.
05 RELEASE
Whether this vehicle is going back out
A vehicle with an uncalibrated safety system should not be treated as finished work. The release decision has to be visible on the job, and so does the reason, because the alternative is a vehicle leaving with an unrecorded fault.
Prepared: the job held open until a calibration outcome exists, and a redirect prepared for the cases that need one. Human: the release itself. That is the sign-off, and it belongs to the shop.
Four ways a calibration ends
"Not calibrated" is a legitimate outcome, and it needs its own state.
Most job tracking has two states: done and not done. A calibration has at least four, and collapsing them is what makes a shop's records unreliable.
Outcome 1
Calibrated to procedure
The procedure ran as written, the conditions were confirmed, and the post-scan shows the system reporting correctly. The record names the procedure and both scans.
Outcome 2
Calibrated with a documented deviation
The procedure passed but a prerequisite was not exactly as specified, and the deviation is written down. Honest only when the deviation is on the record, never when it lives in memory.
Outcome 3
Not calibrated, redirected
The target set does not cover this make, the space is unavailable, or the system will not accept the calibration. The vehicle goes elsewhere, and the reason goes on the record.
Outcome 4
Not applicable
The repair did not disturb a sensor, so no calibration is required. Record the reasoning: "we did not calibrate it" and "it did not need calibrating" read identically later.
The sublet relationship
Two shops, one vehicle, and a handoff that leaks.
Body shops and general repair shops sublet calibration, and calibration shops take work from both. The friction sits at the handoff, in both directions.
Inbound from a body or repair shop
The vehicle arrives with the repair already performed and one question the sending shop needs answered: is it calibrated, and if not, why. What comes with it is a phone call and a hope.
What helps: the sending shop's job details, the repair that triggered the calibration, and the outcome returned as a document.
Outbound to a dealer or specialist
When the vehicle cannot be calibrated here, someone has to find where it can be, tell the owner, and keep the job alive while it is gone.
What helps: the redirect tracked as an open state with an owner and a follow-up, instead of a note that the customer was told.
This is where the problem stops being technical: the procedure is documented, the equipment is in place, and the vehicle still sits because nobody owns the handoff.
Common questions
The three things shop owners ask first.
Can I do ADAS calibration myself?
Yes, if you own the targets, the space, and the OE procedure for that vehicle. The hard part is the prerequisite conditions: a level floor, the specified target distance, the lighting the procedure calls for, the ride height and tire pressure it assumes, and the pre-scan that comes first. Static procedures need a dedicated bay; dynamic ones need a road and a driver. Miss any and the calibration is not valid.
How much does it cost to calibrate an ADAS system?
No single number covers it, and any page offering one is quoting a different vehicle than yours. The cost turns on how many systems the vehicle carries, whether the procedure is static or dynamic, how much bay time it consumes, what triggered it, whether you own the target set for that make, and whether it must be sublet. The variable that catches shops out is time, not equipment.
What is the best ADAS calibration system?
The best system carries the OE procedures for the vehicles you actually see and fits the space you have. Target sets, alignment rigs, and scan tools are a coverage question before a quality question. Thin coverage for the makes on your lot sends vehicles to a sublet partner.
Bring a week of calibrations
Show us the vehicles that waited on a bay.
Bring the sublets, the redirects, and the jobs that sat for a target set. We will show you where an operating layer kept them moving.