An automotive customer scheduled a one-day audit with two weeks of warning, and the QC lab passed with zero non-conformities. The margin came from standards and gates, not luck.
This case shows how quality management builds an audit-proof QC system: lab standards, calibration traceability, gate governance and the evidence trail that answers any auditor.
Common Mistakes and How to Avoid Them
| Mistake | Why It Happens | Practical Fix |
|---|---|---|
| 1. Calibration expiry tracked in a notebook | Instruments slip past expiry | Use a dated register with an owner |
| 2. Release without the full test set | Gates are bypassed quietly | Freeze release until tests are logged |
| 3. Standards held in one person's head | Auditors find no document | Write and approve every method |
| 4. Records stored by individual operators | Evidence vanishes with staff | Central archive with retention rules |
| 5. Instruments shared across shifts | Results become untraceable | Log instrument ID on every record |
| 6. Training not tracked | New staff test without sign-off | Keep a person-versus-method matrix |
| 7. Non-conformances closed verbally | Fixes are never verified | Close only with evidence of the fix |
| 8. No mock audits | The first real audit finds gaps | Run quarterly internal audits |
| 9. Customer spec never reviewed | The lab tests the wrong thing | Review spec versus test matrix yearly |
Best Practices
- Keep one calibration register with an owner and a weekly review
- Freeze product release until the full test set is logged
- Document every test method with a version and approval date
- Archive records centrally with written retention rules
- Log instrument ID and operator on every test record
- Run a quarterly mock audit with a scored checklist
Implementation Roadmap
| Step | Frequency |
|---|---|
| Review the calibration register | Weekly |
| Audit open non-conformances | Weekly |
| Verify gate compliance on released lots | Weekly |
| Run a mock audit with a checklist | Quarterly |
| Review spec versus test matrix | Yearly |
Audit readiness flow
- Map - Specs, methods, instruments. (Unmapped gaps get found by auditors.)
- Train - Sign-off matrix per method. (Untrained testers fail audits.)
- Gate - No test, no release. (Bypassed gates erode trust.)
- Verify - Mock audits and records. (Unverified systems drift.)
Auditors follow the record trail from one part back to its tests. | Calibration traceability is the most-checked evidence.
QC governance reference data
Reference values for a plating QC laboratory management system.
| Parameter | Reference | Why It Matters |
|---|---|---|
| Calibration register | 100 percent of instruments, dated | Expired instruments invalidate lots |
| Calibration interval | 6-12 months per instrument type | Track by usage and drift |
| Check standards | Daily or per shift | Catches drift between calibrations |
| Test matrix | Customer spec versus internal test | Review yearly or on spec change |
| Gate rule | Release blocked until tests logged | No test, no release |
| Record retention | 2-5 years per contract | Auditors verify retention works |
| Mock audit | Quarterly, scored | Finds gaps before customers do |
Gate governance board
| Gate | Test set | Release rule |
|---|---|---|
| Incoming material | Cert, hardness, surface | Block if missing |
| In-process | Bath analysis, thickness | Block if out of window |
| Final | Thickness, adhesion, salt spray | Block until logged |
| Shipment | Lot record, retention sample | Block if archive incomplete |
Audit evidence trail
| Layer | Example | Retention |
|---|---|---|
| Part record | Lot number, process times | 2 years |
| Test record | Instrument ID, operator, values | 2 years |
| Calibration | Certificate, date, result | 3 years |
| Training | Sign-off matrix, dates | 5 years |
Case 1 - a zero non-conformity automotive audit
Scenario. An automotive tier-one customer gave a plating plant two weeks' notice for a full system audit; previous audits had found calibration and record gaps.
Action. The QC manager froze all releases until test logs were complete, updated the calibration register, ran a mock audit, and closed three open non-conformances with evidence.
Result. The audit closed with zero non-conformities, and the plant earned a two-year supplier qualification.
Case 2 - a European appliance maker's surprise record check
Scenario. An appliance customer requested shipping records for a batch shipped eleven months earlier, without warning, during a routine review.
Action. The plant pulled lot, test and calibration records from the central archive within one day, including instrument IDs and operator names.
Result. The customer's risk rating improved, and the plant kept its preferred supplier status for the following year.
Frequently Asked Questions
What do auditors check first?
Calibration traceability, training records, and whether the release gate can be bypassed.
How do I prove instruments are current?
One dated register with every instrument, its calibration due date, and the certificate archive.
How often do I calibrate?
Typically every 6-12 months per instrument type; daily check standards catch drift between calibrations.
What is a gate in QC?
A release rule that blocks product until the required tests are logged; no test, no release.
How long do I keep records?
Two to five years per contract; auditors verify that retention actually works.
How do I handle a bypassed gate?
Treat it as a non-conformance, correct the lot, and change the process so a bypass is impossible.
Do I need mock audits?
Quarterly scored mock audits find gaps while there is still time to fix them.
What training evidence do auditors want?
A matrix showing which operators are signed off for which methods, with dates.
How do I review customer specs?
Compare the customer spec against your test matrix yearly, or whenever the spec changes.
What Would You Like to Solve?
Describe your customer base, current QC gates and record system, and share which audit findings worry you most.