IMScollect
ISO 9001

ISO 9001, clause 8.6: Release

Title in the standard: “Release of products and services”

Who decides in your organisation that something may go out, and what is that decision based on? Clause 8.6 of ISO 9001 as seen from the audit.

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Updated 15 November 2026

What it is about

Clause 8.6 is the last threshold before the customer. Before a product is delivered or a service is completed, it should be established that the planned checks have taken place and the acceptance criteria are met. Release can come at the end or be spread across stages, for example after the first article, after an operation and before dispatch.

If a check is missing or a criterion is not met, release is only allowed if an authority entitled to do so approves it and, where applicable, the customer as well. That is the route of the concession. It is permitted, but it is not a side issue.

Two things must be recorded: evidence that the acceptance criteria are met, and who released. The second point is often overlooked. A stamp without an identifiable person, or a status in the system that nobody is accountable for, does not answer the question of who released.

For services, release looks different but is required just the same: the acceptance of a project, a second review of an expert report before it is sent, the check after maintenance. The question is always the same: who confirmed that the result meets the requirements?

What the auditor checks

  • “Who released this delivery?”

    Whether the person who released can be seen from the record and not only from memory. The question is asked about a specific delivery from dispatch or from the archive.

  • “Against which criteria was it released?”

    Whether acceptance criteria are defined, for example in an inspection plan, drawing or contract, and whether the record shows that they were met.

  • “Has anything ever been delivered before all checks were complete?”

    The route of early release or concession: whether an authorised person decided, whether the customer was asked where this is agreed, and whether it is recorded.

  • “Who is allowed to release in your organisation?”

    Whether the authority is defined and matches the people who actually release. A release by someone without that authority is not a release in the sense of the standard.

  • “How do you release a service?”

    For service providers, whether there is an identifiable conclusion, an acceptance, a second review or a check, and who confirms it.

Which evidence convinces

  • Inspection plans or defined acceptance criteria

    They set out what must be met before release. Without them, there is nothing to check a release against.

  • Release records with batch, date, result and person

    They are the core of 8.6. What is required is evidence of conformity and traceability to the person who authorised the release.

  • Rules on release authority

    Who may release which products or stages, for example in a job description, a signature policy or under the [roles](/en/standard-chapters/5-3-roles).

  • Recorded concessions

    With the reason, the decision of the authorised person and, where necessary, the customer’s consent. They show that exceptions are decided consciously.

  • Inspection certificates for the customer

    Where agreed, mill certificates or inspection reports show the customer that release took place, and show the auditor whether the data behind them are right.

Typical nonconformities

  1. The person who released cannot be identified

    The delivery is marked as “inspected”, but nobody can say who decided that. If the information is missing in individual cases, it is a minor nonconformity.

  2. Delivered before checks were complete

    Under time pressure the goods go out, and the final inspection is done afterwards or dropped, without a concession. If this happens regularly and without any rules, the requirement is not met: a major nonconformity.

  3. No defined acceptance criteria

    Release is based on experience. What “OK” means is written down nowhere.

  4. Concession without authority

    A shift supervisor releases a part outside tolerance, although the quality manager or the customer would be responsible for that.

  5. Services without release

    Projects, expert reports or maintenance jobs are completed without anyone checking the result against the requirements.

Differences by standard

ISO 9001ISO 9001

Only ISO 9001 has a requirement of its own for the release of products and services. In ISO 14001 the closest equivalent is control against defined criteria in 8.1; in ISO/IEC 27001, controls in Annex A deal with the acceptance of changes to systems and software, for example testing before going live. The 2026 edition of ISO 9001 keeps 8.6 with its number and title. What happens to a product that fails release is governed by 8.7.

How IMScollect covers it

In IMScollect you record every release in the release area: batch or order, date, the person releasing and the result, all four as mandatory fields. The result is released, blocked or concession; for a concession you also state who granted it. The result is never preselected; it is chosen deliberately every time.

You describe the evidence of conformity in the entry and attach supporting documents such as inspection records as a document or file. The list filters by concessions and blocked releases, and every entry shows its history.

Try it yourself, no call needed.Prefer a walkthrough? Book a guided demo →

Frequently asked questions

Does every single delivery have to be released?▾

Every product and every service is released before it goes to the customer. The record can, however, be kept per batch, lot or order and can also sit in the ERP system, as long as the person who released can be identified.

What is the difference between release and concession?▾

A release confirms that all requirements are met. A concession allows delivery although a check is missing or a criterion is not met. It needs an authorised person and, where agreed, the customer’s consent.

May the system release automatically?▾

Yes, if the criteria are defined and the system checks them reliably, for example with automatic measurement. It should then be defined who is accountable for the rule, so that the release can still be traced to a person.

What does release look like for services?▾

As acceptance by the customer, as a second review before dispatch or as a check at the end of an assignment. What is recorded is that the service meets the requirements and who confirmed it.

Further reading and viewing

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Philipp builds IMScollect. TÜV-certified auditor with a background in governance, risk and compliance, more than 200 audits conducted and supported.

This page explains in our own words and does not replace the text of the standard. You can obtain the standards from ISO(opens in a new window) or from your national standards body. Clause numbers and titles follow ISO 9001:2026, ISO 14001:2026 and ISO/IEC 27001:2022.