Write the Inspection Plan Before You Place the Order: Acceptance Criteria and One Named Decision Owner

An inspection plan written before you commit money settles four things in writing: what you are checking, how much of it will be looked at, who decides whether the result is a pass, and what happens next when it is not. If those answers exist only in someone's head during quoting, the other side is being asked to hit a target that was never described, and any later disagreement is an argument about memory rather than about requirements.

The deliverable below is an acceptance-criteria brief: a short document you attach to the purchase order, containing your criteria and the name of the person who accepts or rejects the lot. Nothing here offers a standard pass rate. Thresholds are yours to set per product, because a limit copied from another category carries none of the reasoning that produced it.

Define acceptable for one product at a time

Start with a physical and written reference. A specification sheet, an approved sample kept under your control, and photographs of failure modes you already know about do more useful work than any adjective in an email. Good enough is not a criterion; a criterion is something two people can look at and reach the same verdict on.

Group the failure modes into three buckets rather than one list: defects that make the item unusable or unsafe, defects a customer would notice and object to, and cosmetic issues most users would not notice. Where the line falls between those buckets is a product decision, influenced by who buys the item and what happens after it reaches them. Write the bucket next to each failure mode, along with the method used to judge it: which gauge or jig, what lighting, what viewing distance, which surface, which side of the unit counts as visible.

Choose when the checks happen

Checks at different moments answer different questions, which is why the timing belongs in the plan rather than in a later conversation.

• Early checks on materials and components tell you whether the build starts from the right inputs.
• A check on initial output tells you the line was set up correctly before the whole run repeats a mistake.
• A check on packed finished goods tells you what you are about to pay for.
• A loading check tells you what actually went into the container, in what quantity and packing.

You do not need every stage on every order. The test is how expensive it is for you to discover the problem late: mistakes caught after shipping cost far more than mistakes caught during production, because by then they carry freight, delay, and an unhappy customer rather than a rework instruction.

How much to look at, without pretending there is a rule for everyone

Sample size and tolerance depend on order size, how the failure modes distribute across a run, and how much risk you can absorb on a single lot. Some buyers inspect every unit of a high-value item; others sample. Both positions are defensible when the buyer can explain why.

What is not defensible is importing a defect percentage from another product line and treating it as a benchmark. That figure was derived from someone else's risk tolerance, someone else's customer expectations, and someone else's cost of being wrong. Instead, set your own limits for this product, write them down, and revisit them once real results come back for the first lot. Treat the first batch as calibration rather than as proof that the numbers were right.

The acceptance-criteria worksheet

Copy this table into your purchase-order document. The rows are deliberately blank: a worksheet you complete from your own product knowledge is worth more than a worked example from somebody else's category.

Failure mode	How it is checked	Bucket	Action if found	Evidence to keep	Decided by
[describe the defect or failure]	[tool, method, lighting, distance, sample piece]	[unusable / customer-visible / cosmetic]	[accept / rework and re-check / hold for written decision / reject lot]	[photo, retained unit, written record]	[name]
[ ]	[ ]	[ ]	[ ]	[ ]	[ ]
[ ]	[ ]	[ ]	[ ]	[ ]	[ ]
[ ]	[ ]	[ ]	[ ]	[ ]	[ ]

Give packing, labelling, quantity and document errors their own rows. Those failures are discovered at the worst possible moment, usually at destination, and are rarely covered by a product-focused checklist.

Above the table, add a header block so nobody has to guess at the context later:

• Order reference and product revision number: [ ]
• Specification version and approved sample held by: [ ]
• Inspection stage or stages commissioned: [ ]
• Named decision owner, plus a named backup: [ ]
• Working contact channel during the inspection window: [ ]
• Time allowed for your decision once the report arrives: [ ]
• Where the report, photos and retained units are stored: [ ]

Name the decision owner

One person should be named as the decision owner for this lot, with authority to say pass or fail, plus a backup who can act if they are unreachable and a clear escalation contact for hard cases. Inspector findings are input to that decision, not the decision itself. When acceptance floats between the factory, the inspector and your own team, nobody owns the outcome and every borderline finding becomes a search for whoever is willing to answer.

Record the role, the working contact during inspection, and explicitly what the owner is NOT deciding. Acceptance of goods is a different question from authorising payment, and an inspection result on its own does not change commercial terms. Keep the two questions separate, in separate written agreements, so an inspection report never gets read as a payment instruction or vice versa.

Decide the fail path while nobody is upset

Write the outcomes in advance, in the same document:

• Clean pass: what the record looks like and who releases the lot.
• Borderline finding: who interprets it, who is allowed to grant a concession, and the requirement that any concession is in writing.
• Rework followed by re-check: who confirms the second check is genuinely independent of the first.
• Rejection: what happens to held goods and what must be true before they are released.

Cost allocation for rework or re-inspection belongs alongside these outcomes and has to be confirmed case by case; it is a commercial term between you and the other party, not something an inspection method settles for you. So does the decision window: set how long the owner has to respond after receiving the report, because goods sitting in a hold cost money on both sides while everyone waits for an answer.

Quality management systems are context, not proof

A supplier's quality management system tells you something about how processes are documented and reviewed. ISO publishes ISO 9001 as a quality management system standard (ISO 9001 overview). Read that as background about process discipline, not as evidence that a particular shipment meets your criteria and not as a verdict on any individual business: a system-level document and lot-specific acceptance criteria answer different questions. This note makes no claim about any edition or clause-level requirement, and nothing here is legal, customs or regulatory advice.

Two related cautions follow from the same idea. A screening or registry check tells you what was examined at that time and nothing more; it is not a certificate, and repeating it later tells you nothing new. And the commercial delivery term agreed for the order does not by itself define either the quality requirement or the payment terms, because those live in your written criteria and your commercial agreement respectively.

What happens after you send a brief

Use the worksheet to identify missing acceptance methods, decision owners and packing checks before discussing a purchase. Sourcing Desk's on-site tool can format your draft brief locally, but it does not transmit it or arrange a review. A supplier match, quotation or next step would need separate case-specific confirmation. This checklist is an editorial suggestion, not a requirement imposed on a counterparty.

Before your next purchase order

Open the worksheet for the one product you are about to buy. List the failure modes you actually worry about for that product specifically, add the method for judging each one, put one name and one backup name in the decided-by column, then attach the sheet to the brief you send for review along with the order reference and your escalation contact. Any row you struggle to fill, usually the method or the consequence column, is the row most worth arguing about now, while changing it still costs nothing.