An incoming inspection plan decides what gets checked before a component reaches the line, how much of it, and what record proves the check happened. Written badly it becomes either a full inspection nobody can afford or a signature that means nothing. Written well it puts the effort on the lines where a defect is expensive to find later, and leaves the rest to sampling with a history behind it.
The plan is also the first place where a shortage gets absorbed badly. When a line is short, an inspector under pressure accepts a lot on deviation, and the record that would have flagged the risk is the one that gets skipped.
Why incoming inspection plans fail
The first failure is one sampling level for everything. A 0402 resistor and a GaN transistor do not carry the same consequence, and a plan that treats them the same either over-inspects passives or under-inspects the parts that stop a build.
The second is inspection at the wrong point. Once a part is inside a kit, the lot identity blurs, and a defect found at first article can no longer be traced to the reel it came from.
The third is a record that does not survive. If the result is a tick on a sheet with no lot, no inspector and no characteristic, it answers nothing when a customer asks two years later.
The fourth is no feedback loop. Inspection data that never reaches the supplier score means the same lot arrives again next quarter with the same defect, and the plan keeps paying for it.
The plan by part class
Most plans become workable once the BOM is split into part classes and each class gets a level, a characteristic list and a record format. The table below is the shape we use.
| Part class | Level | What is checked | Record |
|---|---|---|---|
| Chip passives | Sampling | Value, tolerance, marking, reel count | Lot and result |
| RF transistors and MMIC | Count all, sample test | Marking, date code, DC or S parameter sample | Lot and test data |
| Analog and mixed signal ICs | Sample plus provenance | Marking, date code, lead finish, decap where risk justifies | Lot and image |
| MCU and memory | Sample plus provenance | Same as above, package condition, revision check | Lot and image |
| Crystals and oscillators | Sampling | Frequency at 25 C, marking, date code | Lot and result |
| Connectors and mechanical | Visual sampling | Plating, key dimensions, mating check | Lot and result |
| Modules | Sample functional | Firmware revision, band, current draw | Lot and result |
| Bare PCB | Per batch | Impedance coupon, microsection on first batch, solderability | Test report |
| Moisture sensitive parts | Register check | Floor life, bake record to J-STD-033 | Bake log |
| Cable and harness | Continuity all | Pinout, pull test on sample | Lot and result |
Where the zero accept rule belongs
A sampling plan is reasonable for a mature line with history: same maker, same part, no recent escape. It stops being reasonable on a new maker, a new part number, a lot from a secondary route, or any line that has already escaped once. Those go to zero accept on the characteristics that matter, which usually means marking and date code, provenance evidence, and one electrical check that would move if the die were wrong.
Whatever the level, the record has to name the lot, the quantity received, the sample size, the characteristic, the result and the inspector. That is the minimum a customer audit asks for, and it is also the minimum that lets a decision be reviewed later without arguing about memory.
How SUPERB PCBA runs the plan
Receiving is a physical process, not a paperwork step. Components are counted by X-ray, markings and date codes are compared with maker data, parts that carry provenance risk are opened and checked, and aged stock is verified for solderability before it is released to a kit. Moisture sensitive parts sit in a register and are baked at 125 C to J-STD-033 before use, stored under ANSI/ESD S20.20 in an SMT area held at ISO 8, 22 plus or minus 3 C and 45 to 65 percent relative humidity.
The plan continues inside the build rather than stopping at the door. First article is checked on a JCX-830 against the CAD data, paste volume runs on 3D SPI, 3D AOI and DIP AOI cover placement and joints, X-ray in 2D and CT is judged to IPC-7095 with voiding below 5 percent, and ICT on a bed of nails plus flying probe is followed by functional test on fixtures built internally. The flow runs seventeen steps with ten QC stations, at IPC-A-610 Class 2 or Class 3, under ISO 9001 and ISO 13485 for medical programs. The test sequence itself is compared on ICT versus FCT testing.
Inspection output is reported, not kept internally: the standard shipment report, a microsection report where the program asks for it, and an impedance test report on RF boards where a TDR coupon is built into every panel. Verified lots carry a 730 day warranty, and a pin to pin change is made only with written approval. What an inspection can and cannot prove about a part is covered on component inspection and counterfeit detection, and the wider test flow on PCB testing. Where optical and X-ray methods overlap, AOI versus X-ray inspection sets out which one answers which question.
Signing the plan off
Four questions are worth settling before the plan becomes a controlled document. Who owns it, and who is allowed to change a level. Which characteristics are critical, and who decided that. What happens to a failed lot, meaning segregation, review, return, or a deviation with a name against it. And which supplier moves to a higher level next quarter, and on what evidence.
A plan that answers those four can be defended in an audit. A plan that only lists characteristics is a wish list with a revision number.
Incoming inspection plan questions
Should any line be inspected one hundred percent?
Only where a single escape stops the build and the measurement is cheap. Continuity on a harness qualifies. Visual inspection of a thousand passives does not, because attention fails before the lot ends.
Where should incoming inspection sit?
At receiving, before kitting. After kitting the lot identity blurs, and a defect found at test can no longer be pointed at a reel.
How much record is enough?
Enough to answer a field return two years later: lot, date code, characteristic, result, inspector, and the board serials the lot went into.
Can a supplier report replace our own inspection?
For a supplier with history and a clause that lets you audit the method, on a defined list of characteristics. Not for a first lot, and not for a part bought through a secondary route.
Next step
Send the BOM with part classes and quantities, plus the characteristics your product cannot tolerate. The reply maps an inspection level, a characteristic list and a record format to each line before the kit is built, so the plan is agreed before the first lot lands.