The Difference Between Scrubbing an Estimate and Completing One

An estimate scrubber can't find what was never written. That's the core problem with relying on one for not-included operations on modern vehicle repairs.

What "Not-Included" Means on a P-Page

Every estimating platform, CCC ONE, Mitchell, Audatex, is built on a database of labor times developed by MOTOR Information Systems. Those times cover the core operation. They do not cover every associated task the OEM requires to do that job correctly.

The platform calls those associated tasks "not-included operations." They're documented in the P-pages: the procedural notes attached to every operation in the database. Flash time between coats. Corrosion protection on bare aluminum. Trial fit before panel installation. Camera R&I when a liftgate replacement blocks a sensor. Jamb refinish when a door opens to a freshly painted adjacent panel.

These aren't edge cases. They're standard OEM-required steps on common repairs. The platform defaults to not-including them because they require a judgment call about the specific vehicle and damage. That judgment call is your estimator's job. The platform won't flag what it never calculated.

And here's the other part nobody talks about: estimators who've been burned enough times start pre-removing line items before the estimate goes out. They know what carriers push back on, so they don't write it. That's learned helplessness baked into the estimate itself. A scrubber can't reverse what was never written. It has nothing to work with.

How Many Not-Included Operations Did Your Last Aluminum Job Capture?

This is the question worth asking before your next supplement.

Under 5 operations flagged on an aluminum panel repair is typical for a scrubber output. The scrubber cross-references what's on the estimate against common missed items. It can't generate operations that were never written.

A RAM 2500 aluminum liftgate replacement had 16 not-included operations identified through a full OEM procedure cross-reference: corrosion protection on bare aluminum, seam sealer application, trial fit, camera R&I, jamb refinish, and more, all documented in Stellantis's own service procedures. The shop was on its fifth supplement and considered the job done. All 16 were in the OEM procedures. Zero were on any version of the estimate.

That's not a scrubbing problem. A scrubber running against that estimate would have returned a clean result. Nothing to flag. Nothing to add. The gap was upstream, before the first line was written.

When one estimator was asked how long it would take to research those operations manually, his answer was direct: "You're talking a couple hours. At least." That's the real cost of not having a systematic process. The missed revenue, and the hours spent chasing it after the fact.

RepairLogic's data shows shops using OEM procedure research tools find an average of $151 in previously missed operations per repair order. That's a per-job average across all repair types. On aluminum-intensive vehicles with complex sensor packages, the number is higher. But the pattern is the same: 14 small misses per job, each documented in OEM procedures, none on the estimate.

The Fix Is Research Before Estimating, Not After

The way most shops run it: estimate first, scrub after, supplement when denied. That workflow catches transcription errors and line items that were reduced or removed. It doesn't catch what was never researched.

The workflow that closes this gap runs OEM procedure research during the estimate, not as a QA step afterward. Before the first line goes on the RAM 2500 liftgate job, the estimator opens the Stellantis service procedures and works through the full R&I sequence. Every required step that isn't in the platform's calculated time gets added as a manual line item with the OEM source cited.

SCRS's DEG database confirms this pattern holds across all three estimating platforms: steering gear initialization after replacement is not included in any of them. Camera prep steps before ADAS aiming are not included. OEM research time itself is not included. These are consistent, documented gaps, not anomalies on one job.

We covered the broader distinction between scrubbing and documentation-first estimating in this week's post on estimate scrubbers vs. Estimate Optimizer. The short version: a scrubber flags what's there. A documentation-first process captures what's required.

The Bottom Line

If your supplement count is high and your approval rate is frustrating, the problem may not be how you're fighting the carrier. It may be how the estimate was built in the first place. A scrubber audits the record you already created. It can't audit a record that doesn't exist yet.

Closing the not-included operations gap requires OEM procedure research before the estimate leaves the building. Tools like Estimate Optimizer™ run that cross-reference automatically, flagging every operation the platform defaulted to not-included and attaching the OEM source documentation so the carrier is already obligated to pay before anyone pushes back.

The shops recovering the most per job aren't fighting harder on supplements. They're building the case before the estimate is submitted.