Deep Interpretation of ISO9001 Clause (24) | 8.6 Release of Products and Services: Release Criteria and Record Requirements

1. Key Points of the Clause

The core requirements of Clause 8.6 "Release of Products and Services" in ISO9001:2015 can be summarized in four sentences:

First, the organization should implement planned arrangements at appropriate stages to verify that the requirements for products and services have been met. This means that release is not limited to the final stage before shipment; any node where requirements need to be verified can and should be set as a release point.

Second, the organization should ensure that all planned verification activities are completed before delivery to the customer. Note the word "before" — it is not permissible to use methods such as "release and verify simultaneously" or "release first, verify later."

Third, the organization should retain documented information to provide evidence that the release criteria have been met, i.e., evidence of release.

Fourth, the documented information should include the traceability of the release personnel. This is one of the most significant changes in the 2015 version compared to the old version: responsibility must be assigned to specific individuals.

2. Interpretation of Intent

Release is the final physical gate for compliance. Clause 8.5.1 requires "production under controlled conditions," while Clause 8.6 ensures an independent confirmation of compliance before the product leaves the organization. The standard lists release as a separate clause because the cost leverage of this stage is extremely high — a single release oversight can lead to multiple times the cost in returns, recalls, claims, and reputational damage.

Why emphasize "planned arrangements"? Because release criteria must be "defined first, then executed." If criteria can be agreed upon after the fact, "conformity" ceases to be an objective criterion and becomes a matter of interpretation. The standard requires that criteria come from prior planning: regulatory requirements, customer requirements, and the organization's own technical specifications. Release without documented criteria is essentially based on experience.

Why emphasize "traceability of release personnel"? The foundation of system effectiveness is the responsibility mechanism. Writing "released by the Quality Inspection Department" versus writing "released by Zhang San (employee ID XXX) at a specific time" has entirely different effects in terms of accountability and behavior constraints. Traceability transforms collective responsibility into individual judgment, which is the true form of effective record-keeping.

Relationship with Clause 8.7: Two sides of the same gate. Clause 8.6 manages "how conforming products are released," while Clause 8.7 manages "what to do with nonconforming products." These two clauses cannot be mixed: using Clause 8.7's concession acceptance to bypass Clause 8.6's criteria without written authorization and scope limitation is equivalent to nullifying the release criteria.

3. Implementation Practices

Step 1: Compile the "Release Criteria List." For each category of product or service, create a table that includes key characteristics, acceptance standards, sampling plans, and judgment rules, clearly defining "who tests, what is tested, how it is judged, and the source of the criteria (regulation/customer/internal control)." This table is the sole basis for release and is the first document that auditors will request.

Step 2: Set release stages and checkpoints. Typical checkpoints include incoming material release, first article inspection, process patrol inspection, final inspection, and pre-delivery confirmation. Each checkpoint must have a hard rule that "if not passed, it cannot proceed to the next stage," and the specific points should be clearly defined in the process documents (e.g., the warehouse must not release batches that have not been approved).

Step 3: Design release record templates. The templates should at least include: batch number or serial number, release stage, inspection items, actual measurement values, judgment criteria, release date, and the signature of the release personnel (handwritten or identifiable employee ID). Records should correspond one-to-one with batch numbers, allowing for reverse tracing of all release stages from the finished product batch number.

Step 4: Establish files for exception paths. Situations such as concession acceptance and emergency release, which deviate from standard release procedures, must be approved in writing by authorized personnel. The records should specify the "concession" identifier, the applicable scope, and the validity period (e.g., limited to a specific order, quantity, or time frame), and necessary notifications should be provided to the customer at the time of delivery.

Step 5: Regular sampling review. It is recommended to sample release records monthly or quarterly to check for completeness, timeliness, and authenticity, particularly focusing on "complete records, all values conforming, and highly concentrated time entries." These are often signs of abnormal practices.

4. Auditor's Perspective

Common Finding 1: Release criteria are not documented or are too vague. When auditors ask, "What criteria were used to release this batch of products?" the on-site response is often "according to the drawings," "according to the standards," or "we've always done it this way," but no documented criteria list is provided. This indicates a lack of planning arrangements under Clause 8.6.

Common Finding 2: Release records lack traceable signatures of release personnel. This is evident when only the quality inspection department stamp, printed department name, or blank spaces are found in the records. Sometimes, the signature is a job title like "inspector" rather than a specific individual. This is one of the most frequently cited nonconformities in the 2015 version, and rectification cannot be achieved simply by adding signatures; the system needs to be revised.

Common Finding 3: Verification after delivery. This is indicated by shipping dates that precede the completion of inspection dates, or inspection records for the month being concentrated and written in the same handwriting at the end of the month. This directly violates the requirement to "complete verification activities before delivery to the customer" and is typically judged as a nonconformity.

Common Finding 4: Release data contradicts customer feedback. A manufacturing company may release thousands of batches in a year with no nonconformities and no concession acceptances, yet the return rate and customer complaints for the same period are not low. The "perfect" data itself is a risk signal, indicating that release records do not reflect actual verification activities. Auditors will follow this lead to check the sampling plans and actual measurement records.

Misconception 1: Viewing release as solely the responsibility of the Quality Inspection Department. Release responsibility is determined by planned arrangements, and the actual chain covers production, technology, storage, and delivery. The execution of checkpoint rules often does not fall to the Quality Inspection Department.

Misconception 2: Believing that concession acceptance can be approved verbally. Exceptional releases without written authorization and scope limitation effectively nullify the release criteria. In the event of a batch issue, it is impossible to trace who approved the release and the extent of the approval.

5. Self-Inspection Checklist

• Each category of product or service has documented release criteria, which specify the sampling plan and judgment rules.
• Release stages and checkpoints have been set, and there are hard rules in place that "if not passed, it cannot proceed" that are being enforced on-site.
• Release records can be matched one-to-one with product batch numbers and include traceable signatures of the release personnel.
• Concession acceptance and emergency release have clear approval authorities, written records, and specified applicable scopes.
• Sampling reviews of the last three months' release records have not found instances of verification after delivery or concentrated record-keeping.

Criteria first, responsibility to individuals, and traceable records.

Knowledge code: 2.1.1

Version: v20260922

Author: QTank QTank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.