Where to start, and what happens after the first order

One inspection is one photograph of one moment. It tells you what the shipment looked like on the day someone looked at it. It does not tell you what the next batch will look like.

What carries across batches is the written standard: the sealed golden sample, the specification with tolerances and measuring conditions, the change-notification clause, and the batch records. What has to be repeated is verification — against those documents, not against memory.

A practical schedule for a repeat order:

• Every batch: batch number, key measured values, retained sample, production record.
• Every batch before the balance: inspection against the agreed limits.
• Periodically: targeted testing on the items that drift — solvent residue and barrier for films, colour for printed work.
• Every time something changes: material grade, resin, adhesive, ink, substrate source, grammage, process parameters, subcontracted operation or production site — declare it, approve it in writing, then verify it.

What I can't promise: I cannot guarantee that the second batch matches the first, and I will not sell "one check, permanently valid". Even in regulated systems a declaration of compliance has a validity period — one authority's guidance says update at least every years, with earlier updates when composition changes. If a document has an expiry, an inspection certainly does.

That is your choice, and it should be priced as a choice — not as an implied lifelong obligation.

Three shapes it can take:

• One-off: the verification report before you pay. It stands on its own, and I do not pretend it covers the future.
• Per batch: I check the documents and the numbers each time, and I tell you whether the batch is inside the agreed limits.
• Ongoing: a written update at each milestone, change notices logged, and a short monthly note on what changed at the supplier — status, certificates, and any document that has expired or is about to.

What I will not do is let the first report quietly become the basis for trusting everything afterwards. A check has a date on it.

What I can't promise: I am not liable for a supplier's performance. My deliverable is information: what I found, what I verified, and what I could not. If a supplier goes bad later, that is between you and them — I will tell you what evidence we have and where it is weak.

It works as a form and a date, not as a promise.

The clause says what may not change without written approval: material grade, resin, adhesive or ink supplier, source of substrate, grammage, process parameters, subcontracted operations, production site. It says that verbal approval is not valid. It says the obligation reaches the factory's own suppliers. And it sets the lead time for a request — one car maker's standard requires change requests at least 12 weeks before introduction, which tells you the scale of a real approval process.

In practice, each proposed change comes with a one-page form: what changes, from what to what, why, which batches are affected, what evidence is attached, who signs. One copy for the factory, one for you, and I keep a log with the date.

The part that makes it real is what happens when a change is not declared: the goods can be rejected, and the cost position changes. Without that, the clause is a courtesy.

What I can't promise: I cannot detect every change a factory makes. What I can do is make declarations auditable — the records that should exist for each declared change, checked against the physical goods at the points where I can see them. And I will not tell you that a factory never changes anything; every factory does.

You keep everything, and you should own it from the start.

What I hand over: the report with its evidence list and its limits, the signed and dated sample records, the written specification and clause pack, the inspection records, and the correspondence log with dates. The files are yours; I do not hold your documents hostage, and I do not reuse your project as a public case study without your written approval.

What I keep for continuity: the change log for each SKU, the batch history, the documents I verified with the dates I verified them, and the list of dates on which those documents expire. That last list is where suppliers get caught — a declaration or a certificate that was valid when you started is often not valid two years later.

Retention beyond that is your call. I will tell you what I recommend keeping and for how long, based on the market's rules rather than on my convenience.

What I can't promise: I cannot promise that a document that was valid stays valid. Registration status, accreditation and declarations all change, and I have found published cases where an accreditation was withdrawn and a certificate was declared invalid after the fact. If you want me to keep watching those statuses, that is ongoing work and it is priced as such.

On site, and more than once. As a quality engineer I ran on-site quality-system audits at multiple suppliers, and I was on the receiving end of customer audits too — six of them, from the inside: preparing the plant, then sitting through the findings.

That is the part a desk check cannot give you. Once you have walked an incoming-material area and read the calibration labels on the machines, you stop trusting a certificate that says “ISO 9001” on its own. You start asking which line, which shift, which batch record.

One thing to be clear about: those audits happened in my previous job, as the quality engineer of a manufacturer. I was auditing suppliers to my own employer, not acting as an independent inspector for paying clients. What I sell today is the same skill applied to your order, on your side of the table.

If you want to know precisely what I have and have not done commercially under my own name, ask me and I will tell you plainly. I would rather lose an enquiry than have you discover later that I overstated it.