For buyers in EPC, engineering procurement, and industrial equipment purchasing, inspection isn’t a single event — it’s a sequence of gates, each with its own status, and treating the whole thing as one checkbox (“inspection: done/not done”) hides exactly the information an expeditor needs to manage risk.
In plain terms, the sequence runs: both sides agree the inspection plan (pre-inspection meeting) → the vendor confirms the work is ready → inspection happens against that plan and passes or fails → any failure is logged and tracked to a fix → once everything is clear, the goods are formally released to ship. The sections below track each of those stages separately, because collapsing them into one status hides exactly where a PO actually stands.
The pre-inspection meeting (PIM)
Before manufacturing reaches a stage where problems become expensive to fix, a PIM aligns both parties on:
- What inspection standard applies
- Which hold points require witness by the buyer or a third party, and which are vendor-only
- What documentation must be available at each hold point
- Who attends, and how much notice the vendor must give before each hold point
Skipping or rushing the PIM is a common source of disputes later — when a hold point is reached and the buyer wasn’t given adequate notice, or the vendor didn’t realize a particular stage required witness inspection.
The clear-to-inspect gate
Before any inspection can proceed, there’s an implicit gate: is the work actually ready to be inspected? Sending an inspector to a facility where the relevant stage isn’t genuinely complete wastes time and, more importantly, can force a choice between inspecting incomplete work or rescheduling — both of which cost time. Tracking a clear “ready for inspection” confirmation from the vendor, separate from the inspection result itself, avoids this.
Hold points
A hold point is a stage in manufacturing where work cannot proceed until inspection has occurred and passed. Which stages are witness points versus strict hold points isn’t a fixed universal rule — it’s set by the applicable inspection and test plan (ITP) for that specific order, agreed during the PIM. The two categories, as that plan typically defines them:
- Witness points — the vendor can proceed after notifying the buyer, whether or not the buyer actually attends
- Hold points (strict) — work cannot continue until the buyer or their representative has actually witnessed and approved the stage
Confusing these two is a real operational risk. Treating a strict hold point as a witness point can mean a vendor proceeds with manufacturing before an inspection that was supposed to be mandatory.
Pass / fail status
Each inspection stage resolves to a clear status — passed or failed — and this status should be recorded against the specific stage and date, not summarized later as a single overall “inspection status” for the whole PO. A PO can pass three hold points and fail a fourth; collapsing that into “inspection: mostly fine” loses the specific information about where the problem actually is.
NCR raised, NCR closed
A non-conformance report (NCR) is raised when inspected work doesn’t meet the required standard. Two dates matter:
- NCR raised date — when the non-conformance was identified
- NCR closed date — when corrective action was completed and verified
The gap between these two dates is itself useful information: an NCR that sits open for weeks with no movement is a different risk than one closed within days. Tracking NCRs as a simple count (“3 open NCRs”) without individual raised and closed dates makes it impossible to see which ones are actually stalling progress.
Release certificate
Once all applicable hold points have passed and any NCRs are closed, a release certificate (or equivalent documentation, depending on industry and contract) confirms the goods are cleared to ship. Tracking whether this certificate has actually been issued — rather than assuming it follows automatically once inspection is marked “done” — keeps the release decision explicit and auditable.
Inspection completed date
Separate from any individual hold point, tracking the date all required inspection activity is genuinely complete gives a clean reference point — distinct from the vendor’s forecast ready date, and distinct from the release certificate date, both of which can lag behind the actual completion of inspection work itself.
How PIM and inspection status should interact
Whether inspection is gated behind PIM depends on whether PIM actually applies to a given purchase order. If a PO doesn’t require a PIM at all, inspection shouldn’t be artificially blocked waiting for a meeting that was never going to happen. But if PIM does apply, inspection should genuinely stay locked until PIM clearance is recorded — allowing inspection to proceed regardless defeats the purpose of holding the meeting in the first place. Getting this conditional logic right matters more than it might seem: treating every PO identically here either creates unnecessary bottlenecks on POs that never needed a PIM, or removes a genuine safeguard on POs that did.
Guardrails worth building into the process
A few specific situations are worth catching explicitly, rather than trusting that whoever’s closing out inspection will remember to check manually:
- Marking inspection “complete” while a hold point has failed and hasn’t been re-inspected
- Marking inspection “complete” while an NCR raised against that PO is still open
- Recording an inspection completed date that falls before the PIM clearance date, which shouldn’t be possible if PIM genuinely gates inspection
- Closing out a PO’s final status with no release certificate reference on file, even though every hold point shows “passed”
None of these are exotic edge cases — they’re the specific, ordinary mistakes that happen when inspection status is tracked as a single field someone updates by hand, under time pressure, without anything flagging that the update is internally inconsistent with the PO’s other recorded facts.
Why one checkbox isn’t enough
A single “inspection: done” field can’t show you which specific hold point failed, how long an NCR has been open, or whether a release certificate has actually been issued versus just expected. Each of those is a different piece of information, relevant to a different decision — escalating a stalled NCR is a different action than confirming a release certificate before authorizing final payment. Tracking inspection as a sequence of distinct, dated events, rather than a single milestone, is what makes that level of decision-making possible.
The PO Delivery Tracker tracks PIM, hold points, inspection results, NCRs, and release status as connected, dated stages against each purchase order — not a single inspection checkbox.