Card quality plans: connect requirements to tests

A quality plan names the test that proves each requirement and the person who can refuse the lot. Without those two columns it is a list of good intentions.

The gap it closes is narrow and expensive. A purchase specification says what the card has to be. A quality plan says how anyone will know before a pallet ships, and what happens to material already produced when a check fails.

This guide is for whoever signs the acceptance criteria: a technical buyer, a quality manager at a distributor, or an integrator answering for credentials on a live site. It assumes a specification already exists. If it does not, the brief comes first: see what a card order brief has to contain.

01. What a quality plan has to decide

A quality plan answers four questions and nothing else belongs in it: what is being checked, how it is checked, what counts as a pass, and who signs. Procedure, training records and calibration schedules are a different document.

Keep it that narrow because a quality plan is read in an argument. Six weeks after delivery, somebody is holding a card that does not work and asking what was agreed. A four page table that answers those four questions settles it. A forty page manual does not, because it never names the acceptance rule.

Avoid a single quality checked statement on a quotation. It says nothing about what was assessed, on how many cards, against which drawing, by whom. It is not a claim that can be tested later, which is why it appears so often.

02. Assign a test method to each critical requirement

List the checks in four groups, because cards fail in four independent ways: physical, visual, electronic and data. A card can be dimensionally perfect, print perfect, and still be rejected at enrolment.

Physical requirements are the ones with a published standard behind them. ISO/IEC 7810 defines the ID-1 format and its physical characteristics, and ISO/IEC 10373-1 defines how those characteristics are measured, so the test method does not have to be invented. Dimensions, thickness and warp can be written as a requirement, a measured value and a tolerance band: the detail sits in CR80 dimensions, fit and tolerances and in card thickness and lamination.

Visual requirements have no standard and need a physical reference instead. The usable form is a signed master card plus an agreed defect classification: which marks are critical, which are major, which are cosmetic, and at what viewing distance. A plan that says good print quality has delegated the decision to whoever is holding the card at the time. Printing methods and finishes change what defects are possible, so the reference card comes from the same process as the run.

Electronic requirements are checked against the system that will read the card, not against the datasheet. The acceptance rule is a read at a target reader or lock, and zero failures in the sample is the only rule worth writing: a credential that works nineteen times out of twenty generates support calls for years.

Data requirements are the group most often missing. Numbering, barcodes, photo files and encoded identifiers come from a source file, and the check is a reconciliation against that file: no gaps, no duplicates, no offsets. Blank or pre encoded cards decides who owns that reconciliation, which is why it has to be settled before production rather than after.

03. Separate process checks from release checks

Some checks detect a problem while the product is still being made. Others support the final decision to ship. The two are not interchangeable, and a plan that does not distinguish them hides its own cost.

Ask where each critical requirement is checked, and what a failed result does to material already produced. Two plans can list the same twelve checks and behave completely differently, because one catches a lamination fault on the second sheet and the other catches it on the finished pallet.

The production sequence is what makes that question answerable. Each stage closes off what the next one can inspect: once a sheet is laminated, the layer underneath cannot be examined again. How plastic and RFID cards are manufactured sets out that order.

The purpose of a plan is not to collect inspection forms. It is to make sure an important failure cannot pass between production, packing and dispatch without an owner.

04. Sampling and the acceptance rule

Sampling is a decision with a named basis, not a default. ISO 2859-1 provides sampling schemes indexed by an acceptance quality limit, and naming a scheme and an AQL turns how many did you check into a number both sides agreed in advance.

Two rules behave differently and the choice has to be deliberate. An AQL scheme accepts a known, small proportion of defects in exchange for inspecting a fraction of the lot, which suits cosmetic print defects on 20,000 cards. A zero defect rule checks every unit, which is what encoded data loaded into an access system needs.

Write the sample size, the inspection level and the acceptance number on the same line as the requirement. A rule that lives in a separate document gets separated from the requirement at the worst moment. Incoming inspection at the buyer's own door is a different plan: the card delivery inspection checklist covers that side.

05. Agree escalation before production

Define how failures are recorded, contained and resolved before anything is printed. Escalation negotiated during a failure is negotiated from the worst position either side will ever hold.

Keep inspection records connected to the lot and to the specification revision. A record that says passed visual inspection, with no lot reference and no revision number, cannot settle a complaint six weeks later, because nothing shows which requirements the lot was released against.

Identify which changes require a new sample approval: material, thickness, chip, artwork and encoding layout. A correction that quietly changes any of those produces a card that is no longer the card that was approved, and the next order inherits the ambiguity. Consistency across lots is its own problem, handled in reordering and batch consistency.

06. The Kaway quality plan line

The Kaway quality plan line is a single row carrying five fields: requirement, test method, acceptance rule, sample plan and release authority, all read against one specification revision number. It is the smallest unit that can release or refuse a lot on its own.

The test for a finished plan is mechanical. Cover every field but one and ask whether the line still means anything. Remove the test method and the requirement becomes an opinion. Remove the acceptance rule and the measurement has nothing to be judged against. Remove the release authority and a failure has no owner, which is the condition in which suspect material ships.

07. Buyer checklist

Before approval

• Requirement, written as a measurable characteristic rather than a goal.
• Test method, naming the instrument, the reference card or the target reader.
• Acceptance rule, with the numbers that separate a pass from a fail.
• Sample plan, naming the scheme and the acceptance number, or stating one hundred per cent.
• Release authority, a role that can stop a shipment.
• Specification revision on the plan, matching the revision on the drawing.
• Escalation path, including what gets segregated and who agrees the disposition.
• Change list, naming which corrections require a new sample approval.

Six of the eight can be settled in one exchange of emails before a quotation is accepted. The sample plan takes longer because it has a commercial consequence, and the change list because it is where both sides discover they assumed different things.

08. Worked example

Illustrative scenario, not a Kaway case study. A batch of 12,000 member cards passes appearance inspection against a signed master card and a dimensional check at five points per sheet. The cards are rejected on arrival: a numbering offset put 400 identifiers one position out of step with the photo file, and the enrolment import fails on all of them.

Every check in the plan passed. Nothing in the plan looked at the data. The plan had three physical lines, two visual lines and no reconciliation line, so the one failure mode that could stop the cards being issued was the only one with no owner.

The correction is one line, not a new procedure: data reconciliation against the source file, one hundred per cent, signed by the party that generated the file. A plan is not improved by adding checks. It is improved by closing the group that has none.

09. Technical references

• ISO 2859-1, the sampling procedures for inspection by attributes indexed by acceptance quality limit, which is the published basis for naming a sample plan and an acceptance number rather than agreeing a quantity informally: iso.org/standard/85464.html.
• ISO/IEC 10373-1, the test methods for the general characteristics of identification cards, which is why the physical lines of a quality plan can name an established method instead of inventing one: iso.org/standard/70482.html.

10. Where Kaway fits

Kaway manufactures for the trade and does not sell to a client a distributor or integrator has introduced. PVC and recycled PVC cards are printed, laminated, personalised and encoded in one place: Kaway manufactures in its own plant in Dongguan, China, which is what lets a single quality plan cover the whole route rather than stopping at a subcontractor's door.

Kaway asks for the acceptance criteria together with the specification, so that the test method and the release authority are agreed before a quotation is issued rather than after a complaint. Personalisation, encoding and security features are listed separately because each one adds its own line to a plan.

Minimum order is 500 units. Standard production is 13 calendar days, 8 calendar days on express and 12 calendar days for wooden cards. Quote requests are answered the same working day. A free sample is available where the request is qualified, and that sample is the reference the visual and electronic lines of a plan are written against.

Discuss the specification and the acceptance evidence your card project needs with Kaway Group.

11. Frequently asked questions

What is the difference between a specification and a quality plan?

A specification says what the card has to be. A quality plan says how each of those requirements will be proven, on how many cards, against what rule, and by whom. One is the target and the other is the evidence.

Can we accept a supplier's standard inspection sheet instead?

It is a reasonable starting point and rarely a finished plan. A standard sheet covers what that plant checks routinely, normally the physical and visual groups. The data and electronic lines are specific to one order and have to be added.

Who should hold the release authority on the data line?

Whoever generated the source file, because a reconciliation can only be judged against the original. Where the buyer supplies the numbering or the photo file, the buyer owns that line, and the plan should say so rather than leave it with production.

What has to change on a quality plan when the artwork changes?

The revision number, and any line whose reference has moved. A new artwork file makes the signed master card obsolete, so the visual lines point at a reference that no longer matches what is being produced.