The Waiting-List Test: collision claim tracking from the shop's seat

Who this is for

This test is for collision shop owners, office managers and estimators who are looking at AI or software for claims, or who just want to see where their open files are stuck. It goes with our short video on the Waiting-List Test and the longer page on AI for collision claims.

The point from the video: you'd think a claims tool should argue with the insurer for you, but the honest job is smaller. Your clock and the insurer's clock don't agree. The insurer counts days from report to settlement. You count days the car sits in a bay, days a rental burns, and days between finishing the repair and getting paid.

There's more than one way to count it, too. CCC's guide to measuring cycle time performance describes cycle time from vehicle in to vehicle out, from repair start to repair complete, from loss reported to vehicle out, and by length of rental. The Waiting-List Test doesn't pick one for you; it shows which files are waiting, whatever clock you use.

The question to ask

In any demo, or of your own system, ask exactly this:

List every open file where we're waiting on someone else, oldest first.
For each one, show who we're waiting on and since when.

A good answer is a short sorted list, each row with an age, the file, and who holds it. A status screen answers with charts, colors or "in progress" on every row. If the tool can't tell you who you're waiting on, it can't help you chase them.

The seven claim stages, and where each stalls

Stage	Where it stalls for the shop	What the list should show
1. First notice and who is paying	Deductible, coverage or payer unknown, and nobody asks	Missing carrier, claim number, deductible or payer on the job
2. DRP or non-DRP	Staff mix up the two sets of rules	Which path the job is on, and its checklist
3. Estimate and appraisal	The file sits in insurer review with no visible clock	Days in review, and what is holding it
4. Supplement	Hidden damage found, approval takes days	Days since the supplement was sent, photos attached
5. Total-loss threshold	A teardown turns into a settlement conversation	Repair position against vehicle value, early
6. Rental and loss of use	Rental days end before the repair does	Rental end date against projected completion
7. Getting paid	The receivable ages and nobody owns it	Invoice matched to claim, the missing document holding payment

Stages 3, 4, 6 and 7 are where the week usually goes: an approval, a supplement, a rental and a payment, each sitting on someone else's desk.

Why the waiting is getting longer

The supplement and total-loss stages carry more of the work than they used to. CCC data reported by Repairer Driven News found 56.5% of Q1 2025 DRP calibrations appeared on a supplement, and that repairs with multiple calibrations averaged more than 17 days keys to keys. Total losses are rising as well: Autobody News, citing CCC, reported total loss frequency at 22.8% through October 2025, up from 22.1% a year earlier. More supplements and more total-loss conversations mean more files parked on someone else's desk.

The waiting reasons to track

Give every waiting file one reason, so the list can be sorted and chased:

• Waiting on appraiser: estimate in review, re-inspection requested
• Waiting on insurer approval: supplement sent, decision pending
• Waiting on customer: deductible, authorization, a signature
• Waiting on rental: extension needed before the projected completion
• Waiting on vendor: a part or sublet with no date
• Waiting on payment: invoice sent, a document missing

Each row on the list then reads like this (demo): "6 days · Estimate C-2207 · waiting on appraiser".

What AI must never do inside a claim

AI doesn't negotiate with an insurer, decide fault, sign a direction to pay or a release, or answer a coverage question, because coverage is between the carrier and the policyholder. It doesn't give legal advice or argue a number in front of an appraiser. A person owns the estimate, the supplement and the appraiser relationship.

What the system does is narrower: it watches the clock, keeps the file complete, drafts the customer update so nobody is left guessing, and puts the item in front of someone who can act. Risk frameworks such as the NIST AI Risk Management Framework start with governance, deciding who is accountable for what a system does. In a claim, that line is simple: the system shows the waiting, a person decides.

Run the list yourself, every Monday

1. Pull every open collision job.
2. Mark each one that's waiting on someone else, with the reason from the list above.
3. Write the date it started waiting.
4. Sort oldest first.
5. Give each of the top five a person and a next step for today.

Do it by hand for three Mondays before you buy anything. If the top of the list is always rentals, start there. If it's supplements, look at how quickly they're raised after teardown.

Where RevvOS fits

RevvOS doesn't negotiate claims or replace your estimating platform. It reads the jobs you connect, shows what's waiting and on whom, and drafts the next step for a named person, with the source on every item. See how collision estimate automation handles the estimate side, or book an assessment and bring a week of open claims.