Quality Record Management Guide — How to Determine and Manage Record Retention Periods
Quality records are the "evidence" of a quality management system (QMS) — auditors need to review them, customer complaints require checking them, and product recalls necessitate tracing them. However, many companies face a practical dilemma: How long should records be retained? Which ones should be kept long-term, and which can be destroyed?
1. General Rules for Record Retention Periods
Different types of records have different legal and system requirements. Below are the recommended retention periods for common records:
| Record Type | Suggested Retention Period | Basis |
|---|---|---|
| Product inspection records | Product lifecycle + 1 year | Traceability requirements |
| Internal audit records | 3～5 years | IATF 16949 / ISO 9001 |
| Management review records | 3～5 years | ISO 9001 requirement |
| Calibration/verification certificates | Validity period + 1 cycle | Metrology regulations |
| Training records | Employee tenure + 2 years | System audit needs |
| Supplier approval records | Cooperation period + 3 years | Supply chain management |
| Customer complaint records | 3～5 years | Regulations + system |
| Nonconforming/corrective action records | 5 years | Quality traceability |
The above are general recommendations, and specific requirements should be combined with industry regulations — for example, medical devices require that product records be retained for at least 2 years after the expiration of the product registration certificate, and the automotive industry typically requires retention periods of over 15 years.
2. Four Key Steps in Record Management
1. Establish a Record List
Each company should have a "Comprehensive Quality Record List" that includes:
- Record name/number
- Responsible department
- Storage location (electronic/paper)
- Retention period
- Destruction approval process
2. Determine Storage Media
For paper records, consider moisture-proofing, fireproofing, and pest control. For electronic records, consider backup frequency, storage capacity, and format readability (for example, can a 10-year-old Excel file still be opened today?).
Recommendation: For key records (product inspection, calibration certificates, certification documents), use both paper and electronic backups. For general records, electronic storage is sufficient.
3. Execute Regular Archiving
Archive records annually or quarterly. For electronic records, create a folder structure based on "year-record category." For paper records, use uniform labels and archive box numbers.
4. Destruction Requires Approval
The expiration of a record does not mean it should be automatically destroyed — a "Record Destruction Approval Form" should be established. This form must be signed by the department head and the quality manager before destruction can proceed. Recommended destruction methods: use a paper shredder for paper records, and thoroughly erase (not just delete) electronic records.
3. Common Questions
Q: Can records be written in pencil? No. The basic requirement for quality records is "clear, complete, and not easily erasable." Pencil marks can be erased, which does not meet the requirements. Use ballpoint pens, fountain pens, or rollerball pens for filling out records.
Q: How should errors be corrected? Strike through the error (draw a line through the incorrect content while keeping it legible), write the correct content next to it, and sign and date it. Do not use correction fluid, scraping, or covering.
Q: Are electronic signatures valid? Reliable electronic signatures recognized by the "Electronic Signature Law" have the same legal effect as handwritten signatures. However, companies need to first establish electronic signature management guidelines internally.
Summary
The core of quality record management can be summarized in three sentences: Record what needs to be recorded, store what needs to be stored, and destroy what needs to be destroyed with approval. Properly managing records ensures that audits can be conducted without fear and that traceability is supported.
Knowledge code: 2.3.2
Version: v20260604
Author: Quality Think Tank