Pre-delivery inspection is measured almost everywhere as a labour operation and managed almost nowhere as a flow. A technician is allotted a standard time — one manufacturer allows 1.8 hours regardless of model, across a six-section checklist — and productivity is judged against that figure. But the number that actually determines how many vehicles leave the compound this week is not how long an inspection takes. It is how many vehicles go through it more than once. A unit that fails, waits for a part, gets rectified and returns for re-inspection has consumed the standard time twice, occupied a bay twice, and delayed everything queued behind it. That loop is invisible in a productivity report and obvious in a release-to-ship figure. Request the integration datasheet to see PDI flow, rework and release timing measured on the same record.
2026 GUIDE · PDI OPERATIONS
PDI Operations Tracking and Throughput
Inspection flow measured end to end, rework loops made visible, technician productivity judged against real time rather than allowance, and release-to-ship timing that reflects what the compound actually achieves.
Arrive
›
Inspect
›
Rectify
›
Release
↰ back to inspection — the loop nobody counts
Every return trip through this loop consumes the standard time a second time, holds a bay, and pushes the queue behind it. It is the difference between a productive shop and a fast one.
What PDI Is Actually Catching
Worth restating for anyone running a compound rather than a service bay, because the usual framing points at the factory and most of what you find did not come from there.
Damage from transit and handling
Vehicles are tested thoroughly during production, but small issues emerge during shipping, storage and handling. PDI is the safeguard that catches them — which means your own compound and carrier chain generate a share of what the inspection finds.
Storage effects
Batteries, tyre pressures, fluid levels and surface condition all move while a unit sits. The longer the dwell before inspection, the more the inspection has to correct — which links PDI workload directly to compound dwell.
Items shipped deliberately incomplete
Vehicles frequently arrive with items requiring attention as part of preparation — shipping fuses to be removed or replaced, battery terminal connections to be made, and similar transit-protection measures.
Outstanding safety recalls
New vehicles can arrive carrying recall notifications, and outstanding safety recalls must be resolved before delivery. This is a hard gate rather than a checklist item, and it belongs before the inspection begins rather than inside it.
Check the gate before you start the clock
Verify required documentation, recall status and compliance items before PDI begins, not during it. A unit discovered mid-inspection to be carrying an unresolved recall has already consumed technician time on work that cannot result in a release — and it now occupies a bay while a campaign part is sourced. Screening at intake costs minutes and prevents a bay being held for days.
The Six-Section Flow
Published checklists commonly run to six sections and around thirty-five inspection points. The sections matter operationally because they fail differently, and a failure in one has very different rework consequences from a failure in another.
01
Documentation and compliance verification
Paperwork, recall status, and compliance items confirmed. Fast to check and the most expensive to discover late.
If it failsThe vehicle should not have entered the bay. Screen this at intake.
02
Exterior body and paint
Paintwork imperfections, panel gaps and body lines, dents, scratches, wheels and tyres.
If it failsOften a body shop routing with a long tail — the single largest driver of extended cycle time.
03
Interior condition and equipment
Trim condition, controls and features operating correctly, equipment present and complete.
If it failsUsually a parts wait rather than a labour problem — and parts waits are what fill a compound.
04
Mechanical and fluid systems
Engine checks, fluid levels, tyre pressures, leaks, and the mechanical items the manufacturer specifies.
If it failsFrequently correctable in the bay, which makes it the cheapest failure category to carry.
05
Electronic and driver assistance verification
Onboard systems, infotainment, and verification of advanced driver assistance functions — a section that has grown considerably and continues to.
If it failsMay require calibration rather than repair, with its own equipment and time requirement.
06
Road test
Commonly around ten kilometres across both urban and highway conditions. Checks steering remaining centred with the vehicle tracking straight, absence of vibration at moderate and higher speeds indicating wheel balance, and overall performance under real conditions.
If it failsThe most disruptive point to fail, because everything before it has already been consumed.
Note where section six sits. A road test failure means the full standard time has been spent, the bay has been occupied, and the vehicle now returns to the queue carrying a fault that will require its own rectification and a repeat road test. Sequencing the checks that most often fail earlier in the flow — where local practice and manufacturer procedure allow — reduces the cost of each failure without changing what gets inspected.
1.8
hours allotted
×2 when it comes back
How many of your units go through PDI more than once?
Most operations cannot answer this, because a re-inspection is logged as another inspection rather than as a repeat. Bring a month of PDI records to a 30-minute session and we'll separate first-pass units from repeats in Fleet Rabbit, and show which failure section is generating the loops.
Where the Rework Loops Come From
Five loops, each returning a vehicle to an earlier stage. Only the first is a genuine quality find; the rest are process failures wearing a quality label.
A genuine defect found
The inspection worked. The vehicle goes for rectification and returns. This loop is the system functioning correctly, and the only useful lever is shortening the rectification rather than avoiding the loop.
Legitimate
A missed item found later
Something that should have been caught during inspection surfaces afterwards — at handover, or worse, after delivery. Defective vehicles returned entail repairs that could have been completed beforehand, spending duplicated labour hours on work already paid for once.
Avoidable
Parts unavailable at rectification
The fault was found correctly and the part was not on hand, so the unit waits. This is the loop that converts a two-hour job into a two-week dwell, and it is a supply decision rather than a workshop one.
Plannable
Compliance discovered mid-flow
An unresolved recall or missing documentation found after the inspection started. Entirely preventable with an intake screen, and expensive every time because the bay is already committed.
Avoidable
New damage during handling
A unit that passed inspection and acquired damage afterwards, in the yard or during movement. The most frustrating loop because the work was done correctly and has to be done again — and the only defence is condition capture between PDI and dispatch.
Avoidable
Count loops, not inspections
An operation completing four hundred inspections a month on three hundred and forty vehicles has a first-pass rate of eighty-five per cent and sixty loops it is not measuring. Those sixty consumed a hundred hours of allotted time and produced no additional releases. The productivity report shows four hundred inspections and looks healthy; the throughput figure disagrees, and only one of them is telling the truth about capacity.
Technician Productivity, Honestly Measured
Standard time allowances are useful for costing and misleading for capacity planning. Four measures give a truer picture.
← Swipe to see all columns →
| Measure | What it tells you | What it hides on its own |
|---|---|---|
| Inspections completed | Volume of work performed | Whether any of it was a repeat of work already done |
| Actual time against allowance | Whether the standard time is realistic for your models and conditions | Time lost waiting for parts, bays or information, which is not technician time at all |
| First-pass rate | Share of vehicles released after one inspection | Nothing much — this is the measure most operations are missing |
| Defects found per inspection | Whether inspections are thorough or being rushed through | Needs pairing with post-delivery returns to distinguish thorough from over-flagging |
A low defect-find rate paired with a high rate of issues surfacing after handover is the clearest evidence available that inspections are being completed rather than performed. Conversely, a high find rate with almost no post-delivery returns is a shop doing its job — even where the average inspection runs over its allowance. Judge the pair, never the single figure.
Release-to-Ship Timing
The metric the rest of the business cares about, and the one PDI productivity least reliably predicts. Four intervals, and the middle two are usually where the days go.
Interval 1
Arrival to inspection startQueue time before any work begins. Driven by bay capacity, scheduling and whether the unit was screened at intake — and it is pure dwell, adding nothing.
Interval 2
Inspection to rectification startThe gap between finding a fault and beginning to fix it. Usually a parts availability or scheduling gap, and frequently the longest single interval in the whole chain.
Interval 3
Rectification complete to re-inspectionThe second queue. A rectified vehicle waiting for a bay it already occupied once, competing with new arrivals for the same capacity.
Interval 4
Release to dispatchPassed and ready, waiting for a carrier slot or a load. Worth measuring separately, because it belongs to transport rather than to the shop and mixing them obscures both.
Where the schedule actually breaks
Delivery schedules slip as sold vehicles accumulate in the service bay, and the accumulation is rarely caused by slow inspection. It is caused by units sitting in intervals two and three — found faulty, waiting for something, occupying space. An operation that halves its parts-wait interval gains more throughput than one that shaves ten minutes off every inspection, and the first costs nothing in labour.
Paper Is the Constraint Nobody Prices
Four documented consequences of running the process on paper or on memory, all of them costs that appear somewhere other than the inspection line.
01
Time and energy lost to the checklist itself
Inspectors either spend excessive effort working through paper checklists or work from memory, which is fallible by definition. Neither produces a record anyone can query afterwards.
02
Common issues missed
Items that an effective inspection should have detected slip through — and each one becomes a post-delivery return, a duplicated repair, and a satisfaction problem.
03
Duplicated labour hours
Vehicles returned for repairs that could have been completed before delivery consume costly hours doing work that was already paid for once. This is the rework loop expressed as a wage cost.
04
No data to improve from
The compounding cost. Without structured records there is no first-pass rate, no failure distribution by section, no parts-wait analysis — and therefore no way to identify which of the five loops is actually consuming your capacity.
The fix is not a different checklist, it is a structured workflow — the same digital approach used for reconditioning, applied to new vehicle preparation, so that everything is tested and evaluated properly without wasting time and each result lands somewhere it can be counted. The inspection content does not change. What changes is whether the operation can see itself.
Making the Flow Visible
Six things to record per vehicle. Together they turn PDI from a labour line into a managed process.
VIN and every pass through the flowFirst inspection, rectification and each re-inspection recorded as distinct events rather than as separate jobs — the only way a loop becomes visible.
Failure section and itemWhich of the six sections failed and on what. The distribution tells you where to invest, and it is usually concentrated far more narrowly than expected.
Timestamps at every stage transitionArrival, start, fail, rectification start, complete, re-inspection, release, dispatch. This is what produces the interval breakdown.
Reason for any waitParts, bay, technician, information, campaign. Waiting time attributed to a cause is actionable; waiting time in aggregate is just a number.
Technician and actual timeAgainst allowance, but reported alongside first-pass rate so speed and thoroughness are judged together rather than one at the expense of the other.
Condition capture at releaseSo damage acquired after a passed inspection is attributable to the period after it, rather than reopening the question of whether the inspection was done properly.
Twenty minutes on your PDI volume, first-pass rate and release timing
On a working session we'll take a month of PDI records into Fleet Rabbit, separate first-pass units from repeats, break the release-to-ship time into its four intervals, and show which failure section and which wait reason are consuming the most capacity. You keep the breakdown either way — and most operations discover their constraint is not where their productivity report suggested.
Frequently Asked Questions
How long should a PDI take?
It varies by manufacturer and model, and it is normally set as a standard allowance rather than measured. One manufacturer allots 1.8 hours regardless of model across a six-section checklist; a large executive saloon at a premium brand takes considerably longer. The allowance is useful for costing and poor for capacity planning, because it describes a single clean pass and says nothing about vehicles that go through the process more than once.
What should we check before the inspection starts?
Documentation, recall status and compliance items. Outstanding safety recalls must be resolved before a vehicle is delivered, so a unit carrying one cannot be released regardless of how well it inspects. Screening at intake takes minutes; discovering it mid-inspection means technician time has been spent on work that cannot produce a release, and a bay is now held while a campaign part is sourced.
Why is our throughput poor when productivity looks fine?
Almost always because repeat passes are being counted as inspections. An operation completing four hundred inspections on three hundred and forty vehicles looks productive and has sixty rework loops nobody is measuring — around a hundred hours of allotted time that produced no additional releases. Measure first-pass rate alongside inspection volume, and the two figures will disagree in a way that explains the throughput gap.
Which rework loops are actually avoidable?
Three of five. A genuine defect found during inspection is the system working — only the rectification speed is improvable. But items missed during inspection and surfacing later, compliance issues discovered mid-flow, and damage acquired after a passed inspection are all avoidable, and each carries duplicated labour on work already performed once. Parts unavailability sits in between: not avoidable in the moment, but entirely plannable from failure history.
Where does release-to-ship time actually go?
Rarely into the inspection itself. Break it into four intervals — arrival to start, inspection to rectification start, rectification complete to re-inspection, and release to dispatch — and the days usually sit in the middle two, where vehicles wait for parts or for a bay they have already occupied once. An operation that halves its parts-wait interval gains more throughput than one shaving ten minutes off every inspection, at no labour cost at all.
Does the inspection catch factory defects or our own damage?
Both, and the balance matters. Vehicles are thoroughly tested during production, but issues emerge during shipping, storage and handling — which means a meaningful share of what PDI finds originated in your own compound and carrier chain rather than at the plant. Tracking failure items against transit and dwell history is what separates the two, and it turns a quality problem into a handling one where that is the real cause.
Where should we start?
By recording each pass through the flow as a distinct event against the VIN, so first-pass rate becomes calculable. That single change reveals the rework volume and, with the failure section recorded alongside, shows where it originates — which is usually far more concentrated than anyone expects. Everything else on this page follows from having those two numbers. Book a session with a month of PDI records and we'll produce them with you.
Measure the Loop, Not the Lap
Compliance screened at intake, failures recorded by section, every repeat pass counted as a repeat, waiting time attributed to a cause, and release-to-ship broken into intervals — so the constraint is visible rather than inferred from a productivity figure that cannot see it.
Inspection content and time allowances vary by manufacturer — follow the applicable procedure and franchise standards for each brand · Bring a month of PDI records to the call
August 31, 2026By Alex Rowan
All Blogs
