Inspection cycle time
Inspection cycle time explained: what is inspection cycle time?
Inspection cycle time is the total elapsed time between the moment an inspection is requested and the moment a usable report exists for someone to act on. It is measured in calendar hours or days, including nights, weekends and waiting, because that is the time the customer, the asset or the decision actually spends held up.
The metric is also called inspection turnaround time or inspection lead time. In insurance it sits inside the broader claims cycle time, where the inspection is one segment of a longer clock.
How is inspection cycle time calculated?
End timestamp minus start timestamp, reported as a median rather than a mean. Where you put those two timestamps matters more than the arithmetic.
- Start at the request, not the visit. If the clock starts when the inspector arrives, every hour of scheduling delay disappears from the number.
- Stop at usable, not submitted. A report that still needs a reviewer's sign-off before anyone can act on it is not finished work.
- Report the median and the 90th percentile. The mean is dragged around by a handful of stalled cases. The 90th percentile is what your complaints are about.
- Use calendar time. Working-hours-only clocks make a four-day wait look like sixteen hours and remove the weekend problem from view.
A common reporting error is measuring only the middle: clock starts at capture, stops at submission, and the dashboard proudly shows three hours out of a process that really takes six days.
The four segments of inspection cycle time
A single elapsed number tells you there is a problem and nothing about where it lives. Split it at four points and the picture changes.
- Request to capture. From the inspection being raised to someone physically starting it. Scheduling, travel, access, availability, and the person on site simply not getting to it.
- Capture to submission. From the first photo to the completed report leaving the site. Form length, connectivity, and paperwork done in the van at the end of the day.
- Submission to review. Queue time. The report exists and nobody has opened it yet.
- Review to decision. From a reviewer opening the case to a recorded outcome, including any round trip for missing evidence.
A worked example: where 156 hours actually goes
A facilities team requires 320 condition inspections in a month and closes 288 of them, an inspection completion rate of 90 percent. Across those 288 the median cycle time from request to usable report is 156 hours, or six and a half days.
Broken into segments, the median case runs 103 hours from request to capture, 4 hours from capture to submission, 31 hours sitting in the review queue, and 18 hours from a reviewer opening it to a recorded decision. Two thirds of the total elapsed time is spent before anyone points a camera at anything.
The management attention in that team was aimed almost entirely at the last segment, the 18 hours, because that is the part with a named person attached to it. Halving reviewer time saves 9 hours out of 156. Halving the request-to-capture wait saves 51.
Why the dominant segment is rarely the assumed one
Teams reliably guess wrong about this, and the reason is structural rather than careless. Review time is visible: it has a queue, a name, and a person who can be asked why. Waiting time has no owner, so nothing reports it.
Three patterns show up repeatedly once the segments get measured:
- Request to capture is usually the largest and least managed segment. It is dead time in a diary rather than slow work, so it never appears in a productivity review.
- Submission to review is spiky, not slow. Median queue time can look fine while Friday afternoon submissions sit until Monday. Plot it by day of week before optimising anything.
- Round trips are hidden inside the last segment. A retake request for a missing angle restarts a mini-cycle of its own. Count retakes separately or their cost stays buried in an average.
How inspection cycle time relates to completion rate
They share a denominator problem, and reading one without the other is how teams get surprised. Cycle time can only be measured on inspections that finished. In the example above, the 32 inspections that were never carried out contribute nothing to the 156 hours, so the reported cycle time describes the compliant population only.
Worse, closing a record early improves both numbers at once. A record marked done without the asset being seen raises completion rate and shortens cycle time. Any pairing of these two metrics needs an inspection audit underneath it, or you are measuring administrative speed.
What actually shortens the clock
Since the front segment usually dominates, the effective moves target waiting rather than working: sending the request the same day the need is identified, removing the appointment where an appointment is not needed, and making the first submission complete enough that no round trip is required.
That last point is where asynchronous capture changes the arithmetic. Venta Capture, a product of VentaVid, sends a link to whoever is already at the location and guides them through the required steps in their phone browser, so the request-to-capture segment stops depending on aligning two calendars, and the submission arrives structured enough to review without a chase.
