The estimate went in on Tuesday and came back on Thursday
An estimator walks round a customer's car in the car park with a phone, takes a dozen photos, and uploads them with the estimate. Two days later the engineer's note arrives: no photo of the VIN, no odometer reading, the rear quarter damage is not visible from the angle supplied, please resubmit. By then the customer has been told the car will be booked in next week.
It is rarely laziness. It is a wet car park, a customer in a hurry, a phone full of other jobs' photos and a slightly different list of required images for each insurer. One wants four corners, another wants eight. One wants the paint code label, another does not care.
Photos are taken on memory, not on a checklist
Most shops have a laminated sheet somewhere saying which images to take. Nobody reads it in the rain. The phone camera does not know which job it is photographing, so pictures are sorted afterwards on a desktop, sometimes into the wrong job folder, and the upload to the estimating system or provider portal happens later still.
- Required shots vary by work provider and sometimes by damage type.
- Photos are named by the phone, not by job or position, so gaps are hard to spot.
- Blurry or dark images only get noticed by the engineer.
- Images from two cars of the same colour can end up in the same folder.
The days lost each time a set bounces
Every rejected image set restarts part of the authorisation wait. The car either sits in your yard taking up space, or the customer is still driving it and has to come back for more photos. The estimator repeats a walk round they already did, and the front desk makes an awkward call explaining the delay.
It also counts against you. Work providers look at how often estimates need more information, and a shop that regularly resubmits images looks less organised than it is.
How we build guided image capture
- The estimator opens the job on a phone or tablet app, found by registration or job number, so every photo is tied to the right job from the start.
- The app shows the shot list for that work provider: each corner, VIN plate, odometer, paint code, damage wide, damage close, interior if required.
- Each photo is taken against its slot, named automatically and time stamped. Extra photos can be added freely.
- A simple quality check flags images that are very dark or blurred so they can be retaken while the car is still there.
- Until every required slot is filled, the set is marked incomplete and the estimator is told which shots are missing.
- The complete set is sent to your estimating system, job folder or provider route in the order and naming that provider expects, where an upload route exists.
| Check | Before | With guided capture |
|---|---|---|
| Which shots are needed | Estimator's memory | Provider's list on screen |
| VIN and mileage | Often forgotten | Required slots |
| Photo filing | Sorted later on a PC | Attached to the job when taken |
| Poor quality image | Found by the engineer | Flagged on the spot |
The app does not judge the damage or write the estimate. Estimating stays in the system you use now, such as Audatex, and with your estimator.
What changes on the forecourt
Estimators spend the same few minutes with the car but leave knowing the set is complete. The office stops sorting photos into folders. If an engineer does ask for more, the reply is usually a specific extra angle rather than basics that were missed.
Because every image carries its job, date and position, the same photos are there later when you need to show the condition of the car on arrival.
Is this happening in your shop?
- Engineers ask for VIN, mileage or wider shots more than occasionally.
- Photos are moved from phones to a PC and sorted by hand.
- Different insurers want different image sets and staff mix them up.
- Customers have come back just for extra photos.
- You cannot quickly find the arrival photos for a job from last month.