Incoming inspection best practices — inspecting against the GRN

What incoming inspection is

Incoming inspection — sometimes called incoming goods inspection, receiving inspection or incoming quality control (IQC) — is the check a manufacturer performs on purchased material and bought-out parts before they are accepted into stock and issued to production. It is the first quality gate in the plant, and the cheapest place to stop a defect: a non-conforming casting caught at the receiving dock costs a fraction of the same casting discovered after it has been machined, assembled and shipped to a customer.

For an IATF 16949 or ISO 9001 supplier, incoming inspection is not optional paperwork. It is how you verify that what a supplier delivered actually matches the drawing, the purchase order and the agreed specification — and it is the evidence an auditor expects when they ask, “how do you control the quality of material you did not make yourself?” Done properly it also feeds your supplier quality data: every rejection at receiving is a data point about a supplier’s real performance, not the performance printed on their certificate of conformance.

Why you inspect against the GRN

Most quality problems at receiving are not measurement problems — they are reconciliation problems. Material arrives, a store person books a goods receipt note (GRN), and somewhere else an inspector fills a separate inspection sheet on paper or in a spreadsheet. The two records never join up. Nobody can say with certainty which received lot a given inspection covered, how many pieces were accepted versus rejected, or whether the rejected quantity was actually held back from issue.

The best practice is to make the inspection an operation on the goods receipt itself. When incoming inspection is booked against the GRN line, the received quantity, the item, the supplier and the purchase order are all inherited from the receipt — the inspector does not re-key them, and there is no ambiguity about what was inspected. More importantly, the disposition then drives stock: accepted quantity is released into usable inventory, rejected quantity is held in a quarantine or reject location, and the numbers reconcile because they came from one record.

This is exactly the structural advantage an integrated quality-and-inventory system gives you. In Fast Quality Software, InspectionAgainstReceipt pulls the received line straight from the store receipt, so inspection results are booked against the real GRN and the accepted/rejected quantities move actual stock — where a bolt-on spreadsheet leaves the inspection in a different file from the receipt and the reconciliation to a human at month-end.

The incoming inspection procedure, step by step

Whatever you receive — castings, forgings, machined parts, raw bar, fasteners or bought-out assemblies — a disciplined incoming inspection follows the same sequence. Each step is a real action in the system so the whole flow is traceable rather than anecdotal.

The step that most plants skip is allocation — putting the receipt into a controlled pending queue with an owner. Without it, inspection depends on someone noticing that material has arrived. With a pending-inspection list, nothing sits at the dock uninspected and untracked; the inspector works a queue and a manager can see the backlog. In Fast Quality this is the inspector’s pending list and dashboard, and the disposition step is where the lot is judged against the item’s specification.

Building the inspection checklist from the specification

An incoming inspection checklist is only as good as the specification behind it. If the checklist is a free-text sheet that each inspector fills from memory, two inspectors will check two different things. The best practice is to derive the checklist from a single specification master that holds, per item, the characteristics to check, the nominal value, the upper and lower tolerance limits and the acceptance criteria.

A well-formed incoming checklist usually covers four layers:

• Documentation — does the delivery carry the certificate of conformance, material test certificate (MTC) or heat-number traceability the part requires?
• Identity & quantity — is it the right item and revision, in the quantity the GRN says, with correct labelling and packaging?
• Dimensional — the measured characteristics against nominal/USL/LSL, using a specified, calibrated gauge for each.
• Visual & functional — surface finish, damage, corrosion, and any go/no-go or functional check the characteristic demands.

Because the specification master feeds both incoming inspection and downstream in-process inspection and SPC from one source of limits, the number an inspector records at receiving is measured against exactly the same tolerance the process is later held to. There is no second, slightly-different spreadsheet of limits to drift out of sync.

Sampling — how much of the lot to check

You rarely inspect every piece. The question is how much of a lot to sample so that the accept/reject decision is statistically defensible without inspecting 100 %. Most manufacturers work to a published sampling standard — commonly ISO 2859-1 (equivalent to the older MIL-STD-105E / ANSI Z1.4) for attribute inspection — which uses the lot size and an Acceptable Quality Level (AQL) to give a sample size and an accept/reject number.

Three practical rules keep sampling honest:

• Tie the AQL to the characteristic’s severity. Safety and special characteristics (flagged from the FMEA and control plan) warrant a tighter AQL — often zero-defect sampling — than cosmetic features.
• Use tightened, normal and reduced inspection. A supplier with a clean history earns reduced sampling; a supplier that just failed moves to tightened inspection until they prove themselves again.
• Record the sample, not just the verdict. The individual readings — not merely “pass” — are what let you calculate capability later and defend the decision in an audit or a supplier dispute.

A mature receiving process is dynamic: the sampling plan tightens or loosens based on the supplier’s measured rejection history, and a supplier who consistently ships to spec can graduate to skip-lot or dock-to-stock arrangements that cut inspection cost without cutting risk.

Disposition — AC, RJ and AD

Every inspected lot ends in one of three dispositions. Getting this vocabulary right — and applying it consistently — is what separates a real quality gate from a rubber stamp.

The AD disposition is the one most often abused. Accept-under-deviation exists for genuine situations — a minor cosmetic non-conformance on an urgently needed lot, accepted for a defined quantity with sign-off — not as a convenient way to make a rejection disappear. Best practice is to route every AD through a formal deviation approval, with an approver, a reason and a boundary, so the concession is visible and finite rather than a habit. In Fast Quality, a minor non-conformance is dispositioned AD only through a controlled deviation-approval step, while an RJ raises a material rejection.

Closing the loop with the supplier

An incoming rejection that stops at “reject and return” is a wasted opportunity. The point of catching a supplier defect is to make it not happen again, and that means the rejection must carry enough structured data to drive action. Best practice tags every material rejection with a defect code and the supplier, so the same defect language links receiving, the supplier scorecard and any corrective action that follows.

From there the loop has three outlets. A one-off, low-severity rejection may simply be returned and replaced. A rejection that carries real cost becomes a supplier claim. And a significant or recurring supplier defect escalates into a full 8D, where the supplier finds the root cause and proves the permanent fix — feeding your NCR, rejection and 8D/CAPA process and, where relevant, a control-plan amendment through change management. Because every rejection is coded, a Pareto by supplier and defect tells you which to attack first, instead of chasing whichever complaint shouted loudest this week.

How Fast Quality runs incoming inspection

Fast Quality Software implements every best practice above as a working workflow, built by Improsys in Pune on the shared Fast Suite platform and deployed cloud or on-premise:

Because it rides one shared platform, incoming inspection ties natively to the goods receipt from production and inbound, and calibration follow-up keeps every gauge used at receiving in-date. For the wider picture, see the pillar guide on what quality management software is, and the sibling operations guides below.

Frequently asked questions